Google Gemini Adds Toggle to Hide Visible AI Watermarks
In this article
Google has handed users a toggle that removes the visible "sparkle" watermark from AI-generated images, videos, and music produced through Gemini and the AI video generator Flow. The setting, labelled "Media watermark," lives inside Gemini's settings menu and, once disabled, strips the bottom-right-corner indicator that previously appeared on content generated by Google's Nano Banana and Omni models.
What changes — and what doesn't
Toggling off visible watermarks does not remove the provenance signals that matter for downstream verification. Google confirmed through Josh Woodward, VP of Google Labs, Gemini, and AI Studio, that invisible SynthID watermarks and C2PA metadata remain embedded in all generated content regardless of the visible-watermark setting. Both Gemini and Google Search retain the ability to detect those hidden markers when queried directly about whether a piece of content is AI-generated.
This distinction matters for developers building pipelines where content authenticity needs to be auditable without surfacing AI provenance to end users. SynthID operates at the signal level inside the media file itself; C2PA metadata travels as structured provenance data attached to the asset — two complementary mechanisms that survive re-hosting and light post-processing far better than a corner icon. As AI-generated content becomes harder to distinguish visually, the ability to programmatically query provenance through these invisible channels becomes the only reliable verification path — a challenge that mirrors broader AI agents direct corpus interaction concerns about unverified content entering automated pipelines.
Competitive landscape
Google's move aligns it with existing practice across major competitors. OpenAI and Meta's image generators do not apply visible watermarks: OpenAI relies on SynthID and C2PA, while Meta operates its own Content Seal standard. Anthropic announced this week that it is applying invisible watermarks to both AI-generated text and images. The competitive matrix now looks like this:
| Provider | Visible watermark | Invisible watermark standard | Text watermarking |
|---|---|---|---|
| Google (Gemini / Flow) | Optional (toggle off) | SynthID + C2PA | Not confirmed |
| OpenAI | None | SynthID + C2PA | Not confirmed |
| Meta | None | Content Seal | Not confirmed |
| Anthropic | None confirmed | Invisible (images + text) | Yes (announced this week) |
Anthropic's text watermarking is the notable differentiator — extending provenance signalling beyond binary media files into generated prose is a meaningfully harder problem, and the timing alongside Google's toggle is likely deliberate.
Rollout and regulatory carve-outs
Google's watermark toggle will extend to Search-generated media, but carries an explicit geographic exception: the setting will not launch in countries that legally require visible watermarks on AI-generated content. That carve-out is significant for developers targeting EU deployments, where the AI Act's transparency obligations are already in effect. The toggle being available in a given region does not mean it is legally safe to use — legal counsel familiar with local AI labelling rules should assess applicability before products disable the visible marker.
The broader pattern is that the industry has collectively concluded invisible, cryptographic provenance beats visible iconography as the durable standard — partly because, as the source notes, users were already editing visible watermarks out anyway. The open question for security-conscious teams is whether SynthID and C2PA survive the post-processing pipelines their users will actually run — JPEG recompression, social-platform transcoding, and similar transforms. Invisible watermarks that don't survive those steps offer little more assurance than the sparkle icon they replaced, a concern worth stress-testing in the same spirit as AI bug hunters probing infrastructure assumptions.