gemini-3.1-flash-lite model retirement
Stops workingSubscribe to Gemini APIShare
On May 7, 2027, model gemini-3.1-flash-lite reaches its shutdown date and stops working. Any calls targeting this model on or after that date will fail.
The error you get from May 7, 2027
What Gemini API answers a call to gemini-3.1-flash-lite once the model is gone, as recorded from real responses:
{"error":{"code":404,"message":"This model models/gemini-3.1-flash-lite 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-3.1-flash-lite 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-3.1-flash-lite
Move to the recommended replacement gemini-3.5-flash-lite.
In Gemini API's words
Model: gemini-3.1-flash-lite; Release date: May 7, 2026; Shutdown date: May 7, 2027; Recommended replacement: gemini-3.5-flash-lite
Facts
- API
- Gemini API
generativelanguage.googleapis.com - Model
gemini-3.1-flash-lite- Released
- May 7, 2026 (models.dev)
- Kind
- Model retirement
- Takes effect
- May 7, 2027
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Gemini API's own pages
Questions
When does gemini-3.1-flash-lite shut down?
Calls to the model gemini-3.1-flash-lite stop working on May 7, 2027.
What happens to calls after May 7, 2027?
They fail from that day.
What error does gemini-3.1-flash-lite return once it is shut down?
Gemini API answers HTTP 404: "This model models/gemini-3.1-flash-lite 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.
When was gemini-3.1-flash-lite released?
gemini-3.1-flash-lite was released on May 7, 2026, according to models.dev.
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-omni-flash-previewModel retirement Stopped working -
gemini-2.5-flash-native-audio-preview-12-2025Model retirement Stops workingin 11 days -
gemini-2.5-flash-preview-ttsModel retirement Stops workingin 11 days -
gemini-2.5-pro-preview-ttsModel retirement Stops workingin 11 days -
gemini-3.1-flash-live-previewModel retirement Stops workingin 11 days -
gemini-3.1-flash-tts-previewModel retirement Stops workingin 11 days -
gemini-2.5-flashModel retirement Redirectsin 25 days -
gemini-2.5-proModel retirement Redirectsin 25 days -
gemini-omni-1.1-flashModel retirement Stops workingin 27 days -
gemini-2.5-flash-imageModel retirement Stops workingin 129 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before May 7, 2027.