If you are comparing "FLUX vs DALL·E 3 vs GPT Image 1," two of those three names are already out of date — and the third has moved on twice.
OpenAI's current image line is GPT Image, and their documentation names gpt-image-2 as the latest, alongside gpt-image-1.5, gpt-image-1 and gpt-image-1-mini. DALL·E 3 no longer appears in OpenAI's image-generation pricing table; DALL·E 2 survives mainly as the model behind a legacy variations endpoint.
So the real 2026 question is: FLUX or GPT Image — and the answer turns on three things that have nothing to do with which makes prettier pictures.
Sourcing note: OpenAI facts come from OpenAI's own API documentation and pricing pages. FLUX facts come from Black Forest Labs' pricing, model pages and documentation. No cross-vendor quality benchmark is quoted here, because neither vendor publishes a neutral one — and, as shown below, their pricing units are not even comparable without assumptions. Last verified July 29, 2026.
What this comparison solves
The pain point: people search for model names that no longer exist, and get comparison tables built on 2024 specs. Worse, most "FLUX vs DALL·E" pages present a cost comparison as if the two were billed the same way. They are not — one bills per megapixel, the other per token.
The differentiator: this names the models that actually exist today, shows exactly why a straight price comparison is unavailable, and gives you the three axes that do decide the choice — access friction, deployment control, and reference-image workflow.
The line-ups, current
OpenAI — GPT Image
Access is through two APIs, per OpenAI's documentation:
- Image API —
generations(create from a prompt) andedits(modify an existing image), plus avariationsendpoint for models that support it, such as DALL·E 2 - Responses API — image generation as a built-in tool inside conversations, adding multi-turn editing and image File IDs as inputs
OpenAI's own guidance: use the Image API for one-prompt-one-image work; use the Responses API for conversational, iteratively editable image experiences.
An access gate most comparisons omit: OpenAI's docs state you may need to complete API Organization Verification in the developer console before using GPT Image models — including gpt-image-2, gpt-image-1.5, gpt-image-1 and gpt-image-1-mini.
Black Forest Labs — FLUX
The shipping family is FLUX.2: [max], [pro], [flex] and the [klein] 4B/9B variants via an async REST API, plus open weights you can download and run. FLUX.2 edits at up to 4MP and accepts up to 10 reference images simultaneously. FLUX 3 — multimodal, video-first — exists but is request-gated with no public API.
Why you cannot compare the prices directly
This is the most useful thing in this article, and almost nobody says it.
BFL bills per megapixel. Published rates: $0.014 (klein 4B) / $0.015 (klein 9B) / $0.03 (pro) / $0.05 (flex) / $0.07 (max) for the first megapixel, with cheaper additional megapixels and a separate per-megapixel charge for every reference image. 1 MP = 1024×1024.
OpenAI bills per token. From their pricing table, per 1M tokens:
| Model | Image input | Cached image input | Output |
|---|---|---|---|
| gpt-image-2 | $8.00 | $2.00 | $30.00 |
| gpt-image-1.5 | $8.00 | $2.00 | $32.00 |
| gpt-image-1-mini | $2.50 | $0.25 | $8.00 |
Image output is billed in tokens, and how many tokens an image costs depends on its size and quality settings — which is why OpenAI points you at a calculator in their image-generation guide rather than publishing a per-image price. Responses API requests also add the mainline model's own token usage on top.
The consequence: any article showing you "FLUX $0.03 vs GPT Image $0.04 per image" invented an assumption about resolution and quality settings and did not tell you. You can only compare these honestly by pricing your actual workload — your resolution, your quality tier, your number of reference images — on both.
Rules of thumb that survive the unit mismatch:
- FLUX's cheap tier is very cheap and very predictable: klein 4B at $0.014 for a 1MP image, with no quality-setting variable to reason about.
- FLUX's reference-image billing punishes multi-reference work: every reference counts as at least 1 MP, so a four-reference edit is several times the base price.
- OpenAI's cached image input at $2.00/1M (versus $8.00) rewards workflows that reuse the same input image repeatedly.
The three axes that actually decide it
1. Access friction
FLUX: create an account, add credits, call the API. No verification step documented for the standard endpoints.
GPT Image: you may need to complete API Organization Verification before you can call the models at all. If you are prototyping this afternoon, that is a real difference — and if you are in a company where compliance owns the OpenAI org, it may be a multi-day difference.
2. Deployment control
FLUX: open weights exist. FLUX.1 [schnell] and FLUX.2 [klein] 4B / 4B Base are Apache 2.0 — self-host, fine-tune, ship commercially, no licence conversation. FLUX.2 [dev] (32B) is downloadable under a non-commercial licence with commercial terms sold separately, in tiers from Builder through Enterprise, including a synthetic-data licence with rights to train on outputs.
GPT Image: API only. No weights, no self-hosting, no fine-tuning on your own infrastructure.
If your requirement includes air-gapped deployment, data residency you control, or training on outputs, this axis ends the comparison before anything else is discussed.
3. Reference-image workflow
FLUX.2: up to 10 reference images in a single request, positioned by BFL around character, product and style consistency, in one checkpoint that both generates and edits, at up to 4MP.
GPT Image: the Responses API is built for multi-turn iterative editing with image File IDs as inputs — a conversational shape rather than a batch-of-references shape.
These are genuinely different models of work. Ten references in one call suits catalogue and campaign production. Multi-turn refinement suits exploratory art direction. Pick the one that matches how your team actually works.
Not ready to commit to either API? Flux 3 AI is an independent browser workspace — prompt-to-image, reference workflows, editing and upscaling with credits instead of integration work. Open the image generator or see the plans.
Quick decision guide
| If you need… | Choose |
|---|---|
| Weights you can self-host and fine-tune | FLUX (Apache 2.0 tier, or a licensed dev tier) |
| Free commercial rights on downloadable weights | FLUX — klein 4B or FLUX.1 [schnell] |
| Many reference images in one call | FLUX.2 — up to 10 |
| Conversational, multi-turn image editing | GPT Image via the Responses API |
| Images inside an existing OpenAI-based agent | GPT Image — one vendor, one bill |
| Cheapest predictable per-image cost | FLUX.2 [klein] 4B, $0.014 first MP |
| Video with native audio | Neither of these lines — that is FLUX 3, gated |
FAQ
Is DALL·E 3 still available? It is superseded. OpenAI's current image line is GPT Image, with gpt-image-2 named as the latest; DALL·E 3 is absent from the current image-generation pricing table.
What replaced DALL·E 3? The GPT Image family — gpt-image-1, gpt-image-1-mini, gpt-image-1.5 and gpt-image-2.
Is FLUX cheaper than GPT Image? Not answerable in the abstract. BFL bills per megapixel and OpenAI per token, with image-output tokens varying by size and quality. Price your own workload on both.
Can I self-host either? FLUX, yes — several models are downloadable, some Apache 2.0. GPT Image, no.
Do I need approval to use GPT Image? OpenAI's documentation says you may need to complete API Organization Verification first.
Which is better at text in images? Both vendors claim strong typography. No neutral head-to-head exists, so test your own strings — brand names and long headlines are where models actually differ.
What about FLUX 3? Multimodal, video with native audio, in request-gated early access. Not comparable to either image API today.
Bottom line
The matchup people search for is two generations stale on OpenAI's side. In 2026 it is FLUX versus GPT Image, and the deciding factors are structural: open weights and multi-reference batching on the FLUX side, conversational multi-turn editing and one-vendor consolidation on OpenAI's side — with pricing units so different that anyone quoting a clean per-image comparison is guessing.
Decide on deployment control and workflow shape first. Then price your real workload on both, at your real resolution.
If you would rather skip the integration question entirely, work in the Flux 3 AI browser workspace and revisit APIs when volume justifies them.
Sources
- Image generation guide (OpenAI API documentation) — GPT Image model list, Image vs Responses API, organization verification requirement, DALL·E 2 variations endpoint
- OpenAI API pricing — gpt-image-2 / 1.5 / 1-mini token rates, absence of DALL·E 3 from the current image table
- BFL API pricing — per-megapixel rates and reference-image billing rules
- Image generation quick start (BFL docs) — FLUX endpoints, async pattern, limits
- FLUX.2 pro / flex model page — up to 10 reference images, production positioning
- FLUX.2 max model page — top-tier capabilities and 4MP output
- FLUX.2 klein model page — Apache 2.0 variants, local deployment
- FLUX open weights licensing — commercial tiers and synthetic-data rights
- black-forest-labs/flux on GitHub — open model list and licences
- FLUX 3 — Real World Models (BFL, July 23, 2026) — status of BFL's multimodal frontier model
Scope note: model availability and pricing as of July 29, 2026 — both vendors ship fast. Flux 3 AI is an independent creator workspace, not affiliated with Black Forest Labs or OpenAI.


