"QR Code Wedding RSVP: Wording, Placement and What to Avoid"

A QR code on a wedding invitation does one job: it removes the moment where a guest has to type oursite.com/jamie-and-alex/rsvp into a phone keyboard without a typo. That moment is where RSVPs get postponed and then forgotten, so removing it is worth doing well.

It's also easy to do badly, usually in ways you can't discover until the invitations are already printed.

What it actually is

A QR code is a link in a form a camera can read. Your guest points their phone at the invitation, taps the notification, and lands on your page. That's the entire mechanism — the code doesn't collect anything, store anything or know who scanned it. It's a shortcut, and everything that matters happens at the other end.

Which means a QR code can't rescue a bad RSVP page. If the link lands on a homepage where the guest still has to hunt for a menu item, you've moved the friction rather than removed it.

Where to put it

• On a separate RSVP or details card. The best option for a formal suite. The code has room to be scannable, and the main invitation stays uncluttered.
• On the back of the invitation. Clean, and it keeps the suite to one piece.
• On a save-the-date. Good for pointing early to the wedding website, before RSVPs open.
• On the front of a formal invitation. Usually a mistake. A QR code is a piece of machine-readable ink; on a letterpress invitation with a calligraphic name it fights everything around it.

For a minimalist or digital-first design, working the code into the layout deliberately can look excellent. The failure mode is treating it as an afterthought stamped in a corner.

Wording that works

Simple

Kindly reply by 15 May Scan the code or visit oursite.com/jamie-and-alex

Warm

We'd love to know if you can make it. Scan below to reply by 15 May.

Formal

The favour of a reply is requested by the fifteenth of May. Please scan below to respond.

Casual

Are you in? Scan to let us know.

Whichever tone you take, the code needs a label. An unexplained square gets scanned by roughly the people who were going to reply anyway; "Scan to RSVP" gets scanned by everyone else.

Always print the address too

This is the rule people skip, and it costs responses.

A guest reading your invitation while holding their phone can't scan it with that phone. Guests who use a tablet, who have an older phone, or who simply don't trust scanning codes need a way through. And anyone forwarding your details to a relative needs something they can type or paste.

Print the URL near the code. It costs one line and it's the difference between a shortcut and a gate.

The printing mistakes

Too small. A code needs roughly 2cm square to scan reliably at arm's length on card. Designers shrink them for balance; test at the real size before you approve a proof.

Not enough quiet zone. A QR code needs blank space around it — about four modules' worth. Type or a border pressed against the edge stops it resolving. This is the single most common reason a printed code fails when the digital file scanned fine.

Not enough contrast. Dark code on a light ground. Cream and charcoal is fine. Blush on ivory, gold foil on white, or a code printed over a photograph will fail in half the lighting conditions your guests are in.

Never tested on paper. Scanning the PDF on your monitor proves nothing about the printed piece. Get a proof, test it with an iPhone and an Android, in daylight and under a lamp, at arm's length. Do this before the full run, every time.

Send them to the right place

Every step between the scan and the reply loses people. The worst version is: scan → homepage → find the menu → find RSVP → search for your own name → reply. That's four opportunities to put the phone down.

Link as deep as your platform allows — ideally straight to the RSVP itself. Better still if the link identifies the invitation, so the guest doesn't have to find their household in a list before answering. (Shared Beginning's QR codes go directly to your RSVP page, and stationery QR codes are part of the invitation suite rather than something you generate and paste in separately.)

One thing to think about before you use a personalised, per-guest code: an invitation-specific link means anyone holding that card can open that household's RSVP. That's usually fine — it's the same trust model as a physical reply card in a mailbox — but it's worth a conscious decision rather than a surprise.

What to collect once they arrive

A paper reply card had one question because it had one card. Online, you can reasonably ask about meal choices, dietary needs, plus-one names, which events they'll attend, arrival dates and shuttle use.

Reasonably — not automatically. The same rule applies as anywhere else: ask what will change a decision you make, and skip the rest. There's more on which questions earn their place in our wedding RSVP questions guide.

Before you approve the proof

• The code is at least 2cm square at print size
• Blank margin all the way round it
• Dark ink on a light ground
• The written URL appears nearby
• A short instruction — "Scan to RSVP" — sits with it
• It scans from a printed proof, on two different phones
• It lands on the RSVP page, not the homepage
• The RSVP deadline is on the same card

Seven of those cost nothing. The eighth costs a reprint.