Skip to main content
Nano Banana Pro is the model Google offers for its most complex visual tasks, with the family’s broadest world knowledge, advanced localization, brand consistency, and precise creative control. On LaoZhang API it costs $0.09 per image at 1K, 2K, and 4K, so 4K comes in under 40% of Google’s standard $0.24. There is no concurrency cap or rate limit, and requests fail over across several official Google routes.

What Nano Banana Pro supports

Every size costs less than Google’s standard price per output image:
  • 1K and 2K: $0.134 at Google, $0.09 on LaoZhang API
  • 4K: $0.24 at Google, $0.09 on LaoZhang API
The model comes from Google’s official channel. Public pricing as of September 24, 2026, with Google’s prices checked on November 5, 2026; current prices are in Models and pricing.
A futuristic city skyline at sunset with a NEO TOKYO billboard, generated by Nano Banana Pro

Output of the generate example below: 4K, 16:9 (shown scaled down)

Parameters and limits

Thinking and Search grounding aren’t exclusive to Pro: Nano Banana 2 supports both, adds image search grounding and 512px output, and costs less per call. Google shut down gemini-3-pro-image-preview on June 25, 2026, according to its deprecations page. On LaoZhang API, the -preview IDs are mapped to the matching stable IDs; use the stable ID, gemini-3-pro-image, directly. To compare Pro with the other Nano Banana models, see the Nano Banana overview.

Before you call

1

Create an API key

In Token management, open the create-token dialog (创建令牌), set Billing mode (计费模式) to Usage first (按量优先, recommended) or Per-call (按次计费), and click Create (创建). Nano Banana Pro has only a per-call price, and a Usage-based (按量计费) key can’t call it; the billing rules explain when a request is charged.Create-token dialog in the LaoZhang API console with Billing mode set to Per-call (按次计费)
2

Set the key and install the dependencies

3

Add a save function for cURL

The cURL examples need jq. Define this shell function to save the last image in a Gemini-native response, which is the final result if interim images come back too, with the extension that matches its mimeType:
When the response holds no image, the function prints the error, promptFeedback, and finishReason fields instead.

Generate an image

This request creates a 4K, 16:9 image and saves it:
The image comes back as Base64 in candidates[0].content.parts[].inlineData.data, and mimeType gives its format. Both examples decode it and save a PNG, JPEG, or WebP file to match. A 4K image takes longer than a 1K image, so keep a generous client timeout; the examples allow 300 seconds.

Output sizes

imageSize accepts 1K (the default), 2K, and 4K, with the K in uppercase. Google publishes these pixel dimensions for Nano Banana Pro:

Edit an image

nano_banana_pro.py also edits: list image files after the prompt, and it sends each one as an inlineData part after the instruction.
Without --ratio, the request sets no aspect ratio, and Google’s default is to match the input image’s shape. For cURL edits, combining up to 14 references, public-URL input, and edit prompts, see Nano Banana Pro image editing. Add the googleSearch tool to base an image on current information, such as a weather forecast or recent events. Allow TEXT in responseModalities so any text the model writes alongside the image comes back too:
Grounding sources are in candidates[0].groundingMetadata. The same request works on Nano Banana 2.1 or Nano Banana 2 with their model IDs; Nano Banana 2 Lite doesn’t support grounding. If you show grounded results to end users, follow Google’s grounding guide on displaying search suggestions. Grounding costs $0.014 per search on top of the per-call price. The model decides how many searches to run, and call logs show the count, as described in the Nano Banana billing rules.

Use the OpenAI-compatible route

If your app already uses the OpenAI SDK, call Pro through chat completions. The SDK sends your key as Authorization: Bearer. This route has no ratio or size settings, so a text-only prompt returns a 1:1 image at 1K. The image comes back as a Base64 data URL inside message.content. Save this script as nano_banana_pro_chat.py:
Generate a poster:
To send images for editing over this route, see the OpenAI-compatible section of the editing guide.

Prompt tips

  • Describe the subject, setting, style, lighting, and camera angle in full sentences instead of keyword lists.
  • For text inside the image, put the exact words in quotes and name the font style.
  • Describe what you want rather than what you don’t: “an empty street” works better than “no cars”.
  • Say “Generate an image of…” so the model doesn’t answer with text only.

Errors and billing

Send values that Pro accepts:
  • Google rejects lowercase sizes such as 4k.
  • A request can return HTTP 200 without an image, for example when the prompt doesn’t ask for one or a safety check blocks the output. It is charged as one call. Check finishReason (and promptFeedback if present), then change the prompt or references before resending; see Avoid paying for empty responses.
  • HTTP 401 means the key or the Authorization: Bearer header is wrong. Retry 429 and 5xx responses with backoff, and check call logs before resending a request that timed out.

FAQ

How much does Nano Banana Pro 4K cost compared with Google?

LaoZhang API charges $0.09 per image at 1K, 2K, and 4K, for generation and editing alike. Google’s standard price is $0.134 at 1K and 2K and $0.24 at 4K, so a 4K image costs about 62% less here. Check current prices on Models and pricing. Non-200 responses from upstream are not charged; an HTTP 200 without an image is charged as one call, see Billing and failure rules.

How do I get a Nano Banana Pro API key?

Register on LaoZhang API and create a token in Token management with the Usage first (recommended) or Per-call billing mode. The sk- string is your key for gemini-3-pro-image; you don’t need a Google account, a Google Cloud project, or a Gemini API key. After topping up, send the first request from Generate an image.

Will batch generation be rate limited?

No. A single key has no RPM (requests per minute), IPM (images per minute), or concurrency cap, and requests fail over across several official Google routes. An occasional 429 comes from upstream capacity, isn’t charged, and can be retried after a short wait; see Concurrency and 429.

Should I use Pro or Nano Banana 2?

Start with Nano Banana 2.1 ($0.045 per call) or Nano Banana 2 for most work: both take the same requests, cost less per call, and add four more aspect ratios and image search grounding, with up to 10 object and 4 character references. Nano Banana 2 also offers 512px output. Choose Pro when the result depends on world knowledge, localized text, or exact brand details, or when an edit needs style references (up to 3) or up to 5 character references. Compare both models on your own prompts before switching a workload. The generate prompt from the Nano Banana 2.1 guide, sent to both models at 2K, 16:9 on October 14, 2026: Pro returned in 69 s and Nano Banana 2.1 in 25 s.
Brick corner cafe at dusk after rain with a BANANA CAFE neon sign and cobblestone street, generated by Nano Banana Pro

Nano Banana Pro, 2K, 16:9: 69 s, $0.09

Corner cafe at dusk after rain with a yellow and red BANANA CAFE neon sign, generated by Nano Banana 2.1

Nano Banana 2.1, 2K, 16:9: 25 s, $0.045

Can I turn off thinking, and does it affect the price?

No, it can’t be turned off. Google says Gemini 3 image models think by default and the API can’t disable it; thinkingLevel applies only to Nano Banana 2.1, 2, and 2 Lite and has no effect on Pro. While thinking, the model creates interim images to test the composition, and these can come back with the result; the last image is the final one. See Can one request return several images? for how to handle them. Pro is billed per call, so the amount of thinking doesn’t change the price.

How do I get accurate text in the image?

Google recommends generating the text first, then asking for an image that contains it. Put the exact words in quotes and name the position and font style, as in the prompt tips. If a word still comes out wrong, send the result back as the input and ask for a change to that text only.