Zhenzhen_nano_banana_edit

Before there was a Banana 2 node and a FAL variant and an async S2A variant, there was Comfly_nano_banana_edit ("Zhenzhen_nano_banana_edit") - the original edit node for the first-generation Nano Banana, back when the model list was just nano-banana and nano-banana-hd. It's the simplest node in the Banana family, and if you have a reason to stay on the original model (older workflows, a specific look you've tuned, cost), it's still here and still works.

It's a Google-class node in the T8mars/Comfyui-zhenzhen pack, the "Comfly" API-wrapper family that calls the author's paid reseller service. Key goes into an apikey field directly. Same submit → poll → download machinery as the rest of the family; the result lands as an IMAGE.

What you set

• prompt - required.
• mode - text2img or img2img.
• model - nano-banana or nano-banana-hd.
• aspect_ratio - a wide set including 16:9, 4:3, 4:5, 3:2, 1:1, 2:3, 3:4, 5:4, 9:16, 21:9, 9:21. Note this one defaults to 1:1 and has no auto.
• image1–image4 - reference images for img2img work.
• response_format - url or b64_json.
• seed (cache control) and skip_error.

One quirk the changelog calls out explicitly: the aspect ratio only applies in text2img mode - in img2img, the output follows your input image, so don't expect the ratio setting to do anything there. That caught a lot of people when the node shipped.

Outputs

• image - the result as an IMAGE.
• response - the raw API payload.

Note this one doesn't have an image_url output - if you need the hosted URL, the response output carries it.

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-zhenzhen
# restart ComfyUI

Or ComfyUI Manager → "Comfyui-zhenzhen", then a key from the author's site into apikey.

The honest part

Be honest about whether you need this one. If you're starting fresh, the Banana 2 nodes are better models and the Comfly_nano_banana general node covers the same ground with more models. This node earns its place in exactly two situations: you've built and tuned a workflow around the original Nano Banana's behavior, or you're working through an older example workflow that references it by name. Otherwise it's the "grandfathered" option - fine, but not what you'd reach for first. The usual pack caveats hold: reseller proxy, your images leave your machine, and a rerun fixes most upstream hiccups.