How do you get client photo approval before editing, straight from Lightroom Classic?

By David · September 14, 2026 · 7 min read

Most photographers edit first and ask questions later - export the whole shoot, grade all of it, then send a gallery and hope the client is happy with the selection you made for them. That works fine for small jobs. It falls apart once a shoot produces more frames than you would want to fully edit without knowing which ones the client actually cares about.

Proofing before editing flips that order: the client picks first, from unedited or lightly-edited previews, and you edit second - only the photos that survived. I build a Lightroom Classic publish plugin that ships this as a workflow step, so I have spent a lot of time on where the "export, upload, wait, cross-reference" version of proofing breaks down.

Why proof before you edit

The math is straightforward. Say a wedding produces 2,500 raw frames. A typical client delivery is 400 to 600 final images. If you edit the full take before you know what the client wants, you have spent editing time on roughly 1,900 to 2,100 photos nobody will ever see delivered. Proof first, and you edit close to the 400 to 600 that make the cut - plus whatever the client's picks add back in that you might not have chosen yourself.

It also removes a specific kind of friction: the client who loves a photo you cut in your own edit. Proofing surfaces that disagreement before you have sunk editing time into your version of the story, not after you have delivered a gallery and they ask "where's the one from the doorway?"

How most photographers proof today, and where it breaks against a Lightroom Classic catalog

There are three common approaches, and each one runs into the same underlying problem: none of them know your catalog exists.

• Watermarked export plus email. Cheapest option, zero extra tools. The client replies with a list of filenames or frame numbers, which you manually cross-reference against your catalog. Fine for 40 photos, painful for 400.
• A generic proofing SaaS bolted on after export. Better client experience - a real gallery with favoriting - but the workflow is still export, upload, wait for picks, then manually translate them back into flags or ratings before you start editing.
• A full studio-suite gallery platform. Pic-Time, Pixieset, and SmugMug all offer proofing on their paid tiers, with a genuinely good client-facing experience. The catch is the same one-way trip: your catalog does not know what the client picked, so you are still reconciling it by hand, or not at all.

In every case, the gallery and the catalog are two separate systems that happen to describe the same shoot. Someone, meaning you, has to keep them in sync by hand.

What changes when proofing is a Publish Service instead of a one-time upload

Lightroom Classic's Publish Services model already solves a version of this for delivery: you publish a collection, and republishing only pushes what changed, because the service tracks state against your catalog instead of treating each export as disconnected. Proofing built the same way gets three things a one-time upload cannot:

• Picks round-trip back to the catalog. A client's selections land as verdicts on the actual source photos, not as a list you have to translate.
• Re-publishing only pushes changes. Add ten more photos to the shoot after the gallery is already live, and you republish just those ten, not the whole set again.
• No duplicate library to keep in sync. There is one source of truth - your catalog - instead of a catalog plus a parallel gallery-platform library that can drift apart.

Setting up a proof-then-edit workflow from Lightroom Classic

Here is the version of this I use, built around Keptfolio's Share for Review flow:

1. Cull for technical quality only - focus, exposure, closed eyes - before anything client-facing. You are removing unusable frames, not making the creative call for the client.
2. Publish the surviving frames to a Share for Review gallery as a Lightroom Classic Publish Service. No separate export step; the plugin reads straight from your catalog's rendered previews.
3. Send the client the link. They review on a phone or desktop, swiping through a mobile-friendly interface, marking picks and rejects.
4. The client's verdicts sync back into your catalog. Rejected photos get a reject verdict you can filter on directly in Library; picks are just as easy to isolate.
5. Filter your catalog to picks only, and start Develop. You are now editing the photos that are actually going to be delivered, not a guess at what the client wants.

Step four is where the time savings actually live. Because the sync happens automatically instead of you reading an email and clicking ratings one photo at a time, the gap between "client finished proofing" and "I'm editing the right photos" is minutes, not an evening.

Proofing tool comparison for Lightroom Classic photographers

If you are choosing a proofing tool, the honest question is not just "does it have proofing" but "what happens to the picks after the client makes them." Here is where the main options land in 2026:

The studio suites are not doing anything wrong - proofing is one feature inside a bigger product built around selling prints, invoicing, and running a whole business. If you already use one for those other features, its proofing tier is a reasonable default. The re-upload and manual reconciliation cost shows up specifically for photographers paying for a full studio suite mainly to get one feature: a gallery the client can pick from.

Frequently asked questions about proofing before editing in Lightroom Classic

Is proofing before editing worth setting up for small sessions?

For a 30-minute mini session, probably not - you can eyeball the keepers yourself. It starts paying off around the point where a shoot produces more frames than you would comfortably want to fully edit unprompted: a wedding, a full-day portrait session, or any job where the client has opinions about which moments matter. The time you save is proportional to how many photos you would otherwise edit and never deliver.

Can clients proof photos from their phone?

Yes, on any tool built for it - Pic-Time, Pixieset, SmugMug's proofing galleries, and Keptfolio's Share for Review links all render as mobile-friendly web pages, no app or account required. Swipe-to-cull interfaces in particular are designed around a phone-sized touch gesture, since that is where most clients actually review their gallery.

What happens to the photos a client rejects during proofing?

That depends on the tool. Some proofing platforms just hide unselected photos from the client-facing gallery without touching your catalog at all, which means you still have to cross-reference picks manually back in Lightroom. A publish-service-based proofing step can instead write the client's picks and rejects directly onto the source photos in your catalog - Keptfolio applies a reject verdict you can filter on, so you can jump straight to editing only the survivors.

Does a proofing gallery replace the final delivery gallery?

No, and treating them as the same step is a common mistake. Proofing happens on unedited or lightly-edited frames, before you commit editing time, and its job is narrowing down the set. Delivery happens after editing, on the final files, and its job is handing over full-resolution originals. Keptfolio keeps these as two separate publish flows - Share for Review before Develop, full-resolution client download galleries after - so a client browsing their final gallery never sees your proofing rejects.

Do I need one tool for proofing and a different one for final delivery?

Not if the tool covers both stages natively. Studio suites like Pic-Time and SmugMug bundle proofing and delivery galleries under one account, generally on their higher tiers. A Lightroom Classic publish service that handles both, like Keptfolio, keeps the two stages inside the same plugin and catalog instead of stitching together a proofing SaaS and a separate delivery tool.