Skip to content
modeldeprecations.dev
Google gemini-3-pro-image

Gemini 3 Pro Image (Google)

Active

No — Gemini 3 Pro Image is not deprecated as of August 3, 2026. Google has announced neither a deprecation nor a shutdown date for it.

Nano Banana Pro, the high-end image model of the Gemini 3 generation, released the same day as the 3.1 Flash Image. It is the only Pro-tier image model Google serves and it carries the Gemini 3 version number rather than 3.1, so the image line's numbering has already drifted from the text line's.

The facts

Provider Google
Model id gemini-3-pro-image
Released May 28, 2026
Deprecated not deprecated
Shutdown not published
Status Active
Last verified August 3, 2026

Frequently asked questions

Is Google Gemini 3 Pro Image still available?
Yes. Google Gemini 3 Pro Image is active and fully supported as of August 3, 2026.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

Drop the badge in a README so it turns red the day this model is retired:

[![gemini-3-pro-image](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/google/gemini-3-pro-image.json)](https://modeldeprecations.dev/google/gemini-3-pro-image)

Other Google models

All Google deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.