Download your event QR code

Where is the QR code in my dashboard?

On the QR & signs tab of the event, alongside the short link and the scan count. The code is issued the first time you open that tab and it belongs to the event from then on. What you see on the page is a small preview rendered for the screen, so judge sharpness from the downloaded file rather than from the thumbnail in front of you.

Nothing has to be ordered or generated first. The tab works on a free event and on one whose date has already passed.

1. Open QR & signs. The tab sits on the event itself. The code exists the moment the event does, on a free plan and on a draft alike.
2. Take the plain code or build a sign. Plain PNG and SVG feed your own layout. The sign studio hands you a finished card with the code already placed.
3. Scan the export before you print a batch. Open the exported file at print size, scan it with a phone that isn’t yours, and read the event name on the page that opens.

PNG or SVG — which one do I print?

A PNG is a fixed grid of pixels, and yours arrives at 2048 px along each edge, which is plenty for A4 and anything smaller. An SVG stores the code as shapes instead, so it holds its edge blown up to a banner, and it’s the file a stationery designer or a print shop will ask you for. Both come out transparent, with no white box behind them.

Both encode the same short link. Converting or renaming the file afterward changes nothing a camera reads.

Why is there no white border around the code?

Because the export is cropped tight to the last dark square, on purpose, so the code drops into your layout at a position you control. A camera needs empty space around a code to find its edges, so leave a clear band at least as wide as 4 of the small squares inside the code. That band is the difference between a card that reads at a glance and one your guests aim at twice.

On a patterned or photographic background, give it more than the minimum. The ready-made signs already carry that margin for you.

Can I download a finished sign instead?

Yes, and that’s the shorter road. The sign studio carries 4 templates across 4 sizes: Classic Serif, Script, Modern Minimal and Festive. Your event name seeds the headline, the line under it and the footer are yours to edit, and the code is placed at a size that suits the format.

Export a PNG at 300 dpi for a printer at home, or a PDF at the exact trim size for a print shop.

Bleed is off by default, since these mostly go through a printer at home. Switch it on for a print shop and the page grows by 3 mm on every side and picks up crop marks.

How big does the printed code have to be?

The studio won’t hand you a card whose code would print under 20 mm, because below that a phone has to sit almost against the paper. On an A6 card the code lands between 42 and 51 mm depending on the template, and on an A4 poster between 84 and 102 mm. Those are the sizes the templates place for you.

For a code somebody scans while seated, 40 to 50 mm is comfortable. For a sign read from across the room, go up to A4 and let the template scale it.

What gets checked before the download?

The studio grades the card while you edit it and tells you what it found. It calls the code a blocker when its color falls below 4.5:1 against the surface behind it, and again when the code would print under 20 mm. It raises a warning when a headline or a subline had to be cut short to fit.

None of it stops the download. It exists so a stack of 40 unreadable cards is caught on screen instead of at the party.

Will the printed code stop working later?

No. Your event gets 1 short code the first time the tab is opened, and every later export reuses it. Renaming the event, moving its date, changing the accent color or upgrading the plan all leave that code untouched, which is why printing weeks ahead costs you nothing.

On the Grand plan you can claim a custom link once payment lands. That adds a second address rather than replacing the first, and the earlier code keeps resolving, so cards already sitting on tables stay good.

What does change is what the code opens into. Closing uploads, archiving the event, or letting the album run to the end of its retention window ends the guest sessions behind it — the code still leads to your event, the album stops taking files.