Skip to main content
AI Watermark Removal

Is it watermarked?

Is Gemini Watermarked?

Google's own SynthID page says Gemini's text output is watermarked. A Google-affiliated reply on Google's own developer forum says it isn't. Images, audio, and video are a different story entirely: SynthID watermarking there is confirmed without dispute, at a scale Google itself puts in the billions. Text is the mess, and the honest answer depends entirely on which Gemini surface produced the words in front of you.

Published 2026-08-11Updated 2026-08-11Official announcement

Key takeaways

  • Confirmed, no dispute: SynthID watermarks Gemini images, audio, and video; a companion DeepMind paper claims the image system alone has marked over ten billion images and video frames across Google's services.
  • Contested for text: DeepMind's marketing page says the Gemini app and web experience are watermarked; a Google-affiliated forum reply says the API is not, as of August 5, 2026, and that native text watermarking "is not planned at the moment."
  • Google's own consumer verification tool doesn't even attempt to check text. It covers only images, video, and audio.
  • Independent, non-Google researchers have repeatedly found SynthID Text weaker under attack than Google's own presentation implies: vulnerable to paraphrasing and back-translation, and, in a 2026 theoretical analysis, its mean-score detector grows less reliable as more tournament-sampling layers are added, while its alternative Bayesian-score detector holds up better.
  • Thorough rewriting or translation can reduce detector confidence, where SynthID Text applies at all.

SynthID Text mechanism

How a statistical text watermark enters output

GeminiGeminiSynthID Text

Prompt context

The model builds next-token probabilities from the text so far.

Sampling pool

Top-K and Top-P narrow the candidate tokens.

Logits processor

SynthID Text adjusts generation-time scores using a keyed signal.

Watermarked text

The chosen tokens still read naturally, but carry a statistical pattern.

Detector score

A detector scores whether enough text matches the configured signal.

Why paraphrasing matters

The watermark is distributed across token choices. Light edits may leave enough signal, while heavy rewriting or translation can reduce detector confidence because many original token choices disappear.

Confirmed, and not close: images, audio, and video

Confirmed

Here's the settled half of the answer, and exactly what Google's own checker will and won't do for you.

Google documents SynthID watermarking for Gemini's image, audio, and video output without qualification, and without any of the hedging that surrounds the text story.

A companion DeepMind paper on the image system alone claims it has been used to watermark more than ten billion images and video frames across Google's services. That's a Google-reported figure no third party has validated, though nobody disputes that the watermarking itself happens.

Google's consumer verification tool, reachable from the Gemini app, is scoped the same way:

  • Checks images, video, and audio. Explicitly not text.
  • Recognizes content created by Google AI tools only, per Google's own wording.
  • Caps you at roughly 10 checks per type every 24 hours.

If you're trying to verify whether a picture or a clip came from a Google AI tool, that's the confirmed, working path. If you're trying to verify text, there is no equivalent tool at all.

Contested for text: two Google sources, one contradiction

Community discussion

You'll get both statements in full, plus the reading that reconciles them and why it's still only a guess.

Google DeepMind's SynthID model page states it plainly: "We've expanded SynthID to watermarking and identifying text generated by the Gemini app and web experience." That's an official marketing claim, unqualified.

On August 5, 2026, a Google-affiliated account on the Google AI Developer Forum answered a narrow technical question about whether gemini-2.5-flash-lite and gemini-3.1-flash-lite output carries a machine-readable provenance signal under EU AI Act Article 50(2). The answer was a flat denial: "Generated text from the API is NOT SynthID-watermarked. There is no machine-readable providence [sic] signal... Native text watermarking is not planned at the moment."

Nobody has published anything reconciling those two statements.

The most charitable reading is that the consumer-facing Gemini app and web chat apply SynthID Text while the developer API doesn't. That would track with how Google scoped its own verification tool, but it's an inference, and no primary source draws that line for current Gemini 3.x models.

Treat a flat "yes, Gemini text is watermarked" or "no, it isn't" as an incomplete answer until it specifies which surface generated the text.

How SynthID Text works, where it actually applies

Confirmed

Here's the mechanism in plain terms, plus the detail that explains why you can't run the check yourself.

