Scan for all the details Dress code, directions, and the day's schedule live on our website.
Print a verb-first prompt of six words or fewer next to the code — “Scan to RSVP,” “Scan to share your photos,” “Scan for all the details” — plus one fallback line for guests who can't scan, like “Can't scan? Text us instead.” The verb tells guests exactly what happens when they do; the fallback rescues everyone else. Below are 20 copyable prompts organized by where the code will be printed — tap Personalize on any of them and the generator opens with that wording already set as your code's label.
The right length depends on how far away guests are when they read it. Arm's length earns you a second line; a sign across the room earns you five big words.
One verb line plus one context line. Guests read this at arm's length, at home, with time — a second line can say why to scan. Keep the first line under six words so it doubles as the code's printed label.
“Scan to RSVP” with the reply-by date beside it. This card has exactly one job, so the prompt names exactly one action. Add “or text your RSVP to us” underneath — guests who can't scan can still reply from the same card.
A verb line, a payoff line, and a fallback line. Three short lines is the ceiling — guests are scanning at arm's length mid-conversation. The fallback (“Can't scan? Text your photos to us”) earns its spot here more than anywhere.
The verb line alone, printed big. At viewing distance, every extra word shrinks the ones that matter. One large line — “Scan to share your photos” — beats a paragraph nobody walks close enough to read.
For the back of the invitation or a details card, pointing guests to your wedding website. Two short lines: the verb, then the reason to bother.
Scan for all the details Dress code, directions, and the day's schedule live on our website.
Everything else you need to know — scan to visit our wedding website.
Scan for the where and when Can't scan? Every detail is on our website — the address is on the details card.
Save the paper — scan instead Our website has the registry, the hotel block, and everything in between.
Tap Personalize on any prompt above and our free generator opens with that line printed under your code and the right destination preselected. Generated in your browser — the link you enter never leaves this page — and static, so it never expires.
The card has one job, so the prompt names one action. Put the reply-by date right beside it — the scan and the deadline should be read in the same glance.
Scan to RSVP Two taps, thirty seconds, done.
Scan to RSVP No stamp, no envelope — your reply reaches us instantly.
Will you be there? Scan to let us know — it takes less than a minute.
Scan to reply Can't scan? Text us your RSVP instead.
For the photo-upload code at each table. Verb line, payoff line, fallback line — then stop. Guests are scanning mid-conversation, not reading.
Scan to share your photos Everything you snap tonight lands in our album.
Caught a good one? Scan to send it straight to our wedding album.
Tonight's album is a group project Scan to add your photos — no app, no sign-up.
Scan to share your photos Can't scan? Text them to us instead — every picture counts.
Signs are read from feet away, so the verb line does the work in big type. The second line here is optional — if the sign hangs where guests walk past, cut it.
Scan to share your photos Every picture goes straight to our album.
Welcome! Before you find your seat — scan for tonight's schedule.
One scan, every detail The schedule, the menu, and the after-party address.
Scan to share your photos Or text them to us — either way, we want them all.
One strip line along the program footer. Programs get held all day, so this is the code guests come back to — point it at the schedule or the album.
Scan for today's schedule Times and locations, kept up to date as the day unfolds.
The ceremony is unplugged — afterward, scan to share every photo you take.
Scan for the reception details Directions, seating, and tonight's timeline.
Keep this program as a keepsake — the living version is one scan away.
The same code needs different wording depending on how far away guests read it. One rule holds everywhere: the prompt sits directly above or below the code, never across a fold or on a different panel.
The code is only about an inch wide here, so the prompt is effectively the code's caption — “Scan for all the details” directly beneath it. A second, smaller line can carry the why, because guests read invitations at arm's length with time to spare.
“Scan to RSVP” with the reply-by date in the same glance. Anything else on the card competes with the one action you need guests to take.
Verb, payoff, fallback — that's the whole card. Guests scan these between courses with a drink in the other hand; a fourth line just doesn't get read.
Guests decide whether to walk over based on the headline alone, so print the verb line in your largest type — it should be legible from as far away as the sign is meant to work. Supporting copy, if any, belongs in smaller type below for the guests who come close.
One line riding the bottom edge — “Scan for today's schedule” — next to a code about an inch wide. The program's job is the ceremony; the footer just needs to earn a glance.
If none of the twenty fit your voice, build your own from the same parts. Every prompt in this library is these four moves in order — use as many as the surface allows.
“Scan” is the whole instruction — start there. “Scan to RSVP” outperforms “RSVP information available via QR code” because guests act on commands, not descriptions.
What happens after the tap: share your photos, RSVP, see the schedule. This is the part “Scan me” is missing — a code with no named destination is a mystery, and guests skip mysteries.
One short reassurance if the surface has room: “no app, no sign-up,” “it takes thirty seconds,” “no stamp needed.” Answer the objection before it forms.
“Can't scan? Text us instead.” One line rescues grandparents, dead batteries, and cracked cameras — texting an RSVP or a photo is something every guest already knows how to do.
The code can be printed perfectly and still get ignored — every one of these is a wording failure, not a printing one.
A bare code with a cute arrow tells guests nothing about what they're opening, and plenty won't risk it. Name the destination in the prompt — “Scan to share your photos” gets scans that “Scan me” never will.
Some guests can't or won't scan, and your wording is where you catch them. One printed line — “Can't scan? Text your RSVP (or your photos) to us instead” — keeps every guest in, because Text My Wedding collects texted replies and MMS photos right alongside the scanned ones.
A prompt on the front of the card with the code on the back — or across a fold, or in a facing corner — breaks the pair. Guests see a naked code and a stray sentence and connect neither. Keep the wording directly above or below the code, inside the same visual block.
A printed URL is a good backup — but only if a guest can actually type it. “VISIT WWW.OURWEDDING-SITE.COM/RSVP” in foil script is unreadable and untypeable. If you print the address, make it short, lowercase, and in plain type.
Explaining what a QR code is, or how to open the camera app, buries the instruction that matters. Guests have been scanning restaurant menus for years — trust the verb line and let the code do the rest.
Pick a prompt above or type your own label, choose where the code will be printed, and download it print-ready. Generated in your browser — the link never leaves this page — and static, so it never expires.
Paste your wedding website's home page — one code covers schedule, travel, and registry.
Private by design: the link you enter never leaves your browser — the code is generated on this page. It's a static code, so it never expires and there's nothing to renew.
A verb-first prompt that names the destination: “Scan for all the details” pointing at your wedding website, or “Scan to RSVP” on the reply card. Keep it to six words or fewer, place it directly above or below the code, and add one smaller context line if the card has room — invitations are read at arm's length, so guests will see both.
One printed line under the code offering the same action by text: “Can't scan? Text your RSVP to us instead” on reply cards, or “Can't scan? Text your photos to us” at the reception. Sending a text or a picture message is something every guest already knows how to do, and Text My Wedding collects those texted RSVPs and MMS photos in the same place as the scanned ones — so nobody's reply or picture depends on the scan.
On paper guests keep — invitations, details cards, programs — yes, it's a sensible second fallback. But it only works if a guest can retype it: short, lowercase, plain type, no “https://”. On signs and table cards, skip the URL and use the text-us fallback line instead; nobody transcribes a web address across a reception table.
Only when something else on the surface already names the destination — a sign headlined “Share your photos” can get away with “Scan me” underneath, because the headline is doing the prompt's job. On its own, a bare “Scan me” is the single most common reason wedding codes go unscanned: guests won't open a link they can't predict.
Either works — below is the most common, reading like a caption — as long as the prompt and the code sit in the same visual block. What fails is separation: wording across a fold, on the reverse side, or floating in another corner. If a guest can see the code without seeing the prompt, they effectively got a code with no wording at all.
Yes — the prompt is how guests tell the codes apart, since every QR code looks identical. “Scan to RSVP” and “Scan to share your photos” each name their own action, and each code should have exactly one job. If the same card carries both, give each code its own labeled prompt rather than one vague line covering two destinations.
Shorter as the reading distance grows. An invitation corner supports a verb line plus one context line; a table card holds three short lines; a sign guests read from feet away gets the verb line alone, printed big. If you're unsure, cut to the verb and the payoff — “Scan to share your photos” — and let the code speak for itself.
Guests scan to share photos and RSVP — and anyone who can't scan just texts instead. Text My Wedding collects both automatically, and your static code never expires.