Appruva

Dropbox for Client Photo Review: What Breaks

A sync tool is not a review tool. The gap shows up in four specific places.

Dropbox is excellent at the job it was built for: making a folder appear on someone else's machine. Photographers reach for it at approval time because the files are already there, and then spend the round doing translation work that the tool cannot do for them.

This is not a case against Dropbox. It is a map of the four places a shared folder stops being a review surface, so you can keep using it for the part it is good at and stop paying for the part it isn't.

Where the shared folder actually breaks

Four failures, in the order most people hit them.

Feedback detaches from the frame. Dropbox comments attach to a file, which sounds right until a client writes “the third one from the left” in a comment on a folder, or replies by email instead. The note and the image end up in different places, and you are the index.

Selects have no state. There is no “approved” in a file system. Clients improvise: renaming files, moving them into a folder called FINAL, or sending a list of numbers. Each improvisation is a convention you now have to learn and maintain per client.

Versions overwrite or multiply. Replace a file and the old one is gone from view; add a suffix and you have two. Neither tells the client which is current, and the printer eventually gets the wrong one.

Access is all-or-nothing per folder. Sharing selects with one stakeholder and the full take with another means two folders and a manual copy that drifts the moment anything changes.

Shared folder

  • Comments live on files, not on what the client sees
  • “Approved” is a naming convention you invented
  • Versions overwrite or accumulate suffixes
  • Everyone with the link sees the same thing
  • Progress is invisible until you ask

Review link

  • A note belongs to the frame it describes
  • Approval is a state on the image
  • Versions stack, with the current one obvious
  • Selects and full take are the same object, filtered
  • You can see what is outstanding without asking

None of these are bugs. A file system stores bytes and tells you when they changed; it was never asked to hold an opinion about them. The mismatch only becomes visible when you put a decision with a deadline on top of it, which is exactly what an approval round is.

The compounding problem is that each workaround you invent has to be taught. A client who learns your FINAL-folder convention on one job will not remember it on the next, and a client who works with three photographers has learned three conventions. The overhead does not amortise across jobs the way real tooling does — it resets every time.

The download-annotate-reupload loop

The most expensive Dropbox habit is invisible because it happens on the client's machine. They download the folder, open images in Preview or Photos, mark them up in whatever they have, and send back a zip or a PowerPoint.

Every step of that loop loses something. The download is a point-in-time copy, so any change you make afterwards is invisible to them. The markup happens in a tool with no colour management, so what they judged is not what you delivered. And the return trip arrives as a second set of files you now have to reconcile against your originals by eye.

The tell

If a client has ever sent you a document containing screenshots of your photographs, the review step has left your tooling entirely. Nothing you do inside Dropbox will pull it back.

Compare that to a round run through a single review link: the client never obtains a copy to mark up, because marking up happens where the image lives.

There is a second-order cost that shows up weeks later. Because the client holds a downloaded copy, they will keep referring to it. When you deliver a corrected version, their mental image of “the photos” is still the copy on their desktop, and any disagreement about what was delivered is really a disagreement about which copy each of you is looking at.

The fix is not a better instruction. It is removing the copy from the loop. If the only place the images exist is a URL, then there is exactly one thing called “the photos” and both of you are looking at it.

What Dropbox is genuinely good at

Worth being fair, because the answer is not “stop using Dropbox”.

Moving large files reliably. Block-level sync and resumable transfers make it a better courier than almost anything else. A 60 GB wedding delivery gets there.

Being the archive. Version history and file recovery are real features, and a finished shoot sitting in a well-named folder tree is a perfectly good long-term home.

Working with a retoucher. A collaborator who wants the actual files on their actual disk is exactly the case sync was designed for.

The split that works: Dropbox as the pipe and the archive, something purpose-built for the decision in the middle. The decision is the part with a deadline attached, and it is the only part where the tool's shape changes how fast it closes.

It is also worth saying that Dropbox's own comment feature is better than most people use. If your client will genuinely comment on files inside Dropbox rather than replying by email, and your shoots are small, you may never hit the ceiling. The limits described here are real but they are volume-dependent — a portrait photographer delivering 25 frames to one decision-maker has a very different experience from someone sending 200 frames to a committee.

