Watermarking and protecting client photos: when and how

Every photographer hits this question eventually: do you stamp your logo across a client's photos, or hand them clean files and trust the gallery to do the protecting? The honest answer is that watermarks are the wrong tool for most of what people use them for, and the right tool is usually a setting you already have.

This guide walks through when a watermark genuinely helps, when it just makes your work look worse, and how to actually keep client photos private using view-only proofing, password protection, search-engine privacy, and expiry. The payoff: galleries that look like finished work, not stock previews, while still being locked down exactly as much as the job requires.

What a watermark can and can't do

A watermark is a visible mark laid over an image, your studio name, a logo, a small overlay. It does one thing well: it makes a photo unpleasant to use as-is, which discourages casual screenshotting and re-sharing of unpaid or unselected work. That's it. It is a deterrent, not a lock.

What a watermark does not do is keep anyone out. The image still loads in the browser, so it can still be captured. A watermark also can't make a gallery private, can't keep it out of Google, and can't stop the link from being forwarded. Those are separate jobs handled by separate settings, and conflating them is where photographers go wrong, plastering logos over delivered finals as if that were security.

When to watermark (and when not to)

Match the decision to the stage of the job and what the client has actually paid for.

Good reasons to watermark:

• ·Proofing and selection rounds, where clients are choosing favorites before paying or before retouch. The files aren't finals yet, so a light mark signals 'preview' and protects work-in-progress.
• ·Public-facing or promotional previews, like a teaser gallery or a sample you'd link from social, where you want eyes on the work but not free full-res use.
• ·Commercial or licensed work where usage rights haven't been settled, and a visible mark reinforces that these frames aren't cleared for use.

Reasons to skip the watermark:

• ·Delivered finals the client paid for. They bought clean images; a logo across them reads as cheap and makes clients quietly resent the experience.
• ·Wedding and family galleries meant to be downloaded, printed, and shared with relatives. A watermark sabotages the exact thing the gallery exists to do.
• ·Any gallery where you've already restricted access another way. If the gallery is view-only or password-protected, the watermark is doing little except hurting how the work looks.

If a client paid for the photos, a watermark isn't protection, it's an apology you didn't owe them. Protect the proofs, deliver the finals clean.

View-only proofing: the better deterrent

For previews and selection rounds, the cleanest setup is often to turn downloads off entirely rather than rely on a stamp. In Capturely, a gallery can be view-only: clients browse the full-screen cover, the justified-grid viewer, and the lightbox, and they heart photos to build their selection, but there's no download button. You can add an optional watermark on top of view-only for an extra layer of 'this is a proof, not a final.'

This pairs naturally with how proofing already works. The client's first action asks their name, then they favorite the frames they want; you can set an optional pick limit so a 'choose 30' package stays at 30, and per-photo comments let them flag a crop or a blink. When selections are locked and paid, you flip the same gallery to allow full-resolution downloads, single photos or a whole-gallery zip, and the watermark comes off the finals. Per-photo download counts then tell you what's actually being saved.

1. Upload the shoot and share the gallery link, no client account required.
2. For the selection round, set the gallery view-only, optionally with a watermark, and an optional pick limit.
3. Client favorites their picks and leaves comments; you get notified.
4. After payment and retouch, enable downloads so they grab clean full-res files or the zip.

Password protection and search-engine privacy

This is the part that actually keeps photos private, and it has nothing to do with watermarks. Two settings carry most of the weight.

First, Capturely galleries are not indexed by search engines by default. A gallery link won't surface in Google results just because it exists, so a private family shoot or an unreleased commercial set isn't one search away from strangers. You don't have to configure anything to get this baseline.

Second, adding a password makes a gallery private. For sensitive work, an NDA-bound commercial job, a boudoir session, anything you wouldn't want a forwarded link to expose, the password is the real gate. And importantly, expired or password-protected galleries are never indexable, so the two privacy layers reinforce each other rather than leaving gaps.

• ·Default: not indexed by search engines, so links don't show up in search.
• ·Password set: the gallery is private, only people with the password get in.
• ·Expired or password-protected: never indexable, full stop.

Expiry: privacy you don't have to remember

The photos that leak are usually the ones nobody's watching, old galleries sitting live years after the job closed. Self-deleting galleries fix that by design. In Capturely you can have a gallery auto-delete anywhere from 7 days to 1 year, on a custom date, or keep it forever when a client genuinely needs long-term access.

When a gallery self-deletes, it's a permanent removal of the gallery and the originals, which is good for both privacy and lean storage, and the client gets a reminder email before it happens, a last chance to download. Expiry is the quiet hero of photo protection: a gallery that no longer exists can't be screenshotted, scraped, or surfaced in search.

Putting it together: a simple protection playbook

Here's how the pieces map to common jobs. Read the Capturely column as exactly what the platform does; for any other tool, check the current behavior on its own site, since privacy and watermarking options vary widely.

The throughline is simple. Watermarks belong on previews and proofs, not on the photos a client paid for. Real privacy comes from view-only delivery, passwords, search-engine privacy by default, and expiry, settings that protect the work without making it look protected. Get those right and you rarely need to stamp a logo on anything you're proud of.