Sending too many photos
More images do not always help. If the client receives too many similar options, the reply is slower and less complete.
Abistu
Simple private galleries for easy client selection.
Guide · sending photos to clients
Common mistakes when sending photos to clients.
Sending photos is easy. Getting one clear client decision back is harder. With Abistu you can send a private gallery, let the client select exact photos, add comments, and submit one structured request.
No credit card. Works in any browser. Your client does not need an account.
The short answer
The problem is rarely sending photos. The problem is sending them in a way that makes the client organise the decision.
A client should not have to download folders, compare filenames, take screenshots, describe rows, or search old messages just to tell you which photos they want.
A better process is simple: curate the set, send one private gallery, ask for one clear action, and collect the selection in one place.
That turns a messy photo handoff into a usable decision: selected images, item comments, one general comment, client contact, and a copy for the client by email.
In one line
Do not make the client translate your photos into filenames.
Mistakes that make selection confusing
Many problems appear before the client replies: in how the photos were sent.
Sending loose photos in chat
WhatsApp and email are useful for communication, but become confusing when images, notes, screenshots, and new versions are mixed together.
Asking for screenshots
Screenshots separate the decision from the original image. Later you have to guess which file, version, or crop the client meant.
Using filenames as the selection method
IMG_4821 or DSC_1034 may work internally, but clients think visually. Selection should happen on the image itself.
Not saying what the client should do
A gallery without a clear instruction creates vague replies. Say whether they should select, approve, comment, or request changes.
Mixing proofing and final delivery
Choosing photos and receiving final files are different stages. If they are mixed, the process becomes slower and less reliable.
Sending folders without structure
A folder can share files, but it rarely helps the client compare, mark favourites, or submit one clear response.
Forgetting the next step
After reviewing photos, the client should know what happens next: retouching, approval, delivery, prints, album, quote, or another revision.
A better process for sending photos
The goal is to help the client decide with less effort and less risk of misunderstanding.
1
Cull before sending
Remove duplicates, weak frames, technical rejects, test shots, and photos you do not want the client to consider.
2
Define the decision
Decide whether you need favourites, retouching selects, final approval, album choices, a request, a comment, or client contact.
3
Create one private gallery
Send one organised link instead of loose photos, attachments, folders, PDFs, or scattered messages.
4
Ask for a concrete action
Ask the client to select photos, choose items for retouching, approve finals, or add comments. The instruction should be direct.
5
Collect visual selection
The client should select exact photos directly, not describe them by row, screenshot, filename, colour, or memory.
6
Move forward from one request
The owner receives the selected items, item comments, general comment, and client contact. The client receives a copy of the request by email.
Sending photos vs collecting a selection
Sharing images is easy. Turning them into a useful decision requires structure.
Just sending
Collecting selection
How you send
Just sending:Loose photos, chat, folder, or PDF without a clear instruction
Collecting selection:Private gallery with organised images and one concrete action
How the client chooses
Just sending:Screenshots, filenames, or phrases like “the third one from the top”
Collecting selection:Selects images directly inside the gallery
How the response arrives
Just sending:Messages split between chat, email, calls, and voice notes
Collecting selection:Selected images, comments, and contact details in one structured request
What you do next
Just sending:Reconstruct what the client meant and confirm again
Collecting selection:Move to retouching, delivery, approval, print, album, or quote
Risk of error
Just sending:High when images are similar or several versions exist
Collecting selection:Lower because the decision stays attached to the right image
Client experience
Just sending:The client has to organise and explain manually
Collecting selection:The client opens, reviews, selects, comments, and submits
Where these mistakes appear
The pattern is not limited to photographers. Any visual job can lose clarity when images are sent badly.
Portrait photographers
Avoid screenshot replies when clients choose favourites, retouching selects, profile images, or personal series.
Weddings and families
When there are many similar photos, clients need a calm way to select album images, prints, favourites, or final edits.
Corporate events
Help clients choose images for websites, LinkedIn, internal communication, press, recaps, and social media.
Product and ecommerce photography
Clients can approve angles, variants, backgrounds, crops, colours, details, or catalogue-ready images.
Designers and creative teams
The same issue appears with mockups, renders, mood boards, layout options, and visual versions.
Catalogues and visual products
When products are sent by image, clients should be able to mark what interests them without replying with screenshots.
How to fix it
You do not need to make the process heavier. You need to make it clearer.
Instead of sending everything, curate first
The client does not need to see every attempt. They need enough good options to make a decision.
Instead of asking for opinions, ask for a decision
Replace “what do you think?” with “select your favourites” or “choose the images for final editing.”
Instead of screenshots, use visual selection
Selection should stay inside the gallery so each decision is attached to the correct image.
Instead of attachments, use one link
One link is cleaner than multiple files, folders, messages, screenshots, and versions.
Instead of technical names, use visual context
The client should not remember codes. They should recognise the image and select it directly.
Instead of mixing stages, separate decisions
First selection or approval. Then retouching, delivery, printing, album design, or the next step.
Best practices
A good handoff protects your time and makes the client decision easier.
Write a short instruction
A good instruction fits in one sentence: select your favourites, choose 15 for retouching, or approve this batch.
Make the gallery mobile-friendly
Many clients review from a phone. If opening, viewing, selecting, and commenting is easy, they reply faster.
Do not use final delivery as proofing
Avoid sending heavy final files when you are still collecting selection, approval, or corrections.
Reduce near-duplicates
If two photos are almost identical, choose one or show them only when the difference matters.
Explain what happens next
Say what you will do after receiving the request: retouch, deliver, prepare a quote, print, or confirm the order.
Keep a clear decision record
A submitted selection is easier to review later than messages scattered across chat and email.
What to use at each stage
Sending photos for selection is not the same as editing, archiving, or delivering final files.
Need
Practical tool
Send photos for selection
Abistu
Notify the client
WhatsApp, email, or SMS
Edit and retouch
Lightroom, Photoshop, Capture One, or similar
Deliver heavy final files
Drive, Dropbox, or WeTransfer
Store originals
Local storage, NAS, cloud backup, or external drives
Manage contracts or invoices
CRM, invoicing, or studio tools
Where Abistu fits
Abistu fits when you want the client to select or approve images without turning the response into a messy chat.
When the client must select photos
The client selects exact photos in a private gallery without screenshots or filenames.
When you want to avoid messy chat
You can still send the link by chat, but the selection stays inside the gallery.
When there are many similar images
Visual selection reduces mistakes with portraits, variants, similar frames, or similar products.
When you need an actionable response
Selected items, item comments, one general comment, and client contact arrive together.
When you do not need a heavy platform
For simple proofing, you may not need a full photography suite, ecommerce system, or CRM.
When the job is visual but not photography
The same logic works for designs, products, catalogues, materials, finishes, and visual proposals.
Where Abistu does not fit
A private gallery helps with selection and approval, but it does not replace the entire photo workflow.
Not storage for originals
Do not use it as your main archive. Keep RAWs, final files, and backups in your normal storage system.
Not a photo editor
It does not replace Lightroom, Photoshop, Capture One, or your retouching process.
Not heavy file delivery
For large ZIPs, RAWs, video, or heavy final files, Drive, Dropbox, or WeTransfer may fit better.
Not a substitute for communication
The gallery organises selection, but your follow-up, tone, and timing still build trust.
Checklist before sending photos
If these points are covered, the client has far fewer reasons to reply with confusion.
✓Cull the selection before sending.
✓Decide what response you need.
✓Do not send too many similar photos.
✓Use one clear link.
✓Avoid asking for screenshots.
✓Do not use filenames as the selection system.
✓Write one concrete instruction.
✓Let the client select images inside the gallery.
✓Let the client leave item comments and one general comment.
✓Explain what happens after the request is submitted.
Try a real gallery
This is a real gallery, not a screenshot. Tap any image to mark it, add a request comment, and submit.
One gallery. Exact selection. One clear response.
Frequently asked questions
What is the most common mistake when sending photos to clients?
The most common mistake is sending too many photos without a clear action. The client does not know whether to select, approve, comment, or simply look.
Is it wrong to send photos by WhatsApp?
WhatsApp is fine for sending a link or a short message. The problem starts when WhatsApp becomes the main selection system for many images.
Why should I avoid screenshot replies?
Screenshots separate the decision from the original image and can create confusion. It is better when the client selects the photo inside the gallery.
Should I send every photo from a shoot?
Usually no. It is better to make a professional preselection and send only images that are useful for the client decision.
What is the difference between selection and final delivery?
Selection is for deciding which images move forward. Final delivery happens later, with finished files prepared for use.
What exactly does the client submit?
The client selects exact photos, can add a comment on each selected item, writes one general comment for the whole request, and submits contact details.
What does the gallery owner receive?
The owner receives the selected items, item comments, general comment, and client contact in one structured request. The client receives an email copy.
Is it free?
During early access, yes. No card and no commitment. Pricing will be introduced later in a simple and transparent way.
Send photos so clients can respond clearly
Create a private gallery, send one link, and let the client select photos, comment on each selected item, write one general comment, and submit the request.
No screenshots. No filename confusion. No scattered approvals.
Currently in early access — no credit card, no commitment.