Nano Banana 2 shutdown on Oct 29? Google's changelog gives no date

Google has not published an October 29 shutdown date for Nano Banana 2 on the pages we read. The Gemini API changelog entry for October 6, 2026 says gemini-nano-banana-2.1 is generally available and that gemini-3.1-flash-image (Nano Banana 2) is deprecated, with no shutdown date announced. Several third-party articles quote 29 October. Treat that date as unconfirmed until Google prints it.

This matters if you plan a migration around a deadline. A deprecation with no date means you should move, but you do not have a verified cutoff to put in a ticket. If you call Nano Banana 2 through Sume, the question is mostly moot, because Sume already redirects the old id.

What each page says

The table separates what Google's own pages state from what we could not confirm.

What Sume does with the old id

In the Sume Image API, google/nano-banana-2 and the bare id nano-banana-2 are retired, but both are still accepted. A request that uses either one runs as google/nano-banana-2.1, and the job stores the 2.1 id. The catalog at GET /v1/images/models does not list the retired id.

So a script that still sends the old id keeps working. Your own records will show the new id on the job, which is useful when you diff cost logs before and after the switch.

Move your code in three steps

• Search your repo for nano-banana-2 and gemini-3.1-flash-image.
• Replace the Sume model value with google/nano-banana-2.1. Keep your aspect_ratio and resolution values; the 2.1 row lists 0.5K, 1K, 2K and 4K.
• Run one request at each resolution you use and compare usage.cost with your old logs. Read the price from GET /v1/images/models/google/nano-banana-2.1/endpoints instead of copying a number from an article.

Why the date matters less than the habit

A rumored date is a poor basis for a migration plan, and a missing date is a poor reason to wait. The practical middle is to treat the deprecation notice as the trigger and your own test run as the gate. Pin one request in staging on the new id, compare the image and the billed amount, and only then change production.

Google's pricing page lists Nano Banana 2.1 at $0.0336 per 1K image on the standard tier and half of that on its batch tier. Sume's own bill is separate and is set by its catalog, so a Google price drop does not by itself change what a Sume request costs. Read usage.cost on a real request to see the number you will pay.

What Sume does not do

Sume does not publish Google's shutdown schedule and does not warn you ahead of a Google date. Sume also does not expose Google-side options such as thinking level on this route. If a date is announced later, the Gemini changelog is the page to trust, not a repost.