Why does Gemini put a watermark on my image?

That small sparkle-shaped mark near a corner of your image is not a rendering glitch. It is a deliberate transparency and provenance decision Google applies on Free and Google AI Pro tier output, and it ships alongside SynthID, an invisible signal, rather than replacing it. Google AI Ultra and API output skip the visible mark but keep SynthID.

What is that sparkle in the corner of my Gemini image?

The mark people describe as a "sparkle," "star," or "watermark in the bottom-right corner" is a small, semi-transparent logo Gemini overlays onto the pixels of a generated or edited image. It sits near a corner rather than across the whole frame, and its exact size and margin scale with the image's output resolution rather than staying fixed. If you want the precise pixel dimensions for a given output size, the supported sizes guide and gemini-watermark-sizes document that separately from the policy question this guide answers.

It is easy to mistake that mark for a photo-editing artifact, a UI element that got baked into an export, or ordinary app branding. It's none of those. It is applied consistently to qualifying output, on purpose, as one part of a larger disclosure strategy that also includes SynthID underneath the visible pixels.

Why does Gemini add a visible watermark to some images?

Google states it as a transparency signal that an image was generated or edited by Gemini's AI tools, layered alongside the invisible SynthID signal on Free and Pro tier output. See visible Gemini watermark vs SynthID for how the two signals actually differ, since they are frequently discussed as if they were one mechanism when they behave nothing alike.

The practical reasoning is straightforward even without access to Google's internal product decisions: a visible mark tells any viewer, immediately and without special tooling, that an image likely came from an AI system. SynthID does the same job for software that can check for it, but it needs a verifier to be legible. The two together cover both a human glancing at an image and a system trying to confirm its origin programmatically.

Is the watermark only about Google's own branding?

Google frames it primarily as a provenance and transparency signal rather than branding, though a visible mark can serve both purposes at once — a recognizable logo also reinforces which product made the image. This project does not have visibility into Google's internal reasoning beyond what Google has published, so anything beyond that published framing is speculation, not a documented fact.

What is not speculation is the tier split: the mark's presence or absence tracks Free/Pro versus Ultra/API access, not a manual per-image setting. See Gemini watermark by tier if you're trying to predict whether a specific image will carry the mark before you generate it.

Does regulation like the EU AI Act require this specific visible mark?

Not this specific implementation. The EU AI Act's Article 50 requires machine-readable marking of AI-generated content from 2 August 2026, but it does not mandate any single vendor's visible logo design. Other jurisdictions, including California, have their own disclosure laws on a similar timeline. None of them specifies a sparkle icon, a corner position, or any other detail of Gemini's particular visible mark — that part is Google's own product design.

It helps to keep three different things apart here, because guides on this topic routinely blur them:

• The law requires some machine-readable AI-content signal by a set date. It does not prescribe Gemini's specific visible logo.
• Google's own product choice is to layer a visible mark on top of SynthID for Free and Pro tier output. That is a company decision, documented by Google, not a legal mandate.
• Good disclosure practice — telling your audience, client, or platform that an image is AI-generated or AI-edited — is a separate judgment call that applies whether or not any visible mark survives editing. Removing a logo does not resolve it.

See the AI disclosure rules guide for what the EU and California laws actually require, independent of what any single product's watermark looks like.

Why do Ultra and API outputs skip the visible mark?

Per Google's own tier documentation, Ultra and AI Studio and API outputs carry SynthID only, without an added visible corner mark. This project cannot independently confirm Google's product reasoning behind that decision — whether it reflects an assumption about professional or developer workflows, a different disclosure approach for those surfaces, or something else entirely is not stated in the sources available to us, so we are not going to guess at it here.

What is confirmed is the outcome: SynthID still applies to Ultra and API output. Skipping the visible mark is not the same as skipping disclosure entirely, and no tier lets you opt out of SynthID.

If you need to work with an existing marked image

Understanding why the mark exists is a different question from what to do with a file that already has one. If you generated an image on Free or Pro and need the visible mark removed from that specific file, the local browser eraser handles the supported visible-mark case: it validates a candidate on your device and leaves the file unchanged if it can't confirm one, rather than forcing a guess. For a fuller comparison of your options, including the tier-switching route, see how to get Gemini images without a watermark. If your goal is figuring out whether removing a visible mark is something you're allowed and willing to do given how the image will be used, how to remove a Gemini watermark responsibly covers that groundwork first.

Frequently asked questions

Why does Gemini add a visible watermark to some images?

Google states it as a transparency signal that an image was generated or edited by Gemini's AI tools, layered alongside the invisible SynthID signal on Free and Pro tier output.

Is the watermark only about Google's own branding?

Google frames it primarily as a provenance and transparency signal rather than branding, though a visible mark can serve both purposes at once.

Does regulation like the EU AI Act require this specific visible mark?

Not this specific implementation. The EU AI Act's Article 50 requires machine-readable marking of AI-generated content from 2 August 2026, but it does not mandate any single vendor's visible logo design.

Why do Ultra and API outputs skip the visible mark?

Per Google's own tier documentation, Ultra and AI Studio and API outputs carry SynthID only, without an added visible corner mark. This project cannot independently confirm Google's product reasoning behind that decision.