On June 3, 2026, OpenAI quietly slid a sentence into its Model Release Notes confirming that GPT-4.5 sunsets on June 27 and o3 follows on August 26. The same release note shipped a quality upgrade to GPT-5.5 Instant — the model that’s now the migration target for both. Twenty-four days until GPT-4.5 disappears from ChatGPT’s model picker. OpenAI’s announcement is explicit: these changes apply to ChatGPT only — there are no changes to the API.

BleepingComputer, gHacks, and 4sysops all confirmed the timeline within hours of the changelog drop. The mechanics are familiar (same playbook OpenAI ran with GPT-4o and o4-mini in February). GPT-4.5 shipped in February 2025 as the “most knowledgeable model” in the family. It lived roughly sixteen months — comparable to GPT-4o’s fourteen and GPT-4’s eighteen. The pace of new model releases is the pressure, not shrinking lifespans.

The headline change is GPT-4.5. The bigger operational story for teams running reasoning pipelines is o3. Two retirements, two different migration paths, one common destination.

Quick Summary: What’s Retiring and When

Detail	Info
GPT-4.5 retirement date	June 27, 2026 (24 days from announcement)
o3 retirement date	August 26, 2026 (90-day sunset window)
Announcement source	OpenAI Model Release Notes, June 3, 2026
Confirmed by	BleepingComputer, gHacks, 4sysops
Migration target	GPT-5.5 Instant (upgraded June 3)
API impact	ChatGPT only — API endpoints unaffected per OpenAI’s announcement
ChatGPT impact	Model selector drops both options on retirement dates
Official deprecations page	developers.openai.com/api/docs/deprecations

Bottom line: ChatGPT users lose GPT-4.5 from the model picker on June 27. API users are not affected by this announcement — check the OpenAI deprecations page for any separate API deprecation timeline.

---

What Actually Got Announced on June 3

OpenAI’s June 3 changelog bundled three things into one post: a quality bump for GPT-5.5 Instant, a confirmed retirement date for GPT-4.5, and a reiteration of the o3 deadline first flagged on May 28. The order of operations matters because it tells you what OpenAI thinks the migration story should be.

The GPT-5.5 Instant upgrade landed first. Per the official announcement, the model now produces tighter responses with better text organization, fewer repetitive bullet lists, and clearer paragraphing. Image understanding improved. STEM accuracy improved. Web-search routing got smarter. None of those changes by themselves are world-historical. Stacked together, they’re the closing argument for “GPT-5.5 Instant is the model you should already be on.”

Then came the retirements. GPT-4.5 leaves ChatGPT on June 27 following a 30-day sunset window. OpenAI’s announcement is explicit: these changes apply to ChatGPT only — there are no changes to the API, confirmed by 4sysops. The OpenAI API deprecations page is the authoritative reference for any future API-level retirement dates.

The o3 retirement is the second shoe. Reasoning model, originally GA in the spring of 2025, retired August 26 after the 90-day window that started May 28. Teams who built reasoning pipelines on o3 over the last twelve months have a longer runway, but the destination is the same — GPT-5.5 Thinking for the reasoning paths, GPT-5.5 Instant for the chat layer.

The pattern across both retirements is unusual in one respect: OpenAI bundled the news with a quality upgrade rather than letting it sit naked in a changelog. Compare that to the GPT-4o retirement in February, which OpenAI shipped without a sweetener. The packaging tells you OpenAI expects GPT-4.5 users to push back harder, and they’re not wrong.

Why GPT-4.5 Has a Vocal User Base

This is the part the migration tooling can’t fix. GPT-4.5 was the closest the GPT-5 generation ever came to GPT-4o’s conversational warmth. Users who built habits around GPT-4o and grudgingly moved to GPT-5.x found GPT-4.5 because it felt closer to what they’d lost. The model didn’t ship the cleanest benchmarks. It shipped a tone.

