Couples usually need more than one QR code, because weddings produce more than one link worth sharing: the wedding website, an RSVP form, a gift registry, a shared photo album, a song request list. One code that tries to carry all of that only opens whichever address was typed in last, so it helps to decide up front which job each printed code is doing before building it.
Each of those jobs, from save-the-dates mailed before the website is finished to thank-you cards mailed after, gets its own page with the exact steps for that one destination. Build each as a free static code, or a dynamic one if the destination isn't final yet when invitations go to print.
Deciding what a wedding QR code should open
Pick the one address this code carries
A code that should get guests to the RSVP page is not the same code that should get them to the registry. Decide the single destination before you build anything.
Check whether that page is finished
If the wedding website, registry or photo album is live and its address won't change, a static code is enough. If invitations are going out before the site is finalized, a dynamic code lets you fix the address later.
Build it and scan it back
Paste the link into the web address field, download the preview, and scan it with a phone that has never opened that page before, to catch typos in the URL.
Match the file to the job
SVG for anything a print shop is producing at scale, such as invitation suites or signage; PNG for a card printed at home or a digital save-the-date.
The stages a wedding QR code actually shows up at
Save-the-dates go out first, often before the wedding website has a final domain or the registry is complete. Formal invitations and detail cards follow, once the website and RSVP are set. On the day itself, signage carries different links again: a welcome sign, table numbers, a favor tag. Thank-you cards mailed afterward are a fourth stage, sometimes repeating the photo album link so guests can see how the pictures they took got used.
Why one link per code beats a link-in-bio page
It is tempting to build one hub page with buttons for the website, RSVP, registry and photos, and put a single code everywhere. That works, but it adds a click for every guest, and it means editing that hub page whenever anything changes. A code that goes straight to the RSVP form, printed only on the RSVP card, gets a guest to the form in one scan instead of two.
Signage on the day, printed once and never touched again
A welcome sign at the ceremony or reception is usually the largest wedding code printed, often 15 to 20 cm across so it reads from across a room, and it is worth a proof print before the final version goes on foam board. A common use is a link to a digital version of the program, or to the same photo album guests will add to later that night.
What a wedding code actually holds
Whichever web address you chose for that job: the wedding website, the RSVP form, the registry page, or the photo album's share link. Nothing about the guest list, the seating chart or anyone's response passes through the code itself; that stays on whatever platform hosts the form or the site.
https://www.zola.com/wedding/janeandjohnSizes across invitations, cards and signage
An insert card or the corner of an invitation needs at least 20 mm to scan reliably from arm's length. A table card at the reception, read from a seat or two away, works better at 30 to 40 mm. A welcome sign or standee near the entrance, read from several meters, needs 15 to 20 cm; a phone reads a code from roughly ten times its own width.
Print it at least 20 mm (2.0 cm) wide
Where wedding codes send guests to the wrong place
Linking the homepage instead of the specific page
A code meant for RSVP that actually opens the wedding website's homepage makes every guest hunt for the RSVP link a second time.
One code doing three jobs
Trying to cover the website, RSVP and registry with a single printed code means picking whichever one link matters least and hoping guests find the rest.
Printing before the site is finished
A static code with a domain that changes later has to be reprinted. If the website isn't locked in yet, use a dynamic code instead.
When a wedding code should be dynamic
Save-the-dates mailed before the wedding website is finished are the clearest case: a dynamic code lets you fix the destination once the site and its domain are locked in, without reprinting anything already mailed. Day-of signage and cards printed after the website is final rarely need it, since a static code is free and never expires.
Dynamic needs a free account with a verified email, and the first 2 dynamic codes stay free for good.
How dynamic QR codes workWedding codes people actually print
- A save-the-date magnet with a dynamic code, mailed before the wedding website's final domain is chosen.
- A welcome sign at the ceremony entrance linking to a digital copy of the program.
- A table card linking to a Spotify playlist for song requests during the reception.
- A thank-you card repeating the photo album link so guests can revisit pictures from the day.
The one job where the free route gives up the most
Of the codes on this page, the photo album is the one where a plain link costs you something. An RSVP form, a registry and a wedding website are all fine behind a free static code — they are pages that already exist and the code just points at them.
Photo collection is different. The shared albums a code can point at were built for families swapping holiday pictures, not for a room of guests uploading at once during a reception. If the photos matter more to you than the other codes do, it is worth looking at something built for the evening itself, where guests upload without an account and the pictures show up on a screen while the party is still going.
Galawall — a photo wall built for weddings