How to collect photos from your wedding guests

Every couple arrives at the same problem about three weeks after the wedding. The photographer's gallery is beautiful and it is not the whole day. The photos you actually want — your uncle mid-speech, the kids under the table, the four people still dancing at 1am — are sitting on a hundred phones, and there is no polite way to ask a hundred people twice.

So the question is not really "how do I collect guest photos". It is "what can I ask a hundred people to do, once, while they are drunk and holding a drink, that will still work". That narrows the field fast.

The seven methods, side by side

Here is the honest version. Nothing on this list is useless — but every one of them charges you something, and the price is not always money.

Group chat: free, instant, and quietly lossy

The wedding WhatsApp group already exists, so this is the path of least resistance, and plenty of couples do fine with it. The catch is invisible: WhatsApp re-encodes photos hard before sending them. What arrives in the thread is not the photo your friend took. It is a smaller, softer copy of it — fine on a phone screen, disappointing at any print size. Guests *can* send originals by attaching them as a document instead, but almost nobody does, and asking them to is a second instruction on top of the first.

iMessage is better between iPhones, but a single Android guest pulls the thread down to RCS or MMS, and MMS compression is brutal. Either way, you end up scrolling a chat six months later, saving photos one at a time between messages about parking.

Shared albums: good quality, wrong door

A Google Photos or iCloud shared album is a genuine step up in organisation — everything lands in one place, in date order. The problem is the door. To *add* photos to a Google Photos album, a guest needs a Google account and to be signed in. To contribute to an iCloud Shared Album, they need an Apple ID. Your guest list does not sort itself neatly into one ecosystem, and the ones who fall outside it will not create an account at a wedding to fix that.

There is a quality footnote too: iCloud Shared Albums resize photos on the way in, capping the long edge at around 2048 pixels. That is a perfectly nice screen image and it is not the file you would want to print at A3.

Cloud folder link: the originals survive, the guests do not

A Dropbox file request or a shared Drive folder gives you the one thing the previous two methods do not: the original files, byte for byte. If print quality is your priority and you only need photos from a handful of people — the bridal party, your two most reliable cousins — this is genuinely the right tool.

At scale it collapses, because the interaction is a file picker. It asks a guest in a suit, holding a drink, to think about *files*. Drop-off between "scans the link" and "actually uploads" is where this method loses, and Google's own upload flows make it worse by requiring a sign-in for most folder and form uploads.

Wedding hashtags: fun, not a collection method

A hashtag is a lovely bit of theatre and a poor archive. You are relying on guests having a public account on the same platform, you get screen-resolution copies rather than files, and you have to save each one by hand. Private accounts — an increasing share of everyone's guest list — never show up in the tag at all.

Have the hashtag. Print it on something. Just do not let it be the plan. (If you want one, our wedding hashtag generator is free and needs no account.)

Disposable cameras: charming, expensive, unreliable

Disposable cameras deserve more respect than the internet gives them. Nothing else produces that specific 1997 flash-lit look, and unlike every digital method, the barrier to using one is zero — you pick it up and press the button.

But be clear about what you are buying. A camera holds around 27 exposures, and a table of six will burn through them in the first hour, mostly on each other. Wedding receptions are dark, which means every usable frame depends on a guest getting the flash distance right by accident. Then there is developing: real money per camera, and a wait measured in weeks. Most couples who do this describe the same outcome — a handful of genuinely wonderful photos, and a lot of blurry orange ones.

A QR code to an upload page

This is the method most weddings settle on now, and the reason is not technology — it is the number of instructions. A card on the table says point your camera here. The guest's phone opens a page. They type their name and start sharing. There is no app to install, no account to make, no password to invent, no ecosystem to belong to. That matters most for exactly the guests who take the photos you cannot get any other way: your grandmother, your dad, the friend who does not use social media.

The trade-offs are real and worth stating. You have to print and place the codes, which is one more thing to do the week before. It costs money — these tools generally charge per event rather than per month. And the upload has to survive venue Wi-Fi, so it is worth checking that whatever you use retries in the background rather than failing silently when someone walks into a stone-walled barn.

What you get in exchange is the full set: originals rather than compressed copies, everything in one gallery instead of five threads, and photos arriving *during* the day rather than after it.

The four things that actually decide this

Strip away the brand names and every method above is trading off the same four variables. If you are choosing between two options, compare these rather than feature lists.

How many instructions the ask contains

Every step between "I want to help" and "photo sent" loses people. "Install this, make an account, find the album" is three chances to give up while the starter is arriving. One scan and a first name is close to the floor.

Who gets excluded

Any method requiring a specific account cuts out part of your guest list, and it is rarely a random part. Ecosystem requirements skew young and skew online — precisely the guests whose photos you were already going to see.

What happens to the file

Ask whether photos are re-encoded on the way in. Chat apps compress by default; some shared albums downscale; cloud folders and good upload tools keep originals. You cannot recover detail later, so this decision is permanent.

Who ends up holding the collection

With a hashtag, the platform holds it. With a group chat, it is spread across everyone's phones. With an album or an upload page, you hold it — check you can download everything in one go, and that guests cannot browse each other's uploads unless you want them to.

What we would actually do

If you want one plan rather than seven options, this is the one that survives contact with a real wedding day.

1. 01

   Pick one primary method and commit to it

   Two methods do not double your photos; they halve the attention each one gets and split the collection in two. Choose the QR upload page if you want everyone, a cloud folder if you only need the bridal party.

2. 02

   Put the ask where people already are looking

   One card per table, plus one larger sign near the bar and one by the guest book. Tables are where phones come out. The bar is where people queue with nothing to do.

3. 03

   Write the card so it answers "what do I get" first

   Guests respond to "help us see the day through your eyes" far better than "upload photos here". Say what it is for, then how, in that order — there are 24 wordings to copy here.

4. 04

   Have someone announce it once, early

   A single line from whoever is on the microphone before the meal is worth more than every printed card combined. Ask your MC or best man to do it, and to do it before the speeches rather than after.

5. 05

   Test it on the least technical phone you can find

   Borrow a parent's phone the week before and run the whole flow on it. If it works there, it works everywhere. This is also how you discover that the venue Wi-Fi needs a captive-portal login.

6. 06

   Send one thank-you with a link, the week after

   Whatever you used, a short thank-you note with the link picks up a surprising number of stragglers who meant to share and forgot. This is the only follow-up worth sending — a second one reads as nagging.