Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

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

Gemini 2.5 Flash (Google)

Shutdown scheduled Shuts down in 78 days

No — Gemini 2.5 Flash is not deprecated as of July 30, 2026. Google has not deprecated it, but publishes October 16, 2026 (in 78 days) as the earliest date it could be retired. Google points new work at Gemini 3.6 Flash.

Probably the highest-volume Gemini model ever deployed: fast, cheap, and the first Flash with a configurable thinking budget. Active, but Google has published October 16, 2026 as the earliest date it could be retired.

The facts

Provider Google
Model id gemini-2.5-flash
Released June 17, 2025
Deprecated not deprecated
Shutdown (earliest) October 16, 2026 · in 78 days

The provider publishes this as the earliest date the model could be retired, not a commitment. It may move later, but not earlier.
Status Shutdown scheduled
Last verified July 30, 2026

What to use instead

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

Google skips 3.1 and 3.5 and names 3.6 Flash directly. The thinking-budget configuration introduced in 2.5 Flash has changed shape since — re-read the thinking docs rather than porting the config.

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.5-flash"
+ "model": "gemini-3.6-flash"

Frequently asked questions

When will Google Gemini 2.5 Flash shut down?
Google Gemini 2.5 Flash is scheduled to shut down on October 16, 2026, in 78 days. Google publishes this as the earliest possible retirement date rather than a firm commitment, so it may move later — but not earlier.
What replaces Google Gemini 2.5 Flash?
Google recommends Gemini 3.6 Flash (`gemini-3.6-flash`) as the replacement for Google Gemini 2.5 Flash. Google skips 3.1 and 3.5 and names 3.6 Flash directly. The thinking-budget configuration introduced in 2.5 Flash has changed shape since — re-read the thinking docs rather than porting the config.
Is Google Gemini 2.5 Flash still available?
Yes. Google Gemini 2.5 Flash is active and fully supported as of July 30, 2026.
How do I migrate from Google Gemini 2.5 Flash to gemini-3.6-flash?
Swap the model id in your API call: replace "gemini-2.5-flash" with "gemini-3.6-flash". Google skips 3.1 and 3.5 and names 3.6 Flash directly. The thinking-budget configuration introduced in 2.5 Flash has changed shape since — re-read the thinking docs rather than porting the config.

Models that migrate here

Google names Gemini 2.5 Flash as the replacement for 2 models.

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.5-flash](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/google/gemini-2.5-flash.json)](https://modeldeprecations.dev/google/gemini-2.5-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.