Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

Anthropic 29 Google 24 OpenAI 103
Google gemini-2.0-flash

Gemini 2.0 Flash (Google)

Retired

Yes — Gemini 2.0 Flash is retired. Google shut it down on June 1, 2026; API requests to it now fail. The recommended replacement is Gemini 3.6 Flash.

The model that made native tool use and a million-token context standard at Flash pricing, and the default Gemini for most of 2025. It was shut down on June 1, 2026 — the largest single removal of live traffic in Gemini's history, since so many integrations had never moved off it.

The facts

Provider Google
Model id gemini-2.0-flash
Also published as gemini-2.0-flash-001
Released February 5, 2025
Deprecated date not published
Shutdown June 1, 2026 · 59 days ago
Status Retired
Last verified July 30, 2026

What to use instead

Google Gemini 3.6 Flash gemini-3.6-flash Provider-recommended Active

Google skips the whole 2.5 and 3.x Flash lineage and names 3.6 Flash directly. Response formats are compatible; the thinking configuration is not, since 2.0 Flash had none.

What parameters gemini-3.6-flash accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them. 

- "model": "gemini-2.0-flash"
+ "model": "gemini-3.6-flash"

Frequently asked questions

When did Google Gemini 2.0 Flash shut down?
Google Gemini 2.0 Flash shut down on June 1, 2026. API requests to it fail from that date onward.
What replaces Google Gemini 2.0 Flash?
Google recommends Gemini 3.6 Flash (`gemini-3.6-flash`) as the replacement for Google Gemini 2.0 Flash. Google skips the whole 2.5 and 3.x Flash lineage and names 3.6 Flash directly. Response formats are compatible; the thinking configuration is not, since 2.0 Flash had none.
Is Google Gemini 2.0 Flash still available?
No. Google Gemini 2.0 Flash is retired and no longer served — it was shut down on June 1, 2026. Calls to it return an error.
How do I migrate from Google Gemini 2.0 Flash to gemini-3.6-flash?
Swap the model id in your API call: replace "gemini-2.0-flash" with "gemini-3.6-flash". Google skips the whole 2.5 and 3.x Flash lineage and names 3.6 Flash directly. Response formats are compatible; the thinking configuration is not, since 2.0 Flash had none.
Does this apply to gemini-2.0-flash-001 too?
Yes. Google Gemini 2.0 Flash is also published as `gemini-2.0-flash-001`; that id shares the same lifecycle dates as `gemini-2.0-flash`.

Sources

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

This page, for machines

JSON Markdown Badge JSON

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

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

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.