A QR code is just a URL you can point a camera at. What makes it useful for events is what's on the other end: a registration page, a personal ticket, an agenda. The first decision isn't which generator to use — it's which of the two kinds of code you need.
The two kinds of event QR codes
Shared codes encode one link for everyone — the registration page on a poster, the agenda on a table card, the Wi-Fi details on a slide. Anyone can generate one in minutes, and one code serves the whole audience.
Unique codes are per-attendee — each registrant’s confirmation email carries a code that identifies them, and scanning it at the door checks that specific person in. These can’t come from a free generator, because each of your 500 attendees needs a different one tied to your registration data.
Most events need both. Here’s how to create each.
Creating a shared QR code (5 minutes)
- Finalize the URL first. The code is permanent once printed; the URL inside it should be too. Link the canonical page, not a shortened link that might expire.
- Generate it. Any reputable free generator works, as does the built-in generator in Chrome (share icon → “Create QR code”). Choose PNG or SVG at high resolution — you’ll want SVG if it’s going on a banner.
- Size it for the scan distance. Rule of thumb: the code should be at least one-tenth of the distance it will be scanned from. A poster scanned from 3 meters needs a 30 cm code; a table card scanned from 30 cm needs 3 cm.
- Test it before printing — on both iOS and Android, in bad lighting, at an angle. Then test the printed proof again: dark ink on light background, no decorative distortion over the corner squares (those are the position markers; the design trend of hiding logos over them is how codes stop scanning).
- Put a caption under it. “Scan to register” outperforms a naked square. People scan codes when they know what they get.
Creating unique per-attendee QR codes
This is a registration-platform feature, not a generator task. The flow:
- Attendee registers through your event registration software.
- The platform generates a unique code tied to their record and embeds it in the confirmation email (and calendar attachment — people search their inbox at the door, so put the code everywhere they’ll look).
- At the event, staff scan with a phone, tablet, or badge-printing kiosk. The scan pulls up the attendee, marks them present, and — if you’re printing on demand — produces their badge in the same interaction.
Because each code maps to one registration record, unique codes also handle the cases shared codes can’t: paid tickets that must not be reusable, session-level access control, VIP routing, and accurate per-person attendance tracking. A scanned unique code is simultaneously the ticket, the check-in record, and the data point.
If your current stack can’t generate per-attendee codes, that’s usually the moment to look at a proper event check-in app rather than to improvise with mail-merged generator links — the improvised version works until the first duplicate scan, refund, or name change, and then it very much doesn’t.
The mistakes that break QR codes on event day
- Shortened URLs that expire — the code outlives the link and scans to a 404 on a printed banner.
- White-on-dark codes — many phone cameras won’t read inverted codes reliably. Dark code, light background.
- Codes in email images that don’t load — attach the ticket as a PDF or use the platform’s hosted ticket page as backup.
- No offline plan — venue Wi-Fi dies; your check-in tooling should scan and sync later, not freeze.
- One kiosk for 400 people — codes make each scan fast, but throughput still needs enough scan points. Count arrival-window minutes, divide by scans-per-minute, and staff accordingly.
Shared codes get people to the event. Unique codes get them through the door with a record behind them. Create both, test both printed, and the square black-and-white box becomes the cheapest infrastructure your event runs on.
Event QR code FAQ
Do QR codes expire? The code itself never expires — it’s just encoded text. What expires is what’s behind it: shortened links, retired pages, or (for per-attendee codes) tickets that were refunded or already scanned. Put permanent URLs in printed codes and let the platform handle validity for tickets.
What size should an event QR code be? At least one-tenth of the scanning distance: 3 cm for a table card scanned from 30 cm, 30 cm for a poster scanned from 3 meters. When in doubt, bigger — no one has ever failed to scan a code for being too large.
Do QR codes work if the venue Wi-Fi goes down? The attendee’s code displays fine offline (it’s in their email or wallet). The scanning side is what needs a plan: choose check-in tooling that scans offline and syncs when the connection returns.
Are free QR code generators safe to use? For shared codes pointing at your own URL, yes — reputable generators just encode the link. Avoid generators that force a redirect through their own domain; that’s the “expiring shortlink” problem wearing a different hat.
Eventtia is the platform behind the brands setting the standard.
Talk to us about how the platform fits into your stack — registration, communications, on-site, and analytics, exposed deeply enough to compose.
