Cafiyn Pulse
← Startup Signals
4 min readUpdated 2026-09-07Issue 2

Whisper shuts down on 26 February. The risk is not the deadline.

Five months is a generous window. Whisper is also typically wired into a background job that fails into a queue rather than into a user's face.

ByKarthik KumarCafiyn Innovations
At a glance
Shutdown date
26 February 2027
Announced
26 August 2026
Affected
whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, gpt-4o-transcribe-diarize
Replacements
gpt-transcribe, gpt-live-transcribe
Related date
Legacy audio and realtime family, 20 January 2027

What was announced

On 26 August 2026 OpenAI deprecated whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe and gpt-4o-transcribe-diarize, with removal from the API on 26 February 2027. The named replacements are gpt-transcribe and gpt-live-transcribe.

It arrives alongside a related date. The legacy audio and realtime family, including gpt-realtime, gpt-audio, gpt-4o-audio, gpt-4o-realtime and the mini variants, shuts down on 20 January 2027, announced 20 July 2026. If you do anything with speech, you likely have exposure to both.

Why this one is easy to miss

Whisper has one of the largest install bases of any OpenAI endpoint, and much of that install base is glue code. Transcription is typically not a feature in itself: it is the first step of a pipeline that summarises a call, indexes a meeting, generates subtitles or feeds a search index.

That shape is what makes it risky. Pipeline steps run on a schedule or off a queue, so when they start failing the first symptom is usually an absence rather than an error: summaries stop appearing, a search index quietly stops growing, a metric drifts. Nobody is watching a screen at the moment it breaks.

Five months of notice is genuinely generous. The failure mode is not that the window is too short, it is that a comfortable window invites deferral until the window is no longer comfortable.

Migrating

The replacement path is named, which puts this in the easier category of deprecation: a model string change plus verification. The verification is the part worth budgeting for, because transcription quality is not uniform across accents, audio quality, domain vocabulary and language, and your evaluation set probably does not cover all four.

Note that gpt-live-transcribe and gpt-transcribe are different tools for different shapes of work. If your pipeline processes a completed file, you want the batch-style endpoint; if you are transcribing an ongoing stream, you want the live one. Picking by name similarity rather than by workload is the easy mistake here.

  • grep -rn "whisper-1\|gpt-4o-transcribe\|gpt-4o-mini-transcribe\|gpt-4o-transcribe-diarize"
  • Check scheduled jobs and queue workers specifically, not just request handlers
  • Check any per-customer configuration stored outside the repo
  • Build a evaluation set that includes your worst audio, not your cleanest
  • Choose between gpt-transcribe and gpt-live-transcribe by workload shape, batch versus streaming

What to do

  1. 1Grep for the four affected identifiers now, so the scope is a list rather than an unknown.
  2. 2Look specifically at scheduled jobs and queue consumers, which fail silently.
  3. 3Assemble an evaluation set from your hardest real audio: accents, background noise, domain terms, non-English.
  4. 4Pick the replacement by workload shape, batch or streaming, rather than by name.
  5. 5Check the 20 January 2027 audio and realtime shutdown at the same time, since the exposure usually overlaps.

Common questions

When does Whisper stop working?

26 February 2027 for whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe and gpt-4o-transcribe-diarize. The deprecation was announced on 26 August 2026.

What replaces Whisper?

OpenAI names gpt-transcribe and gpt-live-transcribe. They serve different shapes of work: batch processing of completed audio versus transcription of an ongoing stream.

Is the realtime audio API affected too?

Separately, yes. The legacy audio and realtime family, including gpt-realtime, gpt-audio, gpt-4o-audio and gpt-4o-realtime, shuts down on 20 January 2027, announced 20 July 2026.

Sources

Read against the primary documentation rather than secondary coverage. Where a figure comes from a provider's own docs, it is quoted as published on 2026-09-07.

Related

What a voice agent actually costs per minute →The full OpenAI shutdown calendar →

More from Signals

