QR Code Event Tickets: How to Create and Check In Guests (Free Guide)

How a QR code ticket actually works

A QR code is just a picture that holds text. When a phone camera reads it, the phone does something with that text: open a link, show a message, save a contact. Nothing magic happens inside the square itself — the value comes from what the text points to.

For an event ticket you normally store a link that includes a unique reference for that guest, for example a booking number or a random string. At the door you open that link, or compare the reference to your guest list, and mark the person as arrived. The code is the fast way to read a long reference without typing it.

You do not need an expensive ticketing platform to start. A spreadsheet of references plus one QR code per guest is enough for a workshop, a wedding, a school show, a meetup or a private launch party.

Step 1 — Decide what goes inside the code

Pick one of three simple patterns. First, a link with a reference: your event page plus something like ?ticket=A7F3K2. This is the most flexible option because you can change the page later without reprinting anything.

Second, plain text: for example TICKET-A7F3K2 with no link at all. Scanning shows the reference on screen and your door staff compares it to the list. It works offline, which matters in a basement venue with no signal.

Third, a calendar or contact code for extra convenience — an event QR that saves the date, or a vCard so guests keep your organiser details. Many events print two codes: the ticket code and a smaller add-to-calendar code.

Whatever you choose, keep the content short. A shorter string produces fewer squares, and fewer squares scan faster from further away — which matters when someone is holding a coffee in one hand and a phone in the other.

Step 2 — Create the codes with QRPixel

Open the generator, choose URL if your ticket points to a link, or Text if you are storing a bare reference. Paste the value for the first guest and watch the preview build as you type.

Now brand it, but gently. Set the dark colour to your event colour and leave the background white or very light. Add your logo in the middle if you have one; QRPixel clears the dots behind it and you should switch error correction to the highest level so the code still reads.

Download SVG when the ticket will be printed and PNG when it will be sent by email or shown on a phone. SVG stays sharp at any size, which is exactly what your printer wants. Repeat for each guest, naming files by reference so you never mix two tickets up.

If you are running dozens of guests, do the design once, then only change the encoded value between exports. Keeping colours, logo and size identical makes the batch look professional and makes problems easier to spot.

Step 3 — Design a ticket people can use

A ticket needs four things around the code: the event name, the date and start time, the venue with a short direction hint, and the guest reference printed as readable text under the square. That last one saves the day when a screen is cracked or the ink smudged — staff can type the reference by hand.

Give the code breathing room. Leave a clear white margin of at least four module widths around it, which is roughly the width of four small squares. Codes that touch a border or sit on top of a photo are the single most common reason scanning fails.

Put the code where a thumb does not naturally rest, usually the upper right or the centre of the ticket. On phone tickets, keep it away from the very bottom of the screen where system gestures and notification bars appear.

Step 4 — Test before you print anything

Print one ticket, not two hundred. Then run four tests: scan with an older Android phone, scan with an iPhone, scan in dim light like your actual venue at night, and scan from about 30 cm away with a slight tilt.

Check the destination too. Open the link the code produces and confirm it loads the page you expect, on mobile data rather than venue WiFi. A ticket that scans perfectly but lands on a broken page still ruins the door experience.

Only after all four tests pass should you order the full run. Ten minutes of testing has saved a lot of events from a reprint bill.

Step 5 — Run the door on event day

Set up two lanes if you expect more than about 100 guests: one for people with a code ready, one for problems and walk-ins. Mixing them is what creates the long line everyone remembers.

Give each staff member a phone or tablet with the guest list open and a simple rule for marking arrivals — a checkbox column in a shared spreadsheet works fine. Agree in advance who fixes duplicates so two people never admit the same reference.

Keep a printed backup of the guest list. Signal drops, batteries die, and a paper list turns a crisis into an inconvenience. Also keep a small torch or a bright phone screen handy: dark entrances are hard on cameras.

Best practices that keep the queue moving

Print the code at least 2.5 cm wide for handheld tickets, and larger for anything scanned from a distance. A good rule of thumb is one tenth of the scanning distance: 30 cm away needs about 3 cm of code.

Use dark ink on a light background, never the other way round. Inverted codes fail on a surprising number of older cameras.

Send tickets in two formats — an attached image and an inline image in the email — so guests can find theirs quickly even in a cluttered inbox.

Tell guests to increase screen brightness before reaching the door. It sounds trivial, and it removes a real percentage of failed scans.

Log every scan you can, even manually. Arrival times tell you when to add staff next time.

Common mistakes to avoid

Reusing one code for every guest. It is fast to make and impossible to control — anyone can forward the image, and you lose all attendance data.

Making the code too small on a folded invitation, then folding the paper straight through the middle of the square. The crease breaks the pattern.

Printing over a busy background photograph. Contrast beats decoration every time.

Relying only on venue WiFi at the door. Test on mobile data and keep an offline fallback.

Forgetting the human-readable reference under the code, so a damaged ticket cannot be checked at all.

Expert tips from real events

Add a colour band or icon per ticket type — general, VIP, staff — so door staff sort people by eye before they even scan. Speed at the door is mostly a sorting problem.

For multi-day events, print the day on the ticket in large type. Codes look identical, dates do not.

If your event has seating, encode the reference only and keep seat numbers in the list. Then last-minute seat changes never require a reprint.

Take a photo of your final approved ticket, including the printed code, and keep it with the event file. Next year you start from a proven design instead of guessing.

Conclusion

QR code tickets are one of the cheapest upgrades an event organiser can make. Choose a short, unique reference, generate a clean branded code, print it big enough with a clear margin, test on real phones, and prepare a paper fallback. That is genuinely the whole system.

Start with your next small event, keep the guest list simple, and refine the design once you have watched real people scan at a real door.

Frequently asked questions