QR Codes for Conference Badges

You send badge art two or three weeks out. The keynote is still a hold. Breakouts will move. I want the square on the lanyard to open the page you are using at 8am, not the Eventbrite URL you had in March and not a vCard you exported from last year's CRM.

Staff can scan a badge. Attendees can scan a booth. Either way the phone should land on one job: this person, this hour. If you also need the agenda, print a second code on the program. A hub page in a doorway is a bounce.

A vCard is static. A URL you own is not.

People still bake a vCard into a conference badge. Name, title, email, phone, company. The pixels hold that payload. There is nothing to edit. If the attendee changes jobs, the title is wrong, or you want the same square to open the app on day one and the survey on day three, you reprint. A URL you control is safer for agendas and support.

A static code that encodes a raw session URL has the same problem. Rooms move. The Zoom dies. The feedback form is not ready until the talk ends. Print that URL into 400 door cards and the first swap makes every card a lie. A dynamic code writes a short link. You change the destination. Same image. New room. New form.

On this site you create a QR code as Link. Do not pick vCard for a badge you will reprint if the contact data shifts. Do not pick Event for a door sign. Event writes a calendar invite into the image. That payload is static. If the start time slips, every printed square is still the old time. Put the calendar button on the page behind the link if people need it.

Badges print weeks early. The agenda does not.

The badge vendor wants a PDF. You want a live grid. Those dates never match. I would rather edit a URL at 10pm than reprint 1,200 badges at 6am. Canceled speaker, flooded breakout, swapped keynote — same square. If you encoded a raw path or a vCard, you reprint. That is why you create a QR code before you send art to the vendor.

• Badge: staff scan at the line, or the attendee scans a booth. Opens the profile, the app, or today's help-desk note.
• Program or chair card: today's grid, then the replay. That is a different job from the lanyard.
• Booth: the sponsor's form or a tagged page. One code per booth if you want a Monday report.
• Session door: this hour's talk page or feedback form. Next hour you retarget or swap the insert.

Smaller gatherings do the same job on a door poster. A salon does it on a mirror decal when the booking link moves. A listing sign does it when the MLS page dies. The print job changes. The rule does not: one scan, one answer, a destination you can edit. See events, salons, and real-estate if that is the surface you are printing.

Booth codes you can report

Sponsors ask which booth was busy. A shared conference URL cannot answer that. Create one code per booth. Point each at that sponsor's form or a tagged page. Scan totals by code are the Monday email. Keep the placements that worked. Drop the ones that sat.

Do not hand every exhibitor the same square. You will spend Wednesday arguing about aisle traffic you cannot prove. I give each booth its own short link even if the landing page is the same template with a different UTM. The report is the reason they bought the space.

Session feedback without a new door card

You tape a URL on a door when the program breaks. Attendees type it wrong. Staff rewrite it in marker. That is the failure a dynamic destination is for. Keep the card. Change the link. The holder on the frame does not need a new insert between the 10am and the 11am.

One code per room is enough if you retarget it on the hour. One code per session is cleaner if you want a score per talk. I would not put the feedback form and the slides on the same square. People in a doorway will not pick.

Size the square for the lanyard

Your monitor lies. A 1 cm code that locked on your desk fails on a swinging badge with a logo eating the quiet zone. Use distance, not layout taste. Printed width should be about one tenth of the scan distance. Add margin for laminate glare and a phone held one-handed in a crowd.

Black modules on a light panel. Leave a quiet zone. Matte beats gloss under hall lights. Add Scan for agenda or Scan to connect in plain type. Test from the real spot with an older Android and a current iPhone before you lock the badge PDF.

Download, confirm email, pay $1

Here is how I create a QR code for a badge that still might change.

1. Paste the first URL. Check-in, profile, or the app page you want today. Pick Link, not vCard and not Event.
2. Hit Download. We ask for email so the code attaches to your account.
3. Confirm the email we send. Check spam if it is slow.
4. Pay $1 to unlock the 1024px PNG. Place it at the size the lanyard needs. Keep it square.

When the room or the survey changes, open the dashboard and edit the URL. Do not generate a new image unless the badge design changed. Printed /r/ links keep scanning if the dashboard later locks. You cannot edit them until you start a plan.

Mistakes that force a reprint

• Encoding a vCard on a badge you will want to retarget.
• Using the Event type in the generator on a door that might change.
• Baking a raw Eventbrite or app URL into a static square.
• One tiny square trying to do check-in, the agenda, and the survey.
• Shrinking the code into the conference logo so the quiet zone dies.
• Skipping the hall scan until attendees arrive.

If a printed code already failed, you can only repair it without reprinting when it is dynamic and you still own the short link. A static vCard or a baked URL means you reprint. For the next run, create a QR code first, then send the badge file.