Use case · Events

QR codes for events

Events are where QR codes earn their reputation — and where they fail most publicly. The difference is almost always whether somebody planned for the venue's terrible signal.

Free
No sign-up
No expiry
Commercial use

Short answer

Events use QR codes for ticket validation, attendee check-in, session schedules, venue maps and contact exchange. The critical planning point is connectivity: a venue with hundreds of people on one cell tower cannot support codes that need to load a page, so validation should work offline.

Six jobs, ranked by how reliably they land

Job	Code type	Needs signal	Reliability
Ticket validation at the door	Unique code per attendee	Scanner only	High
Add to calendar	Event VEVENT	No	High
Venue and room location	Map pin	For directions	High
Session schedule	Link	Yes	Medium
Contact exchange between attendees	vCard	No	High
Feedback form	Link	Yes	Low — nobody fills it in on site

The pattern is clear: the codes that work at events are the ones that do not need the network. Offline payloads — calendar entries, vCards, plain text — always land.

Plan for the venue having no signal

A thousand people in a hall served by one cell site is a network outage with extra steps. Anything that has to load will not.

Validate offline. The door scanner should hold the attendee list locally and sync later. An internet-dependent scanner creates a queue the moment the signal drops.
Print the essentials. Schedule and room numbers on paper as well as behind a code.
Use offline payloads where you can. A calendar code and a vCard need no connection at all.
Test on the day, in the room, at capacity. Signal at 8am in an empty hall tells you nothing about 10am with 900 phones in it.
Have venue Wi-Fi ready and put its Wi-Fi code on the badge.

One code per person, not one per event

An event code is not a ticket. A ticket needs a unique identifier per attendee so it can be checked off a list and refused on a second attempt. Print the same code on every ticket and the first person through the door validates it for everyone.

Generate a unique identifier per attendee — a random token, not a sequential number, or people will guess neighbouring tickets.
Encode a short string containing that token. Keep it short so the badge code stays coarse and scans instantly at the door.
Use the bulk generator or your own pipeline to produce them.
Set error correction to Q — badges get creased, wet and worn against lanyards.
Print at 30 mm minimum on a badge, and never behind a plastic sleeve with a gloss finish.

Frequently asked

Can I use a QR code as an event ticket?

Only with a unique code per attendee, validated against a list. A single shared code cannot be checked off and offers no protection against reuse.

What if the venue has no mobile signal?

Use payloads that work offline — calendar entries, vCards, plain text — and make door validation work from a locally stored list.

What size should a badge QR code be?

30 mm minimum. Badges move while being scanned, so extra size buys you speed at the door.

How do attendees add the event to their calendar?

Encode an iCalendar VEVENT with the title, times and location. Scanning offers to add it directly, with no network needed.

Keep going

Last reviewed 24 August 2026 · Checked by the QR Code Builder team