Event Ticket QR Code
A ticket lives in a pocket, gets folded and comes out creased — build the code to survive that before the doors even open.
02 / Content
What should the code say?
03 / Style
04 / Preview
Exactly what downloads
See it on
Previews only — the card, tent, poster and sticker are not in the download. You get the code.
What a scanner is checking
Point a venue’s scanner at the code and it isn’t reading a seat number off the pattern itself — it’s reading a reference ID and looking that ID up against a guest list or ticketing database in real time. That lookup is what lets staff mark a ticket “used” the instant it’s scanned, which is also how duplicate or screenshotted tickets get caught at the door.
Build in the damage before it happens
Choose high error correction for anything that will spend time in a pocket. A ticket gets folded to fit a wallet, creased against car keys, sometimes printed on a home inkjet that isn’t perfectly calibrated. High error correction lets the code rebuild itself from a smaller, cleaner portion of the pattern, so a scan still succeeds even when part of the code is smudged or torn.
The mistake that undoes all of it
Reusing one QR code across every ticket defeats the point of scanning at all. If everyone’s ticket carries the same code, one screenshot forwarded to a group chat gets an unlimited number of people through the door on a single purchase. Generate a distinct payload — a unique ID or reference — for every ticket sold, even if that means generating them programmatically rather than one at a time.
Reading it in a dark venue
Door staff scan tickets in queues, at night, often under coloured entrance lighting rather than daylight. A high-contrast black-on-white code scans far more reliably under those conditions than a subtle colour scheme that looks sharp on a screen but loses contrast under sodium lighting. Keep the module colour dark and the background plain white, and print at no smaller than about 2.5cm — comfortable for a handheld scanner held 20-25cm from the ticket, not a full arm’s length away.
FAQ
Frequently asked questions
- Should the encoded ticket ID include any personal details, like a name?
- Better not to. Keep the code itself to a neutral reference ID and store personal details in your ticketing system against that ID instead. That way a lost or resold ticket doesn't leak someone's name or email, and a ticket can be revoked or reassigned without reprinting anything.
- Why does error correction matter more for a ticket than for a poster?
- A poster stays flat on a wall; a ticket lives in a pocket or a bag and picks up folds, creases and the odd coffee ring by the time someone reaches the door. High error correction lets a scanner reconstruct the code even with a meaningful chunk damaged or obscured, exactly the kind of damage tickets accumulate.
- Can the same QR code work for every ticket to an event?
- It shouldn't, if you want to stop one ticket being screenshotted and used by several people. Each ticket needs its own unique code tied to a unique record, so a scanner can flag a code as already used the second time it's presented.
Other QR code types
QR code guides
Printing, sizing, or troubleshooting a code? Read our QR code guides and troubleshooting articles.