gemini-2.5-flash-image shutdown on October 2, 2026
Google lists gemini-2.5-flash-image for shutdown on October 2, 2026. Sume lists Nano Banana 2 and Pro under google/ ids to move image requests to.

Google's deprecations table lists gemini-2.5-flash-image with a shutdown date of October 2, 2026 and gemini-3.1-flash-image-preview as the recommended replacement. Sume does not list that original model. It lists Nano Banana 2 and Nano Banana Pro as google/nano-banana-2 and google/nano-banana-pro.
Dates are from Google's deprecations page and changelog, read 2026-09-30. Sume's side is from the Image API docs and the API's model list. This is not migration advice for Google's own API.
What does Google say about the shutdown?
The table gives gemini-2.5-flash-image a release date of October 2, 2025, a shutdown date of October 2, 2026, and the replacement above. Separately, a September 18, 2026 changelog entry says Google is limiting access to the 2.5 models to users who have actively used them in the past, and that those models are not deprecated and keep being served until further notice. The image model is the one with a dated shutdown.
| Model | Release | Shutdown | Replacement |
|---|---|---|---|
gemini-2.5-flash-image | October 2, 2025 | October 2, 2026 | gemini-3.1-flash-image-preview |
gemini-2.5-flash-image-preview | May 7, 2025 | January 15, 2026 | gemini-2.5-flash-image |
Which Google image models does Sume list?
Sume's Image API model enum includes google/nano-banana-2 and google/nano-banana-pro, among others. It has no entry for gemini-2.5-flash-image, so there is nothing on Sume to shut down on that date. Sume's docs do not say which Google model each Nano Banana id maps to, so do not assume a one-to-one swap with Google's named replacement. Bare ids such as nano-banana-2 stay valid as aliases.
How do I move a request over?
Pick a google/ id from GET /v1/images/models, then check every parameter against that model's capability list. A request that sets a parameter the model does not list is rejected with 400 unsupported_parameter, not silently dropped, so a payload ported from another API may fail until you trim it. Nano Banana resolution tiers run up to 4K, and the Nano Banana 2 aspect list is the Pro set plus extreme banners. Prices live on the rate card; see Nano Banana 2 pricing.
What if I only use Sume?
Nothing changes for you on October 2 from this notice. See Nano Banana 2 pricing to choose.
Sources
Related posts
More in Models
- Gemini 3.5 Transcribe API limits: 1 hour vs Sume STT's 10 minutes
Gemini 3.5 Transcribe takes up to 1 hour per request, 30 minutes with diarization or word timestamps. Sume STT takes 600 seconds; split longer audio.
- Gemini API speaker diarization: 8 speakers; Sume STT has no labels
Gemini 3.5 Transcribe diarizes up to 8 speakers, 3+ experimental, within 30 minutes per request. Sume STT returns word timings but no speaker labels.
- Gemini Omni video editing: the EEA, UK and under-10-second rules
Google says editing or extending uploaded videos with Omni is unavailable in the EEA, Switzerland and the UK, and uploads must be under 10 seconds.
- Gemini Omni extend video: Google's 40 s cap vs Sume's modes
Google's Gemini Omni can extend a video by 3-10 s up to 40 s. Sume's Omni row has no extend mode; here is what it offers instead.
Written by Sume