Skip to content

Agents and multimodal systemsComparison

Image models compared: GPT Image 2, Nano Banana, FLUX.2

Image models are billed three different ways — per token, per image and per megapixel — and two well-known ones were retired this year. A comparison on documented facts, and a way to decide on your own prompts.

By INFRO Editorial

Published

7 min read

A row of glowing amber media frames like a film strip on a dark ground, representing image generation models

In short

Image generation APIs differ less in headline price than in how they bill (tokens, images or megapixels), which sizes and references they accept, how long results stay downloadable, and when they retire. Compare those documented facts, then measure cost per accepted image on your own prompts.

Two widely used image models left their vendors' APIs this year, and a third family has a date. Google's Imagen page now says plainly that the Imagen models are shut down and to use Nano Banana instead1; the deprecations table gives 17 August 2026 for Imagen 4 Standard, Ultra and Fast2. OpenAI has announced that gpt-image-1.5, gpt-image-1-mini and chatgpt-image-latest shut down on 1 December 20263.

That churn shapes how to compare image models. A ranking of which model draws best will be stale before a product ships on it. The facts that decide whether a model fits — how it bills, what it accepts, how you get results back and how long it will exist — are documented, and they are what this comparison covers.

Three billing units, not one

The most common mistake in comparing image models is to put a per-image number beside a per-token number as if they measured the same thing. They do not.

Vendor pages, 2026-09-29Billing unitWhat moves the pricePublished rate
OpenAI GPT Image 2TokensQuality and size set the output token countImage output $30 / 1M tokens
Google Nano Banana 2ImageOutput resolution$0.045 (0.5K) to $0.151 (4K)
Google Nano Banana ProImageOutput resolution$0.134 (1K/2K), $0.24 (4K)
BFL FLUX.2 [pro]MegapixelsOutput resolution; editing costs moreFrom $0.03 per image
xAI Grok Imagine imageImageModel variant$0.02, $0.04 (2.0) or $0.05 (quality)
How each vendor bills image generation, from its own pricing page on 2026-09-29. A per-token rate and a per-image rate are not directly comparable until you convert at the size and quality you use.

Per token — OpenAI GPT Image. OpenAI's pricing page lists gpt-image-2 at $8 per 1M image input tokens, $5 per 1M text input tokens and $30 per 1M image output tokens4. The newer gpt-image-2.5-sunburst lists the same image output rate of $30 per 1M, plus cached-input rates, and does not bill text output because it only returns images5. What an image costs therefore depends on how many output tokens it takes, which rises with quality and size.

Per image, by resolution — Google Nano Banana. Google lists Nano Banana 2 (gemini-3.1-flash-image) at $0.045 for a 0.5K image, $0.067 at 1K, $0.101 at 2K and $0.151 at 4K. Nano Banana Pro (gemini-3-pro-image) is $0.134 at 1K or 2K and $0.24 at 4K6.

Per megapixel — Black Forest Labs FLUX.2. BFL prices by output megapixels, so larger images cost more. FLUX.2 [pro] starts from $0.03 for text-to-image and $0.045 for editing, [flex] from $0.05, [max] from $0.07, and the [klein] models from $0.014; [dev] is listed as local only7.

Per image, by variant — xAI Grok Imagine. xAI lists grok-imagine-image at $0.02, grok-imagine-image-2.0 at $0.04 and grok-imagine-image-quality at $0.05 per image8.

What each API accepts

Sizes, references and editing features vary more than prices do, and they decide whether a model can do the job at all.

GPT Image (OpenAI)Nano Banana 2Nano Banana ProFLUX.2 (BFL)
SizesThree recommended sizes; custom sizes in multiples of 16, ratio 1:3 to 3:1, edge up to 3,840 px90.5K, 1K, 2K, 4K; ten aspect ratios101K, 2K, 4K10Priced by megapixel7
Reference imagesImage inputs for editing, masks with alpha9Up to 10 object, 4 character, 3 style10Up to 6 object, 5 character, 3 style10Editing priced separately7
Quality controllow to max, plus auto9ResolutionResolutionModel tier
Transparent outputYes, PNG or WebP9Not statedNot statedNot stated
WatermarkNot statedSynthID10SynthID10Not stated
Documented capabilities on 2026-09-29. "Not stated" means the page opened for this article did not say.

