gemini-2.0-flash-lite-001 model retirement
Stopped workingSubscribe to Gemini APIShare
On June 1, 2026, the model gemini-2.0-flash-lite-001 was shut down. Calls specifying model gemini-2.0-flash-lite-001 fail since that date. Gemini API previously listed this retirement date alongside its release.
The error you get
What Gemini API answers a call to gemini-2.0-flash-lite-001 once the model is gone, as recorded from real responses:
{"error":{"code":404,"message":"This model models/gemini-2.0-flash-lite-001 is no longer available to new users. Please update your code to use a newer model for the latest features and improvements.","status":"NOT_FOUND"}}{"error":{"code":404,"message":"models/gemini-2.0-flash-lite-001 is not found for API version v1beta, or is not supported for generateContent. Call ModelService.ListModels to see the list of available models and their supported methods.","status":"NOT_FOUND"}}What to use instead of gemini-2.0-flash-lite-001
Move to gemini-3.5-flash-lite. The earlier replacement gemini-3.1-flash-lite stops working on May 7, 2027.
In Gemini API's words
Model: gemini-2.0-flash-lite-001; Release date: February 25, 2025; Shutdown date: June 1, 2026; Recommended replacement: gemini-3.1-flash-lite
Facts
- API
- Gemini API
generativelanguage.googleapis.com - Model
gemini-2.0-flash-lite-001- Kind
- Model retirement
- Takes effect
- June 1, 2026
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Gemini API's own pages
Questions
When does gemini-2.0-flash-lite-001 shut down?
Calls to the model gemini-2.0-flash-lite-001 stopped working on June 1, 2026.
What happens to calls after June 1, 2026?
They have failed since June 1, 2026.
What error does gemini-2.0-flash-lite-001 return once it is shut down?
Gemini API answers HTTP 404: "This model models/gemini-2.0-flash-lite-001 is no longer available to new users. Please update your code to use a newer model for the latest features and improvements.". Send another model to fix it.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Gemini API 10
-
gemini-robotics-er-1.5-previewModel retirement Stopped working -
gemini-3.1-flash-lite-previewModel retirement Stopped working -
gemini-2.0-flashModel retirement Stopped working -
gemini-2.0-flash-001Model retirement Stopped working -
gemini-2.0-flash-liteModel retirement Stopped working -
gemini-3-pro-image-previewModel retirement Stopped working -
gemini-3.1-flash-image-previewModel retirement Stopped working -
veo-2.0-generate-001Model retirement Stopped working -
veo-3.0-fast-generate-001Model retirement Stopped working -
veo-3.0-generate-001Model retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.