Does the Gemini API Add a Watermark? Developer Guide for 2026

The Gemini API watermark answer has two parts: raw API-generated images include Google’s invisible SynthID watermark, but developer image outputs are designed for clean visual integration and do not need the visible Gemini sparkle used in some consumer UI contexts. If you see a sparkle, check whether you exported from an interface, not the raw API.

Developers often confuse three separate layers: the visible Gemini sparkle, invisible SynthID, and UI-specific export behavior. A production app needs to know which layer affects pixels, which layer affects compliance, and which layer affects the user-facing image.

The short version is practical. Build your image workflow around raw API output, keep SynthID in place, and only use a visible-cleanup tool when you are dealing with UI-exported Gemini images that already contain the sparkle.

Does the Gemini API Add a Visible Watermark to Generated Images?

The Gemini API does not behave like the consumer Gemini app watermark experience. Google’s image generation docs say all generated images include SynthID, while Google’s Nano Banana Pro announcement says the visible Gemini sparkle is maintained for Free and Google AI Pro tier users and removed for Google AI Ultra subscribers and within the Google AI Studio developer tool.

That means developers should separate “watermarked” from “visibly watermarked.” An image can be watermarked with SynthID and still have no visible logo in the corner.

The short answer: no visible sparkle on raw developer image output

For developer use, the important distinction is visual output versus provenance output. Raw image responses from the API are intended for application integration, not consumer-facing branding overlays.

Google’s official API image generation page lists the available Nano Banana models and says all generated images include SynthID. It does not describe a visible corner sparkle being applied to API binary responses.

The visible sparkle is a consumer-facing disclosure cue. SynthID is the underlying AI provenance layer. Developers usually care about both, but for different reasons.

If your app receives image bytes from the API, your front end should not need to crop or hide a visible Gemini logo. If your file includes a sparkle, it likely came from a browser interface, screenshot, preview export, or consumer workflow.

Why Google omits the visible sparkle for developer integrations

Developer workflows need clean visual canvases. Apps use generated images inside product mockups, dashboards, game assets, marketing tools, design systems, and automated content pipelines. A visible corner logo would break many legitimate integrations.

Google’s own product messaging supports this separation. In the Nano Banana Pro announcement, Google says it keeps the visible Gemini sparkle on images generated by Free and Google AI Pro tier users, but removes the visible watermark for Google AI Ultra subscribers and within the Google AI Studio developer tool because professional work needs a clean canvas.

That is the logic API developers should follow. The visible layer is not the core AI provenance mechanism. SynthID is.

Exception: interactive browser UI previews can create confusion

Developers often test in Google AI Studio, the Gemini app, or a browser UI before moving to code. That is where confusion starts.

Google’s documentation and announcements distinguish between developer tooling, API generation, consumer tiers, and app-level verification. If you download an image from a UI, screenshot a preview, or test through a consumer account, you may not be looking at the same output path your production API uses.

The fix is simple: test the exact code path your app will use.

Use the model string, request type, response data, and saved binary output from your production integration. Do not use a screenshot from a UI preview as proof of API watermark behavior.

Does the Gemini API Still Embed SynthID?

Yes. The Gemini API still embeds SynthID in generated images. Google’s official Gemini API image generation page states that all generated images include a SynthID watermark. SynthID is embedded as an invisible provenance signal, not added as a visible corner logo by the UI.

For developers, this is the main compliance and provenance layer to understand.

SynthID is embedded during generation, not just by the UI

SynthID is not the same thing as a visible logo. Google’s responsible AI documentation describes SynthID as a Google DeepMind technology that embeds digital watermarks directly into AI-generated images, audio, text, or video.

That wording matters. If the watermark is embedded into generated media, it is not merely a UI badge pasted onto the image after preview. It is part of Google’s generation and provenance stack.

Google also says SynthID can help users identify whether content was created or edited by Google AI through Gemini’s verification experience.

SynthID is present in API-generated images

The official Gemini API image generation documentation is direct: all generated images include a SynthID watermark.

That applies even when there is no visible Gemini sparkle. Developers should not market API output as “unwatermarked” without qualifying what they mean.

A more accurate statement is:

• No visible Gemini sparkle in normal developer output.

• SynthID still embedded.

• AI provenance still present.

