Cull before the client sees anything
Client proofing is not dumping the full shoot. Remove duplicates, misfires, closed eyes, technical failures, and images you would not want associated with your work.
Simple private galleries for easy client selection.
Guide · client proofing for photographers
Client proofing should be simple: send a curated gallery, let the client choose visually, and receive a clean selection back. This guide explains the workflow, common mistakes, tool options, and how Abistu keeps proofing out of screenshots and chat chaos.
No credit card. Works in any browser. Your client does not need an account.
Client proofing is not file delivery. It is the decision stage between the shoot and the final work.
After a shoot, you often do not want to retouch or deliver every image. You need the client to choose favourites, approve edits, select album images, or decide which photos should move forward.
That is proofing. It is a visual decision workflow. The client reviews a curated set, makes choices, adds comments when needed, and submits the selection back to you.
The problem begins when proofing happens through folders, screenshots, filenames, email threads, or WhatsApp messages. The images are visible, but the decision is messy.
In one line
Proofing is not showing files. Proofing is collecting a visual decision.
The goal is to move from shoot to client selection without losing the decision inside messages.
Client proofing is not dumping the full shoot. Remove duplicates, misfires, closed eyes, technical failures, and images you would not want associated with your work.
Upload the images the client is allowed to choose from. Keep the gallery clean, fast, and easy to browse on mobile.
Tell the client what they are choosing: favourites for retouching, album images, print candidates, website selects, or final delivery options.
The client should tap the images they want, not reply with filenames, screenshots, positions, or descriptions.
If a selected image needs a note, the client should be able to leave a comment on that specific photo instead of describing it later in chat.
The proofing stage should end with selected images, per-image comments, one general request comment, and client contact details together.
Use the submitted selection as your working list. The client receives an email copy, and you can retouch, print, deliver, or archive without decoding messages.
Different photography genres use proofing differently, but the core problem is the same: the client needs to choose clearly.
A client chooses 10–30 favourites from a portrait session. The final selection usually determines which images you retouch and deliver.
The couple selects album images, print favourites, family portraits, or highlights from a large wedding gallery.
A brand, agency, or business selects which product shots, lifestyle images, or campaign visuals move into retouching or delivery.
An organiser chooses press images, website images, sponsor photos, VIP shots, or internal communication visuals.
Clients choose emotionally important images from a larger set. A calm, simple gallery matters because the decision can feel personal.
Privacy and clarity matter. The client should review privately, choose privately, and submit without public folders or casual chat threads.
The usual problem is not that clients cannot choose. It is that the workflow asks them to choose in the wrong place.
“The third one in the second row” depends on screen size, sorting, and memory. It is not a reliable way to identify a photo.
Screenshots feel easy for the client, but you still have to match them back to originals and figure out which version they meant.
IMG_4271 means something to your file system, not to your client. Filenames are a weak language for visual decisions.
If you send everything, the client gets overwhelmed and delays the decision. Proofing should feel curated, not like homework.
A useful comment should stay attached to the selected image. Otherwise you have to reconstruct which note belongs to which photo.
Likes, comments, screenshots, and chat replies are not the same as a final selection. The workflow needs a clean end point.
A clean proofing workflow does not just show images. It captures the decision in a form you can act on.
The right tool depends on whether you need storage, delivery, print sales, a full studio platform, or just clean selection.
Google Drive, Dropbox, and WeTransfer are useful for storage and delivery, but the client still has to tell you what they chose somewhere else.
Pixieset, Pic-Time, and ShootProof can manage galleries, stores, print sales, contracts, and more. Powerful if you need the whole platform.
A focused tool does one job: private gallery, client selection, clean response. Less setup, fewer features, faster proofing.
WhatsApp, Instagram DMs, and email are convenient for conversation, but weak for structured visual decisions.
The details change by genre, but the proofing principle stays the same: curate, send, select, submit.
Use proofing to collect album favourites, print selections, family portrait choices, and highlight edits without long email threads.
Let clients choose the portraits they want retouched or printed. Keep the gallery limited enough that the decision feels manageable.
Give brands or agencies a clean way to select product shots, campaign images, website visuals, and final retouching candidates.
Let organisers choose press images, sponsor moments, speaker photos, team shots, and website assets from one proofing link.
Make the selection process calm and simple. Clients often need time to choose, but they should not need to learn a complicated platform.
Use private links and a simple proofing experience. The client should not have to send sensitive image choices through casual chat.
Proofing should help the client decide faster and help you work from a reliable selection.
Abistu is not trying to become your whole studio system. It is built for the proofing moment.
Create a gallery, upload images, and send one private link. The client opens it without installing anything or creating an account.
Clients select the exact images they want. No filenames, no screenshots, no “third one in the second row.”
When a selected image needs a note, the comment stays connected to that specific photo.
You receive selected images, per-image comments, one general request comment, and client contact details together.
After submission, the client receives an email copy of the request, so both sides have a record of what was sent.
A focused proofing tool is useful because it stays focused.
No print fulfillment, packages, lab integration, or checkout. Use a full studio platform if print sales are central to your business.
No contracts, invoicing, questionnaires, booking, reminders, or pipeline. Keep using your existing business tools.
Keep RAW files, masters, and originals in Lightroom, Dropbox, NAS, external drives, or your normal storage system.
A proofing request is useful for practical workflow decisions. For legal approvals, usage rights, and contracts, use proper legal tools.
This is a live gallery — not a screenshot. Tap any image to mark it. Press the button to send a request. This is what your client sees.
Proofs in one link. Selection in one response.
Client proofing is the process of showing a curated set of images to a client so they can choose favourites, approve edits, select album images, comment on photos, or decide which images move to the next stage.
The cleanest way is to send a private proof gallery where the client can select images visually and submit one response. Abistu is built for that focused proofing workflow.
Enough to give real choice, but not every frame from the shoot. The right number depends on the job: a portrait session may need 40–120 proofs, while a wedding or event may need hundreds. The key is to remove weak duplicates first.
Yes. A useful proofing flow should let the client leave a comment on each selected image when the note belongs to that photo, plus one general comment for the whole request.
You receive the selected images, per-image comments, one general request comment, and client contact details together. The client receives an email copy of the request after submission.
Usually no, unless download is part of your workflow. Proofing is about choosing images, not delivering final files. You can deliver final high-resolution images separately after the selection is complete.
You can, but Drive is a file-sharing tool, not a proofing workflow. Clients still need to tell you what they chose through email, chat, screenshots, or filenames.
Not always. Proofing often means choosing candidates or favourites. Approval is more final: the client confirms that specific photos, edits, or visuals are ready for the next step.
No. They open the private link, review the images, select what they want, add comments if needed, and submit. No app, no login, no account.
For the proofing and selection part, yes. Abistu does not replace Pixieset's store, CRM, website builder, or print sales. It is a lighter tool for the proofing moment.
Send one private proof gallery. Let the client choose visually, comment clearly, and submit one structured request.
No screenshots. No filenames. No “third one in the second row.”
Currently in early access — no credit card, no commitment.