Indian Wedding Photo Sharing: A Guide for Sangeet, Mehndi & Reception

Why Indian weddings break normal photo sharing

A western wedding is largely one day, one venue, one guest list. A North Indian wedding is a series of functions over three to five days — mehndi, haldi, sangeet, pheras, reception — and each one behaves like a separate event with its own mood, its own photo volume and often its own subset of guests.

Layer on the numbers and the standard playbook stops working:

• Hundreds of guests, not dozens. A single function can run 300–600 people. A WhatsApp group that size doesn't work as a photo channel — it works as chaos.
• Thousands of photos, across days. Three functions can generate 5,000–15,000 frames before culling, or 80–200 GB of edited work.
• Different guests at different events. The bride's office colleagues come to the reception. The groom's cousins are at the sangeet. Nobody attends everything except the immediate family.
• A wide age range. The grandmother hosting the haldi and the friend who flew in for the weekend need the same experience to work on the same phone.
• Out-of-town guests going home. Half your guest list is back in another city — or another country — by the day after the reception.

Any method that depends on a single group, a single link, or a single day will lose most of those people. That's the real problem to solve.

Structure it per function, not per wedding

The single most useful decision you can make is to stop thinking of the wedding as one album. Treat each function as its own event with its own gallery, its own QR code and its own set of guests.

This solves a problem couples hit constantly: someone who attended only the reception doesn't want to scroll past 4,000 sangeet photos to find their own. Separate albums mean separate searches, and each guest only ever looks through the function they actually attended.

Volumes are typical edited-photo counts for a 250–600 guest wedding, based on common Indian wedding delivery ranges. Your actual counts will vary with coverage hours and the number of photographers.

QR placement, function by function

Timing decides whether guests actually scan. Every method that asks guests to do something after the event fails, because motivation fades within days. The QR has to be in front of them while they're still sitting down with their phone out.

Mehndi and haldi. These are long, seated functions — often hours of mehndi application. That's ideal: guests are stationary, phones in hand, with nothing else demanding attention. A small card at each seating cluster works better than a large banner.

Sangeet. This is your highest-yield function. Attendance is big, people are dressed up, and everyone wants photos of themselves. Put a card at every table and you'll see the scan rate spike.

Pheras. Guests are seated and attentive, which means phones are mostly away. A sign at the entrance as they arrive, plus a mention by the anchor, is more effective than table cards here.

Reception. This is where out-of-town guests and colleagues appear for the first time. A welcome board at the entrance with the QR is essential — many guests will only attend this one function, and if they miss the code they have no way to find their photos later.

How the delivery methods handle Indian weddings

Let's be specific about where each approach breaks at Indian scale.

WhatsApp groups

The default, and the one that fails most predictably. A 500-person group is unusable as a photo archive — images are compressed heavily, the thread moves fast, and anything posted on day one is unreachable by day three. Photos also stop arriving after about 48 hours, once the conversation dies. You'll get contributions from a handful of enthusiastic people and nothing from everyone else.

Shared drives

Better quality, worse reach. A Google Drive folder buried in a group chat gets opened by maybe a fifth of guests. iCloud links don't open cleanly for Android guests, and Google Drive demands a sign-in that many older relatives won't complete — precisely the guests who most need help.

Photographer's gallery link

Common, and better than the above, but there's still the findability problem. Guests land in one enormous album and have to scroll through thousands of photos hoping to spot themselves. At 300 guests and 5,000 photos, that isn't a gallery — it's a search task nobody finishes.

Web-animated invites and RSVP platforms

Useful for managing the guest list and invitations, but they don't solve photo delivery. Some platforms bundle both, which is worth knowing if you're already paying for invites.

Face-recognition selfie search

The only method that removes the searching entirely. A guest scans the QR, registers once, uploads a selfie, and sees only the photos they appear in — matched automatically across every photo in that function's gallery.

At Indian wedding scale this is the difference between a gallery guests use and one they abandon. The bride's mother finds the 40 photos she's in across a 2,000-photo sangeet without touching a search box.

The guest-on-a-different-phone problem

This one catches people out, and it's specific to Indian weddings.

Guests often attend different functions on different phones — a work phone for the reception, a personal phone at the sangeet. Or a couple shares one phone across the weekend. Or a guest registers on the bride's cousin's phone at the mehndi and then can't find their photos when they get home.

Face recognition handles this far better than any link-based method, because the identity anchor is the guest's face, not their device or their account. They can register on any phone, at any function, and the same face matches the same photos. With link-based sharing, a lost link on one phone means a guest who simply never gets their photos.

Two practical notes for photographers: tell guests to register with a phone number or email they'll actually check after the wedding, and make sure the gallery stays live long enough for people to come back to it. A gallery that expires in 30 days will generate complaints six months later when relatives finally get round to downloading.

What this costs in rupees

Pricing matters more at Indian wedding volume than most photographers expect, because you're storing real gigabytes. A three-function wedding runs 80–200 GB once edited, and you'd rather not delete last season's galleries to make room.

Snaptide prices purely on storage, in rupees, with the same feature set on every tier:

• ₹833.25/month — 100 GB, billed yearly. Covers roughly one large wedding with room to spare.
• ₹1,166.58/month — 500 GB, billed yearly. The realistic starting point if you shoot regularly.
• ₹1,666.58/month — 1 TB, billed yearly. For a full season with archives retained.
• Free — 1 GB and one album with the complete feature set, enough to test the guest flow on a real event.

Cold storage for archiving finished weddings is bundled equal to your hot allowance, so you don't have to choose between keeping old galleries and having space for new ones. WhatsApp guest notification is included and metered at ₹0.85 per message — email notifications are free. If you sell downloads rather than gifting them, Snaptide pays the photographer 75%.

Frequently asked questions

Sources

Guest photo collection methods and completion rates — wedding.studio/compare-wedding-photo-sharing · guest photo sharing for weddings — guestpix.com/weddings · HEIC upload compatibility — phototools.org/blog/why-heic-not-compatible-web · Snaptide guest flow, per-album structure and plan pricing — snaptide.ai/how-it-works.php and snaptide.ai/pricing.php · All sources accessed September 2026.