Nano Banana Lite
Google Gemini 3.1 Flash Lite Image — efficiency-focused generation and editing. Sub-2s latency, cost-effective, 14 aspect ratios. Auto-switches to editing when you wire an image.
Try Nano Banana Lite in the playground
Nano Banana Lite
Node type: generate:nano_banana_lite
Category: generate
Description
Nano Banana Lite is Google's Gemini 3.1 Flash Lite Image model, built for efficient, cost-effective pictures: wire a text description into Prompt and it returns Generated Images. Wire a picture into Image 1 and the same node switches to editing that picture instead of starting from scratch. Reference Images is a list port, so several wires into that one socket all survive. The model edits whichever image comes first, so wire your subject to Image 1. Only the first 10 images reach the model, and anything past 10 is dropped with no run warning. Don't stitch reference photos into one contact sheet, because that shrinks every face before the model sees it. Set Number of Images anywhere from 1 to 4. It costs about 16 credits per image.
Pricing
- Cost: ~16 credits per image
Variant family
- Family:
nano-banana-lite - Is primary: yes
- All variants:
generate:nano_banana_lite,edit:nano_banana_lite_edit
Canvas ports
These appear as port handles on the left side of the node.
| ID | Label | Details |
|---|---|---|
prompt |
Prompt | TEXT (required) · multiline |
image1 |
Image 1 | IMAGE |
reference_image_urls |
Reference Images | IMAGE · list |
Sidebar config
These render as form fields in the right-side config panel when the node is selected.
| ID | Label | Details |
|---|---|---|
aspect_ratio |
Aspect Ratio | TEXT · options: auto, 21:9, 16:9, 3:2, 4:3, +6 |
num_images |
Number of Images | NUMBER · 1…4 |
output_format |
Output Format | TEXT · options: jpeg, png, webp |
safety_tolerance |
Safety Tolerance | TEXT · options: 1, 2, 3, 4, 5, +1 |
sync_mode |
Sync Mode | BOOLEAN |
Outputs
| ID | Label | Type |
|---|---|---|
images |
Generated Images | IMAGE |
Reference images
Wire Reference Images once and hand it several images: it is a list port, so several wires into that one socket all survive, and so does a single upstream that emits several images.
Image 1 and the numbered Image 2..Image 10 slots go first, in slot order, and then everything on Reference Images, in wire order. The same URL wired into both a slot and the list keeps its slot position and counts once.
Whatever ends up first in the request is the image the model EDITS, and that is Image 1 only when Image 1 is wired. Leave Image 1 empty and wire Image 2 instead, and Image 2 becomes the image being edited. The numbered slots are read in slot order and an empty one is simply skipped. Wire the subject to Image 1.
The first 10 images reach the model. Anything past 10 is dropped, silently as far as the request goes, and the numbered slots win: if 10 slots are wired, nothing on Reference Images is sent. There is no run warning for the drop yet.
You do not need to stitch reference photos into one contact sheet any more, and you should not: stitching divides every face by the number of photos in the sheet before the model ever sees it.
Skip node passes Image 1 through while Image 1 is the ONLY numbered slot wired. It serves whatever is on Image 1, never a reference, and Reference Images can be wired alongside without changing that.
Wire a second numbered slot (Image 2 and up) and the card can no longer be skipped transparently: two numbered slots are two candidate sources and nothing on the card says which one to pass on, so Skip passes NOTHING and the run record says so per node. Leaving Image 1 empty passes nothing for the same reason. This is not new to Reference Images; a card with two numbered slots behaved this way before that socket existed.
Auto-generated from the Wireflow node registry.