Guide · Weddings
Wedding QR codes for invitations, RSVPs and photos
Invitations go out months before the day, and guests keep them long after. That is exactly why the codes on them should be the kind that can’t quietly expire.
Opens the generator set to a website link with the caption “RSVP and wedding details”. Paste your wedding website or RSVP form address.
Why “never expires” matters for weddings
Many QR sites hand out “dynamic” codes that route through their own short link. Some deactivate those codes when a free trial ends; one large provider’s help centre says its dynamic codes are deactivated and point to a service page after the trial. On a save-the-date posted in March for a September wedding, that is a real risk. A static code holds your link directly, so it works as long as the page it points to does.
Codes worth making
- Wedding website or RSVP form on the invitation or save-the-date. One code to your website’s main page is usually better than separate codes for every detail.
- Shared photo album on table cards, so guests add their photos. Create the album first (for example a shared album in Google Photos or iCloud), turn on the option that lets guests contribute, and test the link on a phone that isn’t signed in to your account.
- Venue Wi-Fi for guests, if the venue allows it. See the Wi-Fi QR code guide.
- Programme, menu or seating chart at the entrance, if you prefer not to print one for every guest.
- Registry on the website rather than the invitation, if you follow the etiquette of not printing registry details on invitations.
Step by step
- Set up the destination first and choose the final address. Changing your wedding website’s address after printing breaks the code.
- Open the generator with the button above and paste the address.
- Match your stationery under “Style & quality”: a dark colour from your palette on a light background, rounded or dot style. The generator warns you if contrast gets too low to scan.
- Download an SVG for your stationer, or the printable sign for table cards (change the caption to something like “Share your photos”).
- Scan a printed proof on the real paper stock before ordering the full run.
Sizes that work
A common rule of thumb is that people can scan from about 10 times the code’s width away, with about 2 cm (0.8 in) as a practical minimum.
| Item | Suggested code width |
|---|---|
| Invitation, save-the-date or RSVP card | 2–2.5 cm (about 1 in) |
| Table card | 4–5 cm (about 2 in) |
| Welcome sign or easel, read from 1.5–2 m | 15–20 cm (6–8 in) |
Stationery pitfalls
- Gold or silver foil: beautiful, but reflective foil is hard for cameras to read. Print the code in flat ink, even if the text around it is foiled.
- Light colours: blush pink or sage on cream often fails. Keep the code dark and the background light, never the other way round.
- Textured or handmade paper can break up the small squares. Go a little larger on textured stock.
- Cropping: keep the plain margin around the code; designers sometimes trim it to fit the layout.
- Privacy: anyone with the link can see a public album or website. Use your platform’s password or guest-list features if that matters to you.
FAQ
Will a wedding QR code still work after the wedding?
A static code made here never expires. It keeps working as long as the website or album it points to is online, so guests can find your photos years later.
What size should a QR code be on a wedding invitation?
About 2–2.5 cm (around 1 in) wide, printed in a dark flat ink on a light background with a clear margin around it.
Can I print a QR code in gold foil?
It is risky. Reflective foil often stops phone cameras reading the code. Print the code in flat ink and keep the foil for the lettering.
How do guests share photos with a QR code?
Create a shared album that lets guests add photos, copy its share link, make a code from that link and put it on table cards with a caption such as “Share your photos”.
Sources
Related guides
- Event check-in QR code: simple check-in for other events
- Wi-Fi QR code: venue Wi-Fi with a scan
- QR code that never expires: why a static code keeps working