QR COVE GUIDES
Wedding QR code: RSVPs, photos and directions in one scan
A wedding runs on small pieces of information: where to be, when to reply, what is for dinner, and where the photos should go. Paper carries all of it badly. Invitations get left on fridges, reply cards never make it to a postbox, and the best photographs of the day sit on guests' phones forever. A few well-placed QR codes fix each of those problems for free — one scan for the RSVP, one for the photo album, one for directions — with nothing for guests to install and nothing for you to pay for.
What a wedding QR code can do
Each code is an ordinary QR code containing one link. The trick is to give every job its own code, clearly labeled, rather than expecting one code to do everything.
Collect RSVPs. Link the code to your RSVP form — a Google Form, or the RSVP page of your wedding website. Replies land in one tidy list you can actually plan from, instead of dribbling in as texts, calls, and messages to your parents.
Gather the guests' photos. Link the code to a shared album that guests can add to — for example, a Google Photos shared album with adding turned on. Your photographer cannot be everywhere; ninety guests with phones can. Give those photos one obvious home and you will see the day from every table.
Give directions. Link the code to the venue's location on Google Maps, so guests navigate to the actual door instead of a postcode that lands in a field. Our Google Maps QR code guide walks through getting that link.
Share the program or menu. Link the code to a page or PDF with the order of service, the menu, or the seating plan — for the guest who left the paper copy in the car, and for anyone who wants to keep it.
Step 1: gather your links
- RSVP link: create your form or open your wedding website's RSVP page, copy its link, then submit a test reply yourself so you know exactly what guests will see.
- Photo album link: create the shared album, set it so guests can view and add photos, and copy its link.
- Venue link: find the venue on Google Maps, tap Share, and copy the link — check the pin sits on the right building first.
- Program link: upload the order of service, menu, or seating plan as a page or PDF and copy its link.
- Test every link on a phone that is not yours and not signed in as you. Weddings fail on permissions, not on codes.
Step 2: make the codes, free
For each link, open QR Cove's website QR code generator, choose the URL type, and paste the link. Download the PNG for invitations and table cards, or the SVG for a welcome sign — SVG stays sharp at any size. Make one code per purpose, and save the files with names you will recognise in six months: rsvp.png, photos.png, directions.png. There is no account, no watermark, and no fee, and the codes are static, so they never expire. Keep the codes themselves plain — dark squares on white. Wedding colours are tempting, but a pale gold code on cream card that nobody can scan helps no one; put the styling in the card around the code, not in the code.
Step 3: put each code where it belongs
On the invitation. The RSVP code belongs here, with the reply deadline written out in words beside it — "Please reply by 1 June" — plus the directions code for guests travelling in.
On the table cards. The photo code, on every table, where guests are seated with their phones already out: "Share your photos with us" is all the instruction it needs.
On the welcome sign. At the venue entrance, the photo code and the program code catch everyone as they arrive, including the guests who never opened the invitation properly.
In the order of service. A small program or menu code at the back covers the lost-paper-copy problem for the whole day.
Before the real print run, test with family: print the final cards, hand them to two relatives — one with an iPhone, one with an Android — and have each of them actually complete the action. They submit the test RSVP, add a photo to the album, open the directions. Whatever they fumble, your guests would fumble too, and it is far cheaper to learn that at the kitchen table than on the day.
Mistakes couples learn the hard way
A private album behind a public code. If the photo album is not set to let guests view and add, every scan lands on a request-access wall, mid-party, and the photos never arrive. Test the album link signed out before anything is printed.
Unlabeled codes. Three identical squares on one card, with no words, get scanned by nobody. Every code needs its label: what it is for, in plain words, right next to it.
Leaving it to the final week. Codes made in a rush skip the testing step, and untested links are where weddings quietly break. Make them when the invitations are ordered, not after.
Too small, too glossy. A tiny code on shiny card defeats phone cameras with glare and size at once. Go bigger than you think, choose matte card if you can, and check the size with our print size estimator. If a code still will not scan, our troubleshooting guide covers the causes.
Frequently asked questions
How many QR codes does a wedding need?
Usually three: one for RSVPs, one for guest photos, and one for venue directions. A fourth for the program or menu is a nice extra. One code per purpose, each clearly labeled, is the whole system.
Do guests need an app to scan them?
No. Any modern phone camera scans a QR code, and the links open in the browser or in apps guests already have, like Google Maps. Nothing needs installing.
Can we change what a code opens after printing?
The code holds its link permanently, but you can freely update what lives at that link — add photos to the album, adjust the program page, extend a deadline on the form. Changing to a completely different link would need a new code.
When should we make and test the codes?
When you order the invitations. Test the final printed cards with family on both iPhone and Android, completing each action for real, well before the day itself.
Make yours free
Make your free wedding QR codes now — one for the RSVPs, one for the photos, one for directions — and give your guests the easiest wedding instructions they have ever received.