2026-11-04

Event QR Code: Check-in, Tickets and Per-Attendee Codes

Event QR codes do two different jobs. A single event code is a link: the schedule, the map, the feedback form. A per-attendee code is a credential: it identifies one ticket and must not be shared. Mixing the two is how queues stall and tickets leak.

One code per attendee or one code for the event?

Use a single code for information everyone needs. Use a unique code per attendee for admission, because a shared code cannot tell you who arrived and cannot be revoked. A unique code usually points at a check-in URL with an opaque token; the scanner app validates the token against your list, so the QR payload never contains personal data.

Screen brightness and check-in speed

• Ask attendees to raise screen brightness; a dimmed phone is the most common no-scan at a door.
• Scan from a fixed distance and keep the code at 40 mm or more on a phone screen.
• Print a backup list of names; a cracked phone should not block the queue.
• Use one scanner per 150–200 arrivals and test the whole flow with ten real tickets first.

Batch generation for a guest list

A guest list is a batch job: one token per row, one image per row, named so the badge printer can match it to a person. Paste the list into the batch panel, check the failed rows, and export a ZIP of SVGs or PNGs. Keep the token column separate from the name column so a renamed guest does not invalidate a code.

Print the badge, sticker or table card

On a badge, place the code on the upper half and the name in large type below it; a lanyard twists, and the code must survive being held at an angle. Stickers need a matte surface and a quiet zone that the die cut does not trim. Table cards work at 30–40 mm, and a printed code on the back of a name badge is a useful fallback when a phone dies. The studio’s name-badge (90 × 54 mm, eight per A4 sheet) and sticker-sheet (63.5 × 38.1 mm, 21-up) templates already reserve that space.

Frequently asked questions