How wedding photographers collect guest photos in one link
WhatsApp galleries, three-day Dropbox links, and lost AirDrops are not a system. Here is the setup wedding photographers use to collect every guest photo into one branded inbox.
June 16, 2026 · 9 min read · Dropspot
By the Monday after a wedding, the bride and groom have been sent a
photograph by their aunt over WhatsApp, two videos by a groomsman
on AirDrop, three half-screen iPhone shots in an iMessage thread,
a WeTransfer link with seven days left from a guest who shot on a
real camera, and a Google Drive folder shared by a guest who
"thought it would be easier."
You are the photographer. None of this is your fault and all of it
is your problem.
This post is about the setup that fixes it — a single link in the
welcome email, the table cards, and the wedding website, that lands
every guest photo into one inbox with the right metadata attached.
Every wedding photographer has lived this. The taxonomy of what
arrives over the week after the wedding looks roughly like:
Guest phones. HEIC photos at full resolution, often a few
hundred of them, mostly through WhatsApp (which silently
downsizes them) or AirDrop (which sometimes drops a few).
The second shooter. Several gigabytes of RAW files from a
second camera body, plus probably some video — needs to come to
you fast, in full quality, ideally before they leave for their
next gig.
Vendors. Florists, DJs, and venue staff sometimes shoot a
few frames they think you'd want. They're not photographers; they
send through whatever they have open.
The couple themselves. Whatever they captured that day plus
a few photos from family members they've forwarded.
The aunt with the real camera. One person, every wedding,
who has a DSLR and "wants to help." Usually a Canon. Usually a
CR2 file. Usually doesn't know what to do with it.
The friction in collecting this is not the file size — it's that
every guest uses a different channel and every channel loses
something. Resolution, metadata, audio, frame rate, or the file
entirely.
Two weeks before the wedding, the couple sends the welcome email to
all confirmed guests. One sentence in that email: "Photos and
videos from the day go here:dropspot.me/[couplename]. Upload
anything you'd like us to see."
This is the highest-yield placement because the email is open at
the moment people are thinking about the wedding logistically, and
they're already scrolling for the dress code or the venue address.
Try the shape
One link to receive anything from anyone.
Pick a handle. Live in 60 seconds. Free until you're getting real volume.
Small card on each table with the URL + a QR code. Most guests
won't scan it immediately, but they'll see it, they'll know what
it's for, and a meaningful fraction will scan it before they leave
because they took a photo they want to share.
QR design tip: the URL should be readable underneath the QR.
Roughly half of guests will type the URL instead of scanning,
and a typo-able URL costs you uploads.
The morning after, the couple sends a thank-you. One line in that
email reminding everyone the upload link is still open. This is
the highest volume placement — the welcome email seeds the link,
the table card surfaces it during, and the thank-you email is when
most uploads actually happen.
Friction floor matters here more than anywhere else. A wedding
guest will not install an app. They will not make an account.
They might not even put down their champagne.
The flow on the guest side:
They tap the link (or scan the QR, or type the URL).
The page loads — branded with the couple's accent color, their
names at the top, the date.
They see one upload field. "Add your photos and videos here."
Tap.
They select from their camera roll (multi-select supported on
iOS + Android). They can also drag-and-drop on desktop.
They optionally type their name. The form encourages it but
doesn't strictly require it.
They tap upload. Done.
The whole thing takes under 30 seconds. The friction floor matches
WhatsApp — which is the bar you have to clear.
Photographers care about this because every other tool degrades
quality silently.
HEIC photos. Land at full resolution. Modern iPhones shoot HEIC
by default at 12 megapixels (or 48 on the Pro); WhatsApp downscales
to about 2 megapixels, which is why guest photos sent via WhatsApp
look so much worse than the same photos AirDropped to the couple.
A direct upload preserves the original file. You get the HEIC at
its native resolution, with all the EXIF intact — including the
phone model, GPS coordinates if the guest has it enabled, and the
exact timestamp. That metadata becomes useful when you're stitching
together a timeline of the day from multiple sources.
4K video from iPhones. Lands at 100–200 MB per minute,
unmodified. WhatsApp caps at 16 MB and aggressively transcodes; a
direct upload skips that entirely.
RAW from a guest's camera. CR2, NEF, ARW, DNG — all upload
fine. The magic-byte sniff (Dropspot validates every file at the
byte level on arrival) accepts them; the actual format is whatever
the camera wrote. Useful when the second shooter or that one aunt
with the DSLR uploads.
Original timestamps preserved. Files keep their creation time
from the camera, not the upload time. This matters for stitching
the timeline.
The setup that scales: turn on the optional name field, and
optionally add a single dropdown — "Which table were you at?" or
"Was this taken during ceremony, dinner, or dancing?"
Three benefits:
Triage speed. You see at a glance who sent what, when in the
day they took it, where in the room they sat. The aunt's 50 RAW
files are tagged "Mary Chen" and "Table 3" instead of just being
fifty IMG_xxxx files in the inbox.
Couple's experience later. When you deliver the final
collection to the couple, they can search "photos from Table 3"
or "videos from dancing." Family albums get to be family
conversations, not just a file dump.
Privacy on request. If a guest later says "please don't use
the photos I uploaded" — you can find their uploads instantly
and delete them.
The dropdown is optional. Half of guests won't fill it in. The
half who do still make the inbox dramatically more useful than no
tags at all.
Auto-delete after 60 days (privacy + storage hygiene)#
A practical detail that gives guests confidence and saves you from
storing thousands of gigabytes per wedding indefinitely.
Set retention to 60 days. Guests see a countdown — "this file will
auto-delete on August 15" — when they upload. Two weeks after the
wedding, you've triaged everything you wanted to keep. The rest
ages out on its own.
You can extend retention per-file (star a photo to keep it forever)
or in bulk (extend the whole event to a year if you're slow to
process). Defaults that respect privacy are the right default —
explicit overrides for the exceptions.
The wedding-day link is for guests. The second shooter needs a
different surface.
Create a second handle — dropspot.me/[your-studio]-shooters — or
add a separate field on your main link that's marked "for second
shooters only." The upload limit goes up (Pro tier allows 10 GB
sessions vs the default 1 GB for guest uploads), and you can
require a password or a magic-link gate so it isn't publicly
accessible.
The shape stays the same: one URL, drag and drop, no account.
What changes is the file-size ceiling and the access gate.
A short list of cases where this setup isn't the right fit:
Tiny wedding, technical couple. Twelve guests, all of whom
are comfortable on Dropbox. A shared folder is fine. The link
shape pays off at scale.
Couples who specifically want a curated experience. Some
couples want only the photographer's images to exist for the
wedding — no guest contributions on purpose. Don't impose the
link on them.
Single-photographer weddings with no second-shooter handoff.
If you're the only camera and the couple isn't asking for guest
photos, your existing workflow probably already works fine.
For everything else — the standard "we want everyone's photos" job
— the link shape outperforms the channel pile.
Do guests need a Dropspot account?
No. The whole point is the no-account upload. They click the link,
drop photos, optionally type their name, done.
Do they have to enable any permissions?
On iOS the first upload prompts for photo library access — they tap
"Allow" once and don't see it again. On Android the flow is the
same. On desktop it's drag-and-drop with no permission prompt.
What about guests who are at the wedding without a phone (kids,
older relatives)?
The link doesn't care when you upload. Older relatives often upload
the next day from a laptop after they've gone through their
camera. The 60-day window covers it.
Can I customize the page with the couple's names and colors?
Yes. Custom accent color, custom title, custom background. The page
becomes part of the couple's wedding identity — same way the
wedding website does.
What about copyright?
Guest uploads are governed by whatever you put in the upload
description. The standard "by uploading you grant the couple
permission to use these photos" line covers most use. If you have
specific legal requirements, the description field is where they
live.
How does this compare to a Google Photos shared album?
Google Photos works as a single shared destination but assumes
guests have or will create Google accounts. The album also doesn't
let you tag, retain, or auto-forward. For just a shared gallery
it's fine; for the photographer's intake workflow, the Dropspot
shape carries more.
The wedding-day file collection problem is solved by anchoring
everyone to one link. Set up the couple's page two
weeks before the wedding, put the URL on the welcome email, the
table cards, and the thank-you note — and the post-wedding photo
chaos becomes a triage workflow instead of an archeological dig.