Skip to main content
AI Watermark Removal

Core topic

AI Watermark Removal: What It Can and Cannot Mean

AI watermark removal is not one technical problem. It is at least four, aimed at four different mechanisms, with wildly different odds of working. Stripping file metadata, altering pixels, rewriting text, and defeating a statistical signal are separate jobs, and treating them as interchangeable is how removal claims end up sounding far more confident than the research behind them.

By ignacio-sjPublished Revised Research/proposal

Correction,

Until October 6, 2026 the overview of the Gemini section said Google's developer forum "says API text is not" watermarked. That was the forum's 2026-08-05 answer, which the same account retracted on 2026-08-19. The overview and the section's conclusion now give both posts and say no Google documentation covers API text.

All corrections

Key takeaways

  • Do not assume any AI output carries a removable watermark until you know the source system and the watermark type. C2PA metadata, invisible media watermarks, and statistical text watermarks fail for entirely different reasons.
  • The strongest published research on actually defeating a watermark is a stealing attack: ETH Zurich's SRI Lab approximated a provider's secret watermarking rule for under $50 in ordinary API queries, then used it to push scrubbing success from near zero to over 85 percent (Jovanović et al., ICML 2024).
  • That result targets research reimplementations of green-list, red-list watermarking, not a confirmed production configuration from Anthropic, OpenAI, or Google. It proves a real technique exists, not that a consumer bypass exists.
  • Robustness cuts both ways: the team behind the original green-list watermark found the same scheme still statistically detectable after strong human paraphrasing once roughly 800 tokens have been generated, at a false-positive rate of one in 100,000.
  • Media watermarking is the settled half of the picture. OpenAI documents C2PA and SynthID on its images, and Google documents SynthID across images, audio, and video without real dispute. Text is where providers diverge sharply, and even one provider's own pages can conflict.
  • Nobody, including well-funded academic red teams, has published a peer-reviewed method that reliably strips a production text watermark from Claude, ChatGPT, or Gemini while preserving what the text actually says.

Removal difficulty by signal

Four different jobs, four different odds

Metadata

Easiest thing in the world to lose, often with nobody trying to remove it.

Media watermarks (pixels, audio)

Built tougher, but leak in documented, repeatable ways.

Text watermarks

Bend under heavy rewriting well before most of them fully break.

Why one number for "removal" is misleading

Bar length here stands for relative difficulty, not a measured percentage. Treating removal as one problem instead of at least four, aimed at four different mechanisms, is how removal claims end up sounding far more confident than the research behind them.

What does AI watermark removal actually mean?

One phrase, four unrelated jobs: erasing a visible label, stripping metadata, defeating a pixel signal, rewriting text. A tool built for one does nothing for the others.

People typing "AI watermark removal" want at least four different things.

  • Erase a visible label burned into an image.
  • Strip file metadata such as a C2PA manifest.
  • Defeat an invisible provenance signal hidden in pixels or audio.
  • Rewrite text until a detector stops flagging it.

These are not variations on one task. They are four attack surfaces against four mechanisms, and a tool built for one does nothing for the others.

A metadata cleaner never touches a pixel-level watermark. Rewriting text does not prove a statistical watermark was ever there in the first place.

And a high detector score was never a watermark to begin with. It is a guess about writing style, not a decoded signal. Confusing these categories is the single biggest reason removal claims online sound more confident than the technology they describe. The basics of AI watermarking explain what each mechanism is.

Did researchers really break a text watermark for $50?

Research/proposal

The best published removal attack cost under $50 and pushed scrubbing past 85 percent. Its target was a research reimplementation, which is exactly where it stops.

Jovanović, Staab, and Vechev showed at ICML 2024 that an attacker can approximate a provider's secret green-list rule using only public API queries, for under $50.

That approximation powered scrubbing attacks that jumped from near-zero success to over 85 percent in configurations "previously believed safe," alongside spoofing attacks that forged the watermark onto attacker-written text more than 80 percent of the time.

The limit lives in the setup. The target was a research implementation of green-list, red-list watermarking, not a confirmed production configuration from Anthropic, OpenAI, or Google.

So it proves a real technique exists. It does not prove a consumer bypass exists.

Does paraphrasing remove an AI text watermark?

Research/proposal

Two serious labs, opposite conclusions on whether paraphrasing defeats a watermark, roughly 800 tokens sitting between them, and three independent SynthID Text evaluations that lean toward signal loss.

The published research does not agree, because robustness depends on the scheme, the length of the passage, and how much work an attacker is willing to do. Kirchenbauer's team, the same group behind the original green-list watermark, found their scheme still statistically detectable after strong human paraphrasing once roughly 800 tokens have been generated, at a false-positive rate of one in 100,000.

Sadasivan and coauthors argue close to the opposite in the most-cited attack paper in the field: no watermark or detector holds up against a sufficiently motivated, sufficiently thorough rewriter.

