QR code check-in has become a normal part of concerts, conferences, school fundraisers and community events. Done well, it means guests walk up, a volunteer scans a phone screen, and the line keeps moving. Done badly, it means a crowd at the door while someone squints at a laptop.
This guide focuses on the door: how QR tickets and check-in actually work, which kind of code you need, and how to set up scanning. If you're looking for promotional QR codes for posters, schedules or venue WiFi, see our guide to making a QR code for an event.
Two very different kinds of event QR code
The most important thing to understand is that "QR code check-in" can mean two separate setups.
1. One shared code that guests scan
You print a single QR code at the entrance. Guests scan it with their own phone, and it opens a sign-in form, a waiver or a "check in here" page. Everyone scans the same code.
Good for: free events, meetups, workshops, volunteer sign-ins, classes, and any event where you mainly want an attendance list.
Limitation: a shared code can't prove that someone has a ticket. Anyone who sees the code can scan it.
You can make this kind of code yourself in a few seconds with a free generator: point it to your form (for example, a Google Form or Microsoft Forms link).
2. A unique code on every ticket that staff scan
Each guest gets a different QR code, usually by email or in a ticketing app. At the door, staff scan the guest's code with a check-in app, which looks the code up in the ticket list and marks it as used.
Good for: paid events, events with limited capacity, and anything where you need to stop people getting in twice.
Key point: the security doesn't come from the QR code itself. A QR code is just a way of writing text or a link in a scannable pattern. The protection comes from the ticketing system that checks each code against its list and rejects one that has already been scanned.
Make a free QR code for a link, WiFi or contact card — generated in your browser.
Open the free QR code generator →Why a QR generator alone can't run paid ticketing
It's tempting to make 200 QR codes in a generator and email one to each guest. The problem is that nothing remembers which codes have been used. If a guest forwards a screenshot to a friend, both scans look the same.
For paid or capacity-limited events, use an event ticketing or registration platform that includes check-in scanning. Many of these offer a companion app that turns a phone into a scanner, shows the guest's name, and warns when a ticket was already scanned. A standalone generator like ours is the right tool for the shared-code setup, and for signage around the check-in area.
Handling screenshots and duplicate tickets
Screenshots are the most common concern with QR tickets. Ways organizers reduce the risk:
- Single-use scanning. The check-in system marks a ticket as used on first scan, so a second copy is rejected. This is the main protection.
- Name on the ticket. Showing the guest's name on the scan screen lets staff do a quick ID check for high-value tickets.
- Codes that change. Some ticketing apps show a code that refreshes regularly, so an old screenshot won't work.
- Releasing tickets close to the event. Some platforms send the scannable ticket only shortly before doors open.
For a free community event, single-use scanning is usually plenty.