FoddoLearn
Chapter 1 of 13 · Start here · 7 min

Visible watermarks deter. Invisible IDs attribute.

Two different jobs. Visible marks make casual reposts ugly. Invisible per-subscriber IDs answer which copy escaped after a leak. Most creators need both, in different places.

Before you start

Your mission in this chapter

  1. Learn

    Separate deterrence from attribution before choosing a watermark.

  2. Try

    Tune opacity and placement, then compare public previews with paid full-resolution files.

  3. Prove

    You can name where each layer belongs and what it can prove.

Loading the interactive demo for "Visible watermarks deter. Invisible IDs attribute."… The lesson text below is already here. The hands-on part loads next (requires JavaScript).

Creators ask for the best watermark as if one setting covered every risk. It doesn't. You are solving two problems, deterrence and attribution, and each lives in a different file.

Play with opacity above. Then read where each layer belongs, because putting the wrong layer in the wrong place is how paid packs leak with zero recourse.

Where visible belongs

Public teasers, social previews, portfolio crops. Anywhere drive-by downloaders need friction. A tiled mark at 22-38% opacity stays readable through casual screenshots and signals ownership.

Weakness: one crop removes a corner mark. That is why tiling exists, and why the demo defaults to tiled.

Where invisible belongs

Full-resolution paid packs, one unique copy per subscriber. The files look identical on screen but carry different private IDs, and your delivery log maps each ID to a human.

Weakness: fragile methods die on re-encode. Chapters 3 to 5 cover that. It is a reason to pick the method carefully, not to skip invisible IDs.

The revenue rule

Visible without invisible: you discourage sharing but still guess after a leak. Invisible without visible: your marketing assets are frictionless to steal.

Use both layers. Deter in public, attribute in private.

Takeaways

  • Visible marks deter casual sharing but every subscriber gets the same pixels.
  • Invisible IDs look identical on screen yet carry a private recipient fingerprint.
  • Use visible on public teasers, invisible on paid full-resolution packs.

Check yourself

Optional, local, instant. 0/2 answered.

  1. A pack protected only by a tiled visible mark leaks. What can you prove?
  2. Where does each layer belong?

For your niche

Photographers

Tiled proofs for client galleries, invisible IDs on delivered full-resolution sets. A cropped corner must never be the whole story.

Subscription creators

Visible handle on public teasers, unique invisible copy per subscriber for paid packs. Teasers get copied; packs can be traced.

Illustrators & designers

Centered marks on portfolio pieces, invisible IDs on source files sent to clients. Watermarked previews close deals; traced originals protect them.

Demo transcript

Questions creators ask

Keep handyLearn glossary11 recurring terms
Carrier
The image content that offers texture or edges where a watermark can be tested.

A carrier estimate is not a survival result.

Delivery ID
An identifier for one particular delivery event or copy.

Keep it separate from the stable recipient ID.

DCT
A transform that represents image blocks as spatial-frequency coefficients.

The Learn visualization is illustrative.

LSB
Least-significant-bit hiding: changing the smallest binary bit of pixel values.

It is fragile under common re-encodes.

Metadata
Attached file information such as EXIF, GPS, software, color, and creation tags.

Metadata hygiene does not protect pixel payloads.

Payload recovery
Successfully reading the hidden identifier from the exact leaked file.

This is different from visual similarity or carrier capacity.

Re-encode
Decoding and saving an image again, often with a different format or quality setting.

It can change pixels, metadata, dimensions, and color behavior.

Recipient ID
A stable opaque identifier for the person or account receiving a copy.

Never recycle it between recipients or releases.

Release ID
An identifier for a batch, edition, or release of content.

One recipient may receive multiple releases.

Similarity
A visual or perceptual comparison suggesting whether two files resemble each other.

It is triage, not attribution.

Stable map
A validated delivery record connecting a recovered ID to one unambiguous recipient.

Duplicate IDs break attribution.