Independent red-teaming lands in between. Han, Li, Ni, and Zulkernine tested Google's open-sourced SynthID-Text algorithm, not Google's actual production configuration, and found it "susceptible to meaning-preserving attacks, such as paraphrasing, copy-paste modifications, and back-translation."

Two more independent evaluations of SynthID Text point the same way. An EMNLP 2025 paper found its resilience to paraphrasing and translation similar to a much older, simpler baseline, and a 2026 preprint found that 98.3 percent of initially detected watermarked texts lost their signal after paraphrasing.

All three test the open-sourced algorithm or a reimplementation, never Google's production configuration, which Google has never published. Read them as limits of the published method, not measurements of Gemini.

Nobody has reconciled those positions.

How do you remove an AI watermark from text?

For text, removal is three separate jobs: cleaning invisible Unicode, lowering a statistical watermark's score, and stripping C2PA metadata. Only the first has an answer you can check yourself.

Removing a watermark from text covers three jobs that have little in common.

  • Cleaning invisible Unicode characters out of pasted text. This is formatting cleanup, not defeating anything a provider built on purpose, and you can check the result yourself in seconds with the free in-browser checker.
  • Lowering a statistical watermark's detector score by rewriting, paraphrasing, or translating. The research above treats this as an open contest, not a problem solved in either direction.
  • Stripping file-level C2PA provenance metadata. Ordinary uploads and screenshots already destroy it, so this is closer to routine file handling than to breaking a scheme.

What people actually try on the statistical layer is simple. A Reddit thread asking how to remove Claude's text watermark proposed two methods: rewriting the text by hand, or running it through a second model to add noise.

Neither method is documented. Both are commenter speculation, and heavy rewriting can damage the writing along with whatever mark it carried.

Nobody outside the providers can test a removal attempt either. Anthropic's detector shipped on 1 September 2026 into a private preview for eligible organizations under EU law, and OpenAI limits its textGrain detector to approved researchers.

Anthropic is also explicit that a detector match would only mean text may have been processed by Claude, not proof that it was.

Some AI text never had to carry a mark. The European Commission's FAQ on Article 50 lists these as outside the marking duty:

  • Short sequences of numbers, symbols, or letters
  • Source code
  • Machine-to-machine output a human never sees
  • Closed-loop industrial processes, short of their final output
  • Standard editing-assistive functions

The voluntary Code of Practice adds carve-outs of its own for signatories: it does not require marks on outputs under 200 tokens or on code snippets.

For any text that might be watermarked, four steps apply whichever provider wrote it:

  1. Scan for hidden Unicode first. It is the one layer you can verify yourself, and the only one where removal means something definite.
  2. Identify the source. Claude, Gemini's app and web experience, and ChatGPT have different statuses. Anthropic marks text from every marked Claude model. OpenAI's textGrain, announced on 2026-10-05, marks API text where a customer opts in, with EU ChatGPT and Codex text rolling out over the coming weeks. Google's forum has answered both ways about Gemini API text, and no Google documentation covers it.
  3. Weigh the length. The strongest published survival result needed roughly 800 tokens, so a short passage was weakly marked before anyone edited it.
  4. Hold every removal claim to one standard: tested against a real detector and corroborated by someone else, or it is only a claim on a page.

Has anyone cracked Google's SynthID watermark?

Community discussion

A thread with 1.2 million views said SynthID was broken. Three days later the researcher posted his own 16 percent evasion rate.

The widely shared claim that SynthID was cracked has never been peer reviewed or replicated. An independent hobbyist going by aloshdenny says spectral analysis of image pixels achieved 90 percent detection and 91 percent removal of image SynthID marks while keeping image similarity at 0.997, plus over 90 percent scrubbing of text watermarks via paraphrasing, with code posted publicly.

The claim went wide on April 9, 2026 in a thread that cleared 1.2 million views. Nobody has peer reviewed it and nobody else has replicated it, which makes it an interesting lead to watch rather than evidence anything works today.

Do Anthropic and Google agree with their own watermark claims?

Confirmed

Google's SynthID page says Gemini app text is watermarked. Google's developer forum said API text was not, then retracted that two weeks later. No Google document covers API text either way.

Not always: Anthropic states one clear claim, while Google's statements about Gemini text have pointed in both directions. Anthropic's claim is clean and present-tense. A supported Claude model "weaves an imperceptible watermark directly into the text itself," stated in a published support article.

Anthropic's help centre says the mark is applied at the model level, so it is present whichever surface the text comes from: the Claude app, Claude Code, Claude Cowork, Claude Tag, the Claude API, and supported Claude models on AWS, Google Cloud, and Microsoft Foundry.

Models launched on or after August 2, 2026 support marking at launch. Every model released before that date must be marked by December 2, 2026 under the AI Act; since October 7, 2026 Anthropic's help page no longer repeats that date.