Two notes. OpenAI says resolutions above 2560×1440 are experimental and that complex prompts can take up to two minutes9 — relevant if you planned to hold a user request open. And Google documents text rendering and search grounding for its Nano Banana models, with grounding unavailable on the Lite variant10; if your images must contain accurate text, test that specifically.

How results come back, and how long they last

Image generation is often called synchronous, but not every vendor's native API is. BFL's API answers a submit with an id and a polling_url; you poll until the status is Ready, and the signed result URL in result.sample is valid for 10 minutes only11. BFL also offers global, EU-only and US-only endpoints, which matters if your images must stay in a region11. OpenAI can stream up to three partial images while a render is in progress9.

The practical rule is the same as for video: treat any provider URL as a short-lived handoff and copy the bytes to your own storage as part of the request that produced them.

Retirements are part of the comparison

  1. 2026-08-17Imagen 4 shut downStandard, Ultra and Fast. Google names gemini-3.1-flash-image as the replacement.
  2. 2026-10-02gemini-2.5-flash-imageNano Banana (the first) reaches its listed shutdown date.
  3. 2026-12-01gpt-image-1.5 and gpt-image-1-miniAlso chatgpt-image-latest. OpenAI names the GPT Image 2.5 models as replacements.
Image model shutdown dates from Google's and OpenAI's deprecation pages, read 2026-09-29.

Google also lists gemini-2.5-flash-image — the original Nano Banana — with a 2 October 2026 shutdown date2. OpenAI's replacements for the GPT Image 1.x family are the GPT Image 2.5 models3. If you pick a model today, look up its vendor's deprecation page as part of the decision, and prefer a model that is generally available over a preview when you need it for longer than a few months.

A method for choosing

  1. Write down hard constraints: output size, aspect ratio, transparency, text-in-image, reference images, region.
  2. Assemble 50 real prompts, including edits, text rendering and prompts that must be refused.
  3. Generate on two or three candidates at the size and quality you will actually use, and let the people who own the output choose blind.
  4. Compute cost per accepted image from the vendor's billing unit and your acceptance rate.
  5. Check lifecycle: deprecation status, notice policy and whether a replacement is named.
  6. Qualify a fallback on the same prompts, so a retirement or an outage is a configuration change.

Serving image models through INFRO

INFRO serves images through POST /v1/images/generations and POST /v1/images/edits, synchronously: the request stays open while your provider renders, and the response carries the images. model is a catalog id such as bfl/flux-2-pro or the slug of one of your routes; size must have the WIDTHxHEIGHT shape and is passed to your provider unchanged, so a provider that cannot render it picks its nearest size or refuses, by its own rules. quality and seed are forwarded on generations only. See image generation.

Synchronous

POST /v1/images/generations

model is a catalog id or a route slug; size is passed through unchanged.

Policy and budget check

A request with no room under a budget is refused with 402; the provider is never called.

Your connection renders

OpenAI, Azure OpenAI, Together, OpenRouter or an OpenAI-compatible endpoint. A failure before any image moves to the next target, then to fallbacks.

Response

A signed URL to a copy kept for 24 hours, or base64. Store the bytes yourself.
An image request through INFRO. Every step is documented in the image generation reference.

Image requests are served by connections whose provider kind handles images through OpenAI's images API: OpenAI, Azure OpenAI, Together, OpenRouter and OpenAI-compatible endpoints. A model that its vendor offers only through a native API — Gemini's image models, for instance — is reachable only where one of those providers exposes it, so check your provider's model list before planning on it.

image_with_fallback.py
import os
from openai import OpenAI

client = OpenAI(base_url="https://api.infro.io/v1", api_key=os.environ["INFRO_API_KEY"])