Where SynthID Text does run, Google describes it as a logits processor applied during generation, after ordinary Top-K and Top-P sampling has narrowed the candidate tokens. The underlying Nature paper calls the technique tournament sampling.

That paper, authored by Google DeepMind researchers, reports a live experiment across a large sample of real Gemini responses that found no detectable drop in output quality from applying the watermark. It describes SynthID Text as productionized specifically for Gemini and Gemini Advanced.

The method has also been open-sourced, with a production-grade reference implementation shipping in Hugging Face Transformers since version 4.46.

Google documents the same robustness pattern independent researchers keep finding elsewhere. The signal survives cropping, minor word changes, and mild paraphrasing reasonably well, but confidence drops sharply under thorough rewriting or translation.

A standalone SynthID Detector portal exists for scanning content directly, launched at Google I/O in 2025. Access has stayed waitlist-gated to journalists and researchers since launch with no public API, and the most recent independent check, by journalist Henk van Ess in November 2025, still found it waitlist-only.

Independent research complicates the confident version of the robustness story

Research/proposal

Here's what non-Google teams found when they attacked SynthID Text, and how much weight each result can carry.

Multiple independent teams have stress-tested SynthID Text since it launched, and the results complicate Google's framing.

  • A 2025 EMNLP Findings paper found its resilience to paraphrasing and translation attacks was "similar to" a much simpler, older green/red-list watermark, meaning no clear robustness advantage despite the more sophisticated design.
  • A separate 2025 paper found SynthID Text "susceptible to meaning-preserving attacks, such as paraphrasing, copy-paste modifications, and back-translation," and built a hybrid defense that improved detection accuracy by an average of 11.1% over the vanilla version.
  • A 2026 theoretical analysis proved that SynthID Text's mean-score detector becomes less reliable as more tournament-sampling layers are added, while the alternative Bayesian-score detector in the same system holds up better.

A 2026 preprint went further, testing an open-source SynthID Text reimplementation and reporting three numbers worth holding onto:

  • 80% of untouched, genuinely watermarked passages fell into SynthID's own "uncertain" confidence zone.
  • 98.3% of texts that were initially detected lost their signal after a single round of aggressive paraphrasing.
  • 5.4% of human-written text got flagged as AI-generated.

None of this is peer-reviewed, large-scale, first-party Google data, and some of it tests a reimplementation rather than Google's actual production keys. Treat the exact numbers as early and unreplicated, not settled science.

But the pattern is consistent enough across separate independent teams that "SynthID Text is highly robust" shouldn't get repeated as an unqualified fact.

FAQ

Is Gemini different from Claude and ChatGPT here?

Gemini's image, audio, and video watermarking is unambiguously confirmed. For text, Gemini is now the murkiest of the three: Claude has a clear, recent official statement covering its text watermark; Gemini has two conflicting official-ish statements about app/web versus API, with nothing published to resolve them.

Is the SynthID Detector portal something I can use to check my own text?

Not really, not yet. Google launched a standalone SynthID Detector portal at I/O in 2025 to scan images, audio, video, and text for SynthID marks, but access has stayed limited to a waitlist for journalists, media, and researchers, with no public API. The most recent independent check, from journalist Henk van Ess in November 2025, still found it waitlist-only, and nothing since confirms broader availability.

Does Google say how reliable Gemini's image watermark detection is at scale?

Only in a self-reported way. A Google DeepMind paper on the image-watermarking system claims it has been used to mark more than ten billion images and video frames across Google's services. That's a real, dated, Google-authored figure, but it hasn't been independently validated by anyone outside Google.

Next steps

  • For the full provider timeline, including Google's EU AI Act commitments and the documented checker bug it had to fix, start with the tracker page. Gemini watermark tracker
  • If you want the mechanism rather than the verdict, tournament sampling and the three-state detector are covered on their own page. SynthID watermark
  • If your actual question is whether a rewrite defeats it, the removal evidence is collected separately. Remove Gemini watermark
  • A watermark and an AI detector are different things that fail differently, which matters a lot if you've been accused of using AI. Watermark vs detector

Sources and citation status