Your parents are printing 400 cards for the extended family. You're also building a website, because a multi-event wedding has several functions and every guest needs to know which ones they're invited to. These aren't competing plans. They're the same plan, if the card has a QR code that points somewhere useful.
Most don't. QR codes are showing up on more Indian wedding cards every year, but the code itself is usually an afterthought, added because it's expected now, not because anyone thought through what a guest sees after they scan it. A QR code that opens a Google Drive folder or a single blurry photo of the venue address isn't an upgrade on the card. It's a broken promise printed in ink.
This isn't a digital-vs-physical debate. The card stays. For most Indian families, elders still expect one delivered by hand, and that's not changing. The question is narrower: what should the seven square centimetres of that QR code do.
What not to link
A Google Drive folder. Permissions expire, links rot, and half your guests will see "request access" instead of the venue map.
A WhatsApp group invite. You're not inviting 400 people into a group chat with each other. You're inviting them to a wedding.
A single image. A photo of the invite text, a screenshot of the schedule — it answers one question and closes the door on every other one a guest might have.
Each of these treats the QR code as a shortcut for something you were going to send anyway. It's worth more than that.
What to link
A wedding website, not a document, a page that holds everything a card can't:
- The full schedule, per event. Mehendi Thursday, Sangeet Friday, Pheras Saturday morning, Reception Saturday evening — a card can print the dates, but not comfortably explain what each one is or who's invited to which.
- RSVP guests can revisit and update, not submit once and lose access. Plans change between the invite going out and the wedding.
- Venue details and maps for however many locations the events span.
- Dress code, per event, since Sangeet and Pheras rarely call for the same outfit.
- Travel and hotel information for anyone flying or driving in.
- A photo gallery that fills in after the fact, using the same link you already handed out.
The advantage that matters most: it updates. If the reception venue changes eleven days out, everyone who has the card already has the new address the moment you update the page. Nobody reprints anything.
It's worth being specific about why "one link" beats the alternative most families reach for instead, which is a WhatsApp forward with five separate messages: a text with the date, a photo of the venue, a voice note about timing, a second voice note correcting the first one. Each of those lives in a different place in the chat, in a different format, and none of them update if something changes. A guest scrolling back through three weeks of family group messages to find "what time was the sangeet again" is the exact problem a single page solves — everything sits behind one scan, in one place, current as of today rather than current as of whenever it was sent.
What each event needs on the page
This is where a generic "add your wedding details" template falls short of what a multi-event Indian wedding requires. Five events isn't five lines under one heading — each one has its own timing, venue, and dress code, and guests invited to some events aren't invited to others. And for Hindu ceremonies, the wedding's own start time usually isn't the couple's to move: it's set by the muhurat, the astrologically auspicious window a priest calculates, which is exactly why the page needs to state it precisely rather than approximately:
| Event | What guests need to know |
|---|---|
| Mehendi | Date, start time, whether it's daytime or evening, casual dress code |
| Sangeet | Venue (often different from the wedding venue), dress code, whether it's a performance night guests should prepare for |
| Haldi | Time (usually morning), a note that guests should wear old or yellow clothing — this one genuinely needs to be said |
| Pheras / Nikah | Exact ceremony start time, set by the muhurat for a Hindu wedding, venue, and whether it's outdoors (weather-appropriate dress) |
| Reception | Date if it differs from the wedding day, formal dress code, timing |
A card can print a date range. It can't comfortably hold five rows of this without becoming unreadable, and it's exactly what a guest lands on after they scan.
Put the link in plain text under the QR code too, not just the code itself. Some guests won't scan — a QR code is genuinely tiny on a wedding card, and older phones or shaky hands can miss the framing. A visible URL is the fallback that costs you one line of print.
How to get one
If you're building your wedding website on The Curated Knot, this part is already done for you. Once your website or RSVP form is published, a QR code appears automatically on your dashboard — in the Share card, and again in the RSVP hub's Share tab — captioned "Scan to open." Download it and you get a high-resolution PNG, generated specifically to stay crisp when it's printed small on a card, not just readable on a screen.
There's no separate QR generator to find, no account a guest needs to create, and nothing to regenerate later. The same download stays valid for as long as your page does.
A few things worth getting right when you hand it to your printer:
- Keep it modest in size. A QR code doesn't need to dominate the card — a corner, roughly 2–3 cm square, scans fine from arm's length.
- Don't print it on a busy background. High-contrast printing (dark code on light card stock) scans faster and more reliably than a code sitting over a pattern or photo.
- Test it before the print run. Scan the PNG on two or three different phones before 400 copies go to the printer, not after.
What you get back, not just what guests see
The point of the link isn't only that guests reach the right page. It's that the RSVPs they submit through it come back to you in one place instead of scattered across calls, texts, and whoever happened to answer the phone. A guest who scans the code, opens the RSVP form, and confirms for two of the five events shows up on your side as exactly that — which events, how many people, any dietary notes — rather than a verbal "yes we're coming" that someone has to remember to write down and pass along to catering.
For a 400-card wedding, that difference is the gap between a guest count you're confident in a week before the event and one you're still guessing at the morning of.
Building the site the QR code points to is the harder half of this — not the code itself. The Curated Knot generates the download the moment your website or RSVP form goes live, sized for print from the start. Try it free →
Beyond the printed card
The same QR download works anywhere a card would have gone but didn't:
- WhatsApp status, for the week leading up to the wedding, as a visual reminder alongside the text invite.
- The family WhatsApp group's pinned message — easier to find again in a group that will otherwise scroll past it within a day.
- Email signatures, if either family is sending out-of-town guests logistics by email during wedding season.
Ready to create yours?
Publish your wedding website and the QR code is ready to download the same day — no separate tool, no extra step.
Frequently Asked Questions
Do I still need a physical wedding card if I have a QR code?
For most Indian families, yes. Elders in particular still expect a card delivered in person or by post, and that custom isn't going away. A QR code doesn't replace it. What the QR code replaces is the second card you'd otherwise need to hand-write with directions, dress code, and a phone number for RSVPs.
What happens if a guest can't scan the QR code?
Print the link in plain text underneath it. Anyone who can't or won't scan can type the address instead — it costs one extra line on the card and covers everyone who'd otherwise be stuck.
Can I update the details after the cards are already printed?
Yes, and that's the point of using a website instead of a static image. The QR code and the printed link both point at your live website, so a venue change, a new hotel block, or an updated dress code shows up for every guest instantly, without a reprint.
Does one QR code cover all the wedding events, or do I need one per function?
One link. A wedding website built for multiple events — Mehendi, Sangeet, Pheras, Reception — holds the full schedule and per-event RSVP behind a single URL, so one QR code on the card is enough.
Is there a cost to generate the QR code?
Not on The Curated Knot. It's generated automatically once your website or RSVP form is live, at no separate cost.
Should the QR code go on the invitation or a separate insert card?
Either works. A corner of the main card is more likely to be seen by every recipient; a separate insert gives you more room for the plain-text link and a short line of instructions, useful if a large share of your guest list skews older.
Related read
Digital vs Physical Wedding Invitations in India (2026)
The cost, etiquette, and community expectations behind choosing — or combining — digital and printed invites.
Related read
8 Elements Every Indian Wedding Website Must Have
What belongs on the page your QR code opens: schedule, RSVP, travel, and more.