• Disclosure obligations still depend on context, platform, and law.

This is the distinction your product documentation should use.

SynthID is not something GeminiErase removes

GeminiErase is designed to remove the visible Gemini sparkle from images that contain it. It does not remove SynthID. The tool works by reversing the visible alpha compositing layer, not by attacking Google’s invisible forensic watermark.

That matters for developer trust. If you use GeminiErase on a UI-exported image, you are cleaning the visible corner mark. You are not removing the underlying AI provenance signal.

For deeper context, read Gemini watermark vs SynthID.

Which Gemini Models Add Watermarks Through the API?

Gemini image models add SynthID through the API. The official Gemini API image generation docs list Nano Banana 2 as gemini-3.1-flash-image, Nano Banana Pro as gemini-3-pro-image, and Nano Banana as gemini-2.5-flash-image, and the same page states that all generated images include SynthID.

This section uses the current Google AI for Developers documentation as the source of truth as of June 23, 2026.

Gemini 3.1 Flash Image: SynthID only for developer output

Google’s image generation documentation identifies Nano Banana 2 as the Gemini 3.1 Flash Image model, using the model string gemini-3.1-flash-image. The docs describe it as the high-efficiency counterpart to Gemini 3 Pro Image, optimized for speed and high-volume developer use cases.

For this model, the developer-relevant answer is SynthID, not visible sparkle.

Use it when you need speed, high-volume generation, and app-integrated image workflows. Do not expect a consumer-style visible logo in raw binary responses, but do expect SynthID to remain.

Gemini 3 Pro Image: SynthID only for developer output

Google’s documentation identifies Nano Banana Pro as Gemini 3 Pro Image, with the model string gemini-3-pro-image. The docs describe it as designed for professional asset production, using advanced reasoning to follow complex instructions and render high-fidelity text.

Google’s Nano Banana Pro announcement says professional clean-canvas needs are why visible watermarks are removed from Google AI Ultra and Google AI Studio developer tool outputs.

For API developers, the practical expectation is clean visual output with SynthID embedded.

Gemini 2.5 Flash Image: legacy Nano Banana API workflows

The same official Gemini API page identifies Nano Banana as Gemini 2.5 Flash Image, using gemini-2.5-flash-image. Google describes it as optimized for speed and low-latency image tasks.

If you are maintaining existing code that uses gemini-2.5-flash-image, you should still expect generated images to include SynthID.

Do not confuse this with a visible watermark. The docs’ explicit watermark statement is about SynthID.

Imagen 4: paid API access and deprecation timeline

Imagen 4 is available through the Gemini API, but Google’s pricing page now warns that Imagen 4 models are deprecated and will be shut down on August 17, 2026. Google recommends migrating to Gemini 2.5 Flash Image.

The Imagen 4 model strings listed in pricing are:

• imagen-4.0-generate-001

• imagen-4.0-ultra-generate-001

• imagen-4.0-fast-generate-001

Google’s developer blog announced Imagen 4 in the Gemini API and Google AI Studio on June 24, 2025, with paid preview access and limited free testing in AI Studio.

For developers in June 2026, Imagen 4 should be treated as a migration concern, not the default long-term image generation path.

Gemini API vs UI Watermark Behavior

Gemini API vs UI watermark behavior is the source of most confusion. API-generated images should be evaluated through raw response files, while consumer UI images and some browser exports may include the visible Gemini sparkle depending on tier, product, and workflow. SynthID remains the common invisible provenance layer.

This is the simplest mental model:

This is also why “Gemini API image generation no watermark” is an imprecise phrase. It should mean “no visible sparkle,” not “no AI provenance watermark.”

Why screenshots are unreliable evidence

Screenshots can preserve the visible UI state, not the raw API output. If you screenshot an AI Studio preview, Gemini app result, browser canvas, or downloaded UI image, you may capture a workflow-specific visual mark.

A proper API test should save the inline image data returned by the model. The official docs show a Python example that decodes interaction.output_image.data and writes it to generated_image.png.

That file is the artifact you should inspect.

Why AI Studio can still confuse teams

Google AI Studio is a developer tool, but it is still a browser interface. Teams often mix UI testing, prompt experimentation, and production API output in the same conversation.

Keep your QA language precise:

• “AI Studio preview”

