Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

Anthropic 29 Google 24 OpenAI 103
OpenAI gpt-image-1

GPT Image 1 (OpenAI)

Deprecated Shuts down in 85 days

Yes — OpenAI deprecated GPT Image 1 on April 22, 2026 and shuts it down on October 23, 2026 (in 85 days). The recommended replacement is GPT Image 2.

The first image model of the GPT era, and the one that made image editing with a reference picture routine. It replaced the DALL·E line and was itself deprecated less than a year later, in the same April 2026 announcement that took out the o-series.

The facts

Provider OpenAI
Model id gpt-image-1
Released —
Deprecated April 22, 2026
Shutdown October 23, 2026 · in 85 days
Status Deprecated
Last verified July 30, 2026

What to use instead

OpenAI GPT Image 2 gpt-image-2 Provider-recommended Active

A same-family upgrade, so the request shape carries over. Check output pricing per image size before rolling out — the tiers changed.

What parameters gpt-image-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": "gpt-image-1"
+ "model": "gpt-image-2"

Frequently asked questions

When will OpenAI GPT Image 1 shut down?
OpenAI GPT Image 1 is scheduled to shut down on October 23, 2026, in 85 days.
What replaces OpenAI GPT Image 1?
OpenAI recommends GPT Image 2 (`gpt-image-2`) as the replacement for OpenAI GPT Image 1. A same-family upgrade, so the request shape carries over. Check output pricing per image size before rolling out — the tiers changed.
Is OpenAI GPT Image 1 still available?
Yes, for now. OpenAI GPT Image 1 is deprecated but still answers requests until October 23, 2026. Deprecated models get no further updates and are the first to lose capacity.
How do I migrate from OpenAI GPT Image 1 to gpt-image-2?
Swap the model id in your API call: replace "gpt-image-1" with "gpt-image-2". A same-family upgrade, so the request shape carries over. Check output pricing per image size before rolling out — the tiers changed.

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:

[![gpt-image-1](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-image-1.json)](https://modeldeprecations.dev/openai/gpt-image-1)

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.