Storage economics deserve a mention too. Keeping a year of full-resolution deliveries permanently accessible is a real cost wherever you put it, and sync tools price for exactly that job. If your galleries live somewhere else, Dropbox becomes the cold archive — cheaper to reason about, and no longer load-bearing for anything with a deadline.

The mistake is not using a sync tool. It is letting the tool that happens to hold the files decide how the decision gets made, purely because the files are already there. Convenience at the start of a round is a poor trade for translation work at the end of it.

If you are staying on Dropbox, do these four things

Plenty of people cannot move tools this quarter. These reduce the damage.

  1. Number the files yourself, visibly. Put the sequence in the filename — 001_ceremony.jpg — so “number 14” means one thing to both of you. Most reconciliation work is caused by the client and you counting differently.
  2. Send a shortlist folder, not the take. One folder, culled, no subfolders. Every extra folder is a place feedback can get lost.
  3. Give them a reply format. Ask for a plain list of filenames and one line each. Say it explicitly in the message; clients default to prose because nobody told them otherwise.
  4. Never replace a file in place. Add _v2 and say which is current in writing. Silent replacement is how the wrong frame reaches production.
Pro Tip

Put the deadline and the reply format in the first two lines of the sharing message, above the link. Anything below the link is read after the client has already clicked away.

One more that costs nothing: put the number of images in the message. “42 selects” sets an expectation of effort, and a client who knows the task is bounded starts it sooner than one facing an unlabelled folder. Unbounded tasks get postponed; that is true of clients and it is true of you.

And resist the temptation to add structure with subfolders. Every folder is a decision the client has to make before they can start looking, and each one is a place a note can be filed and lost. One flat folder, culled, is easier to review than a tidy hierarchy.

How to tell when the folder is costing you money

The switch is worth making when reconciliation time exceeds the time you spend actually choosing photographs. Track one round honestly:

Activity in one roundIs it judgement work?
Culling the take to selectsYes — only you can do it
Deciding which edit note to act onYes
Matching “the third one” to a filenameNo — pure translation
Chasing a client who has gone quietNo
Working out which version is currentNo

The bottom three are what a shared folder adds and a review surface removes. If they are a rounding error on your week, stay where you are. If they are an afternoon, the tooling is the problem, not the client. Google Drive has the same shape of problem, for the same underlying reason: both are file systems being asked to hold a decision.

Be honest about the direction of the number too. Translation work does not scale with the quality of your photography — it scales with the number of frames and the number of people commenting. So it grows exactly as your business grows, which is the worst possible shape for a cost. The photographer shooting eight weddings a year barely notices it. At thirty it is a part-time job nobody is paying for.

If you want a single question to decide on: after your next round closes, ask whether you could produce a list of exactly which frames were approved, by whom, and on what date, in under a minute. If yes, your process is fine. If it means reading an email thread, the folder has been holding something it cannot hold.

Frequently asked questions

Can clients comment on photos in Dropbox?

Yes, Dropbox supports comments on individual files, and for a small set of images that can be enough. It breaks down when a client replies by email instead, refers to images by position rather than filename, or needs to mark a specific area of a frame, because a file-level comment cannot point at a region of an image.

Is Dropbox secure enough for client photos?

For most commercial work, yes. Shared links can be password-protected and given expiry dates on paid plans. The bigger practical risk is not interception but over-sharing: a link forwarded onward still works, so treat any shared folder as readable by anyone who receives the URL.

Should I send clients the full take or just selects in Dropbox?

Selects only. A client shown several hundred frames reviews the first thirty and then replies vaguely, and in a folder there is no mechanism to guide attention. Culling first is the single change that most improves the quality of feedback you get back.

What is the best way to handle photo revisions in Dropbox?

Never replace a file in place. Add a version suffix, keep the original, and state in writing which version is current. Silent replacement removes the client's ability to see what changed and is the most common route to the wrong file reaching print.