Ticket Designer

Design event tickets with seat info, tear-off stubs, QR codes, and perforation guides.

Tested tool guide Tested browser tools Checked August 16, 2026

What Ticket Designer does and how it behaves

Ticket Designer lays out an event ticket as a printable sheet: the ticket itself with seat, row, and venue fields, a tear-off stub that repeats the essentials for the door, a QR code that carries a booking reference or entry link, and perforation guides that show where to cut. The content is text you type, so what you see is what prints. The usual surprise is the QR code: it encodes exactly the text you give it, and a code that looks fine on screen can refuse to scan once printed small, dense, or low-contrast.

How the result is produced

QR payload and scanability

The QR code encodes the text you enter - a booking reference, ticket ID, or entry URL - and the pattern gets denser as the payload grows. A short booking ID produces fewer, larger modules that print and scan reliably. A long URL with query parameters produces a dense code that needs generous print size, flat paper, and strong contrast, plus the blank quiet zone around it, to read at the door.

Stub, ticket, and the cut line

The perforation guide marks where the stub separates from the ticket, and anything placed across that line gets cut in half. The stub repeats the essentials - event, date, seat - so the door can tear it off and keep the main ticket intact. Recheck what sits near the line: text, a QR code, or a ticket number too close to the cut will come out damaged or trimmed.

Good uses

A school play or community event selling tickets at the door: produce a run of identical tickets, each with a numbered stub the usher tears off on entry.
A club night or theater show with reserved seating: each ticket carries its own row and seat number, repeated on the stub so staff can verify it at the aisle.
A fundraiser where every ticket has a unique QR code pointing to a check-in page or entry link, so guests are scanned in without a printed name list.

Limits and checks

On-screen rendering is not proof the print will scan. Ink spread, low contrast, curling paper, or a missing quiet zone can break a QR code that looks perfect in the browser. Print one ticket and scan it with a phone before running the full batch.
Perforation guides are visual cut marks, not a physical perforation. On plain paper you cut by hand, so content near the line is at risk; on pre-perforated stock, the tool cannot know where the stock's real perforations fall, so align the guide to them yourself. Printers also refuse to print into the page margin.
The data is not validated: a duplicated ticket number, a seat that does not exist, or a typo in the event name prints exactly as entered. The tool cannot cross-check against a venue's seat map or a booking system, so proofread before printing the run.

Common questions

Will my QR code scan after I print it?

Usually, but test first. Scanning depends on printed size, contrast, paper flatness, and the quiet zone around the code - a code that renders perfectly on screen can fail on paper from ink spread or glare. Print one ticket and scan it with a phone before running the whole batch. If it fails, enlarge the code or shorten the payload.

How many tickets fit on one page?

The classic roll-ticket size is 2 1/8 by 5 1/2 in (54 by 140 mm). At that size a US Letter sheet holds exactly 4 across and 2 deep (8.5 / 2.125 = 4, 11 / 5.5 = 2), so 8 per page before margins; A4 holds 3 across, so 6. Printers cannot print to the page edge, so treat those as upper bounds and shrink the ticket if the layout needs breathing room.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.