Gemini's visible watermark and its provenance signals are different things. Google currently documents a Media Watermark setting in Gemini Apps. Turning that visible mark off does not turn off SynthID or Content Credentials. Check the current export route instead of assuming a clean corner means an image has no provenance information.
This guide is for creators preparing their own images for a website, product brief or campaign. It explains the current documented setting, what an ordinary file inspection can establish and how to keep an original export with its review record. The instructions were checked on November 3, 2026.
Check the current Gemini setting first
Google's watermark settings guide gives this computer route: open Gemini, choose Settings, then Media Watermark. Read the setting shown for your account and media type. The guide notes regional conditions: in India, South Korea and Vietnam, the setting requires an AI Ultra subscription. Check the current help page if your control differs.
Use that documented control before looking for an unrelated removal utility. The setting concerns visible marks in Gemini Apps; it does not describe every Google product or API route. Keep the product name with your instructions so an Apps setting is not presented as a universal switch for every service that uses a Gemini model.
For an actual production job, save the account route, media type, setting and export date. You do not need to record private account details. The useful evidence is which documented path produced the file you intend to use.
Separate three kinds of evidence
| Layer | What you can inspect | What that inspection does not prove |
|---|---|---|
| Visible pixels | A corner mark, label or overlay in the image | Whether invisible watermarking is present |
| File metadata | Information exposed by the file and your inspection tool | That every provenance system was detected |
| Embedded watermark detection | A supported detector's result for the actual file | A complete license or factual history of the scene |
Google DeepMind describes SynthID as an imperceptible watermark embedded in generated content. It is designed to survive modifications such as cropping and lossy compression. That is why looking at a clean image or changing its format is not a reliable test of whether that watermark remains.
Content Credentials are another kind of provenance signal. Keep that concept separate from a logo in the pixels and from an invisible watermark. A tool that reports some metadata has not necessarily examined every layer of provenance, and an empty metadata panel is not a universal absence test.
Try an original file-inspection exercise
The exercise starts with a simple original lamp illustration. It was rendered into PNG and WebP, then inspected for format, dimensions, file size and SHA-256. The files can show essentially the same composition while containing different bytes. That observation is useful for delivery tracking; it does not establish anything about a provider watermark.
Download the export inspection exercise. It includes the files, the checked observations and a small inspection script. Run it on copies. The script reports a file signature and hash; it is not a provenance detector or a commercial-rights checker.
A SHA-256 value identifies the bytes you inspected. If the file is re-encoded later, its hash can change even when the subject looks the same. Record the new output as another version rather than silently replacing the original record.
Keep the original and delivery export connected
Save the original download in a source folder. Make a separate delivery copy for the website or editor, using the format and dimensions that destination requires. Give the two files distinct names and retain a note connecting them.
For example, your record might identify a source image, a smaller WebP delivery, the crop you approved and the date of inspection. Use filenames that make sense to the next person. A folder full of “final” files does not explain which one contains the complete product or which one was approved for the campaign.
Our creative asset versioning guide covers that record in more detail. The purpose here is to preserve the relationship between source, export and evidence, including when a website build optimizes the delivery image.
Review the image after export
Open the saved delivery file outside the generation conversation. Inspect the complete frame, important edges, product label, color impression and any visible mark. Check it at the size people will actually see. A correct file extension does not guarantee a readable label or a useful crop.
If you need exact advertising text, add it as an editable element in the finishing workflow where appropriate. Do not treat the absence of a visible watermark as evidence that every other part of the picture is accurate. A generated package can still have incorrect lettering or changed geometry.
The Gemini image creation guide owns the first-image and controlled-edit workflow. This article addresses the later export and provenance check. Link the two steps in your project record rather than mixing account setup, image direction and file inspection into one undocumented process.
Use the right check for the question
If your question is whether a mark is visible, inspect the pixels. If it is whether a specific download matches an approved file, compare the hash. If it concerns a supported watermark, use the provider's current verification route and keep the result with the exact file tested.
Do not convert one result into a broader claim. “No corner logo visible” is a visual observation. “These bytes match the approved export” is a file-identity observation. Neither statement establishes who owns every depicted object or whether a client permits the intended use.
Keep the source, permission record and publication approval alongside the export. When a fact remains unresolved, record that uncertainty instead of filling the gap with a confident label such as “watermark free.” That phrase can mean several different things to a collaborator.
Continue with the reviewed creative asset
Bring a permitted reference and an approved brief to Image Lab for the next visual task. Inspect the current controls and cost before generating. Preserve the output you accept and review its exported form just as you would review an image from another route.
For mixed references, use the source-role briefing workflow to decide which image controls product identity and which supplies atmosphere. Provenance review and visual direction support each other, but they answer different questions.
Frequently asked questions
Can I turn off Gemini's visible watermark?
Google currently documents a Media Watermark setting in Gemini Apps. Availability has regional conditions, so check the control and current help page for your account and media type.
Does the visible-mark setting remove SynthID?
No. Google's guide distinguishes the visible setting from SynthID and Content Credentials. A clean-looking image does not establish the absence of those provenance signals.
Does converting an image to WebP prove the watermark is gone?
No. A format conversion changes the file representation. It is not a supported test for the absence of an embedded watermark or all metadata.
Are the downloadable examples Gemini exports?
No. They are actual PNG and WebP exports of an original illustrated fixture. Their format, dimensions, sizes and hashes were checked; no SynthID detection result is claimed.
What should I save with a delivery image?
Keep its original source, export settings, version relationship, inspection date, permission record and approval decision. Retain the exact file used for any detector check.
Keep a reviewed export with the project
Use Image Lab for the creative image task, then retain the accepted asset and its source record.
