How to turn off the Gemini image watermark
Gemini stamps a small semi-transparent sparkle on the images it generates. You can switch it off before generating — the setting is one toggle away in most regions — and for images you already published there are two honest ways to deal with it.
Turn it off at the source (new images)
Gemini has a built-in setting for the visible watermark. The path is the same on the web app and the mobile app:
- Open Gemini and go to Settings (side menu on the web, profile menu in the app).
- Find Media Watermark in the settings list.
- Switch Add watermark off.
Images you generate after the change no longer carry the visible sparkle. Images generated before the change keep it — the mark was blended into those pixels at export time, so changing the setting later does not retroactively clean them.
Region caveat. In India, South Korea and Vietnam the media watermark setting is locked behind the Google AI Ultra subscription — free and Pro tiers cannot turn it off there. Everywhere else the toggle is available on free accounts.
Images you already published: two paths
Once an image is out with the sparkle on it, no setting helps. You have two realistic options:
1. Reconstruct the pixels
The sparkle is a semi-transparent white mark, so the pixels behind it can be recovered by inverting the blend — deterministic pixel-exact reconstruction. Bimta's Gemini watermark remover does this in your browser: it finds the mark automatically, lets you check the before/after, and handles batches up to 50 images free.
2. Crop it out
The sparkle sits in the bottom-right corner, so cropping that corner removes it at the cost of composition and a few percent of resolution. For photos where the corner is expendable, this is the zero-tool option — any editor or your phone's gallery app can do it.
What turning it off does not do
Three different things get called a "watermark" on a Gemini image, and they behave very differently:
- The visible sparkle — the mark this guide is about. Optional, removable, or croppable.
- SynthID — an invisible watermark Google embeds across the whole image. It survives editing, cropping, screenshots and re-encoding, and no tool removes it. Turning the visible watermark off does not remove SynthID.
- C2PA content credentials — provenance metadata in the file that platforms read to label AI content. It is data, not pixels; if you want it gone, that is a metadata job (see the C2PA remover), and note that editing an image invalidates its existing credentials rather than preserving them.
Also worth knowing: some platforms add their own AI labels after you upload, based on their own classifiers. Neither the Gemini setting nor any removal tool controls those.
Use it responsibly. Removing a visible watermark is a presentation choice, not a licence to misrepresent. If you publish AI-generated work where disclosure is expected — news, contests, stock, advertising — disclose it yourself. Invisible watermarks and platform classifiers are unaffected by anything on this page.
Related: What is C2PA and how do Content Credentials work?
Sparkle already on your images? Bimta reconstructs the pixels behind the visible Gemini watermark locally — free, batches included, with an honest before/after check.
Remove the sparkleCommon questions
Does turning off the watermark remove SynthID?
No. SynthID is separate, invisible and permanent. The setting only controls the visible sparkle.
Can I turn the watermark off in India, South Korea or Vietnam without AI Ultra?
No. In those regions the media watermark setting requires a Google AI Ultra subscription. The alternatives are removing the visible mark afterwards with a reconstruction tool, or cropping the corner.
Why did my watermark come back after editing?
Some Gemini editing flows re-stamp the output even when the setting is off for generation. Check the toggle after major app updates, and inspect the exported image rather than trusting the setting alone.
Is removing the sparkle against the rules?
Removing a visible mark from a file you own is a normal edit. What you do with the result can still be governed by platform policies or disclosure laws in your context.