• “AI Studio downloaded file”

• “Raw API response”

• “Consumer Gemini app export”

• “Production app output”

Those are not always the same artifact path.

For more context on this distinction, read Google AI Studio watermark.

The Free Tier API Exception: Image Generation Is a Billing Issue, Not a Watermark Issue

Free tier API limitations are often mistaken for a watermark problem. Google’s pricing page lists Gemini 2.5 Flash Image input and output pricing as “Not available” on the Free Tier and paid per-image on the Paid Tier. That means developers may need billing enabled for image generation access.

If your API call fails, do not assume Google added or blocked a watermark. Check pricing, tier, model availability, and rate limits first.

Free tier availability depends on the model

Google’s pricing page shows Gemini 2.5 Flash Image as not available on the Free Tier, with paid output pricing per image.

That is a product access issue. It does not imply that the API would add a visible watermark if you upgraded. It means your project may not be allowed to generate images with that model under the free tier.

The same pricing page shows Imagen 4 image prices as not available on Free Tier and paid per image. It also warns that Imagen 4 models are deprecated and will be shut down on August 17, 2026.

Rate limits are separate from watermark behavior

Google’s rate limit documentation explains that rate limits regulate how many requests you can make within a timeframe, and that exceeding a limit triggers a rate limit error. It also states that rate limits are tied to the project’s usage tier.

A 429 error means you hit a rate limit or quota condition. It does not mean the image was watermarked.

Common causes include:

• Using a model unavailable on your tier.

• Exceeding requests per minute.

• Exceeding requests per day.

• Missing billing setup for paid-only image models.

• Calling a deprecated or shut-down model.

• Confusing API access with AI Studio testing access.

Billing must be enabled for paid image generation

If a model is not available in Free Tier, you need a paid tier path for production use. Google’s pricing page is the correct source for current model availability and per-image costs.

Do not design production behavior around temporary free testing in UI tools. AI Studio experimentation and API billing are separate planning concerns.

For developers building SaaS tools, the safe pattern is to confirm:

1. Exact model string.

2. Pricing tier.

3. Rate limits.

4. Response format.

5. File output.

6. SynthID expectations.

7. Visible watermark behavior.

What to Do If Your API Images Show a Watermark

If your API images show a visible Gemini watermark, first verify that the file truly came from the raw API response. Check whether it was downloaded from a UI, screenshotted, exported from the consumer Gemini app, routed through AI Studio preview behavior, or processed by a front-end layer that added a logo.

Do not debug watermark behavior until you confirm the artifact source.

Verify raw API output, not AI Studio UI export

Save the image directly from the API response data. Do not use a screenshot. Do not drag from a browser preview. Do not test with an image copied out of a consumer app.

In Python, follow Google’s documented pattern: call the model, decode the returned image data, and write the file directly. The official image generation guide shows this flow for Nano Banana image generation.

Once saved, inspect that exact file. That is the only reliable evidence of API output.

Check model string and tier

Use the current model string from Google’s documentation. As of the page retrieved on June 23, 2026, Google lists these Gemini image models:

• gemini-3.1-flash-image

• gemini-3-pro-image

• gemini-2.5-flash-image

The same page states that all generated images include SynthID.

If you use Imagen 4, check the deprecation warning. Google’s pricing page says Imagen 4 models will shut down on August 17, 2026.

Check whether your own app overlays branding

Sometimes the visible watermark is not from Google. It may come from your own preview component, demo watermark, storage proxy, CDN transformation, or front-end placeholder overlay.

Check the file at each stage:

1. Raw API response file.

2. Server-stored file.

3. CDN-served file.

4. Front-end rendered image.

5. Downloaded final file.

6. Social or CMS upload derivative.

If the watermark appears after step one, Google API output is not the problem.

Use GeminiErase for UI-exported images with the sparkle

If you are working with images that came from the Gemini app, a UI preview, or a browser export that includes the visible sparkle, use GeminiErase for visual cleanup.

GeminiErase removes the visible four-pointed Gemini watermark using deterministic reverse alpha blending. It runs locally in the browser, requires no account, supports PNG, JPG, and WebP files up to 15MB, and does not remove SynthID.

Use remove your Gemini watermark with GeminiErase for UI-exported images that need clean presentation. For raw API production output, you should not need it unless your workflow introduced the visible mark elsewhere.

