QR Code on a Wedding Invitation: How to Add One That Actually Scans

A printed invitation with a digital RSVP is the combination where a QR code earns its place. A guest holds the card, points a phone at it and lands on your invitation page in two seconds, with no web address to type. When it works, it is the smoothest bridge between paper and digital. When it does not, the card carries a small black square nobody can use, and you spend the next month answering "how do I RSVP?" by text.

This guide covers what to link to, the size and spacing that make a code scan reliably, where to place it, what to write beside it, and the backup you need for guests who cannot or will not scan.

Do you even need a QR code?

If you send your invitation as a link by message or email, you do not need one. The guest simply taps the link. A QR code is for the moment a guest has a printed card in one hand and a phone in the other, and needs to get from one to the other. Typical cases:

• A printed invitation or details card that points to your digital RSVP page.
• A printed save the date that points to your wedding details.
• A welcome sign or table card on the day, linking to the schedule or a photo-sharing page.

If none of these apply, skip the code and send the link directly.

Decide what the code points to

A QR code is just a web address in a different shape, so the first decision is the destination. Three rules prevent most problems.

Point to one place. One code, one page. If that page is your invitation, the guest should be able to read the details and reply there. A code that opens a menu of links adds a step at the exact moment you want fewer.

Point to a page that works on a phone. Most scans happen on a phone, standing up, possibly on mobile data at a family dinner. Open your destination on a phone, on mobile data, without being logged in anywhere. If it asks for an account, an app download or a password you forgot to print, the code has failed.

Keep the address short. The more characters in a link, the more tiny squares (called modules) the code needs, and denser codes are harder to scan at small sizes. A short, clean link produces a simpler, more forgiving code. If your address has long tracking parameters, remove them or use a shorter version.

Size, contrast and spacing

Most scan failures on printed cards come from the same four things.

Two more details. Never stretch or squash the code to fit your layout, because it must stay perfectly square. And if you want a small monogram or logo in the middle, choose a higher error-correction level when you generate the code. QR codes have four levels (L, M, Q and H) that can recover roughly 7, 15, 25 and 30 percent of a damaged or covered area. Higher levels survive a logo or a scuff, but they also make the code denser, so keep the address short.

Static or dynamic code?

This is the detail that bites people months later.

A static QR code contains your web address directly. It works as long as the page exists, and nobody can switch it off.

A dynamic QR code contains a short redirect address owned by the QR service, which forwards guests to your page. It lets you change the destination later and sometimes shows scan counts, but it only works while the service keeps it active. Some free generators disable dynamic codes after a trial period or a set number of scans.

For a wedding, where cards are mailed weeks ahead and may sit on a fridge until the day, a code that stops working is the worst outcome. Unless you have a clear reason to want the redirect, use a static code that points to a page whose address you control, and update the page itself if details change.

Where to put it and what to write beside it

Put the code where guests already look for how to reply: on the RSVP or details card, not on the main invitation face, where it competes with your names and the formal wording. Always write an instruction next to it. A bare square makes guests guess.

Examples you can adapt:

• Scan to RSVP by 15 May
• Scan for the schedule, directions and RSVP
• Please reply by 15 May: scan the code or visit [short address]

The deadline matters as much as the code. For deadline wording, see how to word an RSVP request, and for the dates themselves, when to send wedding invitations.

The backup every code needs

Plan for three kinds of guests: those whose camera does not read the code, those who see a code and do not know what to do with it, and those with no smartphone. Cover all of them with the same small block under the code:

1. The link in plain text, in readable type, so it can be typed on a laptop or read aloud over the phone.
2. A phone number or email of someone who will answer, for guests who prefer to reply by talking.
3. A paper reply option for the few guests who need one.

Nearly every guest will manage the code. The backup exists for the handful who will not, and for them it is the entire invitation. Our guide to inviting older and non-tech guests shows how to plan for that group.

One shared code or one per guest?

A single printed code on every card is simple, and every guest lands on the same page. The trade-off is identification: the guest has to say who they are, and you cannot tell from the scan alone which household replied.

If your printer can produce a different code on each invitation (variable data printing), each household can get its own link. That makes tracking cleaner and stops one link from being forwarded to people you did not invite. It also costs more and needs extra care at the proof stage. Read how unique RSVP links work first and decide whether the added complexity is worth it for your guest list.

Test before you print

Do this before you order the full print run:

1. Print a proof at the real size on the real paper, not just on screen.
2. Scan it with at least two different phones, ideally one iPhone and one Android, in normal room light.
3. Scan it at the distance a person would hold a card, then lay it flat on a table and scan again.
4. Open the destination on mobile data, not your home Wi-Fi.
5. Ask an older relative to try it without your help, and watch what they do.

If any scan hesitates, enlarge the code, shorten the address or simplify the design around it.

Common mistakes

• Placing the code over a patterned or photographic background.
• Printing it too small to make room for decoration.
• Using a dynamic code from a free service that later expires.
• Linking to a page that needs a login or an app.
• Giving no instruction, so guests do not know what the code is for.
• Offering the code as the only way to reply.

Frequently asked questions

Is a QR code on a wedding invitation tacky? Not when it sits on the reply or details card with a clear instruction and a backup. Many guests now expect one on a printed invitation.

Do phones read QR codes without an app? Most current iPhone and Android cameras scan them directly. The plain-text link covers anyone whose phone does not.

Can I put a QR code on the save the date? Yes, if it leads to a page with the date and location. The code on the invitation can then lead to the RSVP. See save the date vs wedding invitation for what goes on each.

What if my details change after printing? With a static code, update the page the code points to. See managing a guest list when event details change.

Checklist

• One code, one destination, a short address.
• At least 2 cm square, with a clear margin and dark-on-light contrast.
• A static code, unless you have a reason to use a dynamic one.
• A written instruction and a deadline next to it.
• Plain-text link, contact details and a paper option as the backup.
• A printed proof tested on two phones.

If you are still building the page your code will lead to, start with how to create a digital wedding invitation or browse the invitation templates.