image = client.images.generate(
    model="bfl/flux-2-pro",
    prompt="An isometric cutaway of a small data center, soft studio lighting",
    size="1024x1024",
    n=1,
    extra_body={"fallbacks": ["bfl/flux-2-dev"]},
)

# The URL points at a copy INFRO keeps for 24 hours. Store the bytes yourself.
print(image.data[0].url)

If a connection errors before producing an image, INFRO tries the next target on the route and then each model in fallbacks, which must be image models too. The response names the provider, connection and route that served it, and usage.cost estimates what your provider will bill, counting only the images that came back; usage.price_source says whether that estimate used the vendor's list rate or a rate you entered. For a token-priced model, reconcile that estimate against your provider's own usage data. A request that would exceed a budget you set is refused with 402 budget_exceeded before any provider is called. The data[].url link expires 24 hours after the request, the same retention as async job outputs.

Edits go to /v1/images/edits as multipart form data: the image and an optional mask, each PNG, JPEG or WebP up to 25 MB, in a request body of up to 51 MB. quality and seed are accepted there but not forwarded, and which dimensions and aspect ratios an edit accepts is your provider's decision. On OpenAI's API the mask is a PNG with an alpha channel the same size as the image, and transparent pixels mark the region to repaint. Because editing behaviour differs more between vendors than generation does, qualify any fallback for edits separately rather than assuming a model that generates well also edits the way your product expects.

Questions readers ask

Is Imagen 4 still available in the Gemini API?
No. Google's Imagen page says the Imagen models are shut down, and the deprecations page lists 17 August 2026 for all three Imagen 4 models, with gemini-3.1-flash-image as the replacement.
Why does the same image cost different amounts on the same model?
Most image APIs price by output size or quality. Google prices Nano Banana 2 by resolution, BFL prices FLUX.2 by megapixel, and OpenAI bills GPT Image by tokens, which grow with quality and size.

From the team that builds it

Where this shows up in INFRO

INFRO is a control plane in front of the provider accounts you already hold. The capabilities below are the parts of it this article touches, each with the documentation that defines its behaviour.

INFRO is in private early access. Provider usage is billed to you by your providers; INFRO charges a software subscription and takes 0% of model spend. See plans.

Sources

Numbered in order of first citation. Each was opened and checked against the claim on the date shown.

  1. 1.Imagen (opens in a new tab) — Google. Accessed Sep 29, 2026.
  2. 2.Gemini deprecations (opens in a new tab) — Google. Accessed Sep 29, 2026.
  3. 3.Deprecations (opens in a new tab) — OpenAI. Accessed Sep 29, 2026.
  4. 4.Pricing (opens in a new tab) — OpenAI. Accessed Sep 29, 2026.
  5. 5.GPT Image 2.5 Sunburst model page (opens in a new tab) — OpenAI. Accessed Sep 29, 2026.
  6. 6.Gemini Developer API pricing (opens in a new tab) — Google. Accessed Sep 29, 2026.
  7. 7.Pricing (opens in a new tab) — Black Forest Labs. Accessed Sep 29, 2026.
  8. 8.Models and pricing (opens in a new tab) — xAI. Accessed Sep 29, 2026.
  9. 9.Image generation (opens in a new tab) — OpenAI. Accessed Sep 29, 2026.
  10. 10.Image generation with Gemini (Nano Banana) (opens in a new tab) — Google. Accessed Sep 29, 2026.
  11. 11.Generating images (opens in a new tab) — Black Forest Labs. Accessed Sep 29, 2026.

About this article

Written from each vendor's own documentation, pricing and deprecation pages, opened on 2026-09-29, and from INFRO's public image-generation documentation, which the authors build. Published rates are quoted from the vendor pages, not from INFRO's catalog, where the two differ. No images were generated or scored for this article, and no quality ranking is implied.

Last checked against its sources on . The next review is due by . No separate named reviewer is recorded for this article.

How articles are written, sourced and corrected is set out in the editorial standards.