Operations

Event badge design best practices: function over branding

What to put on a conference badge, what to leave off, and why the readability of your name from 6 feet away matters more than your logo placement.

7 min read min read · Published March 23, 2026

Walk into any B2B conference and watch how people actually use badges. An attendee approaches a stranger at the coffee station. Their eyes dart to the badge. They squint. They tilt their head because the badge has flipped backward on the lanyard. They give up and introduce themselves with "I'm sorry, I didn't quite catch your name" — which they never heard, because they never had it.

This is a solvable problem. The conference badge is a tool, not a brand asset. Its job is to help two strangers introduce themselves with minimum awkwardness. Most badges fail at this — too much logo, too small a name, too much wasted space. This guide covers the badge design choices that consistently work, with specific measurements and format recommendations you can hand to a print vendor.

1. What goes on a great badge

In order of priority:

  1. First name. Big — readable from 2 meters. This is the single most important element on the badge. Everything else is supporting information.
  2. Last name. Smaller, beneath first name.
  3. Company. Mid-size, beneath name. Critical for B2B contexts.
  4. Role/title. Optional. Helpful for sales-driven events; noise at community events.
  5. City or region. Optional. Useful for international events where geography is relevant.
  6. QR code. For lead capture and badge scanning. On the back, not the front.
  7. Track or session indicator. Optional. Color stripe or icon for events with multiple tracks.
  8. Event branding. Small footer. Not the dominant element.

What gets cut:

  • Pronouns become optional (encouraged at registration, small print if used).
  • Social handles only if specifically requested at registration.
  • Sponsor logos almost never (they belong on lanyards instead).
  • Event tagline, year, date — nobody needs this on the badge during the event.

2. The font-size test

Your first name should be readable from 2 meters in normal indoor lighting. Print a test, walk 2 meters away, confirm. Most badges fail this — designers default to 14pt nameplates that disappear at conversational distance.

A working size guide (for a 4x6 inch badge):

  • First name: 36-48pt bold. Huge. Bigger than feels comfortable. Test it.
  • Last name: 18-24pt. Smaller, same font family.
  • Company: 14-18pt. Should be readable from 1 meter.
  • Role/title: 10-14pt. Readable up close, not from a distance.
  • Event branding footer: 8-10pt. Decorative only.

If your registration data has long first names ("Alessandro" or "Constanze"), size the field for that — not the ideal case of "Mike." Auto-sizing code that scales the first name down for long entries preserves readability.

High-contrast text on light backgrounds. Dark text on dark background (e.g., event colors) fails readability every time. The badge exists to be read, not to match the color palette.

3. Lanyard and badge format

  • Double-sided printing. Badges flip backward constantly on lanyards. A blank back is a failure; a duplicate front is the solution.
  • Vertical orientation. More readable from the side. Landscape badges disappear when viewed at an angle.
  • A6 or 4x6 inch sizing. Readable, fits in pockets, survives lanyard weight without bending.
  • Lanyards in a single neutral color. Black, navy, or event-primary. Not a branded mess of logos on the strap.
  • Optional sponsor color stripe on lanyard for sponsor differentiation (attendees vs speakers vs staff vs sponsors).
  • Detachable card holder for badge reuse or storage.
  • Lanyard length: 36 inches. Standard. Longer rides too low; shorter feels constrictive.
  • Printed on rigid card, not flexible paper. Flexible badges curl and become unreadable by day 2.

4. QR codes — what they should encode

A clean attendee QR code encodes:

  • Attendee ID (your system's internal UUID).
  • Their email address (for lead retrieval follow-up).
  • Optional vCard with name, company, title.

What it should NOT encode:

  • Full personal data unencrypted.
  • A URL to a profile page that requires login.
  • Tracking identifiers that link to marketing systems without consent.

The QR code is for lead retrieval and badge scanning. See lead retrieval best practices for how this integrates with sponsor scanning workflows.

Place QR codes on the back of the badge, not the front. Front QR codes look cluttered and imply the badge is a brochure. Back QR codes do their job without visual noise.

5. Role differentiation (subtle, not aggressive)

Multi-role events need to signal who's who:

  • Attendee: standard badge, standard lanyard.
  • Speaker: thin color stripe on top of badge, matching lanyard stripe.
  • Staff: distinct lanyard color + "STAFF" banner on badge.
  • Sponsor/Exhibitor: company logo on badge (bottom third), distinct lanyard.
  • VIP: subtle gold or silver stripe — attendees notice but it doesn't create a bad social dynamic.
  • Press: clearly marked "PRESS" badge for access reasons.

Aggressive differentiation (e.g., VIP attendees in totally different colored badges) creates resentment at networking events where the point is equality of access. Keep the differentiation subtle enough that it signals identity but doesn't create a caste system.

6. Common mistakes

  1. Logos overwhelming names. Ratio should be 90% useful info, 10% branding. Your brand is the attendee experience, not the badge.
  2. Tiny names. Defeats the purpose of a badge. If people can't read it from conversational distance, it isn't a badge.
  3. Badges that flip backward. Double-sided printing solves this completely.
  4. Lanyards too short or too long. Standard 36-inch lanyards work for 95% of adults. Longer rides uncomfortable; shorter constricts.
  5. Color-coded role badges with no legend visible at the venue. Color codes are useless if attendees can't decode them. A single legend sign at the entrance solves this.
  6. Printing roles that change mid-event. "Speaker on day 1, attendee on day 2" creates confusion. Keep the role static for the entire event.
  7. Not printing job titles. For sales-driven events, job title is second only to company in information value.
  8. Using the badge as a swag coupon. Attendees don't appreciate a badge that doubles as a punch card. Separate coupons.

Badge design checklist

Before signing off on the print file:

  • [ ] First name readable from 2m in test print
  • [ ] Double-sided printing confirmed
  • [ ] Vertical orientation
  • [ ] A6 or 4x6 sizing
  • [ ] High-contrast text on solid background
  • [ ] QR code on back with ID + email only
  • [ ] Role differentiation via stripe or lanyard color
  • [ ] Company and title present (B2B events)
  • [ ] Pronouns optional, small if used
  • [ ] Event logo in footer, not dominant
  • [ ] Print vendor confirms trim and bleed allowance
  • [ ] 10% overprint to cover no-shows and reprints

Modern event management software handles the data layout automatically; the design decisions are still yours.

FAQ

Should we have different badge designs for VIPs? Subtle differentiation (a color stripe or symbol) yes. Aggressive differentiation creates a bad social dynamic.

What about digital badges in apps? Useful as a backup but not a replacement. Physical badges work for the social cue at distance that a phone screen can't provide.

Should I print pronouns? Optional. Encourage attendees to add at registration; print if they do. Don't make pronouns mandatory — some attendees prefer to opt out.

How many badges should I print? Registered attendees + 10% overprint for no-shows, misprints, and on-site additions.

Should sponsors get their logo on attendee badges? No. Sponsor logos belong on lanyards and on signage, not on attendees' badges. Attendees are not a sponsor placement.

Related guides


Ready to run your next event? Create your event on WebMobi →

Related guides

Run your next event on WebMobi

Build the registration page, app, and analytics in under an hour. No credit card required.

Create your event →