← Back to all deprecations

Migrating off GPT-4o

GPT-4o (OpenAI) — no announced shutdown date, but superseded. Replaced by GPT-5.6 Terra. Source · Verified 2026-08-14.

GPT-4o has no announced OpenAI shutdown date, but it's several generations behind the current GPT-5.6 line and is the single highest-search-volume "legacy model" query we see. This is the migration that most people land on this page looking for.

What should I use instead of GPT-4o?

GPT-4o, from OpenAI, has no announced shutdown date but is superseded. The recommended successor is GPT-5.6 Terra, priced +29% more at blended (3:1) rates — swap the model id in your API calls and test side by side before cutting over production traffic.

Verified 2026-08-14 source

The swap

// All AI Ask API
{
-  "model": "gpt-4o",
+  "model": "gpt-5.6-terra",
   "messages": [...]
}

Same change applies if you call OpenAI directly with its own SDK — only the model identifier changes; request/response shape is otherwise unaffected for a same-provider swap.

What actually changes

GPT-4oGPT-5.6 Terra
Blended $/M$4.38$5.63
Context window128,000 tokens1,000,000 tokens
Max output16,384 tokens128,000 tokens
Modalitiestext, visiontext, vision
Tokens / secunchanged / not measured78

Pricing from our live pricing registry; speed from our benchmark leaderboard where measured.

Gotchas

  • GPT-4o is a non-reasoning model. GPT-5.6 Terra supports an optional reasoning mode — leaving it off gives you a comparable latency profile to GPT-4o; turning it on trades latency for materially better multi-step accuracy at higher token cost. Decide explicitly rather than inheriting whatever the default is.
  • GPT-4o's max output is capped at 16,384 tokens. GPT-5.6 Terra allows much longer completions — if you built retry/continuation logic around hitting that 16K ceiling, you can likely simplify it away.
  • Pricing structure changed generation to generation, not just the headline number — re-check your blended cost estimate at your actual input:output ratio rather than assuming the 3:1 blended figure applies to your workload.
  • If your integration parses OpenAI SDK response objects directly (not just our unified API), double-check any GPT-4o-specific fields your code depends on — the SDK response shape for reasoning-capable models includes additional fields non-reasoning GPT-4o responses never had.

Alternatives beyond the obvious successor

Claude Sonnet 4.6$6.00/M blended

Similar "balanced" positioning from Anthropic, if you want to compare across providers rather than stay in the OpenAI family.

Gemini 3.6 Flash$3.00/M blended

Faster and cheaper than GPT-5.6 Terra with a much larger context window, if raw speed matters more than the OpenAI ecosystem.

DeepSeek V4 Flash$0.66/M blended

Substantially cheaper if budget is the primary driver and you can tolerate a less-polished tool-calling implementation.

Not tied to OpenAI? See cross-vendor alternatives to GPT-5.6 Terra.

FAQ

Is GPT-4o being shut down?

GPT-4o has no announced shutdown date, but it is superseded and no longer the recommended choice. Source: https://platform.openai.com/docs/deprecations.

What should I switch to from GPT-4o?

GPT-5.6 Terra is the direct successor. See "The swap" below for the exact model id change.

Will switching cost more or less?

The successor is +29% more expensive at blended (3:1) pricing. See the comparison table for exact per-million-token numbers.

Batch 50 · gpt-4o decision and evidence contributions. Surface verification: 2026-08-14. These are route-local, server-rendered fixtures; unavailable values are not inferred.

OpenAI API vs product lifecycle disambiguation board

Frozen Batch 50 fixture board. Formula / decision rule: resolved = host + product surface (API / ChatGPT / Enterprise) + exact model version + shutdown evidence Boundary: ChatGPT product deprecation and API deprecation have separate notice and shutdown timelines.

