Put your wedding details behind a single scan
A wedding QR code takes guests straight to your RSVP form, the running order, the gift list and, after the day, the shared photo gallery — printed once on the invitation and reused on the order of service. Guests scan instead of typing a long URL nobody copies correctly.
The detail couples miss is that invitations go out months early, while venues, timings and even the ceremony address can still shift. Encode a link you own and can repoint, and a last-minute change never turns fifty posted invitations into wrong information.
Fill the form to generate a QR code
One code for RSVP, gallery and seating
Send the code to a single wedding page that holds everything: an RSVP button, the timeline, directions, and later a link where guests upload their own photos. Guests bookmark that one page rather than juggling separate codes for each thing.
Add the photo-gallery link to the page only after you have chosen where photos live, so the printed code never needs to change — the page behind it does.
- RSVP form guests can fill on their phone at the table.
- Ceremony and reception timings with a map link.
- A post-wedding upload folder so guests' candids reach you.
Printing it on the invitation suite
Invitations use fine typography and often dark or textured card, which fights a QR code. Keep a clear light panel behind the code and print it at least 2 cm square with a quiet margin, so it reads against the design instead of blending into a foil border.
On the order of service or a welcome sign, you can go larger — 8 to 12 cm — so guests scan from a pew or across a table without crowding.
Why encode a link you can redirect
Point the code at a short link on a domain you control, then redirect that link to your wedding page. If the reception moves or the RSVP tool changes, you update the redirect once and every printed invitation still works. Encoding the wedding page URL directly ties you to that exact address forever.
The RSVP deadline problem
Guests scan whenever the invitation surfaces on the fridge, so make the RSVP page state the deadline and what happens after it. Once replies close, repoint the same link to a thank-you-and-directions page rather than a dead form, and late scanners still land somewhere useful on the day itself.
How to set up your wedding code
- Build one wedding page. Put RSVP, timings, directions and a photo-upload link on a single page guests can reach from their phones.
- Encode a link you control. Generate the code from a short link on your own domain that redirects to that page, not the page URL itself.
- Print with a light backing. Give the code a clear light panel and quiet margin so it survives dark or foil invitation stock.
- Repoint it as the day nears. Swap the redirect to the photo gallery or directions after RSVPs close. The common mistake is baking the raw page URL in and losing that flexibility.
Technical details
- Maximum characters: 2953
- Recommended error correction: Q (quartile) recommended for printed invitations — cards get handled, posted and propped on shelves, so extra recovery keeps the code scanning after months on a fridge.
- The code carries a plain URL; the redirect that lets you switch RSVP, timings or gallery lives on your own domain, not inside the code.
- Keep a light backing panel behind the code on dark or foil invitation stock, or the camera cannot separate the pattern.
Frequently asked questions
- Can one code do RSVP and photos?
- Yes. Send the code to a single wedding page and put both an RSVP button and, later, a photo-upload link on it. Guests use the same scan before and after the day, and you never print a second code.
- What if our venue changes after we post invitations?
- You are covered if you encoded a link you control. Update the redirect to the new venue page and every posted invitation now points to the right place. That is the whole reason to avoid baking the raw address into the code.
- How do I collect guests' photos with it?
- Point the code, after the wedding, at a shared upload folder or gallery and add that link to your wedding page. Guests scan, tap upload, and their candids land in one place instead of scattered across group chats.
- How big should the code be on an invitation?
- At least 2 cm square with a light backing panel and a quiet margin. On a large welcome sign or order of service you can print it 8 to 12 cm so guests scan from a distance.
- Will guests need internet to use it?
- Yes, to load the wedding page. The scan itself works offline, but RSVP, maps and the gallery all live online. Venues with weak signal should show the timings on printed cards too as a fallback.
- Should we add the code to the order of service?
- Yes, and make it larger there since guests are seated and relaxed. Reuse the same link so the printed invitation and the ceremony booklet both point at your single wedding page.
- Can guests RSVP without an account or app?
- That depends on your RSVP tool, but choose one that opens as a plain web form. A code that demands guests install an app before replying loses your least tech-comfortable relatives immediately.