Text Watermarking and the Detectability Tradeoff
How a statistical signal is embedded in generated text by biasing the sampler, the detection test that makes it verifiable, and the reasons the scheme survives paraphrase poorly.
Watermarking an image is a well-understood problem: an image has enormous redundancy and a signal can be hidden in it. Text has far less room. Every token is semantically load-bearing, so a watermark has to live in the choice among acceptable tokens rather than in imperceptible modifications to the content.
The green list scheme
The most influential construction (Kirchenbauer et al., 2023, arXiv:2301.10226) works as follows. At each generation step, hash the preceding token, or a small window of preceding tokens, with a secret key to seed a generator. Use it to partition the vocabulary pseudorandomly into a green list of fraction \(\gamma\) and a red list. Add a bias \(\delta\) to the logits of green tokens before sampling.
The model still produces fluent text, because at most positions many acceptable tokens exist and the bias just tips the choice among them. But the output now contains more green tokens than chance would give.
Detection needs only the key and the text. Recompute the green list at each position and count green tokens. Under the null hypothesis of unwatermarked text, the count is binomial with probability \(\gamma\), so the \(z\)-score
for \(T\) tokens gives a test with a controllable false positive rate. This is a genuine statistical test rather than a classifier, which is why it can give calibrated \(p\)-values instead of an opaque confidence score.
What the parameters trade
\(\delta\), the bias strength, trades detectability against quality. Large \(\delta\) makes the watermark strong and forces the model away from its preferred tokens, degrading output measurably. Small \(\delta\) preserves quality and needs more tokens to detect.
\(\gamma\), the green fraction, controls how much of the vocabulary is favoured. Smaller \(\gamma\) gives a stronger per-token signal and a heavier constraint.
Text length is the parameter that matters most in practice. Detection power grows with \(\sqrt{T}\), so a few hundred tokens is comfortable and a tweet-length output is close to undetectable at any quality-preserving bias. This is a hard limit rather than an implementation weakness: there is not enough entropy in short text to carry a reliable signal.
Low-entropy text is the same problem in a different form. A factual answer, a code completion with one correct continuation, or a quotation has few acceptable alternatives, so the sampler has no freedom to encode anything. Watermarks are weakest exactly where the model is most constrained, which includes much of the output people most want to attribute.
When it breaks
Paraphrase removes it. Rewriting the text, whether by a human or by another model, resamples the token choices and destroys the green-list statistics. This is the decisive practical limitation, and it costs an attacker one cheap model call. Schemes based on semantic rather than token-level features are more robust and correspondingly harder to make precise.
It requires provider cooperation and key management. Only the generating provider can watermark, and detection requires the key. A public key means anyone can detect and anyone can also test candidate outputs to find and remove the signal; a private key means detection is a service, with the trust and access implications that follow.
Absence proves nothing. A negative detection is consistent with human writing, with a different model, with an unwatermarked configuration, or with successful removal. The test supports a positive claim and cannot support a negative one, and using it as evidence that text is human-written is a misuse that has already caused harm in education.
False positives at scale are consequential. A one in ten thousand false positive rate across a million documents is a hundred wrong accusations. The threshold has to be set against the volume and the cost of being wrong, and defaults chosen for a research evaluation are rarely right for deployment.
16 flashcards for this concept
Click a card to reveal the answer.