Skip to content
Safety

Watermarking

Embedding a detectable statistical signal into AI-generated output at the moment it is created, so that a verifier holding the key can later confirm it came from that model.

Why it matters

Watermarking is the technically sound answer to the question AI detectors try to answer by inference, and understanding why it has not settled the matter tells you a lot about the state of the field — it needs provider adoption, survives rewriting poorly, and does nothing about models people run themselves.

A concrete example

Think of it as a signature woven into the fabric rather than a label stuck on afterwards. It is checkable and hard to fake, but only present if the manufacturer wove it in — so it says nothing at all about a garment made on someone else's loom, which is the position with any open-weight model.

How to use it

Watermarking is the technically sound alternative to statistical detection: the model biases its word choices at generation time in a pattern a verifier can later recognise. Where it is implemented it is far more reliable than inferring from statistics after the fact. The reasons it has not settled the question are practical — it requires the provider to implement it, it survives paraphrasing poorly, it does nothing about open-weight models anyone can run unmodified, and it needs an agreed way to verify.

The common mistake

Assuming a detector benefits from watermarking. Almost none do: a watermark can only be checked for output from a model that embedded one, which is a small share of what people actually use, and a tool that examines arbitrary text is doing statistical inference regardless of what its marketing implies.

Related terms

Put Watermarking into practice

Access 750+ AI models and 60+ tools through Vincony — start free with 100 credits.