How to watermark photos before a client pays

You shot the photos. The client wants to see them. But you haven't been paid yet.

If you send clean, high-res images, the client might just use them and never pay. If you don't show anything, the client won't trust that the work is done. It's a standoff that photographers deal with on every single project.

Watermarks solve this. But not all watermarks are created equal.

Why watermarking matters

A watermark lets your client see the quality and composition of your photos without being able to use them commercially. It's the equivalent of a "try before you buy" that doesn't give away the product.

Without watermarks, your only options are:

• Send full-resolution photos and hope the client pays (risky)
• Send tiny thumbnails that don't show the quality (frustrating for the client)
• Refuse to show anything until payment (kills trust)

Watermarks hit the sweet spot. The client can verify the work, approve selects, and feel confident about paying. You retain control of the originals.

CSS overlay vs baked-in watermarks

This is the part most people get wrong.

CSS overlay watermarks (don't do this)

A CSS overlay puts a semi-transparent text or image on top of a photo using HTML and CSS. The actual image file underneath is completely clean. Anyone with basic browser knowledge can:

• Right-click and save the original image
• Open developer tools and hide the overlay
• Disable CSS entirely
• Take a screenshot (but at least this gives lower quality)

CSS watermarks look like protection but provide almost none. They stop honest people. They don't stop anyone who spends 10 seconds in their browser's dev tools.

If your proofing gallery uses CSS overlays on full-res images, your photos are essentially unprotected.

Baked-in watermarks (the right way)

A baked-in watermark is burned directly into the image file itself. The watermark is part of the pixel data. You can't remove it by inspecting CSS or right-clicking. Removing it would require advanced photo editing, and if the watermark is placed well, even that won't produce a usable result.

Best practices for baked-in watermarks:

• Place across the subject. A watermark in the corner can be cropped out. Put it across the center or across the subject of the photo.
• Use semi-transparent text or your logo. Visible enough to prevent use, subtle enough to not ruin the preview experience.
• Lower the resolution of preview images. Even if someone manages to edit out the watermark, a 1200px wide preview is useless for print or large-format use.
• Apply consistently. Every preview photo should be watermarked. One clean image in a gallery of 200 is all a client needs to skip payment.

How to watermark your photos (tools and workflow)

Lightroom

Adobe Lightroom has built-in watermark support on export. You can create text or graphic watermarks, position them, adjust opacity, and apply them to batch exports. This is probably the most common method for photographers.

Export workflow: select photos, choose export settings, enable watermark, set position to centered or tiled, export as JPG at reduced resolution.

Photoshop batch actions

Create an action that adds your watermark layer, flattens, and saves. Then run it as a batch on your entire delivery folder. More manual than Lightroom but gives you full control over placement.

Dedicated watermark tools

Tools like Visual Watermark, uMark, or even the free command-line tool ImageMagick can batch-process watermarks. Good if you don't use Lightroom or Photoshop.

Let FileCheckout handle it

FileCheckout automatically generates blurred previews for uploaded images. You don't need to create separate watermarked versions yourself. Upload the clean originals, set your price, and share the link. Clients see protected previews. When they pay, they get the clean high-res files.

This saves you the entire watermarking step. No batch exports. No managing two sets of files. Upload once and let the platform handle preview protection.

The full workflow for paid photo delivery

Here's what a solid process looks like:

1. Shoot and edit as normal
2. Upload final files to FileCheckout (or your preferred delivery tool)
3. Set the price for the delivery
4. Share the link with your client
5. Client reviews previews and confirms the photos look good
6. Client pays via credit card
7. Files unlock for immediate download

No separate invoice. No emailing watermarked proofs, then waiting, then sending another link, then waiting again. One link handles previews, payment, and delivery.

Common mistakes photographers make

• Watermark in the corner only. Easily cropped out. Always cover the subject area.
• Sending full-res previews. Even watermarked, a 6000px image gives the client more than they need. Export previews at 1200-1600px for web proofing.
• Using CSS overlays on a proofing site. Looks professional, protects nothing. Always use baked-in watermarks or server-generated blurred previews.
• Only watermarking some photos. If you watermark 95% of a gallery, the client will find the 5% that aren't protected.
• Making watermarks too aggressive. A giant opaque logo plastered across every image makes it hard for the client to evaluate the work. Find the balance between visible and viewable.

Frequently asked questions

What's the best way to watermark photos before sending to a client?

Use baked-in watermarks, not CSS overlays. Lightroom's export watermark feature is the fastest for most photographers. Place the watermark across the subject (not in a corner), use semi-transparent text or your logo, and export at reduced resolution. Or use FileCheckout to skip watermarking entirely and let the platform generate protected previews automatically.

Can clients remove watermarks from photos?

CSS overlay watermarks can be removed in seconds using browser dev tools. Baked-in watermarks are much harder to remove. Well-placed watermarks that cross the subject require significant Photoshop skill to eliminate cleanly. Combined with reduced resolution, this makes unauthorized use impractical.

Should I send low-res or watermarked previews to clients?

Both. The best approach is watermarked AND reduced resolution. Watermarks prevent direct use. Lower resolution (1200-1600px) prevents upscaling for print. Together they give the client enough to evaluate quality while keeping your full-res originals protected.

How do I get clients to pay before downloading photos?

Lock the files behind payment. Upload your photos to FileCheckout, set a price, and share the delivery link. Clients see blurred or watermarked previews and can only access the originals after paying via Stripe. Payment and delivery happen in one step.

Are CSS watermarks on gallery sites secure?

No. CSS watermarks are purely visual and don't modify the actual image file. Anyone who right-clicks, opens dev tools, or disables CSS can access the original image. If your proofing site relies on CSS overlays, your photos are not meaningfully protected. Always use baked-in watermarks or server-side image processing.