Developer Checklist for Gemini API Image Watermark QA

A reliable Gemini API watermark QA process should test the exact production image path. Do not rely on screenshots, UI previews, or consumer app exports. Confirm model, tier, raw binary output, SynthID expectations, and any downstream transformations before declaring an image visibly watermarked.

Use this checklist before shipping an image-generation feature.

Step 1: Confirm the model string

Use the current Google model string. As of June 23, 2026, Google’s image generation page lists gemini-3.1-flash-image, gemini-3-pro-image, and gemini-2.5-flash-image for Nano Banana image generation.

Step 2: Confirm tier and billing

Check pricing before testing. Google lists Gemini 2.5 Flash Image as not available on Free Tier and priced per image on Paid Tier.

Step 3: Save the raw image response

Write the returned image bytes to disk directly. Do not test a preview screenshot.

Step 4: Inspect for visible sparkle

Open the saved file and check whether a visible corner sparkle appears. If it does not, your API output is visually clean.

Step 5: Document SynthID

Add a note in your developer docs that generated images include SynthID. This avoids misleading users with phrases like “no watermark” when you mean “no visible watermark.”

Step 6: Check downstream transforms

Run the image through your storage service, CDN, CMS, and front end. If a visible mark appears later, the issue is downstream.

Step 7: Add disclosure controls where needed

SynthID is not a substitute for human-facing disclosure in every context. If your app generates realistic people, product claims, public-interest imagery, or marketing assets, provide a disclosure workflow.

For legal context, read is it legal to remove the Gemini watermark.

FAQ

Does the Gemini API add a visible watermark to generated images?

Raw Gemini API image output is not expected to include the visible Gemini sparkle used in some consumer UI contexts. Google’s docs state that all generated images include SynthID, and Google says the visible watermark is removed within Google AI Studio developer tooling. Always test the raw API response file, not a screenshot or UI export.

Does the Gemini API add SynthID to images?

Yes. Google’s Gemini API image generation documentation states that all generated images include a SynthID watermark. SynthID is an invisible digital watermark used for AI provenance. It is separate from the visible Gemini sparkle and should be treated as part of the generated media, not a removable UI badge.

Why does my Gemini image have a sparkle if I used developer tools?

Check the exact source of the file. A sparkle may appear if the image came from a consumer Gemini app export, a browser preview, a screenshot, or another UI workflow. Save the raw API binary response directly and inspect that file before assuming the Gemini API added a visible watermark.

Which Gemini image models include SynthID?

Google’s Gemini API image generation page lists Nano Banana 2 as gemini-3.1-flash-image, Nano Banana Pro as gemini-3-pro-image, and Nano Banana as gemini-2.5-flash-image. The same page says all generated images include a SynthID watermark, so developers should assume SynthID is present across Gemini image outputs.

Is the Gemini API free for image generation?

Not for the main paid image generation paths shown in Google’s pricing page. Gemini 2.5 Flash Image is listed as not available on Free Tier, with paid per-image pricing. Imagen 4 is also listed as not available on Free Tier and is deprecated with a shutdown date.

Is a 429 error related to image watermarking?

No. A 429 error is a rate limit or quota issue, not a watermark issue. Google’s rate limit documentation explains that limits regulate usage across time windows and are tied to your project’s usage tier. Check RPM, RPD, model availability, billing, and tier before debugging watermark behavior.

Can GeminiErase remove a watermark from API-generated images?

GeminiErase removes the visible Gemini sparkle from images that contain it. If your raw API output has no visible sparkle, you do not need GeminiErase. If you exported an image from a UI workflow that does show the sparkle, GeminiErase can remove the visible mark while leaving SynthID intact.

Can I tell users my Gemini API images are unwatermarked?

Avoid saying “unwatermarked” without qualification. A better phrase is “no visible Gemini sparkle.” Google’s documentation says generated images include SynthID, so the image still carries invisible AI provenance. This distinction is important for developer documentation, compliance, user trust, and platform disclosure workflows.

Get clean UI-exported Gemini images without touching the invisible provenance layer. Remove the visible Gemini sparkle with GeminiErase when a browser or consumer workflow adds the mark, and keep raw API output, SynthID, and disclosure logic separate in your production app.