BleepingComputer’s reporting captured the asymmetry directly: o3 has limited ongoing demand, but GPT-4.5 has a dedicated following. The r/ChatGPT subreddit lit up within hours of the June 3 announcement with users planning to downgrade their subscriptions if 4.5 went away. We’ve been here before. The GPT-4o retirement cycle produced the same backlash and the same eventual quiet acceptance. The difference is that GPT-4.5 had roughly sixteen months to build that loyalty — longer than GPT-4o, and nearly as long as the original GPT-4.

For teams running GPT-4.5 via the OpenAI API, this ChatGPT change doesn’t affect your model access — the retirement is ChatGPT-only. But if your product exposes a ChatGPT model picker to end users, expect customer-support tickets in early July from people who can’t figure out why their favorite voice disappeared. Have the GPT-5.5 Instant migration explanation ready before the inbox fills up.

The 24-Day ChatGPT Migration Checklist

Here’s what ChatGPT users depending on GPT-4.5 need to do before June 27. Note: if you’re using GPT-4.5 via the OpenAI API, this ChatGPT retirement doesn’t affect your API access — check the OpenAI deprecations page for any separate API timeline.

1. Audit your ChatGPT workflows

Check your custom GPTs, ChatGPT automations, and any team workflows that specifically use GPT-4.5 from the model picker. For ChatGPT Team or Enterprise admins, survey your users’ model-specific setups before June 27 so no one is caught off guard when the option disappears.

For teams who have built products that wrap ChatGPT and expose model selection to users, check whether your interface references GPT-4.5 by name. Products built directly on the OpenAI API are unaffected by this announcement — but if your product routes through ChatGPT’s interface or model picker, the change is real.

2. Pick the replacement model

For chat-style workloads, GPT-5.5 Instant is the default answer. The June 3 upgrade closed most of the quality complaints that pushed users to GPT-4.5 in the first place — the responses are less bullet-heavy, the paragraphing is more natural, and the model is more direct about its confidence. For reasoning-heavy workloads currently running on o3, GPT-5.5 Thinking is the corresponding pick.

If your existing workflow depends on the specific writing style GPT-4.5 produces, this is where a prompt revision lives. GPT-5.5 Instant won’t replicate 4.5’s voice for free. Adding explicit instructions about tone, paragraph structure, and avoidance of bullet lists in your system prompt closes most of the gap. Some teams will end up running an A/B against Claude Sonnet 4 or Gemini 3.1 Pro and concluding that the writing tone they actually wanted was never coming from OpenAI in the first place.

3. Run your evals before flipping the switch

Whatever eval suite you have — even an informal “did this fix the customer complaints” sanity check — run it against the new model before the cutover. The OpenAI Evals framework is the standard reference, but a homemade list of fifty representative prompts is also fine. The goal is to catch the regressions you’d otherwise discover via Slack at 11 PM on June 28.

For teams running reasoning pipelines on o3, the eval delta matters more. GPT-5.5 Thinking has different cost characteristics, different latency, and different failure modes than o3. Don’t assume parity. The GPT-5.4 thinking review covered the shift dynamics from the last generation; the same patterns apply here.

4. Update fallback routing

If your application has multi-model fallback — primary on OpenAI, fallback on another vendor — update both sides. The old config might fall back from GPT-4.5 to GPT-4o, and GPT-4o is already gone. Run the fallback path explicitly and verify it lands somewhere that still exists.

This is also the moment to revisit whether your fallback should be another OpenAI model at all. The retirement cadence has been consistent — GPT-4.5 lived roughly sixteen months, o3 lived roughly fourteen, GPT-4o lived around fourteen. If your reliability story depends on model continuity, single-vendor fallback inside OpenAI is no longer a hedge. The multi-model routing pattern is a real answer here, and the architecture cost is lower than re-doing this migration every quarter.

5. Deploy and monitor

