As of September 8, 2026, we could not verify a publicly released Nano Banana 2.5 Flash API in Google's image-generation documentation or Gemini API release notes. The name appears in a recent report about code traces, but a reported name is not a callable model ID. Developers can already build with documented Nano Banana models; the proposed 2.5 Flash version still needs an official identity, access details, and pricing.
The useful distinction is between an early signal and an integration you can ship. This guide separates those two, untangles the similar model names, and explains what to check before changing an image-generation pipeline.
If you need a working integration today, the SeeAPI Nano Banana 2 API documentation describes an existing image-generation route. It is a current alternative, not evidence that Nano Banana 2.5 Flash has launched.
What the latest report actually establishes
TestingCatalog reported on September 5, 2026 that Gemini desktop code traces pointed to a Nano Banana upgrade called Nano Banana 2.5 Flash. Its report also said the discussed features remained in closed testing and that the public-release timeline was unclear. We have not independently inspected that underlying code or tested the reported model.
This supports a narrow statement: a third party has reported a development signal under that name. It does not establish a Google launch announcement, an API endpoint, customer access, or a final feature list. A label found in an application can change before release and may not match the eventual developer-facing name.
For the official baseline, we checked Google's Nano Banana image-generation guide and Gemini API release notes. The guide currently identifies four image models, including Nano Banana 2 Lite. It does not list Nano Banana 2.5 Flash as a separate model in the material reviewed.
Do not confuse Nano Banana 2.5 Flash with Gemini 2.5 Flash Image
The numbering is easy to misread. The original Nano Banana was Gemini 2.5 Flash Image, introduced in August 2025. That does not make it the newly reported Nano Banana 2.5 Flash.
Nano Banana: Gemini 2.5 Flash Image; Google model ID gemini-2.5-flash-image. Google's current guide treats it as the legacy model.
Nano Banana 2: Gemini 3.1 Flash Image; Google model ID gemini-3.1-flash-image. This is the documented general-purpose image model.
Nano Banana 2 Lite: Gemini 3.1 Flash Lite Image; Google model ID gemini-3.1-flash-lite-image. It is a separate speed-and-cost-oriented option, not another spelling of 2.5 Flash.
Nano Banana Pro: Gemini 3 Pro Image; Google model ID gemini-3-pro-image. It is the higher-end option in the current family.
Nano Banana 2.5 Flash: the reported new name. No official model ID was verified in the sources checked for this article.
Google's release notes record the stable Nano Banana 2 and Pro models on May 28, 2026, and Nano Banana 2 Lite on June 30. Older tutorials may still use preview IDs. Use the current model documentation for your chosen provider instead of copying an old alias or constructing a new ID from a headline.
What is confirmed, and what is still unknown?
The following is an editorial evidence checklist, not a model benchmark.
Official identity: the existing family has documented names and IDs. A final official identity for 2.5 Flash remains unverified.
API access: existing Nano Banana routes are documented. A public 2.5 Flash endpoint, account eligibility, supported regions, and rollout schedule remain unverified.
Inputs and output controls: existing models have their own documented capabilities. Resolution, reference-image limits, editing behavior, and aspect ratios for 2.5 Flash are not established by the report.
Performance: no reproducible 2.5 Flash latency, quality, consistency, or text-rendering results were verified. The word Flash is not a measured speed guarantee.
Pricing: no official 2.5 Flash price or billing unit was verified. Existing-model prices must not be presented as its launch price.
SeeAPI availability: SeeAPI documents Nano Banana, Nano Banana 2, Nano Banana 2 Lite, and Nano Banana Pro. We did not find a public 2.5 Flash route in the catalog and documentation checked.
Absence from the reviewed sources does not prove that a model is not being developed. It means there is not enough public evidence here to recommend a production integration under that name.
Which API can developers use now?
For Google's direct API, the current image guide demonstrates Nano Banana 2 with the model ID gemini-3.1-flash-image through the Interactions API. Its capabilities belong to that documented model; they should not be copied into a speculative 2.5 Flash specification sheet.
SeeAPI uses a different public naming and request contract. Its Nano Banana 2 text-to-image documentation specifies model nano-banana-2, endpoint text-to-image, and POST https://api.seeapi.com/v1/generations. A Google model ID cannot simply replace the SeeAPI model field.
Here is a request body adapted from the current SeeAPI documentation for the existing Nano Banana 2 route. It is documentation-based and was not executed as a benchmark for this article.
{
"model": "nano-banana-2",
"endpoint": "text-to-image",
"provider": "seeapi",
"input": {
"prompt": "An editorial product photograph of a ceramic cup on warm ivory paper, soft window light",
"aspect_ratio": "3:2",
"resolution": "1K"
}
}Send the request with Content-Type: application/json, Bearer authentication, and the required Idempotency-Key header. Use a unique idempotency key for a new generation and reuse it only for an identical retry. A 202 response means processing has started; it is not the finished image. Keep the returned generation ID and follow the documented task-status or callback flow to obtain the result.
An unknown-model error after substituting an invented 2.5 Flash ID does not demonstrate a private preview or a regional rollout. Check the documented model, endpoint, provider, and account access first.
How to budget without an announced 2.5 Flash price
Budget against the route you can actually call. On September 8, SeeAPI's Nano Banana 2 text-to-image documentation lists 12 credits per generation at 1K, 18 at 2K, and 26 at 4K for its SeeAPI provider option. These are existing Nano Banana 2 credits, not Google direct pricing and not a 2.5 Flash estimate. Dollar equivalents depend on the selected credit plan.
For planning, multiply expected generation count by the relevant credit rate, then allow for extra attempts needed to obtain an acceptable asset. Record successful outputs, paid attempts, latency, and manual cleanup separately. A lower advertised unit price can still cost more per usable image if your workload needs more revisions.
Keep the model and provider configurable while the new name remains unconfirmed. That makes a later evaluation easier without committing the product to an endpoint or price that has not been documented.
What would change the status from a signal to a usable API?
Look for a complete chain of evidence rather than another headline:
An official Google announcement or model card that establishes the final name and relationship to the existing family.
A documented API model ID, request schema, and access route available to the intended account and region.
Pricing with clear input/output or per-image units, resolution conditions, and any separate tool charges.
Documented limits and a small workload-specific evaluation covering your reference images, text, aspect ratios, and editing requirements.
For a gateway integration, that gateway's own public model ID and endpoint documentation; official Google availability alone does not establish gateway support.
Once those exist, evaluate the new route with the same prompts and references used for your current baseline. Keep failures in the results and compare total cost per usable image. Until then, claims that 2.5 Flash is faster, cheaper, or better than Nano Banana 2 remain unsupported by the evidence reviewed here.
Should you wait for Nano Banana 2.5 Flash?
For a project that needs image generation now, start with a documented model that meets your requirements and keep the integration replaceable. Waiting is reasonable only when a future capability is essential and your schedule can absorb an unknown release date; the reported name alone is not enough to identify that capability.
Use SeeAPI's current model catalog to choose an available image model, then verify its exact API contract. Revisit this article when official documentation establishes Nano Banana 2.5 Flash. For now, the confirmed story is the existing Nano Banana family; the new name remains a development report rather than a verified public API.
