On 30 June 2026, Google DeepMind announced Nano Banana 2 Lite, model ID gemini-3.1-flash-lite-image. Google separated an efficiency specialist from the higher-quality Nano Banana 2 path so bulk creative pipelines could trade some capability for latency and price.
This release brief was checked against first-party material on 10 August 2026. The date above is the public announcement date, not the date a repository was created or a third-party provider added the model. Where access or weights arrived later, that distinction is recorded below.
Release record
| Field | Verified detail |
|---|---|
| Announcement | 30 June 2026 |
| Availability or weight release | 30 June 2026 in Google AI Studio, Gemini API, Enterprise Agent Platform and consumer products |
| Release type | proprietary high-throughput image generation and editing model |
| Access | hosted Google products and Gemini API; no released weights |
| Architecture | an undisclosed Gemini 3.1 Flash-Lite image model optimised for speed and cost |
| Maximum stated context | image inputs and output controls published in the Gemini API rather than a text-only context limit |
What changed
Nano Banana 2 Lite formalises a tier that many teams create informally by routing easy jobs to a cheaper image model. It supports generation and editing across API and consumer surfaces, making model selection a product decision rather than a hidden provider optimisation. A useful evaluation should therefore include retry rate, text rendering, local edit precision and the percentage of outputs that need escalation to the larger model.
The practical comparison is therefore not simply whether Nano Banana 2 Lite, model ID gemini-3.1-flash-lite-image has the largest headline score. Teams need to ask whether its architecture, access terms, latency, tool behaviour and evaluation setup match the workload they actually intend to run. A model can lead one harness while losing on cost, refusal behaviour, multilingual quality or repeatability in another.
Benchmarks worth retaining
| Evaluation | Reported result | How to read it |
|---|---|---|
| Product position | fastest Nano Banana model at launch | Google product claim, not an independent latency result |
| Model identifier | gemini-3.1-flash-lite-image | Pin this identifier rather than a mutable family alias |
| Launch surfaces | 4 major platform groups on day one | AI Studio, API, Enterprise Agent Platform and consumer products |
These are release-time results, not independently reproduced guarantees. The launch did not provide a conventional public benchmark table, and latency or cost claims depend on API region, resolution, quota and product surface. Scores should remain attached to the disclosed effort setting, agent harness, tool access, timeout, context-management policy and judge model. Moving a number into a procurement sheet without those conditions creates false comparability.
Architecture and access
Nano Banana 2 Lite, model ID gemini-3.1-flash-lite-image is described as an undisclosed Gemini 3.1 Flash-Lite image model optimised for speed and cost with image inputs and output controls published in the Gemini API rather than a text-only context limit of stated context. Its access position at verification time is hosted Google products and Gemini API; no released weights. That wording matters: open weights, source-available weights, an API, a product preview and a research demonstration give adopters very different rights and different levels of reproducibility.
Before deployment, record the exact model identifier or checkpoint, inference stack, quantisation, reasoning setting, region, price schedule and supplier terms. If the release uses a custom licence, read the licence itself rather than relying on the word “open” in launch copy. If it is API-only, preserve the dated documentation and change-notice route because the served snapshot can change without a downloadable artefact.
What an evaluation should test next
For Nano Banana 2 Lite, model ID gemini-3.1-flash-lite-image, a credible internal gate should include:
- a frozen set of representative tasks with pass, fail and abstain criteria;
- a matched baseline using the same tools, timeout, prompt budget and reviewer rubric;
- repeated runs to expose variance rather than reporting a single best attempt;
- latency, token use and total task cost alongside task success;
- adversarial, multilingual and long-context cases relevant to the real deployment; and
- rollback evidence showing the previous model can be restored safely.
The wider model change-control guide explains how to keep model, prompt, tool and corpus changes reconstructable. The AI dependency inventory guide covers the release and supplier records needed after deployment.
AIEngine verdict
Nano Banana 2 Lite is significant as an operating model for image scale, not as a claim of absolute visual leadership. Teams should test cost per accepted asset rather than cost per generated image.
This is a launch assessment, not a certification. Benchmark leadership is useful evidence of where to test; it is not authorization to place the model in a high-impact workflow without domain evaluation, security review and an accountable owner.
Primary sources
Image provenance
Hero image: Google official release artwork. The locally served WebP is a crop of the first-party release or model-card asset recorded in the repository provenance manifest.
