Watermark Proofs in Lightroom Without Ruining the Selection

Start by being honest about the threat model. A visible watermark is a social signal, not access control. It changes what a person is willing to do with a file they already have. It does not change what they can do with it.

Read that table as a division of labour. The watermark handles one row well. Every other row is handled by a gate, and a gate is a different tool. If your actual problem is in the rows below the first, marking the photographs is solving the wrong thing while still costing you the selection.

A client choosing from 400 proofs is not judging photography. They are scanning for themselves. The sequence is always the same: find my face, check my expression, check my eyes, move on. A frame where that check fails gets skipped in under a second.

Now put a large semi-transparent logo through the middle of the frame. The check fails on the photographs you were proudest of, because tight portraits are exactly the ones where the subject sits where the mark sits. The wide establishing shots survive. The client sends you a pick list weighted toward the loose frames and you conclude they like the loose frames.

There is a second cost, softer but real. A mark across every frame reads as suspicion. You are handing a client their own wedding and stamping every picture against the possibility that they steal it. Some studios are fine with that trade and some clients never notice. It is still a thing you are saying.

The version that keeps both benefits is a small mark, at the edge, in one corner, at low opacity. It is still a deterrent because a repost carries it. It costs nothing to the selection because it sits over background, not over a face.

Placements, ranked by what they cost you rather than by how safe they feel. The scale figure is the mark against the long edge of the frame.

Two settings matter more than the placement. Opacity first: a mark you can read without effort is already too strong, because the client reads it before they read the picture. Colour second: a white mark disappears on a beach and a black mark disappears in a church, so if you shoot both, a mark with a faint outline or a mid-grey mark survives more of your work than either pure white or pure black.

Do not put a drop shadow on it. A shadow is what makes a mark read as applied rather than as part of the design, and it is also the part that survives a crop worst.

The mark is a Lightroom job. Build it in the watermark editor, save it as a preset, and attach it to the export or publish settings you use for proofs. The publish service renders the proofs from your catalogue, so whatever the watermark panel puts on the render is exactly what the client sees. There is no second place to configure it and no step where it can be stripped.

Two consequences worth planning around. First, decide the mark before the first publish. A watermark change is a change to the pixels, which means a re-render of everything you have already sent, and a gallery your client has already opened is not the moment to change your logo.

Second, the watermark belongs on the proofs and not on the delivery. Those are two different files here. The proofs are what Lightroom publishes. The full-resolution delivery is a ZIP you upload yourself, per gallery, which means it comes from a separate export where you simply leave the watermark off. Marked proofs, clean finals, no special feature required. The client link for that ZIP is live for three days per handoff and you can re-upload it any time they need it again.

Beyond that, the publish service behaves the way Lightroom Classic publish services are supposed to. Lightroom tracks New and Modified, one Publish pushes exactly those, the gallery keeps the same link, renaming the collection renames the gallery, and metadata-only edits do not re-push pixels. The whole two-way loop, including picks coming back as ratings, is covered in the Lightroom client gallery workflow guide. One limit to state plainly: this is Lightroom Classic only. The cloud Lightroom app takes no plugins.

The other way to protect a proof set is to leave the photographs alone and put a door in front of them. A password is set per gallery, either in the studio or right in the Lightroom Classic export dialog, which means the gallery can go live already password-set rather than being public for the few minutes it takes you to remember.

The part that makes it a gate rather than a curtain is where the check happens. It is enforced on the server, and it covers the files and not just the page. The whole-gallery ZIP is behind it, the full-resolution download is behind it, and the face-search index is behind it. A password that guards the page while the download URL stays open is theatre, and it is worth checking that distinction on whatever tool you use, not only this one.

Alongside it, downloads can be switched off entirely until you have been paid. Be clear about how that works: the unlock is manual. You paste your own payment link, a pay button appears beside the download, and when the money lands you flip downloads on yourself. Nothing unlocks by itself and no webhook is watching. That is a smaller promise than some tools make and it is the accurate one.

Put together, a password plus downloads held back is a real lock on the files, and the photographs stay clean while the client is choosing. The longer version of the password side is in how to password protect a client photo gallery.

Here is the honest limit, and it is the reason this page does not simply tell you to skip the watermark. A password stops everyone except the person you gave it to. The person who reposts your proofs before paying is your client, and your client has the password. If that is your actual problem, the gate does not touch it and the mark does.

Match the tool to the thing that has actually gone wrong in your business, not to the thing that worries you most in the abstract.

That last row is worth a sentence, because marketing is the reason a lot of marks exist. If the mark is there so that a shared screenshot carries your name, weigh it against the fact that the client-facing page is already yours end to end: your subdomain, your logo as the only header, no footer, nothing of ours on it. The branding argument for a heavy watermark is weaker than it looks.

One practical note if you do mark. Picks come back as one tap for a star and two taps for a love, and both land in Lightroom as ratings against the original files, so a watermark on the proof never touches your masters. A gallery accepts JPG and PNG, so the mark is baked into a JPEG on the way in and your RAW files stay on your own drives where they belong.

For a studio that takes a deposit and delivers after final payment, this sequence keeps the selection clean and still keeps the files closed.

Build a corner watermark preset in Lightroom and attach it to your proofing publish settings. Set the gallery password in the export dialog so it is never briefly open. Publish. Leave downloads off. The client picks on photographs they can actually see, with a small mark riding the corner in case a frame escapes into a group chat. When the invoice clears, you turn downloads on and upload the clean full-resolution ZIP from a second export with the watermark off.

Every part of that is a setting, not a feature you have to buy, and it takes about the same time as publishing without any of it. If you want the whole picking process rather than the protection part of it, the client photo proofing guide covers the rest.

This page states no external figures, no competitor pricing and no competitor policy, so there is nothing here to cite from another company. The clientgallery.io plan and fair-use facts referred to above, the per-gallery password and where it is set, the server-side gate over the whole-gallery ZIP and the full-resolution download, the manual download unlock, the three-day full-resolution handoff window, and the behaviour of the Lightroom Classic publish service, were all checked against the running product on 12 September 2026. The watermark placement, opacity and colour advice is editorial judgement about how selection galleries are read, not a measurement, and you should treat it as a starting point to test against your own work.