Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Amazon Anthropic Cohere DeepSeek Google MiniMax Mistral Moonshot AI OpenAI Qwen xAI Xiaomi MiMo Z.ai

Providers

Amazon 8 Anthropic 31 Cohere 35 DeepSeek 5 Google 34 MiniMax 17 Mistral 53 Moonshot AI 18 OpenAI 106 Qwen 26 xAI 26 Xiaomi MiMo 4 Z.ai 22
Google gemini-embedding-001

Gemini Embedding 001 (Google)

Shutdown scheduled Shuts down in 650 days

No — Gemini Embedding 001 is not deprecated as of August 3, 2026. Google has not deprecated it, but publishes May 14, 2028 (in 650 days) as the earliest date it could be retired. Google points new work at Gemini Embedding 2.

The first Gemini-branded embedding model, and the holder of the longest runway in Google's entire deprecation table: released July 2025 with a shutdown no earlier than 14 May 2028, almost three years out. Google gives embedding models far more notice than chat models precisely because re-indexing is expensive.

The facts

Provider Google
Model id gemini-embedding-001
Released July 14, 2025
Deprecated not deprecated
Shutdown (earliest) May 14, 2028 · in 650 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 August 3, 2026

What to use instead

Google Gemini Embedding 2 gemini-embedding-2 Provider-recommended Active

What parameters gemini-embedding-2 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-embedding-001"
+ "model": "gemini-embedding-2"

Frequently asked questions

When will Google Gemini Embedding 001 shut down?
Google Gemini Embedding 001 is scheduled to shut down on May 14, 2028, in 650 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 Embedding 001?
Google recommends Gemini Embedding 2 (`gemini-embedding-2`) as the replacement for Google Gemini Embedding 001.
Is Google Gemini Embedding 001 still available?
Yes. Google Gemini Embedding 001 is active and fully supported as of August 3, 2026.
How do I migrate from Google Gemini Embedding 001 to gemini-embedding-2?
Swap the model id in your API call: replace "gemini-embedding-001" with "gemini-embedding-2". Keep the rest of the request the same, then re-check the parameters the new model accepts before you ship.

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

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.