How to Create a QR Code for Wedding RSVPs (Free)
Make a free QR code for wedding RSVPs in 3 minutes. Exact print sizes, placement, testing steps, and how to fix a wrong code after printing.
Planning an event?
Invyt handles your RSVPs so you can focus on the celebration — not the spreadsheet.
Try Invyt free →A QR code for wedding RSVPs is a printed square that opens your online RSVP page when a guest points their phone camera at it. You make one by creating the RSVP page first, copying its link, and running that link through a free generator. The whole thing takes about three minutes and costs nothing.
The part that takes longer, and the part almost nobody plans for, is everything after the code exists: how big to print it, where it goes on the stationery, and what happens if the link turns out to be wrong after 150 invitations have already come back from the printer.
Quick summary: Build the RSVP page, generate the code from its URL, print it at 1 inch or larger with a white border, and test it on two different phones before you approve the printer's proof. You can generate a free event QR code here once your page is live.
What a Wedding RSVP QR Code Actually Links To
The code encodes a web address. Nothing else. There is no data about your wedding stored inside the pattern, and no company holding it hostage. When a camera decodes those squares it gets a string of text, sees that it looks like a URL, and offers to open it.
That single fact decides most of the choices below. A code is only as reliable as the address inside it, which is why the destination deserves more thought than the design. According to The Knot's Real Weddings Study, 74% of couples now run RSVPs through a wedding website, so for most weddings the code has an obvious place to point.
Point it at your RSVP form, not your wedding website homepage. Every tap between the scan and the submitted response costs you replies. If your guest scans and lands on a homepage with a photo gallery, a schedule, a registry link, and an RSVP button somewhere below the fold, a meaningful share of them will read the page, mean to respond later, and never come back.
The exception is the save the date, which usually goes out before you have a finalised guest list. There, point the code at a details page and let the RSVP form come later with the invitation. For the reasoning behind that split, see our guide on save the dates versus wedding invitations.
If you want the broader case for using codes at all, including the response-rate data, our overview of QR code wedding invitations covers the what and the why. This article is the how.
How to Create a QR Code for Wedding RSVPs in 3 Minutes
The order matters. Making the code first and the page second is how couples end up with a beautiful printed square that points at nothing.
- Create the RSVP page. Set up your event with the date, venue, and the questions you actually need answered: attending yes or no, plus-one name, meal choice, dietary notes. If you are building the page from scratch, our walkthrough on creating a wedding RSVP website has the full setup.
- Copy the live URL. Open the page on your phone first and confirm it loads and the form submits. A page that works in a desktop preview but 404s in public is a common trap.
- Paste it into a generator. Use the free event QR code generator, which takes the URL and returns a downloadable image. Anything that asks for a credit card for a basic code is selling you a subscription you do not need.
- Download the largest file offered. PNG at maximum size, or SVG if it is available. SVG is the better answer for print because it is vector art and stays crisp at any size.
- Place it in your design. Drop it into your invitation layout in Canva, Illustrator, or whatever your stationer uses. Readers designing in Canva can follow our guide to adding an RSVP link to a Canva invitation for the layer and export settings.
That is the whole procedure. Three minutes if the page already exists.
Static Versus Dynamic: The One Decision That Prevents a Reprint
This is the distinction that matters most and gets explained badly almost everywhere.
A static code encodes the destination directly. The squares literally spell out https://example.com/rsvp. Change your mind about the destination and the printed code is dead, because the address is baked into the ink.
A dynamic code encodes a short redirect URL that you control. The printed pattern points at a stable address, and that address forwards to wherever you tell it to. Change the forward, and every already-printed invitation now goes somewhere new.
The practical rule: if your code points at a link you can re-point, a mistake is fixable after printing. If it points at raw data, it is not.
Worth knowing, because it is the thing people get wrong: a static code pointing at a URL on a platform you control is functionally dynamic. If your RSVP page lives at a fixed address and you can change what that page shows, you already have the recovery path. What you cannot recover from is a code that encodes raw text, a vCard, or a Wi-Fi credential, since there is no server in the middle to redirect.
Free dynamic-code services are where the traps live. Several popular generators create a dynamic code on a free trial, then disable the redirect after 14 days unless you subscribe. Your invitations are already in the mail at that point. If a generator asks you to sign up so it can "manage" your code, read what happens when you stop paying.
Where the Code Goes
On the invitation suite: the response card or details card, not the main invitation. The main card carries formal wording and a code sits awkwardly against it. Bottom right of the details card, below the website URL written in plain text, is the placement that tests best.
On the save the date: back of the card, or the lower third of the front if it is a single-sided magnet. Fridge magnets are the highest-value QR placement in the entire wedding stationery set, because the card stays visible for months rather than getting filed in a drawer.
On reception signage: larger, and at eye level. Welcome signs, escort card displays, and photo-sharing signs all work. Size scales with distance, covered below.
In the digital version: do not bother. If you are sending the invitation as a PDF or an image over WhatsApp, use a tappable link instead. Asking someone to scan a code displayed on the same phone they would scan it with is a small absurdity that shows up in real wedding stationery more often than you would expect.
Print Rules That Decide Whether It Scans
Five specifics, and each one is a real failure mode rather than general advice.
Size: 1 inch (2.5 cm) minimum on paper. The often-quoted floor is 0.8 inches, and that works in good light with a recent phone. One inch survives dim restaurant lighting and a four-year-old Android. For signage, use the 10:1 rule: the code should be roughly one tenth of the intended scanning distance. A sign read from 10 feet needs a 12 inch code.
Quiet zone: leave a clear margin. The QR specification calls for a blank border of at least four modules, meaning four of the small squares, on all four sides. Designers crop this constantly because the white gap looks like wasted space. It is not decorative. Scanners use it to find the code's edges, and a code butted against a floral border often fails.
Contrast: dark code on light background. Dark foreground, light background, and never the reverse. Inverted codes (light squares on dark card stock) fail on a large share of older camera apps. If your palette is navy and gold, print a small white or cream tile behind the code rather than inverting it.
Stock: avoid heavy texture and gloss. Cotton and linen textured papers scatter the edges of the small squares. High-gloss finishes throw camera glare straight back at the lens. Matte or lightly textured stock is the safe middle. Letterpress deboss on a code is a lovely idea that scans badly, since the ink spreads into the impression.
Colour: keep it near black. A code in your wedding's blush pink at 60% opacity may pass a phone test on screen and fail on paper, because printed ink density differs from a backlit display. If you want a tinted code, test the actual printed proof, not the file.
Test Before You Print, Then Test the Proof
Screen tests do not count. A code that scans from a laptop display can still fail on paper, because the printer's ink spread, paper absorbency, and finish all change how cleanly the squares resolve.
Run this sequence:
- Scan the digital file on two different phones, ideally one iPhone and one Android, and preferably one that is a few years old.
- Scan it in low light. Reception lighting is dim, and a code that needs a bright kitchen window is a code that fails at the venue.
- Ask your printer for a physical proof and scan that. This is the step that gets skipped and the step that catches problems.
- Confirm the page it opens is the RSVP form, not a redirect chain, and that the form submits successfully on mobile.
- Have one person over 60 try it without instructions. If they hesitate about where to point the phone, your wording next to the code needs work.
Native camera scanning has been built into iOS since version 11 and Android since 8, so no guest needs an app. Apple's own instructions are worth linking in your FAQ if your guest list skews older.
Always Print the URL in Plain Text
Under or beside the code, print the address as readable text. Something short enough to type: invyt.app/invite/smith2027 rather than a 60-character link with parameters.
This is not a courtesy for the technically nervous. It is insurance. A cracked phone camera, a broken lens, a guest reading a scanned photo of the invitation someone emailed them, a scratched card: all of these break the code and none of them break a typed URL. In practice a small share of RSVPs will always come through the plain link, and the cost of including it is one line of 8pt type.
Pair it with a short instruction. "Scan to RSVP by 12 April, or visit invyt.app/invite/smith2027" does more work than the code alone.
Troubleshooting
If the Code Is Already Wrong and Already Printed
Do not panic-reprint the whole run. Work through the options in this order.
If the destination is a page you control, change the page rather than the code. Redirect it, or replace its content with the correct RSVP form. The printed squares still point somewhere valid, and nobody ever knows.
If the destination is a dead third-party redirect, regenerate the code against a URL you own. That does require new printed material, but usually only the details card rather than the full suite, which is a fraction of the cost.
If the invitations are already mailed, send a short correction by email or WhatsApp with the working link, and update the page the code points at if you can. A one-line message beats a second mailing.
Then watch the responses arrive. A wedding RSVP tracker tells you within a day or two whether scans are converting into replies, which is the earliest signal that something in the chain is broken. If the first 30 invitations produce zero responses in a week, the problem is almost never that guests are slow. For the wider setup around collecting and chasing those responses, see the complete online wedding RSVP guide.
Ready to Make Yours
Build the RSVP page, copy the link, run it through the free QR code generator, print at 1 inch with a clear white border, and scan the printer's proof on two phones before approving it. That sequence removes almost every way this goes wrong.
Create your free event on Invyt and your RSVP page, guest list, and QR code all come from the same place, which means the link the code points at is one you can always change.
Frequently Asked Questions
How do I make a QR code for my wedding RSVP for free? Create your RSVP page, copy its URL, and paste it into a free generator such as Invyt's event QR code generator. Download the PNG at the largest size offered and place it in your invitation design. No account or payment is needed to download the image.
Do QR codes for weddings expire? The code itself never expires, because it is just a printed pattern encoding a web address. What can expire is the page it points to. Avoid free generators that route through their own short domain with a trial period, and use a code that points straight at your RSVP page instead.
Can I put a QR code on a save the date? Yes, and it is often better than on the invitation because it arrives six to twelve months earlier. Point it at your wedding details page rather than the RSVP form, since most couples have not finalised guest lists or meal options at save the date stage.
What resolution should a wedding QR code be for printing? Export the code as a PNG or SVG and place it so the printed result is at least 300 DPI. For a 1 inch code that means a 300 pixel image minimum. An SVG is safer because it scales to any print size without softening the edges of the squares.
Should the QR code go on the invitation or the response card? Put it on the response or details card, not the main invitation. The main invitation carries the formal wording and looks crowded with a code on it. The details card is the piece guests keep on the fridge, which is where you want the scan target to live.