If you are wondering whether GPT-4o is still available in ChatGPT on April 28, 2026, the short answer is no. OpenAI's current help documentation says GPT-4o was retired from ChatGPT on February 13, 2026. For Business, Enterprise, and Edu users, it remained available inside Custom GPTs until April 3, 2026. After that date, it was fully retired across ChatGPT plans. API access remains available.
That distinction matters because many teams still use "GPT-4o" as shorthand for two different things:
- the model they were used to picking inside ChatGPT
- the model family they may still call through the API
Those are no longer the same product path.
For WisGate readers and other multi-model teams, this is less a nostalgia story than a routing story. If a widely used model disappears from the ChatGPT picker but remains in the API, teams need to decide what replaces it in user-facing workflows, internal evaluation baselines, and support documentation.
What happened
OpenAI's help article on retiring older ChatGPT models was updated on April 28, 2026, and it restates three practical facts:
GPT-4owas retired from ChatGPT on February 13, 2026- ChatGPT Business, Enterprise, and Edu customers kept access to
GPT-4oin Custom GPTs until April 3, 2026 - API access remains unchanged
That means there is no current ChatGPT plan where GPT-4o is still a normal live option after April 3, 2026.
OpenAI's current documentation also points users toward newer defaults in ChatGPT and newer non-reasoning options in the API:
GPT-5.3is the default ChatGPT directionGPT-4.1remains available in the API as a non-reasoning model with a1,047,576token context window
So the real update is not "GPT-4o was just retired today." It was retired earlier. The current news value is that OpenAI's related help documentation was refreshed recently and still confirms the current status, which makes this a good moment to publish a clean status explainer that matches the live product state.
Background: why GPT-4o still matters
GPT-4o was one of the most familiar model names in the OpenAI ecosystem. Even after newer families arrived, many users still associated it with a useful balance of quality, speed, and multimodal flexibility.
That creates two common problems after retirement:
1. Teams keep old model assumptions in current docs
Internal playbooks, onboarding guides, screenshots, and training materials often lag behind the live picker. A product team may still tell users to "choose GPT-4o" even when that is no longer possible in ChatGPT.
2. Teams confuse ChatGPT availability with API availability
A model disappearing from ChatGPT does not automatically mean it is gone from the API. OpenAI's updated help article is explicit on this point: ChatGPT retirement does not change API access.
That is important for developers, but it can also create product confusion. If customer-facing content says a model is gone while backend integrations still use it, teams need cleaner language.
What replaced GPT-4o in practice
There is no one-line replacement because OpenAI split the experience by product surface.
In ChatGPT
OpenAI's current help articles point users toward the GPT-5 family, especially GPT-5.3, as the default ChatGPT experience. If your team used GPT-4o mainly through the ChatGPT interface, the practical replacement is not "keep looking for GPT-4o." It is to adapt workflows to the current GPT-5-based default stack.
In the API
If your use case depended on a fast, capable, non-reasoning model, GPT-4.1 is the clearest documented comparison point in OpenAI's current model docs. OpenAI describes it as its smartest non-reasoning model and lists support for:
- a
1,047,576token context window - function calling
- structured outputs
- fine-tuning
- web search
- file search
- image generation tools
That does not mean GPT-4.1 is a drop-in behavioral clone of GPT-4o. It means developers now have a documented non-reasoning path that is easier to position in modern API stacks than a retired ChatGPT picker model.
Why this matters for developers and AI teams
Model names are product dependencies
Many teams treat model names as implementation details. They are not. They show up in:
- prompts and support docs
- product settings
- internal benchmark baselines
- demo scripts
- customer success enablement
- routing logic for model gateways
When a model leaves a mainstream interface like ChatGPT, those references become operational debt.
Evaluation baselines need to be refreshed
A lot of teams informally benchmark "against GPT-4o" because it was familiar. That baseline is less useful now for two reasons:
- it no longer reflects the normal ChatGPT user experience as of April 28, 2026
- newer OpenAI paths split between ChatGPT-first defaults and API-first model selection
If you compare providers or route across models, your baseline should reflect what users can actually access today.
Routing layers need a cleaner fallback map
For WisGate-style users, the practical question is not whether GPT-4o was good. It is which model should sit in its old slot now.
That usually means separating three categories:
- default ChatGPT-like general assistant behavior
- API-first non-reasoning workloads
- higher-depth reasoning workloads
Once those categories are separated, replacing GPT-4o becomes a system design decision instead of a vague "use the newest model" instruction.
What teams should do now
If your organization still has GPT-4o in docs, settings, or support language, this is the cleanup list:
1. Audit customer-facing references
Check:
- help center articles
- onboarding flows
- product screenshots
- setup tutorials
- sales collateral
- Custom GPT instructions
Any place that still tells end users to choose GPT-4o in ChatGPT is likely outdated after April 3, 2026.
2. Separate ChatGPT guidance from API guidance
Use wording that makes the distinction explicit:
- "Retired from ChatGPT"
- "Still available in the API"
That avoids a common support problem where users assume a model is either fully gone everywhere or fully available everywhere.
3. Re-benchmark current replacements
Test at least three buckets:
- current ChatGPT default experience
GPT-4.1for API non-reasoning tasks- your preferred reasoning model for deeper workflows
The goal is not to find a sentimental replacement for GPT-4o. The goal is to rebuild the task map around current models.
4. Update routing logic and internal defaults
If your application or gateway still points "general purpose" traffic to a legacy GPT-4o assumption, change that logic now. The right replacement depends on latency, tool use, reasoning depth, and cost tolerance, but the old default should no longer be implicit.
Risks and limitations
This is a status update, not a brand-new model launch
The most important caveat is editorial: this topic is current because OpenAI's current documentation still confirms the live status and related help articles were refreshed recently, not because a new foundation model launched today.
That matters because the last 24 hours were relatively thin on official top-tier model launches. It is better to publish a verified, useful status article than to force a fake "breaking model release" angle.
API availability can still change later
OpenAI says GPT-4o remains available in the API and that future API retirements will be announced in advance. That is the current state, not a permanent guarantee.
Behavioral migration is never one-to-one
Even if a replacement model looks stronger on paper, migration can change output style, tool-calling behavior, latency, and user expectations. Teams should validate production tasks instead of assuming equivalence.
Bottom line
GPT-4o is no longer available in ChatGPT as of April 28, 2026. It was retired from ChatGPT on February 13, 2026, retained temporarily in some Custom GPT contexts until April 3, 2026, and remains available in the API.
For users, that means stop looking for GPT-4o in the ChatGPT model picker.
For developers, it means separate interface retirement from API retirement.
For platform teams, it means refresh your baseline, rewrite stale documentation, and make a deliberate replacement decision instead of letting a retired model name linger in your stack.
FAQ
Is GPT-4o still available in ChatGPT?
No. OpenAI says GPT-4o was retired from ChatGPT on February 13, 2026. Business, Enterprise, and Edu customers kept access in Custom GPTs until April 3, 2026, after which it was fully retired across ChatGPT plans.
Is GPT-4o still available in the OpenAI API?
Yes. OpenAI's current help documentation says the ChatGPT retirement does not change API access.
What replaced GPT-4o in ChatGPT?
OpenAI's current help content points users toward the GPT-5 family, with GPT-5.3 described as the default ChatGPT direction.
What is the closest current API alternative to GPT-4o?
OpenAI's current API docs make GPT-4.1 the clearest documented non-reasoning alternative to evaluate, but teams should test behavior on their own tasks rather than assume a direct one-to-one replacement.
Why is this topic worth covering now if GPT-4o was retired earlier?
Because OpenAI's current documentation still confirms the exact retirement dates and many teams still have outdated assumptions about whether GPT-4o exists in ChatGPT, in Custom GPTs, or only in the API.