Event QR Code Generator
Create a QR code for an event page, ticket link, or RSVP form. Download a print-ready PNG or SVG sized for posters, flyers, and standees.
What an event QR code is
An event QR code is a static QR code printed on event material that encodes the URL of a ticket page, RSVP form, schedule, or event listing.
Event material is read at wildly different distances — a flyer at arm’s length, a poster from two metres, a banner from across a hall — and that distance, not the design, decides how big the code has to be. Everything else is picking one URL and keeping it alive until the event is over.
Events are also the one situation where a static code’s lack of an expiry date costs nothing, because the poster itself expires. You get no per-scan fee, no subscription that could lapse mid-campaign, and no redirect service between your audience and your ticket page.
How to create an event QR code
- 01
Choose one destination
Tickets, RSVP, or the schedule — not all three. A poster has room for one action, and a code that lands on a page of choices loses people at the moment they were ready to act.
- 02
Generate the code
Paste the URL above and select Generate QR. Check the encoded address shown underneath, because a ticketing link with a long event ID is easy to truncate when copying.
- 03
Download the SVG for large print
Anything above postcard size should go to the printer as SVG. It is vector, so a code blown up to 30 cm on a banner has the same hard edges as one at 3 cm.
- 04
Size it for the reading distance
Make the printed code about a tenth as wide as the distance people will scan it from, then proof it by scanning from that distance rather than from your desk.
Sizing and placement for event material
Flyers and handbills
Read at roughly 30 cm, so about 3 cm of code. Keep it out of the bleed area — a code trimmed at the edge loses its quiet zone and stops scanning.
Street and venue posters
Read at one to two metres, so 10–20 cm. Place it at chest height where possible; a code at the top of a tall poster is scanned at an angle that shortens the effective read distance.
Banners and stage backdrops
Read from five metres or more, so 50 cm and up. Vector output matters here: a 1024 px PNG stretched across a banner turns every module edge into a soft ramp.
Standees and pull-ups
Read at one to two metres while standing. Keep the code above waist height and away from the curved bottom of a roller banner, where the surface angle distorts it.
Wristbands and lanyards
Read at 15–20 cm, so about 2 cm. Use the shortest possible URL — a schedule page rather than a deep link — because there is no room for a dense pattern.
Tell people what it does
“Scan for tickets” next to the code measurably outperforms a bare square. People do not scan codes out of curiosity; they scan them when they already know what they will get.
What event codes usually link to
- Ticket and registration pages
- RSVP forms
- Programmes and schedules
- Speaker and lineup pages
- Venue maps and directions
- Feedback surveys after the event
- Live streams for remote attendees
- Sponsor and exhibitor pages
Keep the destination page alive until well after the event. Scans keep arriving from posters nobody has taken down, and a dead link is a worse impression than no code.
A static code cannot be re-pointed after printing. If the venue or date might change, link to an event page you control and update that page rather than the code.
Questions about this
About a tenth of the scanning distance. A poster read from two metres wants roughly 20 cm of code; a flyer read at 30 cm wants about 3 cm. When in doubt, go larger — an oversized code costs a little layout space, an undersized one costs every scan.
Yes, any http:// or https:// URL works, including a direct checkout link. Test it on a phone that has never visited the site, since some ticketing platforms behave differently for a fresh session than for a logged-in organiser.
It keeps encoding the same URL for ever — the code has no expiry. Point that URL at a page that ages gracefully, such as one that later says the event has ended and links to the next one.
Only if you need to tell them apart. Give each print run its own URL — different campaign parameters, or different redirect paths on your own domain — and your analytics will separate them. Otherwise one code for everything is simpler and cheaper.
No. The code points directly at your URL with nothing in between, so there is no scan counter to hit a limit and no service that could start charging. A hundred scans and a hundred thousand cost the same: nothing.