Build1 publisher3 min readPublished
Google Makes the Visible Watermark Optional. Your Pixel Check Is Now Decoration.
Gemini and Flow users can switch off the on-image badge while SynthID and C2PA stay behind. Provenance tooling that reads pixels instead of metadata now returns nothing useful.
The Engineer · Build desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

What happened
- Google now lets users turn off the visible watermark on AI-made images, videos and music in Gemini and Flow.
- Invisible SynthID and C2PA provenance remain in place for verification despite the visible watermark being switchable.
- SynthID and C2PA are described as the technical ways Google invisibly watermarks generative AI content.
- Anthropic recently moved to watermark all AI text.
- The source material does not state the default state of the visible-watermark toggle, which tiers or regions it covers, whether third-party access to SynthID detection exists, or how C2PA manifests survive re-encoding.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
Google now lets users turn off the visible watermark on AI-made images, videos and music in Gemini and Flow, while invisible SynthID marking and C2PA provenance stay in place for verification, according to The Neuron's newsletter [1][2]. If your ingest, moderation or compliance path looks for a corner badge to decide whether something was generated, that path has stopped telling you anything [1].
The distinction matters because the visible mark was the only signal that a human could read at a glance and a naive script could find by cropping and template-matching. The remaining two signals are not like that. SynthID and C2PA are described in the same report as the technical means by which Google invisibly watermarks generative content [3], which means detection now requires either a detector that can recover an embedded signal or a parser that can read and validate a provenance manifest. Neither is a pixel operation. Both are dependencies you have to own, version and monitor.
Scope is the other thing to plan around. The change is described as covering three output types: images, video and music [1]. That is at minimum three detection paths, because recovering an embedded mark from audio is not the same job as recovering one from a frame, and a manifest attached to a video container is not read the same way as one attached to a still [2]. Anyone budgeting this as a single "watermark check" ticket has mis-sized it.
Be clear about what the source does not establish. The newsletter does not say whether the toggle is on or off by default, which account tiers or regions it applies to, whether Google exposes a SynthID detector to third parties, or how the C2PA manifest survives the ordinary abuse of re-encoding, resizing and platform upload [5]. Those are the details that decide whether a metadata-first check works in production or fails silently, and they are not in the material. Until they are published, treat any provenance verdict from your own pipeline as unproven rather than negative.
The cross-vendor picture is not converging either. The same report notes Anthropic recently moved to watermark all AI text [4], so one vendor is adding marking to a modality that had none while another is making its most legible mark optional [3]. There is no shared visible convention to build against, which argues for treating provenance as a metadata and detector problem per vendor rather than a display problem.
Three things worth tracking. First, whether Google documents the default state and the availability of SynthID detection to outside parties, since that determines whether "no mark found" is evidence of anything [2][5]. Second, whether other image and video vendors follow the same split of optional visible mark plus retained invisible provenance [1]. Third, whether C2PA manifests hold up end to end through the systems you already run, because a provenance scheme that only survives inside the originating product is a labelling policy rather than a verification mechanism [2].