Skip to content
Bulk Tool

Bulk Ticket QR Generator

Generate many ticket QR codes with unique serials from pasted attendee rows, preview printable ticket layouts, and download everything as a ZIP.

One ticket per line. Columns separated by commas, semicolons, tabs, or pipes: Event, Attendee, Seat. Seat is optional and defaults to General. Columns: Event, Attendee, Seat. Up to 500 rows per batch. Nothing is uploaded; everything is generated in your browser.

256 px (small)512 px (standard)1024 px (print)

How to Use the Bulk Ticket QR Generator

If you are issuing tickets for a concert, gala, workshop, or school play, one QR code per attendee is the simplest reliable way to check people in. Each code on this page carries the event name, the attendee name, the seat, and a unique serial number, so a door volunteer can verify a ticket by scanning it and comparing the name on screen with an ID. Because every serial is unique, a screenshot shared online cannot be reused by ten people: the first scan admits the ticket, and later scans of the same serial can be flagged as duplicates in your check-in sheet.

Prepare your list in a spreadsheet first, with one row per attendee and columns for event, attendee, and seat. Keep names exactly as they appear on ID, because that is what staff will compare at the door. If you have reserved seating, fill in the seat column; for general admission, leave it blank and the generator marks the ticket General. Avoid commas inside names unless you switch to pipe or tab separators, since a stray comma will split one attendee into two columns and produce a wrong ticket.

The trade-off with plain-text ticket payloads is that anyone who can read the QR content can also forge a ticket with the same format. For free community events that risk is usually acceptable, especially when check-in staff verify names against a list. For paid events, treat the QR as one layer only: keep the serial list private, mark each serial as used the moment it is scanned, and consider adding a short secret check code to the payload that only your team knows. Do not rely on the QR alone to prove payment.

Print tickets at a size that scans from a comfortable distance, at least 3 cm wide for handheld tickets, with a quiet white margin around the code. Test with several phones, including an older budget phone, before you print the full run, and print a few spares for guests whose phones die or whose printouts get wet. On the day, keep a printed copy of the serial list at the door so check-in continues even if the venue Wi-Fi drops.

One more decision that pays off is how you handle check-in itself. A printed list of serials at the door is your fallback when phones die or the venue has no signal, and a simple used-marker next to each serial is your duplicate protection. If you expect more than a few hundred guests, split check-in across two tables sorted by surname so the queue never stalls on one volunteer. After the event, keep the used-serial list with your attendance records: it settles disputes about who actually attended, it shows which ticket types were most popular, and it gives you a clean starting list for next year's invitations without reusing anyone's data.

Frequently Asked Questions

How are the ticket serial numbers generated?

Serials are assigned in row order as TKT-0001, TKT-0002, and so on, so each ticket in the batch is unique. The serial is embedded in the QR payload and shown on the ticket label, which makes duplicate detection as simple as checking a serial against your list.

Can I use this for general admission without seat numbers?

Yes. Leave the seat column blank and the ticket is marked General. The attendee name and serial still make every code unique, so you can check people in by name even without assigned seats.

What should door staff do if the same ticket is scanned twice?

Treat the second scan as a possible duplicate. Check the guest's ID against the name on the ticket, look for the serial on your used list, and only admit the person if the first scan was a mistake, for example a mis-scan that was never actually an entry. Keeping a used-serial list is what makes QR tickets secure.

How many tickets can I generate at once?

Up to 500 rows per batch. If your event is larger, split the list into batches of 500 and keep the serial ranges apart by noting which batch each range came from, so no two tickets share a serial.