gemini-omni-flash-preview shuts down 2026-09-30: which line to change, which id to use, how to verify
Google lists gemini-omni-flash-preview under Deprecated models on the Gemini API deprecations page: released 2026-06-30, earliest shutdown 2026-09-30, recommended replacement gemini-omni-1.1-flash. This page covers the migration only - which id expires, which id replaces it, which single field in your request changes, how to check it afterwards, and where both ids actually stand in our catalog (checked 2026-09-20).
Updated 2026-09-20
Four cells on Google's table
earliest shutdown date
The Shutdown date cell for this row reads 2026-09-30. The same page adds that the dates are the earliest possible retirement days and that the exact shutdown date is communicated in advance. Treat it as a deadline, not as a promise that nothing moves before that day.
the only id in Recommended replacement
That cell names one id, gemini-omni-1.1-flash. The same table gives it a release date of 2026-08-27 and no shutdown date. Google publishes no mapping of capability, quota, context or price between the two rows, so equivalence is yours to measure.
the migration surface in the request
The replacement cell swaps an id and says nothing about a new endpoint, new authentication or a different payload shape. If the model name is the only place you hard-code it, the edit is one value - our reading of the table, not a sentence Google wrote.
priced calls on QCode in 30 days (2026-09-20)
Our own check, 2026-09-20: gemini-omni-flash-preview is still an entry in the /models catalog, with 0 priced calls in the last 30 days; gemini-omni-1.1-flash is not in that snapshot at all.
What “shut down” means on that page
The page draws its own border: it lists known deprecation schedules for stable and preview models in the Gemini API - one calling surface, not "all of Gemini". It also separates two words. Deprecation is the announcement that support has ended and shutdown is coming; shutdown means the model is completely turned off and the endpoint is no longer available. The dates carry the same caveat: earliest possible, exact date communicated in advance. This page writes from the text of that table only - the gray row that flags an already-shut-down model is a visual device a text archive cannot read, so nothing here states whether the entry answers at this moment.
Which version of the table this page reads
Our archive of the Google page was captured 2026-09-21, and the page itself says Last updated 2026-09-17 UTC. At capture time the deprecated row already carried all three cells: released 2026-06-30, shutdown 2026-09-30, replacement gemini-omni-1.1-flash. Google adds that announcements go to the Release notes page and that this table only tracks the dates. Our check date is 2026-09-20, i.e. 10 days before 2026-09-30 - our own subtraction, not an official sentence. If the table changes, every number here needs re-verifying.
Timeline
2026-06-30: the table's Release date cell for gemini-omni-flash-preview. Release to the earliest shutdown date 2026-09-30 is about 3 months - our subtraction, not Google's wording.
2026-08-27: the replacement id gemini-omni-1.1-flash appears in the table with No shutdown date announced. It landed 34 days before the old id's earliest shutdown day (our arithmetic), so nobody has to wait for the successor.
2026-09-30: the earliest shutdown date in the table. Our own reading, dated 2026-09-20: gemini-omni-flash-preview is still in the /models catalog with 0 priced calls over the last 30 days.
Confirmed vs caution
Officially confirmed
Confirmable from the archive we hold (captured 2026-09-21, page self-dated 2026-09-17): release 2026-06-30, earliest shutdown 2026-09-30, a replacement cell naming gemini-omni-1.1-flash and nothing else, that replacement released 2026-08-27 with no shutdown date, and the definition that a shut-down model has its endpoint unavailable. All from that table, none inferred.
⚠️ Caution
Four things this page does not write. 1) Whether the two entries match on capability, context length, quota or price - the table has no such column. 2) What the failure looks like on the day: only “no longer available”, no code, no timing. 3) Anything past this one id and this one calling surface; this is not “Gemini being wound down”. 4) Whether QCode will list gemini-omni-1.1-flash: our 2026-09-20 snapshot does not contain it, and “coming soon” is not a fact.
The id from the table vs our catalog as it stands
Official replacement: gemini-omni-1.1-flash
The only id Google names, released 2026-08-27 with no shutdown date announced. It is a separate entry on Google's endpoint, and nothing in the table says the two are equivalent in capability, limits or price.
QCode catalog state
In the 2026-09-20 /models snapshot gemini-omni-flash-preview is still listed, with 0 priced calls in 30 days, and gemini-omni-1.1-flash is not found by the same search that does find the old id - a real negative, not a typo. This page promises no destination on our side.
Four steps: search, swap, verify, keep evidence
First, search everywhere for the string gemini-omni-flash-preview: code, .env, gateway route tables, eval scripts, fallback lists - each leftover is one sudden failure. Second, change the value only: point model at gemini-omni-1.1-flash; the table mentions no change to endpoint, authentication or payload shape. Third, verify: send one minimal request on the new configuration, confirm it answers and that your usage shows the entry you intended, then run your longest production-shaped input. If you call through an aggregator, our 2026-09-20 catalog has no gemini-omni-1.1-flash entry, so check /models first. Fourth, keep the pre-change log and response, so a later difference points at the model or at your config.
On QCode
Two internal facts, both dated 2026-09-20: gemini-omni-flash-preview is still an entry in our /models catalog, with 0 priced calls over the last 30 days; gemini-omni-1.1-flash is not in that snapshot. The one honest conclusion: this Google shutdown touches almost no real traffic on our side, and you still cannot just swap to the official replacement id here today. Whether it lands later is not something this page predicts; availability and prices live on /models and /pricing.
FAQ
Do we have to wait until 2026-09-30?
No, and don't. The table calls its dates the earliest possible retirement days and says the exact shutdown date comes with advance notice. Doing the edit this week is safer than leaving it to 2026-09-30.
How do I know the change actually took?
Three checks: the string is gone from code and config; a minimal request on the new setup answers normally; your usage records show the entry you intended. The first two can be done any day before 2026-09-30.
Will the new id produce the same output?
The table compares nothing, so this page does not write the word “same”. Run your own samples, especially long multi-turn context and anything on the tool-calling path.
What error comes back after the shutdown?
The documentation goes only as far as “the endpoint is no longer available”: no status code, no payload shape. Do not hard-code a branch around a guessed 4xx - keep logs from either side of the date and watch your own alerts.
We call this id through QCode. Do we lose it?
In the catalog of 2026-09-20 it is still an entry, with 0 priced calls in the last 30 days, and the upstream earliest shutdown date is 2026-09-30. What we do with the entry afterwards is not decided on this page: pick another listed row from /models, or ask us first. This page is not a notice that QCode is retiring anything.
Are other ids on that line expiring too?
This page looked at two rows in the Omni Flash section and nothing else, so do not read it as the whole Gemini line being retired. For any other id, find its own row on that table and see whether the Shutdown date cell holds a date or the words No shutdown date announced.
Sources
Google, “Gemini deprecations | Gemini API | Google AI for Developers”, https://ai.google.dev/gemini-api/docs/deprecations - archive captured 2026-09-21, the page itself says Last updated 2026-09-17 UTC; the two rows in the Gemini Omni Flash section are this page's only external evidence. Site side: the https://qcode.cc/models snapshot of 2026-09-20 and our own priced-call count for the preceding 30 days. Dates and ids follow the latest official table; nothing is extrapolated here.
Close that one line first, then choose a home
Our 2026-09-20 catalog still lists gemini-omni-flash-preview (0 priced calls in 30 days); gemini-omni-1.1-flash is not listed. Check /models and /pricing before re-pointing anything.
Related
Gemini 4 tracker: pre-training confirmed, no date given
What Google actually said about the next model, and what it did not.
Gemini 3.8 Flash price and availability
The Flash row with no shutdown date: intro price and the later doubling.
Gemini CLI “Client No Longer Supported” vs a zero quota
Another no-longer-supported message whose cause and fix are not a shutdown.
Not affiliated with Google. Dates and ids are transcribed from a public page captured 2026-09-21 and self-dated 2026-09-17; “3 months”, “34 days” and “10 days” are our own subtractions of two dates in the table. QCode does not resell Google's endpoint and does not quote its prices.