You have a product photo and need more out of it: clean packshots, a few lifestyle scenes, a version where the label still reads. The image models people suggest for that are Google's Nano Banana 2.1 and Nano Banana Pro, and Black Forest Labs' FLUX.2 [pro]. This is a comparison of Nano Banana vs FLUX for product images, built only on what the two labs publish, checked on 1 November 2026: price per image, reference-image limits, output sizes, editing and text. It ends with a test you can run on your own product for under $3.
My short answer, argued below: start edits from a reference photo on Nano Banana 2.1, move to FLUX.2 [pro] when a color must match a hex code or when you need a model snapshot that will not change under you, and pay for Nano Banana Pro only for packaging text and 4K hero images. Then let your own test overrule me.
What the names mean on 1 November 2026
"Nano Banana" is a family. On Google's Gemini API pricing page, the current model is Nano Banana 2.1 (gemini-nano-banana-2.1), an update to Nano Banana 2 (gemini-3.1-flash-image) at half its price in 1K and 2K. Nano Banana Pro is gemini-3-pro-image. The original Nano Banana (gemini-2.5-flash-image) is deprecated and shuts down on 15 March 2027, so start nothing new on it.
Google's image generation guide calls 2.1 "the primary high-efficiency workhorse model for image generation and conversational editing" and recommends it for all new projects. Pro is the one "optimized for professional asset production".
FLUX.2 [pro] is Black Forest Labs' production model. It has two API endpoints: flux-2-pro, a fixed snapshot kept for reproducibility, and flux-2-pro-preview, where improvements land first, per the release notes. The same notes show the lab shipped FLUX 3 Image on 1 October 2026. This comparison sticks to FLUX.2 [pro].
Price per image, from the official pages
Google bills images as output tokens, converted to a price per image. Black Forest Labs bills by the megapixel: its pricing page lists FLUX.2 [pro] at $0.03 for the first megapixel and $0.015 for each additional one, and the API pricing doc lists editing from $0.045, because a reference image counts as megapixels too. Google's 2K is 2048x2048 and BFL's guide counts 2048x2048 as 4MP, which lines the columns up:
| Model (list price) | 1K, 1024x1024 | 2K, 2048x2048 | 4K, 4096x4096 |
|---|---|---|---|
| Nano Banana 2.1 | $0.0336 | $0.0504 | $0.113 |
| Nano Banana Pro | $0.134 | $0.134 | $0.24 |
| FLUX.2 [pro], text to image | $0.03 | $0.075 | not offered |
| FLUX.2 [pro], edit with one 1MP reference | $0.045 | $0.09 | not offered |
Three things move these numbers.
- Thinking. Gemini 3 image models reason before they draw, Google's guide says this cannot be disabled in the API, and thinking bills as text output ($7.50 per million tokens on 2.1, $12 on Pro). Your invoice will sit above the per-image figure.
- Batch. Google's Batch API halves the price for a turnaround of up to 24 hours: $0.0168 per 1K image on 2.1, $0.067 on Pro. BFL's doc says a batch simply multiplies the base cost by the number of images.
- Reference size. FLUX.2 [pro] bills input megapixels. A photo straight off a phone carries many more than you need, so resize references to about 1MP before you send them.
Now a real catalog: 50 SKUs, one packshot and one lifestyle scene each, three candidates per shot, is 300 edits at 1K. Nano Banana 2.1: 300 x $0.0336 = $10.08, or $5.04 in batch. FLUX.2 [pro] with one 1MP reference: 300 x $0.045 = $13.50. Nano Banana Pro: 300 x $0.134 = $40.20, or $20.10 in batch, plus $0.0011 per reference image. The gap is a few tens of dollars; retries and rejected shots cost more, and the test at the end measures them.
Reference images and output sizes
For product work, the reference limit decides what fits in one call: front, back, a label close-up, the cap, a second SKU for a range shot.
- Nano Banana 2.1: up to 10 object images "with high-fidelity" plus up to 4 character images, 14 in total. Output at 1K (the default), 2K or 4K. The 512px size exists on Nano Banana 2 but not on 2.1.
- Nano Banana Pro: up to 6 object images, 5 character images and 3 style references. Output at 1K, 2K or 4K.
- FLUX.2 [pro]: up to 8 reference images through the API. The prompting guide sets a 9MP budget for input plus output: 8 references at 1MP output, 7 at 2MP, fewer as the output grows. Output runs from 64x64 to 4MP, in multiples of 16, with up to 2MP recommended.
Two practical consequences. Only Nano Banana renders 4096x4096, so a print-size hero image is a Google job ($0.113 on 2.1, $0.24 on Pro). And the multiple-of-16 rule means FLUX.2 cannot output the 1080x1350 Instagram portrait directly, since neither number divides by 16. Ask for 1088x1360, which is exactly 4:5, and scale down.