MAI-Image-2.5-Pro vs Flux 3: Same Launch Week, Two Different Realities

MAI-Image-2.5-Pro and Flux 3 were both announced the same week — 23 July 2026. One month later they occupy different universes. MAI-Image-2.5-Pro, Microsoft's quality-tier image model, is in public preview on Microsoft Foundry and has climbed to No. 1 on the Artificial Analysis Image Editing Arena (Elo 1,272 from ~6,100 blind votes). Flux 3, Black Forest Labs' unified multimodal foundation model, has shipped exactly one of its tiers — video — and its image tier has no public endpoint, no price, and no benchmarks anyone can run. A reader asking "which image model should I use" does not have two candidates here; they have one product and one promise.

What each one actually is

• MAI-Image-2.5-Pro — a focused, proprietary image generation and editing model, the highest-fidelity tier of Microsoft's in-house MAI-Image-2.5 family. Token-metered, hosted on Foundry, aimed at hero imagery, detailed editing, and in-image text rendering. This is the whole model: images.

• Flux 3 — a unified multimodal foundation model trained jointly on image, video, and audio (plus robot-action prediction), built on a flow-matching method BFL calls Self-Flow. Five variants were announced: Flux 3 Video, Flux 3 Image, Flux 3 Action, Flux-mimic for robotics, and Flux 3 Dev (open weights planned for later in 2026). Image is one modality inside a bigger bet, not the product itself.

That structural difference matters more than any spec. A focused image model puts its entire capacity into stills; a multimodal model spreads capacity across media. MAI-Image-2.5-Pro exists to win image editing. Flux 3 exists to be one model that does everything, and its image tier is the part of that vision that has not arrived.

Availability: the whole comparison

As of mid-August 2026, the asymmetry is absolute:

• MAI-Image-2.5-Pro — public preview on Azure AI Foundry across seven global regions, plus the free MAI Playground. You can call it today with a Microsoft account; it is already the quality tier of a family that powers Bing Image Creator, PowerPoint, and OneDrive.

• Flux 3 Image — unreleased. BFL's docs list no image endpoint; the current callable image line remains FLUX.2 (Pro, Dev, Flex, Klein). The Flux 3 page carries a "coming soon" label with an application form rather than a get-started button. BFL said image early access would open "in the following weeks" after the 23 July announcement; as of now there is no model ID, no image specs, and no prompt limit published. Only Flux 3 Video reached general availability (4 August, billed per second).

So the practical answer to "which one can I build on for image editing today" has exactly one name in it.

The evidence each side can show

MAI-Image-2.5-Pro's editing strength is independently measured. Beyond the #1 editing Elo, its text-to-image rank is No. 7 at 1,292 Elo — good, not the leader, which is the honest way to read a specialist. Microsoft also publishes vendor-reported claims: 96.8% text-rendering accuracy (flagged as covering five languages), 27% better prompt adherence than GPT Image 1.5 on internal evals, and 94% multi-image character consistency. Label all of those as Microsoft's own numbers; the leaderboard is the independent part.

Flux 3 Image has zero public evidence. There are no image benchmarks, because there is no image endpoint to test. The only BFL-reported numbers in the family are for Flux 3 Video — an internal Elo of 1,135 text-to-video and 1,051 image-to-video that BFL claims beats Omni Flash, H3, and Seedance 2.0 — and those are vendor-reported, unreproduced, and do not transfer to the image tier anyway. Anything you read that "benchmarks" Flux 3 image quality is extrapolating from video numbers or from the older FLUX.2 line.

What Flux 3 promises for images (vendor roadmap, not spec)

BFL's roadmap claims for the image tier are worth knowing precisely because they are claims:

• Image synthesis and editing across styles, aspect ratios, and resolutions

• Improved complex-prompt handling and high-accuracy multilingual text rendering

• Zero-shot style transfer from a reference image, with multiple style references blended in one pass

• Character and brand consistency across generations without fine-tuning

• Non-destructive editing — preserving textures, grain, lighting, and background so multi-turn edits do not degrade

That last one is the interesting claim: it is the same "edit without regenerating the scene" property that MAI-Image-2.5-Pro's surgical-edit design is already shipping and scoring on. If Flux 3 Image delivers on it, it will be competing directly with the thing MAI-Image-2.5-Pro already does. "If" is the operative word — everything in that list is unverified until the endpoint exists.

Cost

• MAI-Image-2.5-Pro — $5 per million text-input tokens, $8 per million image-input tokens, $106 per million image-output tokens. Artificial Analysis's conversion puts a 1024×1024 image near $108.50 per 1,000. Preview pricing; GA could move it.

• Flux 3 Image — no price exists, because no endpoint exists. The only Flux 3 pricing published is for video: $0.17/second (HD) and $0.29/second (FHD) for full renders. For the callable FLUX.2 image line as a reference point, BFL charges roughly $0.04 per image for Flux Pro and $0.015 for Flux Dev — but that is the previous generation, not a forecast.

You cannot compare a price against a blank line. The cost comparison today is MAI-Image-2.5-Pro's premium rate against nothing at all.

Which one to build on

If your deliverable is images in 2026, the answer is MAI-Image-2.5-Pro (or one of the other hosted editors — GPT Image 2 still leads text-to-image and the other main editing board). It is callable, it has an independent #1 editing score, and the resolution cap around a megapixel is the main thing to check against your use case. Flux 3 is a watch item: when the image tier lands, its non-destructive editing and brand-consistency claims will deserve a serious test against exactly the model Microsoft is scoring #1 right now.

There is also a routing-shaped way to think about the wait. When Flux 3 Image finally gets an endpoint, the low-risk way to adopt a brand-new, benchmark-free model is to route a slice of traffic to it and keep the proven model as automatic failover — one endpoint, provider prices passed through at 0% markup, and the unproven model earning its place on live traffic instead of a roadmap slide. That is the pattern OrcaRouter exists for, and it is the same pattern that makes preview-tier models like MAI-Image-2.5-Pro adoptable before they reach general availability.

The verdict

Same launch week, one month later: MAI-Image-2.5-Pro is a measured #1 editor you can call today, and Flux 3 is a multimodal foundation model whose image tier is still a promise with a roadmap. Comparing them on image quality would be comparing a boxer to a fighter who has not yet entered the ring. Use MAI-Image-2.5-Pro for image work now; keep Flux 3 Image on the list of things to re-evaluate the day its endpoint actually ships.