Gemini 2.5 Flash Image shut down Oct 2: check old IDs on Sume

Google shut down gemini-2.5-flash-image on October 2, 2026 and points to Lite. On Sume an unknown model id returns 404 model_not_found; use a catalog id.

4 min readSume
All posts

Google's pricing page says Gemini 2.5 Flash Image was to be shut down on October 2, 2026, and its image-generation page tells you to move the legacy id gemini-2.5-flash-image to Lite. It is now October 5, so a call that still uses that id on Google's API should be treated as broken. On Sume, no catalog row has that id; an unknown model returns 404 model_not_found.

What changed

Google's pages I read do not give the error body for a call to a shut-down model, so inspect the real response rather than matching on a string.

Gemini image ids, read 2026-10-05
IdStatusMove to
gemini-2.5-flash-imageLegacy; shut down October 2, 2026gemini-3.1-flash-lite-image (Lite)
gemini-3.1-flash-lite-imageCurrent, 1K onlyn/a
gemini-3.1-flash-imageCurrentn/a
gemini-3-pro-imageCurrentn/a

Before you swap

Google's Cloud blog says Nano Banana 2 Lite became generally available on June 30, 2026 and replaces Nano Banana (gemini-2.5-flash-image). Lite is 1K only, and it has no Search grounding, so check those two points before you swap.

On Sume

Sume accepts the bare Image Router ids, such as gpt-image-2 and nano-banana-2, as aliases for their org/slug equivalents, and only for catalog models. The model list is GET /v1/images/models. If your Sume client was sending an old Gemini id, expect a 404 with this error code:

{
  "error": {
    "code": "model_not_found"
  }
}

The fix

The Sume docs state the status and code only; the full body carries more fields, so branch on the 404 status and the code. Replace the id with google/nano-banana-2 ($0.08 list x 1.25 = $0.10 in the repo's static table) or another catalog row.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume