QR Codes for Tickets: How to Set Them Up and Scan Them

A QR code on a ticket is only a carrier. The code itself is free to generate. What makes it a ticket is the system behind it, which checks each code against a record of who bought it and whether it has already been used. Get that part right, print or display the code cleanly, and test your scanners at the real venue. Then QR tickets are fast, cheap and hard to fake.

This guide covers what to encode, how to make codes that scan, how to handle screenshots and duplicates, how check-in works at the door, and when QR wristbands are worth it.

Actickety

actickety.com

Simplify Event Ticketing Setup

Actickety helps organizers build event microsites, create AI posters, and configure ticketing without upfront costs before going live.

Visit Actickety

TL;DR

A QR code is free to make, but it only works as a ticket when a database or attendee list validates each scan. A static code has no one-time-use logic of its own.
Encode a unique ticket ID or a link tied to one registration. Never encode names or other personal details.
Most scan failures are physical: low contrast, tiny modules or a missing quiet zone. Print at 100% scale, black on white.
Test your scanners and connectivity in the actual room, at the busiest time, before doors open.
Wristbands are worth it when guests come and go, or when a phone is a hassle. Tie each band to one ticket record.

What a QR code ticket actually is
What to put inside the code
How to make QR tickets that scan
Screenshots, forwarding and duplicate entry
Check-in at the door
QR code wristbands: when they make sense
Our perspective
Setting up ticketing without upfront cost
A short pre-event QR checklist
FAQ
Sources

What a QR code ticket actually is

A QR code is a square grid of dark and light modules that a phone camera or handheld imager reads and turns into text, usually a web address or an ID. It does not know who the guest is, whether they paid or whether they already came in. All of that lives in a database.

That is why a QR code ticket is really two things:

The credential: a unique code, delivered by email, a ticket page, a wallet pass or a printout.
The validator: a scanner app or device that looks the code up and answers yes, no or already used.

If you only have the first, you have a picture. A static code can be copied as easily as any other image, so you must manage it against a guest list or an entry-scanning system. If you have both, a photocopied ticket is useless, because the second scan of the same ID gets flagged.

What to put inside the code

The safest pattern is simple: encode a unique, random ticket ID, or a URL that contains one, and tie it to a single attendee record. The WooCommerce ticket documentation gives an example format like EVT-84G7K2 and notes that an ID is safer than a name. It protects privacy and avoids scanning problems caused by long, complex text strings.

A few rules we follow:

One code per ticket, not per order. If someone buys four tickets, they get four codes. Otherwise one person can walk in and the other three are locked out, or worse, all four enter on one scan.
No personal data in the code. Anyone can read a QR code. Keep names, emails and phone numbers in the database.
Short beats long. The more characters you encode, the denser the grid and the harder it is to scan from a cracked phone screen or a cheap print.
Keep the ID separate from where it points. GS1, the standards body behind barcodes, makes the case that the identity of an item should be separate from the location of its data. In practice, point the code at an ID-based address you control. You can then change what guests see (a new door time, a venue change) without reprinting a single ticket.

Static versus dynamic codes

A static code carries its data inside the pattern, so changing it means a new code. A dynamic code carries a short address that redirects to a page you can edit. For tickets, dynamic is almost always the better choice, because event details change. Doors move, sessions are added, a parking note needs to go out the day before.

The third type is the rotating code, which refreshes every few seconds inside an official app. Large venues use it to stop screen copying. Stadium ticketing guidance points guests to the official app for this reason. Most community, school and charity events do not need rotating codes, because a unique ID plus a one-scan-only rule already closes the common loopholes.

Static, dynamic, and rotating QR ticket codes

How to make QR tickets that scan

Most "my QR code won't scan" problems are print or screen problems, not software problems. A venue-focused troubleshooting guide lists low contrast, undersized modules and sloppy printing among the main causes. Here is a checklist.

Contrast and color

Use dark modules on a light background, ideally black on white. Light gray, eco-toner or pastel brand colors make the modules pale, and imagers need crisp contrast. Inverted codes (white on black) fail on many scanners. If your brand color is the issue, keep it in the border and the surrounding ticket design, not in the code.

Size and module size

The module is the smallest square in the grid. Practitioners recommend a minimum module size of about 0.5 mm for reliable reads with handheld imagers. In everyday terms: do not shrink the code to squeeze it onto a small ticket stub. If the stub is tiny, encode less data so the grid has fewer, larger modules.

The quiet zone

Every code needs a clear border of empty space. The ISO/IEC 18004 QR code standard defines it, and the same troubleshooting guide puts the requirement at at least four modules on every side. Placing a code against a dark edge, a photo or overlapping graphics is a classic way to make it fail. Your ticket designer should treat that border as untouchable.

Print settings

Print at 100% scale, never "fit to page." Use matte white stock, because glossy paper reflects light back at the scanner. If you are exporting codes for print, vector formats such as SVG keep edges sharp at any size, as the WooCommerce documentation recommends. A simple test before a big print run: print one ticket, then scan it with the cheapest phone you can find, in poor light, from arm's length.

Digital tickets

On screen, make sure the code sits on a plain white area and that the ticket page is built for phones. Many guests will have their brightness low or their phone in battery-saver mode. Add a line on the ticket that says to turn the screen brightness up at the door. It costs nothing and removes a surprising number of retries.

If you want a polished ticket and poster look around the code, a design specialist can help. Local agencies that offer event design and branding services are one route. Just brief them on the quiet zone and contrast rules above, so the artwork never crowds the code.

Screenshots, forwarding and duplicate entry

Do screenshots work? It depends on the venue. Large stadiums and arenas do not accept screenshots, and require guests to open tickets in the official app or a digital wallet such as Apple Wallet or Google Pay. A stadium mobile ticketing page explains that venues rely on codes that refresh every few seconds so a copy goes stale.

For a smaller event with static, per-ticket codes, a screenshot of a valid code scans fine, because the code is the same one. What protects you is the validator: the first scan is accepted, the second is rejected. That is a healthier defense than banning screenshots, because guests lose phones, run out of battery and forward tickets to friends.

To reduce fraud without making entry painful:

Enforce one scan per code. The scanner should show a clear "already scanned" result with the time of the first scan.
Let genuine transfers happen. If someone cannot attend, they should be able to pass a ticket on through your ticket page, so the old code is voided and a new one is issued, rather than sharing screenshots.
Only sell through your own page. Venues warn that tickets bought from unauthorized resellers can be counterfeit, stolen or void. Tell your audience clearly where your real tickets are sold.
Watch your checkout, too. Fraud does not only hit the door. Automated card testing attacks hit online checkouts, so keep an eye on odd bursts of small failed payments, and talk to your payment provider if you see them.

Check-in at the door

A QR code makes check-in quick only if the workflow around it is solid. Here is a simple setup for a small or mid-sized event.

Export or sync the attendee list the night before, so every scanner device has the latest data and a fallback copy.
Assign devices and people. One scanner per entry lane is a sensible start. Add a separate lane for problems (lost tickets, name lookups) so one issue does not hold up the line.
Test in the room. Experts recommend checking scanners and connectivity in the actual event environment at peak times, because signal drops and poor lighting slow entry far more than the code does.
Plan for no signal. Know whether your scanning app works offline and syncs later. If it does not, have a printed attendee list as backup.
Brief your volunteers. Show them what a valid, an already-used and an invalid result look like, and what to do with each.
Put signs up early. "Have your ticket ready, brightness up" at the queue start saves minutes at the front.

Using a QR code for walk-up sales

The same technology works before the doors open. A printed sign at the entrance with a QR code that goes straight to your ticket page lets walk-up guests buy on their own phone, with no cash handling. Keep that code on a static, permanent address to your event page, so the printed sign never goes out of date. This is also where a QR on your poster earns its place. Our event poster design guide covers how to make the code readable at a glance.

Guest scans event entrance ticket QR sign

QR code wristbands: when they make sense

Wristbands carry the same kind of code on a band that goes on the guest's wrist, so it can be scanned at the gate, at session doors or at a bar. Custom-printed bands can carry a distinct code tied to each ticket or guest record, which is the same logic as a ticket, just in a different form.

They tend to suit:

Festivals and multi-day events, where guests leave and re-enter and phones run out of battery.
Fundraisers and galas, where guests do not want to pull out a phone in a formal setting.
Sports days and school open days, where children or older guests may not have a phone handy.
Events with zones, such as VIP areas, where staff need a quick visual check as well as a scan.

They cost more than a digital ticket, need ordering in advance and add a distribution step, so they are overkill for a one-evening talk or a small workshop. If you use them, the rule stays the same: each band must map to one record in your attendee database, and you should test the print on a few real bands before ordering hundreds. Bands curve around the wrist, so a code that scans on a flat proof can behave differently once worn.

Our perspective

We build ticketing for organizers who are not technology companies: charities, community groups, school staff, musicians, sports clubs. What we see is that the QR code is rarely the problem. The problems are upstream and downstream. Upstream, organizers are stuck waiting on a setup process or a contract before they can sell a single ticket. Downstream, they have sold the tickets but do not control the attendee data, so they cannot reach their own audience again or fix the door list.

Our view is that a QR ticket should be the last, boring link in a clean chain. The organizer builds the event page, sells tickets, owns the guest data and checks people in from that same data. That is why we put weight on organizers keeping 100% ownership of their event data, and why we do not charge platform fees on ticket sales. A code that scans in two seconds is a small win. A code tied to a list you own, and can use again for your next event, is the bigger one.

Our practical advice: spend your effort on three things. Keep the code clean and well-printed. Make sure every code is unique and validated once. Test at the venue. Everything else is detail.

— Tim

Setting up ticketing without upfront cost

If you are building an event page and ticketing from scratch, Actickety lets you create an event microsite in ten straightforward steps. You can also generate an AI poster and configure tickets and merchandise. Setup is free, and you pay nothing upfront until you are ready to go live. There are no platform fees on ticket sales, and you keep full ownership of your event data.

For a sense of how a small team can go from idea to selling tickets in a day, read our guide to community event ticketing. If you want your own branding on the experience, see how white label ticketing works with a no-upfront-cost model. Once your tickets are live, our list of ways to promote an event online shows what to do with them.

A short pre-event QR checklist

Check	Why it matters	When
One unique code per ticket	Stops duplicate entry	Before sales open
ID or link only, no personal data	Protects attendee privacy	Before sales open
Black on white, quiet zone intact	Avoids most scan failures	Design stage
Print at 100% on matte stock	Keeps modules sharp	Print proof
Scan a proof on an old phone	Catches weak spots	One week out
Scanner and signal test at venue	Finds Wi-Fi and lighting issues	Day before or morning of
Offline fallback list	Keeps the line moving	Day of
Staff briefing on scan results	Fewer disputes at the door	Day of

FAQ

Are QR codes free?

Generating a QR code is free with many online tools. The cost sits in what you build around it: a ticketing or check-in system that validates each code, and any printing. A free code with no validation is just an image that anyone can copy.

Does a screenshot of a QR code work for tickets?

At large venues, usually not. They ask guests to open tickets in an official app or a wallet such as Apple Wallet or Google Pay, and use refreshing codes. At a smaller event with unique per-ticket codes, a screenshot scans like the original, and your one-scan-only rule is what stops duplicates. State your policy on the ticket page so guests know.

How do I make QR tickets?

Give each attendee a unique ticket ID, encode that ID or a link containing it, and link it to one registration record. Add the code to a clean ticket layout with a clear quiet zone, then check each code against your attendee list at the door. The easiest route is to use ticketing that creates and validates the codes for you.

Do I need an app to scan QR tickets?

Not necessarily. Phone cameras can read a code, and many scanning tools run in a browser. What you need is a way to look the code up and mark it used. Test the setup with your own devices at the venue before the event.

Why won't my QR ticket scan?

Check the basics first: low contrast, a code that is too small, no clear border around it, a glossy or scaled print, or a dim phone screen. Print at 100% scale in black on matte white and raise screen brightness. If it still fails, check the scanner's connection to your attendee data.