Proofing
Client Photo Selection Without the Back-and-Forth
Client photo selection is proofing: the client reviews the shoot and approves the photos they want. Done over messages, it collapses into file-name lists and “which one was that again?”. Done in Smart Photo Selection, it is a gallery where every photo is Selected or Not selected, a submit button that locks the decision, and a ZIP download of exactly the approved set.
The problem
Why Choosing Over Messages Fails
Without a selection gallery, approval lives wherever the client last typed: screenshots with circles drawn on, voice notes describing “the one where…”, file names copied by hand. Every handoff risks a wrong photo, and nobody can prove what was agreed.
Lists detach from photos
A file name in a chat is one typo away from the wrong frame getting edited and printed.
No shared state
You and the client each hold a different picture of what was chosen, and both are partly wrong.
Revisions multiply
Every “actually, also this one” restarts the count, the edit queue and the album plan.
Guests pile on
Meanwhile every guest messages separately for their photos - a queue only a self-serve finder clears.
The client side
What the Client Actually Does
- 01
Open the link
One gallery link in the browser - no account, no app, on phone or computer.
- 02
Work folder by folder
Functions or sessions in order, each with a count, at whatever pace suits them.
- 03
Mark favourites
Selected / Not selected on every photo, filters for either view, Select All or Unselect All per view.
- 04
Check the Selected view
The running shortlist, visible as one set - gaps and excess show immediately.
- 05
Submit
One submission locks the set. That lock is the approval you work from.

The client's gallery: photos carry a protective overlay and the bar counts the selection.
Your side
Controls That Keep Proofing Clean
Cull before sharing
The client never scrolls past rejects - confidence in the gallery starts with what is absent.
Lock on submit
After submission nothing can be selected, uploaded or deleted by mistake. Changes after that are visibly change requests.
Downloads per booking
Match the package: client downloads on for digitals-included deals, off where you sell the files.
Photo period
Deletion date visible on the booking, extendable while edits and albums run over.
Studio branding
Name, Instagram and number on the gallery turn every share into a referral surface.
After submit
A Submitted Set Is an Approval Record
The difference between favourites and proofing is the lock. A submitted selection is dated, immutable and downloadable as one ZIP - the input your editing queue, your album plan and your delivery all read from. Disputes about “I chose that one” end where the submitted view begins.
From there the set moves forward: download it for editing, deliver it through the online photo gallery, or start the album automation from the booking's photos.
FAQ
Common Questions
What is client photo selection?
How is this different from favouriting on a shared drive?
Can clients select photos online without an account?
What happens after the client submits their selection?
Can I stop clients downloading everything?
How do guests get their photos during proofing?
- Photo SelectionCull the shoot, let clients select online, deliver the approved set.
- Photo Selection SoftwareWhat online selection software does and how to choose it.
- Online Photo SelectionShare, select and approve in one gallery - no app, no accounts.
- Photo Gallery & DeliveryShare an online client gallery by link or QR code and deliver.
- Face Scan Photo FinderGuests find their own photos with an in-browser face scan.
- Wedding Photography WorkflowSelection, culling, sharing and delivery for wedding shoots.
Replace the Message Thread With a Submit Button
One gallery, one locked set, one ZIP - proofing your clients will actually finish.