Stage the change behind a feature flag if you can. Roll it to a percentage of traffic. Watch error rates and latency for the first 48 hours. Have a rollback path that doesn’t require redeploying the entire service. The window between deploy and the June 27 hard deadline is small enough that a clean rollback to gpt-5.5 is the only option — there’s no rollback to gpt-4.5 after the cutover.

What GPT-5.5 Instant Actually Improved

The June 3 quality bump deserves its own section because it changes the migration calculus for teams who were resisting the move.

The biggest functional change is in response shape. Per the official release post, GPT-5.5 Instant now produces:

1. Tighter, more direct answers with less unnecessary preamble.
2. Better paragraph structure in long-form responses rather than reflexive bullet lists.
3. Less formatting clutter — fewer headers, fewer numbered subsections inside short replies.
4. Improved STEM accuracy for math and science prompts where precision matters.
5. Smarter web-search routing — the model is more conservative about invoking search when its internal knowledge is sufficient.

That fifth point is operationally significant for API users who pay per search invocation. The old GPT-5.5 Instant invoked web search more aggressively than necessary in some workload patterns. The upgrade should reduce that surface, which translates to lower invoice line items for chat applications that route through the search-enabled endpoint.

The one notable removal: Canvas is no longer available inside GPT-5.5 Instant or GPT-5.5 Thinking. Writing and coding workflows now happen through writing blocks and code blocks directly in chat responses. For most API users, this is invisible — Canvas was always primarily a ChatGPT product surface. For teams that built workflows assuming Canvas behavior, the migration includes adapting to the new block-based output format.

The Cost Picture After Migration

Migration pricing matters because it’s the part that doesn’t show up in the changelog.

GPT-5.5 Instant pricing tracks roughly with the rest of the GPT-5 family — meaningfully cheaper than GPT-4.5 was, comparable to GPT-5.3 Instant before it. Most teams will see input/output costs hold roughly flat or drop slightly after migration. The exception is teams whose GPT-4.5 workloads were producing very long responses by default — the new prompts that explicitly request similar response lengths from GPT-5.5 Instant will land in the same cost range, but the baseline before tuning may produce shorter (and cheaper) replies.

For the reasoning-side migration from o3 to GPT-5.5 Thinking, the cost story is less friendly. GPT-5.5 Thinking is more expensive per token than o3 was, and the reasoning trace is longer for equivalent problems. Teams running o3 in cost-sensitive reasoning pipelines should expect the August 26 transition to bump inference spend by 20% to 40% depending on workload shape. The DeepSeek 75% price cut and the Claude Opus 4.8 Fast Mode reduction both made the OpenAI reasoning tier less competitive on pure dollars. For workloads that don’t strictly need OpenAI’s reasoning stack, August 26 is a reasonable forcing function to evaluate alternatives.

The Bigger Picture: Why Models Keep Dying Faster

The retirement cadence is the part worth pulling back on. GPT-4 ran for eighteen months. GPT-4o ran for fourteen. GPT-4.5 ran for sixteen. No generational model has survived past eighteen months — and the release pace is accelerating faster than any individual model’s lifespan is shrinking. The practical effect is the same: migration cycles are now a permanent operational cost, not an exception.

The vendor logic is clean — running multiple model generations in parallel multiplies infrastructure cost, splits the optimization work, and dilutes the brand around whichever model OpenAI actually wants users on. The fastest way to push users onto GPT-5.5 is to make GPT-4.5 stop working. From a margin perspective, the decision is rational and probably overdue.

The user logic is messier. Every retirement cycle resets a community of users who built habits, prompts, and workflows around a specific model’s quirks. The GPT-5.2 retirement guide we ran earlier this year covered the previous wave of this dynamic. The pattern has held: users complain loudly, OpenAI ships the replacement anyway, the community migrates within a few weeks, and the cycle resets. What’s changed is the speed.

For teams building production systems on OpenAI’s API, the strategic read is that model continuity is no longer a feature of the platform. Architect for migration. Keep model strings in configuration rather than hard-coded constants. Maintain a working eval suite that can be pointed at any new model in an afternoon. Treat each new model generation as a six-month tenant rather than a permanent fixture.

