Google Made Visible Watermarks Optional: What Creators Should Actually Do

The visible AI watermark just became optional. On August 14, Google started rolling out a "Media Watermark" setting in Gemini Apps that lets you turn the visible mark on or off for images, video, and music generated with Nano Banana, Omni, and Lyria. Japanese creators picked up on this change quickly, and it deserves more than a headline, because it changes the default assumption behind every image you publish.

Here is what actually changed, what did not, and how to make a deliberate choice instead of a reflexive one.

What changed on August 14

Google's Gemini team announced that the visible watermark, the small sparkle mark in the corner of Nano Banana images and the overlay on Omni video, is now a setting instead of a permanent fixture. VP Josh Woodward confirmed the toggle covers the Nano Banana, Omni, and Lyria models, appears in Gemini and the Flow video editor, and is coming to Search later.

You reach it through Settings > Media Watermark in Gemini Apps. It is a single switch that applies to everything you generate after you flip it, so you do not have to re-decide per image.

Two caveats from Google's own support documentation are easy to miss:

• In India, South Korea, and Vietnam, the setting only appears with an AI Ultra subscription; everyone else keeps the visible watermark automatically.
• Work and school accounts do not get the setting at all.

So "optional" is not universal. It is optional for personal consumer accounts in most regions, and mandatory elsewhere.

The invisible layer is the one that matters

The easy framing is "Google now lets you remove the watermark." The accurate framing is "Google now lets you remove the visible watermark, while the invisible identification stays."

Every generation still carries:

• SynthID, Google's imperceptible pixel-level watermark that usually remains detectable after common edits like cropping, resizing, or compression, though detection can fail after substantial or repeated changes, and
• Content Credentials (C2PA) metadata, the open provenance standard that records how and when the content was created. Metadata lives in file headers, so it can be removed or corrupted when a file is re-encoded or processed by social platforms. A copy of the original Gemini output is not the same as the file that went through another platform's pipeline.

Google's support page is explicit: the Media Watermark setting only controls the visible mark and does not affect SynthID or Content Credentials. Gemini and Search can still verify whether an image was AI-generated.

This is the core distinction for creators. Turning the setting off changes what a human sees, not what the ecosystem can detect. The content remains traceable; it just stops advertising its origin in the frame.

Why this matters for real workflows

Creators who push hundreds of Nano Banana images into client decks, social posts, and composites have been complaining about the corner mark for a while. It sits in the worst possible spot: bottom-right, exactly where a lot of layouts put their weakest visual weight, and it survives into crops you did not intend.

The practical wins of the toggle:

• Social-first images stop wearing a badge that competes with the subject.
• Composites and collages no longer need corner cropping or cover-ups that degrade the composition.
• Client drafts look closer to final art, so stakeholders judge the image instead of the watermark.

None of that changes your obligations. If a platform, client, or brief requires disclosure, the setting is not a compliance workaround; you remain responsible for meeting that disclosure requirement.

What the "should I turn it off" debate actually comes down to

The Japanese source article frames the community question well: is it okay to remove the watermark, or is that hiding AI authorship?

The honest answer is: it depends on the context, and the technical facts shape the ethics.

For personal exploration, drafts, or decorative content where the AI origin is not material, the visible mark is mostly noise. Turning it off is defensible and arguably good design.

For journalism, documentation, education, contest entries, or anything where readers have a reasonable expectation about whether a person or a machine made the image, the visible mark was doing real work. Removing it does not make the content less AI-generated; it makes the disclosure invisible to your audience. Even though SynthID and C2PA remain, most people who look at your image will never run a verification tool.

The sharpest formulation I can offer: the toggle removes the label, not the fact. If your audience needs the fact, keep the label.

What this signals about AI media

Google's stated rationale is balancing creative control with safety. Read it alongside two other recent moves and a pattern appears:

• Anthropic announced watermarking for text and files, and a chunk of its user base reacted badly.
• Google open-sourced Credentio, a library that lets apps embed C2PA-style validation locally.
• Several major platforms are adopting invisible provenance, while visible marks remain a product decision.

The direction is consistent: provenance becomes ambient infrastructure, while the visual badge becomes a product decision. That is a meaningful shift for anyone building AI creative tools. If a vendor can change the visibility of provenance with a settings flag, then the disclosure burden moves from the model to the product and the creator. Build your workflows on the assumption that visible watermarks are a policy choice, not a law of nature, and that the invisible layer is what you can actually rely on.

A practical checklist

• Flip the setting from the app-level settings, not per-generation, and confirm it took effect on a test image.
• Know your regional and account constraints before promising a client "clean" output.
• Treat the visible mark as a communication decision: keep it for public, audience-facing content where provenance is expected; drop it for drafts and personal work.
• Never assume removing the visible mark erases identification. SynthID and C2PA are still there, and tools like Gemini or Search can still verify origin.
• If your platform or client requires AI disclosure, the toggle is not a compliance workaround.

The watermark question is not really about watermarks anymore. It is about who decides what an audience knows about the image they are looking at. That decision just moved one step closer to the creator.