LLMEOL CodeAP Studio

GPT-4 (0613 / 32k / Vision) Deprecation, Shutdown Dates & Migration Guide

Runs locally in your browser — 0 bytes uploaded Synced 2026-11-12 UTC · 10 variants · 1 ecosystems

Track confirmed UTC deprecation and shutdown dates for GPT-4 (0613 / 32k / Vision) (OpenAI) across OpenAI. Preview gpt-4-0613 → gpt-5.6-sol upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.

Tracked Variants 10
Earliest Upcoming EOL 2026-10-23
Recommended Upgrade gpt-5.6-sol
Ecosystems Covered OpenAI

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.

2 of 2 configured models need migration
Full .env Auditor → Compare gpt-5.6-sol Cost in DevToken →

Replacement Diff Preview (gpt-4-0613 → gpt-5.6-sol)

# OPENAI_MODEL: gpt-4-0613 -> gpt-5.6-sol [RETIRED · EOL 2026-10-23]
- OPENAI_MODEL="gpt-4-0613"
+ OPENAI_MODEL="gpt-5.6-sol"

# model: gpt-4-0613 -> gpt-5.6-sol [RETIRED · EOL 2026-10-23]
- model: openai/gpt-4-0613
+ model: openai/gpt-5.6-sol

2. Cross-Ecosystem GPT-4 (0613 / 32k / Vision) Lifecycle Matrix (10)

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.

GPT-4 (0613 / 32k / Vision) lifecycle status, UTC shutdown dates, and replacement models across OpenAI
Model ID Provider Calculated Status Confirmed Shutdown (UTC) Vendor Lifecycle Replacement & Migration Source
gpt-4 OpenAI RETIRED 2026-10-2320d ago Retired
gpt-5.6-sol Cost → Audit →
Docs ↗
gpt-4-0613 OpenAI RETIRED 2026-10-2320d ago Retired
gpt-5.6-sol Cost → Audit →
Docs ↗
gpt-4-0613-completions OpenAI RETIRED 2026-10-2320d ago Retired
gpt-5.6-sol Cost → Audit →
Docs ↗
gpt-4-completions OpenAI RETIRED 2026-10-2320d ago Retired
gpt-5.6-sol Cost → Audit →
Docs ↗
gpt-4-0314 OpenAI RETIRED 2026-03-26231d ago Retired
gpt-5 or gpt-4.1* Cost → Audit →
Docs ↗
gpt-4.5-preview OpenAI RETIRED 2025-07-14486d ago Retired
gpt-4.1 Cost → Audit →
Docs ↗
gpt-4-32k OpenAI RETIRED 2025-06-06524d ago Retired
gpt-4o Cost → Audit →
Docs ↗
gpt-4-32k-0314 OpenAI RETIRED 2025-06-06524d ago Retired
gpt-4o Cost → Audit →
Docs ↗
gpt-4-32k-0613 OpenAI RETIRED 2025-06-06524d ago Retired
gpt-4o Cost → Audit →
Docs ↗
gpt-4-vision-preview OpenAI RETIRED 2024-12-06706d ago Retired
gpt-4o Cost → Audit →
Docs ↗

3. Production Migration Checklist (gpt-4-0613 → gpt-5.6-sol)

Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:

  1. Inventory pinned model IDs: Search repositories and deployment manifests for OPENAI_MODEL, openai/ LiteLLM routes, and dated snapshot strings in the GPT-4 (0613 / 32k / Vision) family (0 deprecated, 10 retired, 0 active variants tracked).
  2. Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against gpt-5.6-sol, then compare input, output, and cached token rates in DevToken.
  3. Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated GPT-4 (0613 / 32k / Vision) identifiers cannot re-enter production.

Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:

5. GPT-4 (0613 / 32k / Vision) Deprecation & Upgrade FAQ

Is GPT-4 (0613 / 32k / Vision) deprecated or retired across OpenAI?

LLMEOL tracks 10 GPT-4 (0613 / 32k / Vision) variants across OpenAI: 0 deprecated with scheduled shutdowns, 10 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-4-0613?

The primary recommended upgrade target for gpt-4-0613 is gpt-5.6-sol. Always test prompt formatting, max output tokens, and tool schemas on gpt-5.6-sol, and compare token pricing in DevToken before switching production traffic.

How can I replace gpt-4-0613 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.