There are about seven realistic ways to get a photo from your camera onto the phone of the person in it. They differ enormously in how fast they are, how much work they cost you during the event, and — the one most comparisons skip — whether the guest receives an edited photo or a straight-out-of-camera frame.
Here is the honest version, including the cases where the method I build is the wrong choice.
The comparison
| Method | Time to guest | Your effort during the event | Edited? | Guest friction | Lead capture | Cost model |
|---|---|---|---|---|---|---|
| AirDrop | Seconds | High — one interaction each | Rarely | iPhone only, must be nearby | No | Free |
| Email at the booth | Minutes–days | High — typing addresses | Usually | Typos, queue | Manual | Free |
| WhatsApp / messaging | Minutes | High | Sometimes | Needs your number | No | Free |
| Printed QR → shared gallery | Minutes–hours | Low | Usually | Finds everyone's photos, not theirs | Varies | Hosting cost |
| Face-recognition event apps | Seconds–minutes | None after setup | No — usually unedited | Selfie or app required | Usually | Per event / per guest |
| Client galleries (Pixieset, Pic-Time) | Days | None | Yes | Link sent later | No | €8–17/month |
| Watch-folder delivery (Fotoflo) | Seconds | None after setup | Yes | Scan a QR | Yes | Per project |
The distinction nobody names: edited or not
Most "instant photo sharing" tools solve the transport problem — moving bytes from camera to phone quickly. They do that well. What they mostly do not do is get your edit in first.
Face-recognition platforms typically ingest straight from the camera or a card, which is what makes them fast. The photo the guest receives is the frame as shot: your white balance, your exposure, no retouching, no crop, no preset. For a festival crowd shot that's completely fine. For a paid headshot with someone's face two feet from the lens, it isn't — and it's your name on that image when they put it on LinkedIn.
Client galleries have the opposite profile. The photo is properly edited, because you edited it, but the guest gets it days later when the moment has passed.
The gap between those two is the interesting part: edited photo, delivered while the guest is still standing there. That requires the delivery step to start from your export folder rather than your camera.
Method by method
AirDrop
Genuinely the fastest thing that exists, and free. It's also one-to-one, iPhone-only, and requires you to stop and interact for each transfer. Fine for ten guests. Impossible for three hundred.
Typing email addresses at the booth
The default, and the worst option at any volume. Typos mean undelivered photos and a support burden. It creates a queue at exactly the moment you want throughput. And you still have to do the sending afterwards.
The one thing it has going for it: you end up with an email list. If that's the actual goal, get it from a proper capture form rather than a photographer squinting at handwriting.
WhatsApp and messaging apps
Works well for small shoots and for clients you already know. It puts your personal number in front of strangers, which is a real consideration at public events, and it doesn't scale past a couple of dozen.
A printed QR pointing at a shared gallery
Cheap, simple, and the traditional answer. One code, everyone lands in the same gallery, everyone scrolls to find themselves.
The failure mode is scale: at 300 guests, "find yourself in this gallery" is a bad experience and a privacy question, since everyone can see and download everyone else's photos. Fine for a wedding where guests know each other. Not fine for a corporate event.
Face-recognition event platforms
Tools like SpotMyPhotos, Honcho and SnapSeek let a guest take a selfie and get every photo they appear in.
These genuinely win in one scenario, and it's a big one: a roaming photographer covering a large event, where you're shooting 500+ candid frames and nobody knows in advance which photos contain which person. No QR-based workflow can solve that, because there's no moment where you and one specific guest are in the same place with one specific photo. If that's your event, use one of these — it's the right tool.
The trade-offs are that the delivered photo is usually unedited, guests must submit a selfie (which some people, reasonably, won't), and pricing tends to be per-event or per-guest.
Client galleries
Pixieset, Pic-Time, ShootProof, CloudSpot, Zenfolio. These are excellent products and they're not really competing for this job. They're built for delivery after the shoot — proofing, print sales, album selection, a permanent archive. Prices are typically €8–17 a month.
If your work is weddings and portraits where the client expects a curated gallery a week later, this is the correct category and nothing here should convince you otherwise.
Watch-folder delivery
You export as you normally would; a folder watcher picks up the finished JPEG and turns it into a QR code the guest scans on the spot.
The advantage is that your edit is already applied, because the pipeline starts after your export rather than before it. The limitation is the mirror image of face recognition: it needs a moment where you and the guest are together — a booth, a headshot station, a portrait chair. It's not the answer for roaming coverage.
Disclosure: this is what I build. I've tried to describe where it loses as clearly as where it wins — a comparison that concludes "my thing is best at everything" isn't worth reading.
Which to pick
- Roaming coverage of a large event, hundreds of candids → face-recognition platform
- Booth, headshot station or portrait chair → watch-folder delivery
- Wedding or portrait client expecting a curated gallery → client gallery
- Under ~20 guests, casual → AirDrop or WhatsApp
- Guests know each other and privacy isn't a concern → shared gallery behind one printed QR
The question that decides it is not "which is fastest." It's whether there's a moment during your event when you and one specific guest are looking at one specific photo together. If there is, you can deliver an edited photo in seconds. If there isn't, you need recognition to do the matching, and you'll be delivering unedited frames.
If your work is the first kind, here's how the watch-folder version works.