GPT-4o API deprecation: Snapshots Shut Down January 14, 2027

The GPT-4o API deprecation notice posted on October 14, 2026 tells developers that several GPT-4 series snapshots leave the API on January 14, 2027. OpenAI’s official deprecations page lists GPT-4o (gpt-4o-2024-08-06, gpt-4o-2024-11-20), GPT-4o mini (gpt-4o-mini-2024-07-18), GPT-4.1 (gpt-4.1-2025-04-14) and GPT-4.1 mini (gpt-4.1-mini-2025-04-14), with gpt-6-luna as the recommended replacement.

What actually happened

OpenAI treats deprecation as the start of the retirement process and shutdown as the day the endpoint stops serving the model. The October 14 entry is labeled “GPT-4 series model deprecations” and sits at the top of the upcoming table on the official page. That is as primary as documentation gets: not a rumor, not a screenshot of a dashboard toast.

The recommended replacement called out in the table is gpt-6-luna. Fine-tunes do not get a special stay of execution; they die with the base. OpenAI’s broader policy text says generally available models normally get at least six months’ notice unless safety or compliance forces a faster timeline — and this January 14, 2027 date is roughly three months from the October 14 announcement for these snapshots, which matches the “specialized variants / shorter notice” spirit more than a leisurely six-month GA runway. Read the page’s notice-period section yourself if you are writing a compliance calendar.

Migration reality for these GPT-4 snapshots

Engineering calendars are the real product impact. Teams still pin gpt-4o-2024-08-06 or gpt-4.1-2025-04-14 in production configs need eval harnesses against gpt-6-luna (or whatever successor their account actually has) before mid-January. Prompt diffs, tool-calling quirks and price cards all move when the model string changes. Secondary write-ups from Times of AI and developer blogs merely restate the GPT-4o API deprecation table; they are useful mirrors, not alternate schedules.

ChatGPT consumer branding is not the same object as these API snapshots. Do not tell a non-technical stakeholder “GPT-4o dies in January” without specifying API. The deprecations page is about API model IDs.

Pinning a snapshot is a contract with a shutdown_date field. Calendar it.

Adjacent OpenAI platform churn — older GPT-5.x codex/nano deprecations, TTS retirements, transcription migrations — is listed on the same page for later dates. We are not collapsing those into this story. One headline, one table row family.

For agent-stack readers, this sits next to other October AI ops notes like Shopify Shop MCP and Anthropic Scion: the interface layer keeps moving under production bots.

What “recommended replacement” does not promise

gpt-6-luna is OpenAI’s pointed successor in the table, not a guarantee that every workload gets cheaper, faster or equally verbose. Run your own golden sets. If a workload needs dedicated capacity after shutdown, OpenAI’s page gestures at sales conversations — that is not a self-serve promise in the docs we read.

Also watch for alias behavior. Some applications call gpt-4o without a dated snapshot. Confirm what that alias resolves to in your account before you assume you are safe until 2027.

Documentation discipline beats folklore. When a coworker forwards a screenshot saying “4o is gone next week,” compare it to the January 14, 2027 row. Premature migrations waste eval time; late migrations create outages. Put the deprecations URL in the ticket template.

If your stack still uses Chat Completions with older function-calling assumptions, budget time for Responses API differences called out in community migration notes — but only after you confirm those notes match OpenAI’s current docs, not a year-old blog. The official table is the schedule source of truth; tooling commentary is optional.

Teams with compliance review boards should attach the October 14 announcement date and the January 14, 2027 shutdown date to every ticket that still mentions GPT-4o snapshots. Auditors like closed loops. A link to the deprecations page plus a grepped list of model strings from your repos is usually enough to start.

Open-source proxies and third-party gateways that hard-code 4o aliases need the same pass. If a gateway silently maps gpt-4o to something else after shutdown, your logs will lie until you notice.

What to do as a reader

If you maintain code against the GPT-4o API deprecation list, inventory every hard-coded model string this week, add shutdown_date checks via the models API, and schedule evals against gpt-6-luna. Tell product owners the January 14, 2027 hard stop in writing.

Keep ChatGPT UI changes out of the same ticket unless they truly share a dependency. Nothing here is investment advice.

Primary sources: OpenAI’s deprecations page and the Times of AI summary.