An RSVP page already exists somewhere, on Zola, The Knot, a plain Google Form or a couple's own wedding website, and entering its address from a printed card is the exact friction a QR code generator removes. Save-the-dates, formal invitations and reception signage all work the same way, since the destination is the same page regardless of which piece it is printed on.
The code carries nothing but that one address: no guest names, meal choices or replies pass through it or through MakeQR, since those stay wherever the form or wedding site already stores them. Built in the browser, a static code costs nothing and never expires, which covers most weddings without further setup.
Turning your RSVP link into a code
Get the exact RSVP link, not the invitation link
On Zola, open your wedding website in the site editor, go to the RSVP page specifically, and copy its address — usually yoursite.zola.com/rsvp or a custom domain with /rsvp at the end. On The Knot or a plain Google Form, copy the share link for that page directly, not the site's home page.
Test it as a guest would
Open the link in a private browser window and, if the form allows it, submit a dummy response. Confirm it asks for what you actually need — meal choice, plus-one, song request — before it goes on a hundred printed cards.
Paste it into the web address field
Choose the URL type in MakeQR, paste the link, and check that the on-screen preview scans to the same page with your own phone before downloading anything.
Pick static for a finished website, dynamic for one still in progress
If the RSVP page address is final, a static code is free and never expires. If you're mailing save-the-dates before the wedding website is finished, a dynamic code lets you fix the destination later without reprinting.
Which RSVP link actually belongs in the code
Wedding website builders like Zola and The Knot generate the RSVP page automatically once a guest list is added, and its address sits under the site's own domain — a free subdomain such as zola.com/wedding/janeandjohn, or a custom domain if one was bought separately. A Google Form works the same way in practice: build it, turn on a name or email field so replies can be matched to the guest list, then copy that form's own share link. Either way, the code only needs that one page's address, never the home page of the wedding website.
One invitation, more than one person to RSVP for
A household invitation or a plus-one still lands on a single shared RSVP page: the code doesn't know how many people are replying, so the form itself has to ask, usually through a name-matching field against the guest list or a count of attendees. If a couple's platform separates the bride's side and groom's side into different forms, decide which one link the printed piece should carry before the code goes out, since a single QR code can only point at one page at a time.
A code does not replace the RSVP deadline
A phone loading the form isn't the same as a completed response, and MakeQR has no way to follow up with someone who scanned but never submitted. Whatever reminder system Zola, The Knot or a spreadsheet already provides still does that job — the code only removes the retyping step between the card in someone's hand and the form asking for their answer.
What the code actually holds
Just the web address of the RSVP page — the same link that would otherwise be texted to a friend. No guest names, meal choices or responses pass through the code itself; those stay wherever the form or wedding site stores them.
https://www.zola.com/wedding/janeandjohn/rsvpPrinting it on invitations and save-the-dates
On an insert card or the corner of the invitation itself, 20 mm is the smallest size that still scans reliably from arm's length. A table sign at the reception, read from a step or two away, works better at 40–50 mm. Leave a plain border around the code — a decorative border, ribbon or wax seal placed too close to the edge can block the finder squares a phone uses to lock onto the pattern.
Print it at least 20 mm (2.0 cm) wide
Mistakes that send guests to the wrong page
Linking to the wedding website's home page
A guest lands on photos and a story instead of the RSVP form, then has to hunt for the right tab on a small phone screen. Copy the RSVP page's own address, not the site's front door.
Printing a Zola link before buying a custom domain
Zola lets couples add a custom domain after the site is already live, which changes the address guests land on. If that's likely, use a dynamic code so the printed invitation doesn't need reprinting when the domain changes.
Metallic or dark card stock with a matching-tone code
Elegant invitations often use foil or deep colors, and a code printed in a similar tone to the paper fails a scan even though it looks fine to the eye. MakeQR warns about low contrast before download — keep the code a dark, flat color on a light background.
Static or dynamic for an RSVP code
If the RSVP page's address is already final, static is the right call — it's free, needs no account and never expires. Switch to dynamic only if invitations are going out before the wedding website or custom domain is locked in, so the destination can be fixed once without a reprint. A dynamic code also shows a scan count, a rough sense of how many guests used it instead of typing the address by hand.
How dynamic QR codes workA few weddings this suits
- A save-the-date magnet with a code linking to the RSVP section, added once the wedding website goes live.
- A formal invitation's insert card, printed next to the RSVP-by date.
- A welcome sign at the reception venue, linking guests to a same-day details page instead of a paper card.
- A baby shower or graduation invitation using the same trick for a Google Form headcount.