Google makes AI watermarks optional. SynthID still marks it.
Google's visible AI watermark is now a toggle in Gemini, but SynthID and C2PA metadata stay embedded. What that means for product imagery you ship.
If you have ever generated a product shot in Gemini and then cropped out the little sparkle in the corner, Google just saved you the step. The visible AI watermark on Google's generated images, video and music is now optional — a setting, not a fact of life. The part worth reading twice: the invisible marking did not go anywhere. You can turn off the badge your customers see. You cannot turn off the one your platform, your marketplace, or a regulator can read.
What actually happened
Josh Woodward, Google's VP for Gemini, confirmed on August 14 that a new Media watermark setting lets users drop the visible mark from output produced by Nano Banana (images), Omni (video) and Lyria (music), inside Gemini and the Flow video editor, with Search support following. He framed it plainly as a tradeoff between creative control and safety: the visible mark is optional now, and invisible SynthID watermarks plus C2PA metadata are still applied (TechCrunch). It rolls out over the coming days.
The day before, Google open-sourced the other half of this. Credentio is a C++ library for validating C2PA Content Credentials, released against spec versions 2.2 and 2.4. Google says the same code already backs close to 40 of its own C2PA-conformant products across tens of billions of generated assets. The design point that matters: it validates entirely locally, so an app can check a file's provenance without shipping the media to somebody's cloud (Google Developers Blog). Today it reads credentials; writing them is on the roadmap.
Why AI watermarks matter for your business
Read those two announcements together and the direction is obvious. The visible sparkle was never the enforcement layer — it was the courtesy. The enforcement layer is metadata riding inside the file, and Google just handed every developer a free, local, fast way to check it.
So plan for a near future where the platforms you sell on can cheaply sort AI-generated media from camera-captured media at upload time. Amazon already asks sellers to tag AI-generated people in product images. The EU AI Act's Article 50 transparency rules landed August 2. Turning off a visible badge does not opt you out of any of that; it just means you can no longer see, at a glance, which assets in your own library are generated.
That is the practical risk, and it is boring: your asset pipeline stops self-documenting. Fix it on your side. Record generation provenance in your DAM or product database when the asset is created — model, prompt, date, operator — instead of relying on a pixel in the corner to remind you six months later. And do not let "the watermark is gone" become internal shorthand for "this is indistinguishable from a photo." It isn't. It's just quieter.
Key takeaways
- Google's visible AI watermark became a user setting on August 14, covering Nano Banana, Omni and Lyria in Gemini and Flow
- Invisible SynthID watermarks and C2PA metadata remain applied regardless of the toggle
- Google open-sourced Credentio on August 13 — a C++ library that validates C2PA Content Credentials locally, no cloud round trip
- Expect marketplaces and platforms to detect generated media cheaply; visible-badge removal changes nothing about disclosure obligations
- Track provenance in your own asset system at generation time — do not rely on a visible mark you can now delete
If you cannot answer "which of our product images are AI-generated," that is a data problem, not a policy problem. We build asset pipelines that stamp provenance at creation and keep it queryable — in systems you own, not a vendor's settings page. See how we build it, or tell us what your catalog looks like today.
Sources: TechCrunch, Google Developers Blog.
- #ai-provenance
- #synthid
- #c2pa
- #product-images
- #watermarking
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Qwen3.8-27B: the open model you can actually self-host
Alibaba shipped Qwen3.8-27B under Apache 2.0 with a 262K context window. Unlike the 2.4T Max, this one fits on hardware you can rent — here's what that buys you.
Read itKog's 3,000 tokens/sec claim: read what was measured
French startup Kog says software alone unlocks 30x faster LLM inference on GPUs you already own. The demo is real. The number you care about isn't in it yet.
Read it