That’s the same posture enterprise procurement teams are starting to take on the vendor risk side. It’s now a posture API consumers need to take on the model risk side too.

How This Compares to Recent Anthropic and Google Moves

The OpenAI retirement contrasts sharply with how Anthropic and Google have been handling the same pressure.

Anthropic’s Claude versioning has been more conservative — older Claude models stay available on the API long after their successor models ship, often with the older versions still serving meaningful production traffic. The Anthropic API documentation keeps a longer historical model list available than OpenAI does, and the retirement notices come further in advance.

Google’s Gemini lineup has more model proliferation but slower deprecation. Gemini 1.5 Pro was still available on the API a year after Gemini 2.0 shipped. The trade-off is that Google’s older models receive fewer updates and slowly drift behind their successors in quality, but they stay available for teams that want continuity.

OpenAI’s faster cadence is the right answer for OpenAI’s business — it focuses the optimization work and forces customers to ride the quality curve. It’s the wrong answer for any customer whose internal change management can’t keep up with quarterly migration cycles. For those customers, the structural answer is to keep a credible second vendor warm so the next retirement cycle is a procurement choice rather than a fire drill.

Where This Leaves Teams Running on the API Today

Three concrete reader segments, three different migration moves.

Teams running GPT-4.5 in production. Migrate this week. June 27 is twenty-four days out and there is no extension. Update model strings, run your eval suite against GPT-5.5 Instant, ship the change behind a feature flag, monitor error rates for 48 hours. If your prompts depended on GPT-4.5’s specific tone, plan a prompt revision pass in the same sprint. Don’t wait for the last week.

Teams running o3 in reasoning pipelines. You have until August 26 — about twelve weeks. Use the runway to actually evaluate alternatives rather than defaulting to GPT-5.5 Thinking. The cost delta is meaningful, and the DeepSeek and Claude reasoning options have closed most of the quality gap that originally justified o3’s premium. The August 26 deadline is the right moment to actually run the comparison rather than reflexively staying on the OpenAI stack.

Teams not currently on either model. The change still affects you indirectly. If your application calls OpenAI through a third-party orchestration layer, check whether that layer’s defaults change with the retirement. The LangChain, LlamaIndex, and Vercel AI SDK defaults shift over time as upstream models retire. Verify your stack’s behavior before the cutover.

Procurement and platform teams. This is the second OpenAI retirement cycle inside six months. The first was GPT-4o, GPT-4.1, and o4-mini in February. The cadence is the new normal. Build the migration playbook now so the next one — and there will be a next one — is a three-day operational task rather than a three-week scramble.

Frequently Asked Questions

When exactly does GPT-4.5 stop working?

June 27, 2026, per OpenAI’s June 3 changelog. The model is removed from ChatGPT on that date following a 30-day sunset window. Per OpenAI’s announcement, this is a ChatGPT-only change — API endpoints are not affected by this retirement. The OpenAI deprecations page is the authoritative reference for any separate API-level deprecation timeline.

What’s the best replacement for GPT-4.5?

GPT-5.5 Instant, upgraded the same day the retirement was announced. The June 3 quality bump addressed most of the response-shape complaints that originally drove users to GPT-4.5 — tighter responses, less bullet-list reflex, better paragraphing. For workloads that specifically need GPT-4.5’s writing tone, prompt-level tone instructions close most of the gap.

When does o3 retire?

August 26, 2026, following a 90-day sunset window that started May 28. The o3 retirement is part of the same June 3 announcement and confirmed by BleepingComputer, gHacks, and 4sysops. GPT-5.5 Thinking is the recommended replacement for reasoning workloads.

Will my API calls actually fail or fall back to another model?

They fail. There’s no silent fallback in the OpenAI API for retired model strings — requests to deprecated models return an error response. This is the same behavior as previous retirements and the reason every team needs to migrate before the cutover rather than relying on a graceful degradation that doesn’t exist.