OpenAI removes o1, o3-mini, o4-mini and GPT-4 Turbo on 23 October. The replacements it names run from 5.5 times the price to 97 percent less.
Eleven models and six fine tuned models go dark in four days. Here is OpenAI's own mapping, what each landing costs on a typical month of traffic, and the places where the named replacement is not the cheapest or cannot be used at all.
OpenCode says a breach hit 1.4 percent of Console users who linked an AI provider. Rotate those keys before the root cause is published.
OpenCode has confirmed the breach and has not said how it happened or what was taken. Here is what the vendor said, who is exposed, the order to work in, and how to limit the damage next time.
GitHub Actions workflow lockfiles are in public preview. Here is how to turn them on, check them in CI, and what they do not protect.
A tag can move after you reviewed it. A lockfile makes the runner use the commit you reviewed. Here is the setup, the CI check, the policy, and what a lockfile cannot tell you.
Next.js 16.4.1 and 15.5.28 fix two critical remote code execution flaws. For one of them there is no workaround.
Two of the three fixes were postponed from September. Here is what each flaw needs in order to be reachable, the one workaround that exists, and what the announcement leaves out.
A poisoned npm release that punishes you for revoking the stolen token. The order of your response is the whole defence.
Most incident guidance starts with revoking the leaked token. Here that is the trigger. What StepSecurity found, the order it recommends, and why a valid provenance attestation did not help.
Claude Haiku 5.5 costs a tenth of Haiku 4.5 per token. One token past 100,000 it costs half.
The rate card is a tenth of Haiku 4.5. The footnote is a threshold that moves the price fivefold and that a tokenizer change pushes you toward.
Gemini 4 Argon launched at $2 and $10 and goes to $4 and $20 on 1 December. Price your product on the second number.
Every tier on the pricing page doubles on the same date. What changes, what the number includes, and what to do if you are building on the launch rate.
Claude Haiku 5.5 is not a model id swap. Five things that worked on Haiku 4.5 now return a 400.
The model id is the easy part. The requests that now fail, the response parsing that changes, and the details that fail quietly.
Next.js shipped 16.3.7 and 16.3.8 a day apart. Only one of them is the security release.
Two patch releases a day apart, one of them a decoy if you are not reading carefully. And the 15.5 line does not get the high severity fix at all.
The EU AI output marking rule is not a December deadline. For most teams it started in August.
Almost every summary of this gives one date. There are two, and which one applies to you depends on when you shipped, not on how big you are.
Sonnet 5.5 cut the rate by a third and the token count went up by about 30 percent.
A third off the per-token rate is not a third off the bill when the same text now costs more tokens. Here is the arithmetic, and the five ways your code can break.
Your AI gateway holds every provider key you have. A 9.9 just landed in LiteLLM.
An AI gateway concentrates every upstream key into one process. That is the point of it, and it is why a privilege escalation there is worse than it looks.
The table your coding agent created does not have row level security on it.
Dashboard-created tables get row level security by default now. API-created tables do not, and API is how your coding agent works.
A 9.5 in next/og. Whether it reaches you depends on one line in your OG route.
The advisory rates it 9.5, but it only fires if your OG image route puts attacker-controlled text into SVG. Here is how to find out which side of that line you are on.
OpenAI and Anthropic both cut prices on 22 September. One of them costs you a refactor.
Two frontier price cuts in one day is a good week for anyone paying a token bill. The migration cost is not evenly distributed, and one of the two prices comes with an expiry hedge.
A package install reads your home directory. This week two of them did it on purpose.
The implant did nothing clever. It read the files your shell reads, in the place your credentials live, and sent them somewhere else. That is the whole attack, and it works.
GitHub is switching off SHA-1 SSH keys. Find out now whether yours is one of them.
The keys at risk are the old ones, on the machines nobody logs into, in the pipelines that have run untouched for three years. Those are also the ones that will fail loudest.
Every third-party script tag is a standing grant to run code on your visitors.
A marketing form, a chat widget, an analytics snippet. Each one is permission for someone else's server to execute whatever it sends, on every page it sits on, forever.
1.8 million Android apps were scanned for hardcoded keys. Here is how to check yours.
Finding secrets in shipped apps is now a cheap, automated pipeline. Anything compiled into an APK, an IPA or a JavaScript bundle should be treated as already published.
OpenAI's Agents API will hold your agent state. What breaks if you ever need to leave.
Two major providers moved into the agent state layer in the same week. A managed harness is a real shortcut, as long as you keep a copy of what it holds.
Meta's Muse agent can now check out at your store. What merchants should change.
Agent purchases are arriving through wallets and single-use cards, not through merchants adopting a new protocol. Many merchants will receive them without choosing to.
What Brevo's SSO incident teaches about multi-tenant SAML and hijacked sending accounts.
One incident, two lessons: why email authentication did not help, and the tenant-scoping mistake anyone shipping SSO can make.
Cloudflare now sorts bots into Search, Training and Agent. What it means for your site and your agent.
The same change lands on two audiences. Site owners can now accidentally block search; agent builders will find more doors closed.
OpenAI has announced ten dated deadlines between 23 October 2026 and 1 April 2027. Here is the calendar.
Ten dated deadlines in six months, every one announced in public. The failure mode is never the notice. Updated 19 October with the entries added since September.
Nvidia bought Hugging Face. Your open-weight fallback is now a vendor relationship.
The commitments say nothing breaks. The structural change is that "we can always self-host" is now a dependency on one vendor rather than on a neutral commons.
The Videos API goes away on 24 September and OpenAI names nothing to move to.
Every other deprecation on OpenAI's page offers a migration target. This one does not, which makes it a different kind of problem.
The Assistants API is gone. Your app may not have told you yet.
It shut down on 26 August 2026. The replacement is not a drop-in, and the most common migration mistake changes your model's behaviour without throwing an error.
One Copilot code review costs 13 requests. Here is the rest of the maths.
Copilot now bills on usage rather than seats. The headline change is simple. The multipliers underneath it are where teams get surprised.
Row-level security is on by default now. That is not the same as being protected.
Lovable fixed the default. The gap that actually leaks data was never the default, it was the policy, and no platform can write that for you.
Your model comparison is measuring the wrong number.
Every price list is per token. Your bill is per finished piece of work. Those two numbers can rank models in opposite orders.
An agent with production log access is a new identity. Treat it like one.
Always-on agents that read production logs are arriving fast. The access-control question they raise is old and well understood, which is the good news.

Open the tool.

Ten production categories, three minutes, and a ranked list of what to fix first.

Check your own stack