GPT-4o Deprecation, Shutdown Dates & Migration Guide
Track confirmed UTC deprecation and shutdown dates for GPT-4o (OpenAI) across OpenAI, Azure OpenAI. Preview gpt-4o-2024-08-06 → gpt-6-luna upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.
1. Quick .env & SDK Snippet Replacement Matcher
Edit or paste your .env assignment, LiteLLM route, or SDK model identifier below to check live 3-state EOL status and copy a ready-to-apply replacement diff locally in your browser.
Replacement Diff Preview (gpt-4o-2024-08-06 → gpt-6-luna)
# OPENAI_MODEL: gpt-4o-2024-08-06 -> gpt-6-luna [DEPRECATED · EOL 2027-01-14]
- OPENAI_MODEL="gpt-4o-2024-08-06"
+ OPENAI_MODEL="gpt-6-luna"
# AZURE_OPENAI_DEPLOYMENT: gpt-4o (2024-05-13) -> gpt-5.1 (2025-11-13) [DEPRECATED · EOL 2027-01-14]
- AZURE_OPENAI_DEPLOYMENT="gpt-4o (2024-05-13)"
+ AZURE_OPENAI_DEPLOYMENT="gpt-5.1 (2025-11-13)"
2. Cross-Ecosystem GPT-4o Lifecycle Matrix (9)
Direct vendor APIs and cloud platforms retire dated snapshots on independent schedules. Verify the exact model ID, vendor lifecycle stage, and UTC shutdown date matching your deployment.
| Model ID | Provider | Calculated Status | Confirmed Shutdown (UTC) | Vendor Lifecycle | Replacement & Migration | Source |
|---|---|---|---|---|---|---|
gpt-4o (2024-05-13) |
Azure OpenAI | DEPRECATED (63d) | 2027-01-14in 63d | Deprecated | Docs ↗ | |
gpt-4o |
OpenAI | DEPRECATED (63d) | 2027-01-14in 63d | Deprecated | Docs ↗ | |
gpt-4o-2024-08-06 |
OpenAI | DEPRECATED (63d) | 2027-01-14in 63d | Deprecated | Docs ↗ | |
gpt-4o-2024-11-20 |
OpenAI | DEPRECATED (63d) | 2027-01-14in 63d | Deprecated | Docs ↗ | |
gpt-4o (2024-08-06) |
Azure OpenAI | DEPRECATED (153d) | 2027-04-14in 153d | Deprecated | Docs ↗ | |
gpt-4o (2024-11-20) |
Azure OpenAI | DEPRECATED (153d) | 2027-04-14in 153d | Legacy | Docs ↗ | |
gpt-4o-2024-05-13 |
OpenAI | RETIRED | 2026-10-2320d ago | Retired | Docs ↗ | |
gpt-4o-search-preview-2025-03-11 |
OpenAI | RETIRED | 2026-07-23112d ago | Retired | Docs ↗ | |
chatgpt-4o-latest |
OpenAI | RETIRED | 2026-02-17268d ago | Retired | Docs ↗ |
3. Production Migration Checklist (gpt-4o-2024-08-06 → gpt-6-luna)
Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:
- Inventory pinned model IDs: Search repositories and deployment manifests for
OPENAI_MODEL,openai/LiteLLM routes, and dated snapshot strings in the GPT-4o family (6 deprecated, 3 retired, 0 active variants tracked). - Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against
gpt-6-luna, then compare input, output, and cached token rates in DevToken. - Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated GPT-4o identifiers cannot re-enter production.
4. Related OpenAI & Ecosystem Migration Guides
Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:
GPT-4.1 & GPT-4.1 mini / nano
DEPRECATED (63d)GPT-4 Turbo
RETIREDGPT-4 (0613 / 32k / Vision)
RETIREDGPT-3.5 Turbo
RETIREDGPT-5, GPT-5.1 – GPT-5.5 & Codex
DEPRECATED (29d)5. GPT-4o Deprecation & Upgrade FAQ
Is GPT-4o deprecated or retired across OpenAI, Azure OpenAI?
LLMEOL tracks 9 GPT-4o variants across OpenAI, Azure OpenAI: 6 deprecated with scheduled shutdowns, 3 retired past their UTC EOL date, and 0 active with no announced shutdown date. Check the cross-ecosystem matrix above for exact snapshot dates.
What is the recommended replacement model when migrating off gpt-4o-2024-08-06?
The primary recommended upgrade target for gpt-4o-2024-08-06 is gpt-6-luna. Always test prompt formatting, max output tokens, and tool schemas on gpt-6-luna, and compare token pricing in DevToken before switching production traffic.
How can I replace gpt-4o-2024-08-06 in .env and LiteLLM configs safely?
Paste your OPENAI_MODEL assignment or LiteLLM model block into the Quick Replacement Matcher on this page to generate an exact diff, or open the full Local Model Config Auditor to scan multi-service manifests with zero network upload.