Is GPT-5.5 Instant cheaper or more expensive than GPT-4.5?

Roughly comparable for most workloads, slightly cheaper for many. GPT-5.5 Instant tracks the GPT-5 family pricing tier, which is below GPT-4.5’s premium rates. The exact savings depend on token volume in your specific workload — teams whose GPT-4.5 calls produced very long responses by default may see meaningful reductions after migration.

What about ChatGPT users who liked GPT-4.5?

Paid ChatGPT users keep access to GPT-4.5 in the model picker through June 27, then lose it. There’s no extension and no premium tier that keeps it alive longer. The vendor framing is that GPT-5.5 Instant’s June 3 quality upgrade addresses the gap. The user response will be mixed for the next several weeks.

Should we switch vendors entirely instead of migrating to GPT-5.5?

For teams whose workflows have a natural fit with OpenAI’s stack, the migration to GPT-5.5 Instant is the lowest-friction path. For teams whose original GPT-4.5 use was bordered by performance issues, cost pressure, or capability gaps, the retirement is the right moment to actually evaluate Claude, Gemini, or DeepSeek on equal footing. Don’t migrate defensively if the migration itself is forcing a strategic question you’ve been deferring.

How do I check what model my application is using?

Inspect the model parameter in your OpenAI API client configuration. For most SDKs, this is either a constant in your code or an environment variable. Common locations include OPENAI_MODEL env vars, model: keys in YAML config files, framework-specific config files (LangChain’s llm initialization, LlamaIndex’s Settings.llm, Vercel AI SDK’s model: parameter), and hard-coded strings in API call sites. Grep for the literal string gpt-4.5 or gpt-4-5 across your codebase to find every instance.

Our Take

The June 3 announcement is operationally fine and culturally tone-deaf. Bundling a quality upgrade with a retirement deadline is the right vendor move — it gives users a clear destination and lets the migration story write itself. The 24-day window for GPT-4.5 is the part that’s too short. ChatGPT users get 30 days of sunset; teams building products on top of ChatGPT get the same window to audit every model reference, test the replacement, and ship a coordinated update through their normal change-management process. Three weeks isn’t enough for any team running this through enterprise change control.

The o3 timeline is more reasonable. Ninety days is a real runway. Teams running reasoning pipelines have time to actually evaluate alternatives rather than reflexively defaulting to GPT-5.5 Thinking. That’s the migration where the strategic question — does OpenAI’s reasoning tier still earn its premium against Claude and DeepSeek? — is worth pausing on.

The bigger pattern is the part most teams should internalize. Sixteen months is what GPT-4.5 got — roughly the same window every recent OpenAI model has run before retirement. The next retirement cycle will start before anyone is ready for it. The teams that come out of this cleanly are the ones who treat model selection as configuration, keep an eval suite warm, and stop assuming any particular model identifier is going to be available next quarter. Build for the migration, not against it. The next one is already on the changelog calendar somewhere.

---

Last updated: June 4, 2026. Sources: OpenAI Model Release Notes · OpenAI GPT-5.5 Instant announcement · OpenAI API deprecations · BleepingComputer on the retirements · gHacks on GPT-4.5 and o3 sunset dates · 4sysops on the June 3 changelog · OpenAI retiring GPT-4o and older models.

Related reading: GPT-5.2 Model Retirements Guide · GPT-5.4 Thinking Review and GPT-4o Retirement · Anthropic’s $965B IPO and Claude Users · Anthropic vs OpenAI in 2026 · ChatGPT vs Claude 2026 · Gemini vs ChatGPT 2026 · DeepSeek vs ChatGPT Comparison · DeepSeek’s 75% Price Cut · Claude Opus 4.8 Review: Fast Mode 3x Cheaper · Gemini 3.1 Pro vs Claude Opus 4.6 vs GPT-5.2