SynthID on what ordinary handling is meant to leave behind
Four named operations, and all four are things that happen to a file on the way to an audience rather than things an attacker does. That choice of list is the substance of the claim. As of 2026-09-12.
| Point | What the record holds |
|---|---|
| What survives | Cropping, filters, frame-rate changes, lossy compression |
| Read from | A research and product page describing the scheme |
| What it does not settle | What a deliberate attempt at removal achieves |
Inclusion rule. One cell of this generator's entry, quoted from the page the entry names. Coverage, commentary and third-hand summaries are not admitted, in either direction. Order. Fixed order: the cell, the page it came off, then the limit on reading it.
1The list describes a distribution pipeline, not an adversary
Cropping for a vertical surface, a filter applied in an app, a frame-rate change for a platform, a compression pass on upload. Every item is a routine step in getting video from a workstation to a viewer.
That is the useful robustness to claim, because it is the damage that happens to every file rather than the damage somebody sets out to do. A mark that survives ordinary handling is a mark that is usually still there.
2Robustness is one of the four words in the clause
The paragraph asks for solutions that are effective, interoperable, robust and reliable as far as technically feasible. This sentence is an answer to the third word, phrased in the operations that test it.
It is also the word most amenable to evidence. Robustness can be measured by running the operations and checking the detector, and nothing in the paragraph requires the measurement to be published.
3Designed to is not the same as always does
The wording recorded is about design intent, and the page does not give a rate at which detection holds under each operation. A reader wanting a number will not find one on this page.
So the cell reports the list and the intent. Whether a specific delivered file still carries a detectable mark is a question about that file and the route it took, not a question any vendor page can answer.
- SynthIDDesigned to stand up to cropping, filters, frame-rate changes and lossy compressionstated robustness
- Article 50(2)Technical solutions must be effective, interoperable, robust and reliable as far as technically feasiblequalifier on the marking duty
4Sources
Wording taken from the SynthID page at deepmind.google, consulted 2026-09-12. All four rows for this generator sit on Google SynthID; the same column across every entry is read down on What survives. Filed beside it: AudioSeal on masking and quality, Synthesia on a mark that stays.