Workflow & Automation

Watermarks That Protect Without Ruining the Picture

A signature and a fence are different jobs, and they need different designs.

A watermark will not stop a determined thief. It will keep your name attached to work that travels, and that is worth designing properly.

A batch watermark dialog with a position grid and opacity controls

There are two kinds of watermark. One is a signature: small, quiet, there so that a picture travelling around the internet keeps a thread back to whoever made it. The other is a fence: large, obtrusive, there to make the image useless until somebody pays. They are different jobs and they need different designs, and most of the bad watermarks in existence are one job done with the other’s tools.

Decide what you are actually protecting against

Be honest about the threat. A watermark does not stop a determined thief; software has been able to reconstruct what is behind a mark for years. What it does do is:

  • make casual reuse slightly awkward, which stops most of it
  • keep your name attached when an image is screenshotted, reposted and stripped of every other trace
  • mark a proof so it cannot be mistaken for the final file

Those are real and worth having. What a watermark cannot do is prevent theft, and designing as though it can is how you end up with a picture nobody wants to look at, including the people you hoped would hire you.

Where to put it

The corner is the default and it is defensible: it is out of the way, it is conventional, and readers ignore it in the way they ignore a page number. Its weakness is equally obvious: a corner crops off in two seconds.

If crop resistance matters, you have three options, in ascending order of aggression.

Off center, over the subject. A single mark placed where it overlaps part of the actual content cannot be removed by cropping without removing the reason the picture exists. Keep it small and low contrast and it is remarkably unobtrusive.

Tiled across the whole frame. A repeating pattern at low opacity, usually rotated so it does not line up with anything in the picture. This is the proof watermark, and it is deliberately annoying, which is its function. Rotation matters: a mark at a slight angle is much harder to remove cleanly than one aligned to the frame.

A bar across the image. Honest, ugly, effective. Reserve it for cases where the image genuinely must not be usable.

A batch watermark dialog with a position grid and opacity controls
Position, size and opacity decided once, then applied to a whole selection. Doing this per image is why it usually gets skipped.

The design details that decide whether it is bearable

Opacity is not the only lever

Everyone reaches for opacity first, and a mark at 30 per cent still sits on top of the picture as a foreign object. Two things work better in combination.

The first is blend mode. A white mark set to overlay or soft light interacts with the tones underneath instead of covering them, so it stays visible on both light and dark areas without ever looking pasted on. The second is a subtle shadow or outline, one or two pixels, which is what keeps a light mark readable when it crosses a bright area.

Size, relative to the frame

A signature mark should occupy somewhere between five and ten per cent of the image width. Smaller and it vanishes on a phone; larger and it becomes the subject. Because it is relative, it must be recalculated per image, which is exactly the kind of arithmetic worth handing to software.

Contrast against unpredictable backgrounds

The problem with a fixed watermark is that it lands on a white sky in one photograph and a black jacket in the next. Pure white with a soft dark shadow survives both. Pure black almost never does.

Vector, not raster

If your mark is a logo, use the vector version. A raster logo scaled up on a large image goes soft, and a soft watermark reads as sloppy rather than subtle.

Do not touch the original

The most expensive watermark mistake has nothing to do with design: overwriting the original file. It happens constantly in batch operations, and it is not recoverable.

Always output to new files. Keep unmarked originals in a place your publishing workflow cannot reach by accident. If your tool offers versioned overwriting rather than plain overwriting, that is the option you want, and you should still keep the originals separately.

The question to ask of any batch operation is not “will this work” but “what happens if it works on the wrong folder”.

A brand kit holding colors, fonts, a logo and a watermark
The mark belongs with the rest of the brand, in one place, so the version applied in a batch is never a slightly different one.

Metadata is the invisible watermark

Every image file can carry embedded information: author, copyright, contact details, license. It costs nothing, it is invisible, and it survives resizing and re-encoding.

It does not survive a screenshot, and many platforms strip it on upload, so it is not a replacement for a visible mark. But it is the thing that lets someone who wants to license your work find you, and it takes one field in a batch operation to apply it to everything you export. Filling it in is close to free and skipping it is close to universal.

A workflow that survives contact with reality

  1. Design one mark, as a vector, with a light version and a dark version.
  2. Decide two presets: a signature for published work, a tiled proof mark for anything shown before payment.
  3. Apply them as a batch operation, positioned proportionally rather than at fixed pixel coordinates.
  4. Write copyright metadata in the same pass.
  5. Output to new files, always.
  6. Look at ten results before running it on a thousand.

That last step is the one people skip, and it is the reason there are portfolios online with a watermark sitting neatly over somebody’s face in every third picture.

When not to watermark at all

For a great deal of work, the honest answer is that a watermark costs more than it saves. Photographs used as social proof, images on your own site, anything whose job is to be shared: a mark makes them slightly worse at their only task in exchange for protection against something that mostly does not happen.

Watermark the proofs. Watermark the work that travels without you. Consider leaving the rest alone, and put the effort into metadata, a decent filename and being easy to find instead.

Table of Contents

Learn it by building something

Every week one thing you can make the same afternoon, from dynamic templates to 3D type. Written down step by step.

One mail a week, and then it ends.
Unsubscribe in one click.

Free

Chaos Art

Autonomous painters make one-of-a-kind abstract art in 3D space - gestures, art movements, painterly media, and embeds that paint a new original for every visitor.

Download the free WunderPaint Plugin for WordPress

The Image Editor & Design Studio

Everything described here can be done in the browser, on your own site. The live demo runs the full editor with nothing to install.

Design Tools

Brush & Paint Styles

Paint with six styles that mix pigment instead of blending it, pick from thirty-seven tips shown as real strokes, draw a tip of your own out of shapes, and let the color travel along the stroke.

Workflow & Automation

Dynamic Templates: Build the Design Once, Let Your Posts Fill It In

You build the layout once, tell a few layers where to get their content, and from then on every post, product or page renders its own version.

Print & Craft

Making Things That Fold: Dielines, Duplex and Why Previews Matter

A gift box, a paper crane, a bunting banner. They look simple, and they fail in ways flat design never does, because there is a second geometry underneath.

WordPress Images

Why Should a Design Become a File at All?

Every static graphic on a page is a snapshot of what was true when somebody exported it. There is a whole category of quiet wrongness that follows from that.