How Google SynthID Works: Invisible Watermarks for Text, Images, Audio and Video
Follow one token through SynthID-Text, see how media watermarks differ, and learn what Google’s detectors can—and cannot—tell you.
SynthID is a family of watermarking systems for text, images, video and audio—not one universal AI detector.
SynthID-Text creates a statistical pattern through token sampling; it does not insert hidden characters or ordinary metadata.
The language model’s probability distribution defines plausible candidates before the watermark key helps resolve a sampling choice.
Detection aggregates many small observations. A result is provenance evidence, not proof of authorship, ownership, truth or misconduct.
Short text, heavy editing, unsupported generators and strong media transformations can make a missing mark inconclusive.
What Google SynthID is
A newsroom receives a polished product image, a 30-second clip and a paragraph said to come from Gemini. The reviewer has one question: can Google’s systems provide evidence that any of those assets were made or edited with supported Google AI? SynthID is designed to supply that evidence by embedding an imperceptible signal during generation and checking for the matching signal later.
The name covers several modality-specific systems. Text carries a statistical pattern in token choices. Images and video carry signals in visual content, while audio carries an inaudible signal in a time-frequency representation. The common idea is embed then detect; the technical carrier is different for each medium. SynthID therefore cannot identify arbitrary AI content that was never watermarked with a compatible system.
One name, four different watermarking mechanisms
It is tempting to describe every SynthID mark as a hidden code. That shortcut is inaccurate. The signal must live in something the medium naturally contains: generated word choices for text, pixels for images and video, and time-frequency structure for audio. Ordinary file metadata is separate and can coexist with SynthID, but it is not the embedded watermark itself.
Where each SynthID signal lives
Modality |
Where the signal is embedded |
What detection examines |
|---|---|---|
Text |
A key-dependent statistical pattern across eligible token choices. |
Many token positions, their recent context and the matching watermark configuration. |
Image |
An imperceptible signal distributed through image pixels by a learned watermarking model. |
The image as a whole and, in supported tools, regions most likely to carry the mark. |
Video |
A related visual signal across generated frames; verification can also inspect a marked audio track. |
Time segments and tracks, not simply one file-level yes-or-no flag. |
Audio |
An inaudible signal in a two-dimensional time-frequency representation of the sound. |
Evidence across the timeline, including the segments where a mark is most likely present. |
Worked example: how SynthID-Text selects a token
The quality safeguard comes first: the language model still supplies its ordinary next-token distribution after decoding controls such as temperature, top-k and top-p. The watermark configuration works inside that distribution. It changes an individual sampling path, but it does not invent a vocabulary outside the model’s plausible continuation set.
Start with ordinary model probabilities
For the unfinished sentence “The sky looked …”, imagine the model assigns vast 40%, endless 30%, blue 20% and grey 9%. An unrelated token such as toaster has less than 1% probability, with any remaining probability distributed across other tokens. These are teaching numbers—not published Gemini probabilities. They show the crucial boundary: high-probability tokens enter the candidate draw more often, so semantic fit remains controlled by the language model.
Simplified from Google DeepMind’s published SynthID-Text reference design. The probabilities, candidate draw and g-values are illustrative; production configurations can differ.
-
Compute the ordinary model distribution
The model scores possible next tokens from the text already written. Sampling controls are applied before SynthID-Text.
Meaning, grammar and factual constraints begin with this distribution.
-
Draw candidate copies from that distribution
In a toy two-layer tournament, four draws might be vast, blue, endless and grey. Sampling is with replacement, so duplicates are possible even though this illustrative draw contains four different candidates.
Every competitor was supplied by the model distribution first.
-
Turn the key and recent context into scores
The watermark key and recent token IDs seed repeatable pseudorandom g-values for each candidate and tournament layer. The key stays with the watermarking system; it is not inserted into the prose.
The same word can receive a different value in a different context.
-
Run the reference tournament
Candidate copies are paired. The higher keyed value advances, ties are broken randomly, and winners compete through another layer until one token remains.
The published implementation can compute this efficiently without drawing a literal bracket.
-
Emit the winner and repeat
Suppose vast wins, completing “The sky looked vast …”. New preceding context creates new keyed values for the next position. Many such choices form the passage-level signal.
One selected token contains almost no useful evidence by itself.
How SynthID-Text detection works
Detection is a separate process. The checker receives a finished passage and the matching watermark configuration. It tokenizes the text, reconstructs the recent context at each eligible position and recomputes the keyed g-values for the token that actually appears. Nothing is decoded from a hidden string, and the underlying language model is not required for the published detector.
A worked detection example
Imagine a 600-word creative explanation with hundreds of eligible positions. Some observed tokens align with the keyed values more often than ordinary text would be expected to; others are neutral. The detector combines all of those small observations. Eight highlighted positions or a meter in the diagram are purely illustrative—not a Google score threshold, confidence percentage or minimum passage length.
A compatible detector follows five conceptual stages:
Tokenize the passage with the tokenizer expected by the watermark configuration.
Mask positions that should not contribute, including repeated contexts in the published non-distortionary design.
For each remaining position, combine the matching key with recent tokens and recompute the g-values for the observed token.
Aggregate evidence with a calibrated scoring method. Google’s reference work describes mean, weighted-mean, frequentist and trained Bayesian options.
Interpret the result at a threshold chosen for the detector, text length, expected data and acceptable false-positive rate.
How image, video and audio watermarks differ
Images and video
For images, Google describes two deep-learning models trained together: one embeds an imperceptible signal into pixels and another identifies it. Training balances detectability with visual fidelity. Video builds on media watermarking across generated frames, and current verification can inspect both visual and audio tracks. The signal is designed to remain detectable after common operations such as resizing, cropping, filters, frame-rate changes and lossy compression—but Google does not describe it as indestructible.
Audio
SynthID’s official audio explanation converts the waveform into a two-dimensional spectrogram showing how frequencies change over time, then embeds an inaudible pattern. The detector can localize likely marked parts of a track. Google says the design tolerates common changes such as added noise, MP3 compression and speed changes; repeated or extreme transformation can still lead to a miss.
When the signal is strong or weak
Detectability depends on three things: whether a compatible watermark was applied during generation, how much eligible evidence the content contains and what happened afterward. Robust means designed to survive specified edits—not permanent, universal or impossible to remove.
Practical examples:
Long, varied text usually offers more token choices and more evidence than a one-line factual answer.
A 600-word generated draft may carry a stronger text signal than a human document where an AI changed three commas.
Mild text cropping or a few word changes may preserve evidence; thorough rewriting or translation can greatly reduce confidence.
Images, video and audio are designed to tolerate common resizing, filtering, compression and timing changes, but repeated or extreme edits can defeat detection.
A positive region or time segment does not mean the entire asset was generated by AI.
Content from an unsupported model will not acquire a Google SynthID mark merely because it looks synthetic.
How to check for a SynthID watermark
Verification is a provenance workflow, not a single magic prompt.
-
Identify the modality and preserve the original
Keep the highest-quality source file or complete text before cropping, recompressing, translating or rewriting it.
-
Use the current supported checker
For media, a signed-in Gemini user can upload one image, video or audio file and ask whether Google AI created or edited it. Public Gemini verification does not currently advertise pasted-text checks.
-
Respect the documented media limits
Google currently documents files up to 100 MB, video shorter than 90 seconds and audio shorter than one hour, with approximate rolling daily quotas.
-
Use a matching configuration for text
A deployer using the open-source SynthID-Text implementation needs the compatible key, configuration, tokenizer and calibrated detector.
-
Record and corroborate the result
Save the tool, date, tested file or passage, exact result and any uncertainty. Combine it with creation records, source history, Content Credentials and human review.
What a SynthID result can and cannot prove
Watermark evidence is asymmetric. A detected compatible signal supports a limited inference about a supported generator or edit. A missing signal often leaves several explanations open: no compatible watermark was applied, the evidence was too weak, the asset was transformed, the wrong detector was used or another AI system created it.
How to interpret SynthID results
Observation |
Reasonable conclusion |
What it does not prove |
|---|---|---|
Media SynthID mark detected |
All or part of the asset was likely generated or edited by a supported Google AI system recognized by the checker. |
Who prompted it, who owns it, whether it is true or whether every part is synthetic. |
Text score exceeds a configured threshold |
The passage shows statistical evidence consistent with that compatible SynthID-Text configuration. |
That Gemini wrote every idea, that a named person used it or that misconduct occurred. |
No mark found |
The checker found no reliable positive signal under its supported configuration. |
Human origin, absence of AI involvement or absence of a different provider’s watermark. |
Only a region, segment or track is detected |
The marked evidence is localized to that part of the asset. |
That the rest of the image, video or audio is synthetic—or authentic. |
A practical checklist for content teams
A defensible workflow:
Keep the original asset and complete generated passage before any editing or conversion.
Record the model, product surface, date, prompt purpose and human reviewer.
Separate “AI drafted” from “AI lightly edited” in your internal provenance record.
Verify media before heavy compression, cropping, remuxing or screenshotting.
Preserve Content Credentials separately when present; they document history differently from SynthID.
Treat detected, not detected and uncertain as evidence states—not labels of guilt or authorship.
Corroborate important decisions with source files, logs, editorial records and human review.
Common questions about Google SynthID
No. SynthID-Text changes the statistical pattern of token sampling during generation. The watermark is not a zero-width character string, readable code, user ID or ordinary file metadata.
The model distribution supplies candidates first, and the key resolves among those candidates. Google’s non-distortionary reference configuration preserves the original token distribution on average, and a roughly 20-million-response Gemini experiment found no statistically significant quality difference. This is an aggregate result, not a guarantee that each response is identical.
No. A generative watermark must be applied by a compatible model or service during generation. SynthID-Text detection also requires the matching configuration. It is not a universal classifier for all AI-written prose.
Common light transformations are part of Google’s robustness goals, but no variant is indestructible. Thorough text rewriting or translation and repeated or extreme media transformation can reduce or erase detectable evidence.
No. It may support that a compatible Google AI system generated or edited all or part of supported content. It does not identify the user, recover the prompt, establish copyright ownership, prove truth or show who originated the ideas.
- SynthID - Google DeepMind
- Scalable watermarking for identifying large language model outputs - Nature
- Watermarking and detecting AI-generated text with SynthID - Google AI for Developers
- SynthID Text reference implementation - Google DeepMind
- Verify AI-generated images, videos, and audio - Google Gemini Help
- Making it easier to understand how content was created and edited - Google
- SynthID Detector - Google
- Identifying AI-generated images with SynthID - Google DeepMind
- Watermarking AI-generated text and video with SynthID - Google DeepMind
- Transforming the future of music creation - Google DeepMind
- AI Content Detection API - Google Cloud