Watermarking for photographers
Photographers don't have one watermarking problem, they have four, and they need opposite settings.
The four jobs
Client proofs — the whole point is that they're unusable until paid for. Tiled, diagonal, 50–70% opacity, right across the frame. It should look slightly annoying. That's the product.
Portfolio and promotion — the image has to sell you. Subtle, 25–35%, ideally embossed so it reads as a signature rather than a sticker. Placed over a subject edge, not out in a corner where it crops off.
Delivered client galleries — often no watermark at all, or a small discreet credit if the client agreed. Check the contract; a couple who paid for their wedding photographs generally did not agree to your logo on them.
Social — assume it will be reposted without credit. Keep the mark in the central third so a crop or screenshot still contains it, 30–45%, legible at thumbnail size.
Four different treatments over the same shoot. Which is why doing it by hand doesn't scale, and why saved profiles matter more than any individual feature.
The metadata problem, which is worse than it looks
You fill in copyright, creator and contact in Lightroom on import. Good.
Then you export, watermark, and publish — and a lot of watermarking tools decode the image, draw on it, and re-encode. Nothing carries IPTC, XMP or EXIF across unless the developer wrote code to do it.
So the published file has your visible watermark and no embedded copyright at all. The visible mark comes off in seconds with any inpainting tool. Underneath it is a file that says nothing about who made the picture.
That matters concretely:
- Stock agencies read IPTC on ingest. Missing creator and copyright means rejection or manual correction.
- Image search and CMS credit lines populate from embedded rights data.
- AI training opt-out — the IPTC/PLUS
plus:DataMiningproperty lives in XMP, in the file. - In a dispute, an intact copyright notice is evidence of a deliberate claim.
TSR Watermark Image preserves EXIF, XMP and IPTC on every paid edition; GPS, ID3 and several hundred further tag groups on Share editions and above.
Whatever you use, test it — there's a two-minute method in Your watermarking tool is deleting your copyright info.
Client work you shouldn't be uploading
This is the one that catches people out.
A wedding shoot before the couple has seen it. A commercial job under embargo. Anything with an NDA. If you run those through a browser-based watermarking service, the files go to a third party's servers.
Most such services are run by decent people and say they delete your files. But if your contract says the work is confidential until delivery, uploading it is a breach whether or not anything goes wrong. And if the images contain identifiable people and you're processing them for a client, GDPR makes that service a sub-processor — which normally needs the client's authorisation and a written agreement.
An installed application avoids the question entirely. Disconnect the network, watermark 500 files, watch it finish. That's a thing you can demonstrate to a client who asks.
Being fair: not every online tool uploads. Some process entirely in your browser and genuinely don't. But that's a claim about code you can't audit, in a page that can change, and it isn't something you can show anyone.
Volume
Wedding: 600–1,200 files. A season: tens of thousands. Archive digitisation: more.
Watch for tools that build the whole job in memory before starting — they're fine at fifty images and die at five thousand, usually two hours in. One of our customers ran over 8,000 TIF files in a single pass after another vendor's support told them out-of-memory on large batches was "normal".
Test any trial against your largest real folder, not a sample.
Making it stop being a job
Once the settings are right, save them and never open the interface again:
WatermarkImage.exe "C:\configs\proofs.wmi"Loads the profile, runs the batch, exits. Put it in Task Scheduler, or on the end of the script that already moves files off cards.
Build one profile per job type — proofs.wmi, portfolio.wmi, social.wmi — and running a job becomes one line each.
On Professional + Share, the run can finish by uploading straight to WordPress or FTP, so portfolio images go from export folder to live site with nothing in between. Secure Share adds secure FTP.
Your originals
Watermarking is irreversible. If you overwrite a source file, the clean version is gone.
TSR Watermark Image refuses to accept your source folder as the destination — not a warning, a refusal. Several people have told us this saved them.
Keep the clean full-resolution originals with capture metadata intact. In any dispute, producing the original when the other party can't is the strongest position you can be in.
Feature checklist for photographers
- Batch with no image limit; flat memory use at thousands of files
- Size as a percentage of output, so mixed portrait/landscape comes out consistently
- EXIF auto-rotation, so nothing arrives sideways
- EXIF, XMP and IPTC preserved
- Tiling, horizontal, vertical, diagonal — for proofs
- 3D / embossed marks derived from the image itself — for portfolio
- Dynamic text: EXIF values, filename, or an incrementing serial number
- Multiple watermarks per image, independently placed
- Multipage TIF for scanned work
- Resize and output format in the same pass — JPEG, TIFF, PNG, BMP, GIF
- Directory structure preserved, or flattened
- Runs offline; nothing uploaded
- Command-line automation
TSR Watermark Image: $29.95 Professional, $59.95 with WordPress/FTP publishing, $139.95 with secure FTP. One-time payment, licensed to you rather than a machine — desktop, laptop and the studio machine on one purchase. 90-day money-back guarantee.
Download the free version → — it's the full application; a key removes the trial stamp.