An RSVP QR code points at your reply form, so a printed invitation collects answers without anyone typing a URL from a card. The payload is just the link, which is why it works with every scanner ever made.
Create unlimited QR codes — right from your phone, anytime, anywhere. Free to download.
Experience this feature seamlessly in our mobile app. Download it today to enjoy the full mobile experience
Download Free AppThe payload is a plain HTTPS address. There is no RSVP format, no reply encoded in the code and nothing that identifies the guest — the code is the same on every invitation unless you deliberately make it different.
That last point decides how you use it. One code for everyone means the form has to ask who is replying, and two people can reply as the same guest. A code per household — a different link, or the same link with a guest token in it — lets the form know who scanned it, at the cost of generating and printing one code per invitation.
For a wedding of 80 households that trade is real: the per-guest version removes the "which Sarah is this" problem entirely, and it is the only version that can tell you who has not replied yet.
Because it is a bare URL, the Website URL generator on this site produces an identical code, free and in the browser. The app’s version keeps it alongside your other event codes; it is not a different kind of code.
The card carries the code, the form collects names, meal choices and plus-ones, and nobody has to read a URL out over the phone.
A poster or a flyer that turns into a registration in one scan, where the alternative is a URL people mean to type later and never do.
A code on a noticeboard pointing at the sign-up sheet, which is a page you can close, reopen or cap without touching the printed notice.
No signal, no reply. The code carries a link, so the phone has to reach the page. That is usually fine for an invitation read at home and a real problem for a code on a wall in a venue basement.
The code does not know who scanned it. Unless you print a different link per guest, the form is the only thing that can identify anyone, and it can only identify people who tell it the truth.
The link has to outlive the print run. A form provider that closes an account, a free tier that expires, a link with a token in it — any of these turns a printed invitation into a dead end months after you sent it. Point the code at a domain you control.
The address is readable by anyone. Decoding a printed code shows the URL in plain text, so a guest-specific link is only as private as the page behind it. If the link alone reveals the guest list, it is a guest list printed on the invitation.
Nothing expires. The code keeps working after the event. If late replies are a problem, close the form — the code cannot close itself.