Google is messier. Google DeepMind's own SynthID product page says, verbatim, "We've expanded SynthID to watermarking and identifying text generated by the Gemini app and web experience."

But on August 5, 2026, a Google-affiliated account on Google's own AI developer forum, replying to a question about gemini-2.5-flash-lite, gemini-3.1-flash-lite, and EU AI Act Article 50(2), wrote that "generated text from the API is NOT SynthID-watermarked" and that "native text watermarking is not planned at the moment."

Then, on August 19, 2026, the same account took it back: "After checking further with the team, it turns out that text generated via the Gemini API IS actually SynthID-watermarked! I apologize for the confusion earlier, the previous statement was incorrect." It added that the correction also covers Google AI Studio and Antigravity. The August 5 post is still live and unedited, so anyone who stops at the first answer reads the withdrawn one.

The retraction removes the clash with the marketing page but claims more than any Google documentation supports. DeepMind's page scopes text watermarking to the Gemini app and web experience, and Google's developer SynthID page does not mention the API. No Google source settles whether API text was always marked, so the status database grades both Gemini text rows Contested.

How do you check an AI watermark removal claim?

A four-step check that holds for text, images, audio, and video, plus the Sora finding that proves a missing signal means almost nothing.

Check any removal claim against the specific system that produced the content and the specific signal that system claims to use, rather than against AI-ness in general. The reliable approach is the same for text, images, audio, and video.

  1. Identify the system that actually produced the content.
  2. Find out what mechanism that system claims to use.
  3. Test for that specific signal rather than for AI-ness in general.
  4. Report what you found, including what you could not test.

In practice that means three concrete checks: look for a C2PA manifest and note whether the file has been through any upload or conversion, scan text for suspicious invisible Unicode characters, and compare a detector's actual confidence before and after an edit instead of treating one pass or fail as proof.

A missing manifest proves nothing by itself. C2PA metadata is routinely destroyed by ordinary uploads, downloads, and format conversions with no removal attempt involved.

Even OpenAI's own rollout has been caught inconsistent. An independent November 2025 investigation found Sora 2 videos carrying a visible watermark with no detectable C2PA metadata at all, while separate Pro-tier videos without any visible watermark did carry detectable metadata.

That is the reverse of what OpenAI's claim that "every video generated with Sora includes both visible and invisible provenance signals" would predict. OpenAI's help page, read 2026-10-06, now lists Sora video as carrying Content Credentials only and says Sora is discontinued, without addressing the finding. A blanket removal promise skips every step above.

FAQ

Can AI watermarks be removed?

Sometimes, but it depends entirely on the watermark type and format. Peer-reviewed research (Jovanović et al., ICML 2024) has demonstrated real scrubbing attacks against research implementations of statistical text watermarking, and independent teams have shown Google's open-sourced SynthID-Text algorithm degrades under paraphrasing and back-translation. None of that adds up to "any AI watermark can be removed," and no published method is confirmed to work against a real production system from Anthropic, OpenAI, or Google.

Is rewriting text the same as removing a watermark?

No. Rewriting can reduce detectability for some schemes, especially on shorter or lightly edited passages, but the original green-list research team found the signal can survive strong paraphrasing once roughly 800 tokens have been generated. Rewriting also changes the words themselves, which is a different cost from cleanly removing a hidden signal.

Is AI text watermark removal the same as AI humanizing?

No. Humanizing is broad rewriting aimed at style. Text watermark removal is narrower: cleanup, targeted signal reduction, and detector-aware transformation. Commercial tool marketing conflates the two constantly.

Does all AI-generated text have to carry a watermark under the EU AI Act?

No. The European Commission's Article 50 FAQ lists short sequences of numbers, symbols, or letters, source code, machine-to-machine output a human never sees, and standard editing-assistive functions as outside the marking duty, and the Code of Practice does not require marks on outputs under 200 tokens or on code snippets. Anthropic and OpenAI document text watermarks, and Google says Gemini app text is watermarked, but the law alone does not mean every piece of AI text will carry one.

Does a missing C2PA manifest prove a watermark was removed?

No. C2PA metadata is destroyed by ordinary uploads, downloads, screenshots, and format conversions without anyone attempting removal. Even OpenAI's own Sora videos have been documented carrying inconsistent metadata independent of any deliberate stripping.

Is there a legitimate way to check for a watermark instead of trying to remove one?

Yes, for some formats. OpenAI runs a public Verify tool for its own images and, since mid-2026, audio, but not text: the detector for textGrain, the text watermark it announced on 2026-10-05 for opted-in API text and, over the coming weeks, EU ChatGPT and Codex text, is limited to approved researchers. Google's SynthID Detector portal checks images, video and audio but not text, and access remains waitlist-gated to journalists, media organizations, and researchers rather than open to the public.

Next steps

Sources and citation status