Google: Nano Banana 2 (Gemini 3.1 Flash Image) provider comparison

google/gemini-3.1-flash-image

Gemini 3.1 Flash Image, a.k.a. "Nano Banana 2," is Google’s latest state of the art image generation and editing model, delivering Pro-level visual quality at Flash speed. It combines advanced...

Endpoints:: 2
Context:: 131.1K
Input:: image, text
Output:: image, text

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per token for output image. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Image prices use OpenRouter’s dedicated endpoint billing records and retain their published units. Missing speed data never removes an endpoint.

Endpoint comparison for Google: Nano Banana 2 (Gemini 3.1 Flash Image)
Provider / route	Current pricing	Speed measurements	Endpoint details
Provider / route Google Vertex`google-vertex/global`	Current pricing $0.00006 per token (output image)	Speed measurements 500-token response Not applicable Response starts Insufficient recent data Output speed Insufficient recent data	Endpoint details Uptime (30 min) Insufficient recent data Context 131.1K Model format N/a Max output N/a 4 parameters aspect_ratio, input_references, n, resolution
Provider / route Google AI Studio`google-ai-studio`	Current pricing $0.00006 per token (output image)	Speed measurements 500-token response Not applicable Response starts Insufficient recent data Output speed Insufficient recent data	Endpoint details Uptime (30 min) Insufficient recent data Context 131.1K Model format N/a Max output N/a 4 parameters aspect_ratio, input_references, n, resolution

Endpoint data fetched Jul 15, 2026, 11:17 PM UTC.

Nano Banana 2 (Gemini 3.1 Flash Image) deployment guide

How to choose a Nano Banana 2 (Gemini 3.1 Flash Image) inference provider

Nano Banana 2 (Gemini 3.1 Flash Image) is indexed here as a image model by Google, with 2 provider endpoints from Google Vertex, Google AI Studio. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 131.1K-token context window. It accepts image, text input and returns image, text output. 4 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare image billing units directly

At least one token is published consistently across the listed endpoints, allowing a direct price chart for output image. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

No model-format or quantization labels are currently published. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.