A lot of avoidable friction in a photography business comes from squashing two different jobs into one. Proofing and delivery sound similar, both involve sharing images with a client through an online gallery, but they exist to accomplish opposite things. Understanding the difference is what lets you run a clean process where the client guides the edit and then receives exactly what they wanted. Here is what each step is for and why you genuinely need both.
Two different jobs
Proofing is a question, and delivery is an answer. During proofing you are asking the client which images they want, and you are collecting their favorites and feedback on previews. During delivery you are handing over the finished, full-resolution files for them to download and keep. One is about gathering decisions; the other is about fulfilling them. When you see them as two distinct jobs, it becomes obvious why doing only one, or blurring the two together, leaves value on the table.
What proofing is for
Proofing exists to narrow and to inform. You shoot far more than the client needs, and proofing is how the client tells you which of those images matter to them before you invest hours in finishing. The images at this stage are previews, often watermarked or with downloads disabled, because their purpose is judgment rather than possession. The output of proofing is not files; it is decisions, a clear shortlist of favorites and a resolved set of comments that together tell you exactly what to retouch. Everything about a good proofing gallery, the one-tap favorites, the per-photo comments, the studio replies, is built to capture those decisions cleanly.
What delivery is for
Delivery exists to hand over the finished work. By the time you deliver, the choices are made and the retouching is done, and the client’s job is no longer to judge but to receive. Here the files are full-resolution, downloads are the whole point, and the experience should make it effortless for the client to save everything and share it. The output of delivery is possession: the client ends up with the images on their own devices, ready to print, post, and keep. Where proofing withholds on purpose, delivery gives freely.
Why conflating them causes problems
When photographers collapse these two steps, they usually do it by skipping proofing and simply delivering everything. On the surface it feels generous and efficient, but it quietly creates problems. The client is handed hundreds of unfiltered images and no guidance, which is overwhelming rather than delightful. You lose the chance to let them shape the edit, so you either finish everything at great cost to your time or finish nothing and hand over raw-looking files. And there is no shortlist to build an album or a print order around, because you never asked for one. Skipping proofing does not save a step; it removes the step that makes all the others efficient.
How they fit together
The two jobs are sequential, and the handoff between them is the natural rhythm of a well-run project. First you proof, sharing previews and collecting the client’s favorites and comments. Then, once the selects are locked, you finish only those images and deliver them as polished final files. The client experiences it as a single smooth arc, choose, then receive, even though behind the scenes you have run two deliberate stages. That full arc is what the proofing workflow lays out end to end.
Doing both in one place
The practical advantage of a modern platform is that proofing and delivery can live in the same gallery, so you are not juggling separate tools. In FrameCourier the client stars favorites and leaves comments during proofing, and the very same gallery becomes the place they download their finished files at delivery, all under your branding. Keeping both stages in one system means nothing has to be re-uploaded or re-shared, the client only ever learns one interface, and you get a clean line from the first selection to the final download. If you are choosing a tool to run both, we compare the options in the best online photo proofing software.