Skip to content
modeldeprecations.dev
OpenAI gpt-4o-mini-transcribe-2025-03-20

GPT-4o mini Transcribe (2025-03-20) (OpenAI)

Deprecated Shuts down in 170 days

Yes — OpenAI deprecated GPT-4o mini Transcribe (2025-03-20) on July 20, 2026 and shuts it down on January 20, 2027 (in 170 days). The recommended replacement is GPT-4o mini Transcribe (2025-12-15).

The March 2025 snapshot of OpenAI's small speech-to-text model, and the first thing to beat Whisper on word error rate on OpenAI's own API. It is the only transcription id in the July 2026 legacy-audio deprecation: the floating gpt-4o-mini-transcribe slug moved to the December snapshot, and this pinned one is what stops answering.

The facts

Provider OpenAI
Model id gpt-4o-mini-transcribe-2025-03-20
Released
Deprecated July 20, 2026
Shutdown January 20, 2027 · in 170 days
Status Deprecated
Last verified August 3, 2026

What to use instead

OpenAI GPT-4o mini Transcribe (2025-12-15) gpt-4o-mini-transcribe-2025-12-15 Provider-recommended Active

If your code says gpt-4o-mini-transcribe without a date you are already on the December snapshot and nothing breaks. Only the pinned March string is going away.

What parameters gpt-4o-mini-transcribe-2025-12-15 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": "gpt-4o-mini-transcribe-2025-03-20"
+ "model": "gpt-4o-mini-transcribe-2025-12-15"

Frequently asked questions

When will OpenAI GPT-4o mini Transcribe (2025-03-20) shut down?
OpenAI GPT-4o mini Transcribe (2025-03-20) is scheduled to shut down on January 20, 2027, in 170 days.
What replaces OpenAI GPT-4o mini Transcribe (2025-03-20)?
OpenAI recommends GPT-4o mini Transcribe (2025-12-15) (`gpt-4o-mini-transcribe-2025-12-15`) as the replacement for OpenAI GPT-4o mini Transcribe (2025-03-20). If your code says gpt-4o-mini-transcribe without a date you are already on the December snapshot and nothing breaks. Only the pinned March string is going away.
Is OpenAI GPT-4o mini Transcribe (2025-03-20) still available?
Yes, for now. OpenAI GPT-4o mini Transcribe (2025-03-20) is deprecated but still answers requests until January 20, 2027. Deprecated models get no further updates and are the first to lose capacity.
How do I migrate from OpenAI GPT-4o mini Transcribe (2025-03-20) to gpt-4o-mini-transcribe-2025-12-15?
Swap the model id in your API call: replace "gpt-4o-mini-transcribe-2025-03-20" with "gpt-4o-mini-transcribe-2025-12-15". If your code says gpt-4o-mini-transcribe without a date you are already on the December snapshot and nothing breaks. Only the pinned March string is going away.

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:

[![gpt-4o-mini-transcribe-2025-03-20](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4o-mini-transcribe-2025-03-20.json)](https://modeldeprecations.dev/openai/gpt-4o-mini-transcribe-2025-03-20)

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.