Skip to content
modeldeprecations.dev
OpenAI text-embedding-ada-002

text-embedding-ada-002 (OpenAI)

Active

No — text-embedding-ada-002 is not deprecated as of July 30, 2026. OpenAI has announced neither a deprecation nor a shutdown date for it. text-embedding-3-small is a newer alternative, but this model is not being retired.

The embedding model behind most retrieval systems built between 2022 and 2024, and one of the most commonly assumed-dead ids on the platform. It is not on OpenAI's deprecations page: re-embedding a corpus is expensive enough that the old vectors have to keep working, so this one has outlived every chat model of its era.

The facts

Provider OpenAI
Model id text-embedding-ada-002
Released December 15, 2022
Deprecated not deprecated
Shutdown not published
Status Active
Last verified July 30, 2026

What to use instead

OpenAI text-embedding-3-small text-embedding-3-small Active

Not a deprecation — but 3-small is cheaper and scores better. Only worth it if you can afford to re-embed everything, since vectors from the two models are not comparable.

What parameters text-embedding-3-small 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": "text-embedding-ada-002"
+ "model": "text-embedding-3-small"

Frequently asked questions

What replaces OpenAI text-embedding-ada-002?
OpenAI recommends text-embedding-3-small (`text-embedding-3-small`) as the replacement for OpenAI text-embedding-ada-002. Not a deprecation — but 3-small is cheaper and scores better. Only worth it if you can afford to re-embed everything, since vectors from the two models are not comparable.
Is OpenAI text-embedding-ada-002 still available?
Yes. OpenAI text-embedding-ada-002 is active and fully supported as of July 30, 2026.
How do I migrate from OpenAI text-embedding-ada-002 to text-embedding-3-small?
Swap the model id in your API call: replace "text-embedding-ada-002" with "text-embedding-3-small". Not a deprecation — but 3-small is cheaper and scores better. Only worth it if you can afford to re-embed everything, since vectors from the two models are not comparable.

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:

[![text-embedding-ada-002](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/text-embedding-ada-002.json)](https://modeldeprecations.dev/openai/text-embedding-ada-002)

Other OpenAI models

All OpenAI 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.