Frozen fixture / field IDJoined inputs and observationCalculated resultState
batch50-gpt-4o-m1-r1
gpt-4o pinned API endpoint · official deprecation notice
host=api.openai.com; endpoint=gpt-4o; version=pinned; surface=API; notice=platform.openai.com/docs/deprecations; shutdown=Unavailable pinned specific 2026-08-14
OpenAI deprecates specific pinned versions; the base gpt-4o string may still route to newer snapshots.
verify exact pinned version in use; shutdown=check notice page for that exact versionVERIFY — pinned version identity required.
batch50-gpt-4o-m1-r2
ChatGPT gpt-4o availability vs API gpt-4o
surface=chatgpt-product; API-endpoint=separate lifecycle; notice=separate
ChatGPT product changes to GPT-4o availability do not affect the API endpoint lifecycle.
product change is not API deprecation; check platform.openai.com/docs/deprecations for APIPASS WITH SEPARATION — product vs API.
batch50-gpt-4o-m1-r3
Azure OpenAI gpt-4o · GCP Vertex gpt-4o
host=azure/vertex; provider=Microsoft/Google; openai-notice=not directly applicable; own-retirement=separate
Cloud provider deployments have their own retirement timelines and notice requirements.
check Azure and Vertex retirement notices independentlyPASS WITH SEPARATION — host-local.

Provenance: Batch 50 gpt-4o module 1 first-party evidence, surface verification date 2026-08-14. OpenAI model deprecation policy. Missing joins fail closed.

Response API vs Chat Completions migration compatibility receipt

Frozen Batch 50 fixture board. Formula / decision rule: compatible = API surface + parameter set + response schema + tool format all joined per successor Boundary: OpenAI may retire older Chat Completions features independently of model deprecation.

Frozen fixture / field IDJoined inputs and observationCalculated resultState
batch50-gpt-4o-m2-r1
Chat Completions gpt-4o to gpt-4.1 · function calling
old surface=Chat Completions; param=tools; successor=gpt-4.1; tool format=same schema; response=same structure
gpt-4.1 supports the same Chat Completions surface; parameter parity documented.
migration path=direct endpoint swap; verify your pinned version cutoffCOMPATIBLE — direct swap candidate.
batch50-gpt-4o-m2-r2
Responses API preview vs Chat Completions gpt-4o
old=gpt-4o Chat Completions; new surface=Responses API; schema=different; migration=API surface change required
Moving to a different API surface requires code changes beyond an endpoint swap.
surface migration is not a drop-in replacement; plan separate integration workCODE CHANGE REQUIRED — surface migration.
batch50-gpt-4o-m2-r3
Vision input workload · base64 image encoding
old=gpt-4o; vision=base64 images in messages; successor=gpt-4.1; vision parity=documented; encoding=same
Vision encoding format is consistent across the Chat Completions surface.
vision migration=compatible; verify token accounting for images on successorCOMPATIBLE — verify image token accounting.

Provenance: Batch 50 gpt-4o module 2 first-party evidence, surface verification date 2026-08-14. OpenAI model deprecation policy. Missing joins fail closed.

Cost-class and capability delta for recommended successors

Frozen Batch 50 fixture board. Formula / decision rule: delta = (successor_blended - gpt4o_blended) / gpt4o_blended x 100 Boundary: Pricing deltas are from public registries as of 2026-08-14; verify before production migration.

Frozen fixture / field IDJoined inputs and observationCalculated resultState
batch50-gpt-4o-m3-r1
gpt-4o to gpt-4.1 price delta
gpt4o blended=approx $3.75/M; gpt4.1 blended=approx $2.00/M (indicative public); delta=approx -47%; verification date=2026-08-14
gpt-4.1 is generally cheaper than pinned gpt-4o; verify current pricing on /llm-api-pricing.
indicative delta = -47%; verify current; quality testing requiredCOST REDUCTION — quality test required.
batch50-gpt-4o-m3-r2
gpt-4o to gpt-4o-mini for cost-sensitive workloads
gpt4o blended=approx $3.75/M; mini blended=approx $0.15/M; delta=-96%; capability trade=significant
Mini costs far less but capability gap may disqualify it for complex workloads.
quality gate must pass before promoting mini; not recommended for all tasksCONDITIONAL — quality gate required.
batch50-gpt-4o-m3-r3
gpt-4o to o3 or o4-mini for reasoning workloads
old=gpt4o; reasoning=extended; o3-blended=higher; o4mini-blended=moderate; capability=reasoning specialist
Reasoning specialist models may handle tasks better but at a different cost class.
reasoning workload test required; cost class = Unavailable until pricing joinedVERIFY — reasoning workload test required.

Provenance: Batch 50 gpt-4o module 3 first-party evidence, surface verification date 2026-08-14. OpenAI model deprecation policy. Missing joins fail closed.

Run the gpt-4o Batch 50 evidence scenario →

Run the old prompt against both models, side by side

The only real way to know if a migration is safe is to test it. One workspace, both models, your actual prompts.

Try It Free