Skip to main content
AI Watermark Removal

Research

Text Watermark Robustness: What Actually Survives an Edit

Robustness is the whole ballgame for a text watermark, because a mark that only survives untouched output traces nothing once people start rewording. Google says SynthID Text tolerates mild paraphrasing and weakens under thorough rewriting or translation. Four independent teams that tested it in 2025 and 2026 found a rockier picture, including 98.3% signal loss after one paraphrasing pass and no measurable advantage over a much older, simpler scheme. Neither side is lying, they are measuring different conditions, and the gap between them is the part worth understanding.

Published 2026-08-11Updated 2026-08-11Research/proposal

Key takeaways

  • Google documents SynthID Text as robust to milder paraphrasing, with detector confidence dropping sharply under thorough rewriting or translation, and scopes that claim to the Gemini app and web experience.
  • A Google-affiliated developer-forum reply dated 2026-08-05 states that text from the Gemini API is not SynthID-watermarked and that native text watermarking is not currently planned, contradicting Google's own SynthID page. No primary source has reconciled the two.
  • The clearest length figure in the literature: the original green-list scheme stayed statistically detectable after strong human paraphrasing once a detector had roughly 800 tokens, at a 1-in-100,000 false-positive rate.
  • Independent 2025-2026 audits of SynthID Text found real cracks: resilience no better than a far simpler older watermark under paraphrase and translation, 98.3% signal loss after one DIPPER-style paraphrase pass, and a 5.4% false-positive rate on paraphrased human writing.
  • Unigram-Watermark fixes one green and red split for the entire generation instead of reseeding it from context, which its authors prove makes it robust to bounded editing. That is a genuinely different kind of evidence than an empirical stress test.
  • A widely cited 2023 paper argues on theoretical grounds that no scheme can be reliably robust against a motivated paraphrasing attacker, and a 2024 paper reverse-engineered a provider's secret rule for under $50 to push a scrubbing attack from near 0% to over 85%.
  • Surveys of the field, including a 2025 systematization-of-knowledge paper with Nicholas Carlini, Florian Tramèr, and Dawn Song among its authors, still list robustness against paraphrasing and editing as the central unresolved problem, not a solved one.

Robustness spectrum

How much editing does it take to lose the signal?

This maps Google's own robustness description for SynthID Text: mild edits can leave signal intact, while thorough rewriting or translation greatly reduces detector confidence. It is not a claim that any exact edit threshold is documented; the boundary between "mild" and "thorough" is not precisely defined by Google. Click a stage below for why it lands where it does.

Typo fix

Signal intact

Reformatting

Signal intact

Mild paraphrase

Uncertain, may partly survive

Thorough rewrite

Confidence greatly reduced

Translation

Confidence greatly reduced

An early, unreplicated data point

A 2026-07-17 AIES preprint using an independent SynthID Text reimplementation (MarkLLM) reported that 98.3% of initially-detected watermarked texts lost their signal after DIPPER-style paraphrasing, with a 5.4% false-positive rate flagging paraphrased human text as AI-generated. This is early-stage, not peer-reviewed, and not independently replicated. It is reported here as a data point from ongoing research, not as an established measurement of SynthID Text's real-world robustness.

What Google claims, and where the claim stops

Official announcement

You'll see exactly what Google promises for SynthID Text, and the one place its own sources contradict each other.

Google documents SynthID Text as robust to milder paraphrasing, with detector confidence greatly reduced by thorough rewriting or translation. The claim is scoped to the Gemini app and web experience, not to everything Google ships.

Then it gets strange. A Google-affiliated reply on Google's own developer forum, dated 2026-08-05, answering a question about Article 50(2) of the EU AI Act, says flatly that text generated through the Gemini API is not SynthID-watermarked and that native text watermarking is not planned at the moment.

That conflicts directly with the DeepMind SynthID page, which says SynthID watermarks text generated by the Gemini app and web experience. Nobody at Google has reconciled the two in a primary source.

How much text a detector actually needs

Research/proposal

Here's the one number to carry around: how much text has to survive before a detection result means anything at all.

The clearest data point comes from Kirchenbauer and coauthors' follow-up study, "On the Reliability of Watermarks for Large Language Models" (ICLR 2024). They stress-tested the original green list and red list scheme against three things:

  • Human rewriting, where real people reworded the text themselves
  • LLM paraphrasing, where another model did the rewriting
  • Dilution, where watermarked text was mixed into a longer human-written document

Even after strong human paraphrasing, the watermark stayed detectable once a detector could observe roughly 800 tokens, at a false-positive rate of 1 in 100,000.

Length matters because the signal is probabilistic. One sentence carries a faint tilt toward green tokens that a few rewritten words can erase, while hundreds of tokens accumulate into a pattern a statistical test can separate from chance.

Four independent audits, four different cracks

Research/proposal

You'll get what each outside team actually found when it tested SynthID Text, plus the caveat that applies to all four.

