Google Retires Gemini 2.0 Flash-001, Replace with 2.5 Flash
Key insights
- gemini-2.0-flash-001 and gemini-2.0-flash-lite-001 both shut down June 1, 2026; replacements are gemini-2.5-flash and gemini-2.5-flash-lite.
- gemini-2.5-flash itself shuts down October 16, 2026, replaced by gemini-3.5-flash, requiring a second migration just 4.5 months away.
- Google's page states shutdown dates are 'the earliest possible dates,' so June 1 may not be a hard cutover deadline.
Why this matters
Production systems hardcoded to gemini-2.0-flash-001 or gemini-2.0-flash-lite-001 face broken API calls starting today, and the required migration is to gemini-2.5-flash or gemini-2.5-flash-lite, not the latest gemini-3.5-flash generation. The migration is not a one-time event: gemini-2.5-flash already carries an October 16, 2026 shutdown date, meaning teams must plan for a second mandatory migration within roughly 4.5 months of completing the first. Google's accelerating model retirement cadence makes abstracting model selection behind a configuration layer table-stakes architecture for any production Gemini API integration.
Summary
Four Gemini 2.0 model IDs reach their June 1, 2026 shutdown date today: gemini-2.0-flash, gemini-2.0-flash-001, gemini-2.0-flash-lite, and gemini-2.0-flash-lite-001. The correct migration targets are gemini-2.5-flash and gemini-2.5-flash-lite, not gemini-3.5-flash as some coverage has suggested.
Google's deprecation page notes shutdown dates are 'the earliest possible dates on which a model might be retired,' leaving ambiguity on whether hard failures begin exactly today.
Essentially: (Google Gemini API) is stepping the flash tier from 2.0 to 2.5 generation now, with another cutover to 3.x already announced for October 2026.
- gemini-2.0-flash-001 (released Feb 5, 2025) and gemini-2.0-flash-lite-001 (Feb 25, 2025) both map to their 2.5-series successors.
- gemini-2.5-flash is itself scheduled for shutdown October 16, 2026, replaced by gemini-3.5-flash.
Teams migrating today have roughly 4.5 months before the next cutover arrives.
Potential risks and opportunities
Risks
- Teams with gemini-2.0-flash-001 or gemini-2.0-flash-lite-001 hardcoded in production face API failures starting June 1, 2026, with no automatic fallback to gemini-2.5-flash.
- Teams who migrate today to gemini-2.5-flash without abstracting model selection face a second mandatory cutover by October 16, 2026, just 4.5 months away.
- Organizations monitoring only product release notes rather than the Gemini API deprecation page risk missing the June 1 cutover and experiencing unplanned service disruption.
Opportunities
- gemini-3.5-flash, released May 19, 2026 with no announced shutdown date, gives teams the option to leapfrog the October 16, 2026 gemini-2.5-flash cutover by migrating directly to the 3.x tier now.
- API abstraction and model-routing layer vendors can use Google's multi-cutover cadence as direct evidence that hardcoded model IDs are a production liability requiring active management.
- Developer tooling that auto-tracks the Gemini API deprecation page and surfaces upcoming shutdowns gains a clear value proposition as Google's model retirement pace accelerates.
What we don't know yet
- Whether Google enforces hard failures on June 1 exactly or extends a grace window, given the page's explicit caveat that shutdown dates are 'the earliest possible dates.'
- Whether gemini-2.5-flash's October 16, 2026 shutdown date will itself shift, as the stated policy indicates listed dates are minimums rather than firm deadlines.
- What the notification mechanism is for affected developers, since the deprecation page does not describe direct outreach to teams using retiring model IDs.
Originally reported by ai.google.dev
Read the original article →Original headline: Google Retires gemini-2.0-flash-001 and gemini-2.0-flash-lite-001 on June 1; Developers Must Migrate to Gemini 3.5 Flash