You can now turn off Google Gemini’s visible watermarks

What happened

I'll draft the post from the given facts only, then count words and strip any markdown before delivering the prose.The draft is over the word limit. I'll tighten it to 600–900 words and stay closer to the given facts.Google will now let you remove visible watermarks from the images, videos, and music made with its AI tools. The control is a new Media watermark setting in Gemini and in Flow, Google's AI video generator. When the setting is toggled off, Google removes the sparkle watermark that appears in the bottom-right corner. That is the change as reported: one setting, two product surfaces, three media types, and one corner mark. Nothing in the announcement describes a separate stripper you run after export, and nothing in it claims that any mark other than the visible sparkle is being added or taken away.

Media watermark is a toggle, not a post-process. You turn it off in Gemini or in Flow, and the generator either stamps the sparkle onto the finished image, video, or music output or it does not. The mark lives in the bottom-right corner, so it occupies a fixed, human-visible region of a still, a video frame, or whatever surface carries the music. Because the same setting covers images, videos, and music, Google is treating the sparkle as a shared disclosure layer across those three outputs rather than as a stills-only overlay. The only guaranteed effect when the toggle is off is that the sparkle is gone from that corner. Whether the setting is sticky across sessions, shared between Gemini and Flow, or applied per generation is not stated, so the safe reading is to check the control on the surface you are actually generating from.

The technical detail

For engineers this is a pipeline detail. If you have been using Gemini or Flow as an upstream generator, the sparkle has been a tax on every asset that left the tool: you left it in the corner, you cropped it out, or you covered it. A first-party toggle removes that step at the source. Video is the expensive case, because a mark locked to the bottom-right is present in every frame, every cut, and every thumbnail. Music is quieter, but a visible mark on generated audio still shows up on artwork or player chrome. If those tools sit in your stack, Media watermark now belongs next to the other generation settings you already pin down before a batch. Leave it on and every downstream file carries the sparkle. Turn it off and the file no longer self-identifies in the corner.

Why it matters for builders

Visible watermarks exist so a casual viewer can tell that an image, a clip, or a track came from a named AI tool. Google is making that casual tell optional in Gemini and in Flow. That is the same tension every major generator hits: a corner mark is useful for brand and for disclosure, and it is also the first thing a professional user wants gone before the asset goes into a product, a deck, or a campaign. A mark you can crop away is a weak provenance signal. A mark you can now switch off is weaker still as a public tell. The update does not say Google is dropping disclosure. It says the disclosure you can see, the sparkle in the bottom-right, is now optional on those two surfaces.

Treat the setting as an explicit choice per workflow. If the file never leaves the team, turning the sparkle off is the clean path. If you ship the file, you now have to decide whether you still want a human-visible Google mark in the corner, because the tool will no longer force that decision. Check Media watermark in both Gemini and Flow before a batch. A toggle that covers images, videos, and music can change the look of an entire export set if someone flipped it earlier. After you generate, look at the bottom-right of the still or the first frame of the video and confirm the sparkle is in the state you intended. A file without the sparkle is not proof it did not come from these tools. A file with the sparkle is not proof it was left untouched.

Market and competitive context

The announcement does not say what else, if anything, still travels with the image, the video, or the music once the sparkle is gone. It does not say whether the toggle is account-wide or per generation, or whether it applies to work already sitting in history. Downstream checks that used the bottom-right sparkle as a cheap detector will fail as soon as users turn Media watermark off. If you needed that mark so reviewers or customers could see the source, you will have to add the label yourself. If you needed it gone so the asset could ship, the setting is the fix.

What to watch next

Anyone who has been using the sparkle as a rule of thumb that a file came from Gemini or Flow should drop that rule. The mark was only a visible corner overlay. It was never a signature over the pixels or the samples, and it never said whether the file was edited after export. With Media watermark off, even that overlay is gone. A sparkle in the bottom-right is still evidence that the file was exported with the setting on. The absence of a sparkle is not evidence of anything. If you need to know the source of an image, a video, or a piece of music, look at your own logs and export trail rather than at the corner of the frame.