Screenshot protection in client galleries: what it can and can't do

A client opens the proofing gallery, loves the portraits, and instead of choosing favourites takes a screenshot. Most photographers who deliver proofs online have seen some version of this.

Phone screenshots are sharp, and there are AI tools built to strip watermarks from images. Gallery platforms have responded with screenshot deterrents and with watermark features meant to resist those tools.

So what does screenshot protection actually buy you? And where does it stop?

What protection can do

Gallery protection works by adding friction and by making the difference between a preview and a final file obvious.

Preview size is the quiet layer. If the gallery shows screen-sized previews instead of full-resolution originals, a quick save or capture gives the client a file made for a screen, not for print.

Browser deterrents are the second layer. Galleries commonly block the usual "Save image" route, and some react to screenshot shortcuts on a computer, for example with a short reminder that the images are proofs.

Watermarks are the third. A mark across the preview tells everyone, the client included, that this is not the purchased file. With AI removal tools around, treat a watermark as a label rather than a lock.

What it cannot do

Vendors are unusually candid here. Read the fine print of the gallery platforms that sell screenshot and watermark protection, and the same point keeps coming back: no feature can guarantee that a photo will never be copied. Even features built specifically to resist AI watermark removers come with a note that protection is not guaranteed. PixiProof's own security page says the same: no solution eliminates 100% of every copy path on the internet.

Take that at face value. If an image can be seen on a screen, it can be photographed with another device. Software can slow down the casual screenshot. It cannot stop a second phone.

Match protection to the gallery's purpose

Not every gallery needs every restriction. What the gallery is for, and whether the client has already paid, should decide the settings.

In practice that often looks like this:

• Unpaid proofing gallery. Screen-sized previews, a visible watermark if your pricing depends on selling individual images, browser friction on.
• Final delivery gallery. A lighter watermark or none. The client has paid; heavy marks now only get in the way.
• Newborn, family and other private sessions. Here protection also protects the people in the photos. Parents may care about that as much as you care about sales.

Two habits help more than any setting:

1. Say it before the link goes out. One line in the welcome message: previews are for choosing, final files come after selection. A client who knows the preview is not the file they are paying for has less reason to screenshot it.
2. Give them a legitimate shortcut. If a client wants one photo for social media today, a clear way to get a proper file after selection or purchase removes most of the temptation.

How PixiProof handles it

PixiProof takes the same honest line. The watermark on previews is optional, and you can set an account default or a watermark for a specific gallery. Clients see previews sized for their screen, not full-resolution originals. Saving from the browser menu is harder, and so are casual screenshots: "still possible, but noticeably more difficult." When a client presses a common screenshot shortcut on a computer, the gallery shows a short note that these previews are not the final files. It does not stop a phone camera pointed at the screen.

The full list is on the PixiProof security page, and the earlier post on how PixiProof protects your photos covers the deterrents in more detail.

FAQ

Can I completely stop clients from taking screenshots?

No. Deterrents make casual screenshots harder, but a client can always photograph the screen with another device. None of the gallery vendors whose documentation we read promises otherwise.

Are watermarks still worth using now that AI can remove them?

As a label, yes: a watermark marks the image as a proof and signals that it is not the purchased file. As a lock, no. Even the vendors that sell watermark features built to resist AI removers say protection is not guaranteed.

Should a final delivery gallery have a watermark?

Usually not. Once the client has paid for the files, a watermark mostly gets in their way. Keep the stronger settings for unpaid proofing.

How do I explain this to clients without sounding suspicious?

Keep it practical. Tell them the gallery holds working previews for choosing favourites and that the finished, full-quality files come after selection.

Next step: open the welcome message you send with your next proofing gallery and add one sentence on what the previews are for.