Google's robustness claim rests on Google's own testing. Four independent teams have since run the experiment themselves, and the answers do not all agree with the product page.

  • "Watermark under Fire" (EMNLP 2025 Findings, from Stony Brook, NUS, and Zhejiang University) tested SynthID Text under paraphrase and translation attacks and found its resilience "similar to the TGRL baseline," meaning no clear advantage over a far simpler, older watermark.
  • SynGuard (Han, Li, Ni, and Zulkernine, IEEE TrustCom 2025) found SynthID Text "susceptible to meaning-preserving attacks, such as paraphrasing, copy-paste modifications, and back-translation," and their own hybrid beat it by an average of 11.1% on the F1 metric.
  • A March 2026 preprint from Illinois Tech researchers went after the detector's math, proving that SynthID Text's mean-scoring detection grows more vulnerable as tournament sampling layers are added, while the alternative Bayesian-scoring detector Google itself built in is provably more robust to that attack.
  • An AIES 2026 preprint from July 2026 reported 98.3% of initially detected texts losing their signal after one DIPPER-style paraphrase pass, a 5.4% false-positive rate on paraphrased human writing, and the lowest composite "Forensic Readiness Score" (35 out of 60) of the three schemes it tested.

None of the four claims to have broken Google's production deployment. All of them test the open-sourced algorithm or reimplementations like MarkLLM, not the real Gemini keys and configuration, which Google has never published.

That cuts both ways. Google's own robustness claim has never been independently verified against production either.

The one scheme with a proof attached

Research/proposal

Here's what it takes to move from "we tested it" to "we proved it," and what that proof costs the design.

Zhao, Ananth, Li, and Wang's Unigram-Watermark (ICLR 2024) fixes the green list and red list split across the whole vocabulary for an entire generation, instead of reseeding it at every position from prior context.

That constant split is what makes a mathematical guarantee possible. The authors prove the scheme stays robust to editing as long as the number of edited tokens stays under a bounded threshold relative to text length.

Schemes that reseed from context fall out of sync the moment an edit changes what came before, because the detector and the generator stop agreeing on which tokens count as green. A fixed split has no such failure mode.

The argument that robustness has a ceiling

Research/proposal

You'll see why one widely cited paper says engineering can't close this gap, and the $50 result that gave the argument teeth.

Step back from any single scheme and a 2023 paper by Sadasivan, Kumar, Balasubramanian, Wang, and Feizi makes a harder claim: no watermarking scheme, however clever, can be reliably robust against a sufficiently motivated paraphrasing attacker.

They pair a recursive paraphrasing attack with a theoretical bound on how close human and AI text distributions can get. Push those distributions close enough together and detection reliability hits a ceiling that engineering alone cannot lift. It is the single most-cited adversarial paper in this space.

Watermark stealing research gives that argument teeth. Once a provider's secret green-list rule was approximated for under $50 in ordinary API queries, a scrubbing attack that barely worked (near 0% success) jumped past 85% against the reconstructed rule.

Robustness proofs describe what a scheme guarantees against a defined class of edits. They say nothing about what happens after the rule leaks.

Why the field still calls this unsolved

Research/proposal

Here's how the people who survey this literature for a living rate the state of play.

A 2025 systematization-of-knowledge paper, "SoK: Watermarking for AI-Generated Content," comes from a security-heavy author list including Nicholas Carlini, Florian Tramèr, and Dawn Song. It maps threat models across text, image, audio, and video watermarking and ties the state of the art to regulatory content-provenance requirements like the EU AI Act.

Alongside the ACM Computing Surveys review and the ACL Anthology's taxonomy, all three list paraphrasing, translation, and adversarial editing as attack categories no scheme fully closes.

They also note that gains against one attack usually cost something elsewhere. Everything above is real progress on specific schemes under specific attacks, not a general solution.

FAQ

Does robustness mean a watermark can't be removed?

No. It means the signal is designed, and in a few proposed schemes proven, to survive certain transformations under tested conditions. That is a much narrower claim than being impossible to remove.

How much text does a detector actually need to catch a paraphrased watermark?

For the original green list and red list scheme, one study found detection held after strong human paraphrasing once roughly 800 tokens were available, at a false-positive rate of 1 in 100,000. That figure describes one scheme under one attack in a research setting, not a guarantee for every watermark in production.

Does Google's robustness claim for SynthID Text cover the Gemini API too?

Not clearly. Google documents the claim for the Gemini app and web experience specifically. A Google-affiliated developer-forum reply dated 2026-08-05 says the API does not apply SynthID Text and that native text watermarking is not currently planned, which contradicts Google's own SynthID page, and no primary source has resolved it.

Have independent researchers actually tested SynthID Text, or is it just Google's word?

Four teams have tested it, and the results were rockier than the product page suggests: no clear advantage over a much older watermark under paraphrase and translation, a detector-math weakness that worsens as tournament layers increase, 98.3% signal loss after one paraphrasing pass, and a 5.4% false-positive rate. All of it tests the open-sourced algorithm or public reimplementations, never Google's production configuration, which has never been published.

Next steps

Sources and citation status