# FLUX 3: when an image model decides to become a world model

> Satyajit Ghana — Head of Engineering @ Inkers Technology
> canonical: https://ai.thesatyajit.com/articles/flux-3
> date: 2026-07-24
> tags: diffusion, image-generation, video-generation, flow-matching, black-forest-labs, explainer
Every FLUX before this one was an image model. FLUX.1 was a 12B rectified-flow text-to-image
transformer; FLUX.2 scaled the same recipe to a ~32B image-and-editing model. [FLUX 3](https://bfl.ai/blog/flux-3),
announced by [Black Forest Labs](https://bfl.ai) on 2026-07-23, is a different kind of object. It is a
single **multimodal foundation model** that learns jointly from images, video, and audio in one
architecture — and then generates all of them, plus robot *action*, from the same backbone. The framing
in the title is deliberate: "Real World Models." BFL is no longer trying to make prettier pictures; it is
trying to build a model of how the world looks, moves, and sounds.

<Figure
  src="/articles/flux-3/fig1.png"
  alt="A dark collage titled FLUX 3, with thumbnails labelled image (a galloping horse), video (a breaking wave), audio (a market scene), and action (a lynx), arranged around the wordmark."
  caption="FLUX 3 spans image, video+audio, and action from one model — the thesis in one frame (FLUX 3, official announcement)."
/>

The argument for one model is an information argument, and it is worth stating in BFL's own terms. No
single modality is a complete description of reality — each is a lossy projection captured by a different
sensor. Images fix spatial structure at one instant; video restores time and reveals physical dynamics;
audio exposes causal links between mechanical events and the sounds they make; language ties all of it to
goals and instructions. Learn from one projection and you get a good model of that projection. Learn from
all of them at once and their **mutual constraints** teach you more: the sound has to match the impact,
the motion has to obey the mass, the future has to follow from the past. The modalities stop being
separate problems and start being evidence about one underlying reality.

That is the pitch. Because FLUX 3 shipped as an Early Access *capabilities* announcement rather than a
tech report — no parameter count, no full architecture, benchmarks that are BFL's own — the honest way to
cover it is to explain the mechanism it is built on from first principles, show the evidence BFL did
publish, and keep the caveats visible. So: two mechanisms first, then the numbers.

## Mechanism 1: flow matching, and why few steps is the whole game

FLUX has always been a **flow-matching** model, and FLUX 3 builds on an approach BFL calls
[Self-Flow](https://bfl.ai/research/self-flow). Flow matching is the cleaner cousin of diffusion, and the
idea is simple enough to hold in your head. You want to turn a sample of pure noise into a sample of data.
So you define a path between them — for training, literally the straight line
$x_t = (1-t)\,x_{\text{noise}} + t\,x_{\text{data}}$ — and you train a network to predict the **velocity**
$v_\theta(x, t)$ that points along that path. Generation is then just solving an ordinary differential
equation: start at noise, and take steps in the direction the velocity field tells you, until $t = 1$.

The subtlety is *how many steps*. Each step is a full forward pass of a huge transformer, so steps are the
cost. And here the geometry of the path matters enormously. If the learned field is **straight** — a
constant velocity, which is what "rectified" flow aims for — then a first-order Euler integrator lands on
the data exactly, no matter how few steps you take. If the field is **curved**, few steps cut the corner
and miss the target; the error only closes as you add steps (and cost). Drag the step count and flip the
field to feel it:

<FlowSteps />

This is why "straighten the transport paths" has been the central obsession of the whole FLUX / rectified-flow
lineage: a straighter field means a few-step sampler that still lands, which means a 20-second video is
merely expensive instead of impossible. The trajectory geometry above is the same one the
[Mage-Flow](/articles/mage-flow) piece leans on for its 4-step Turbo — few-step generation is a property of
the *field*, not a trick bolted on afterward.

## Mechanism 2: one sequence, joint attention across modalities

The second mechanism is how four modalities fit in one model. FLUX 3 sits in the **MMDiT** lineage — the
multimodal diffusion transformer that the [Mage-Flow explainer](/articles/mage-flow) walks through in
detail — and the load-bearing idea is that every modality is tokenized into a *single* sequence, and one
attention operation runs over the whole thing. A query token is not confined to its own modality: an audio
token can attend to the video frame that produced the sound; a video token can attend to the text that
describes the scene. Pick the query's modality below and flip joint versus per-modality attention:

<JointAttention />

Per-modality attention gives you four models in a trenchcoat. **Joint** attention is what lets the mutual
constraints actually do their work — it is the mechanical form of "the modalities are evidence about one
reality." BFL's own diagram makes the shape concrete: shared per-modality encoders feed a single
multimodal transformer, shared decoders read it back out, and *action* is added as one more
lane — explicitly marked extensible.

<Figure
  src="/articles/flux-3/fig2.png"
  alt="FLUX 3 architecture: image, video, audio and action inputs each pass through their own encoder into a single shared Multimodal Transformer, with a text encoder feeding in from the side; matching decoders produce image, video, audio and action outputs. The action lane is labelled extensible."
  caption="One shared Multimodal Transformer with per-modality encoders/decoders and a text conditioner; the action lane is marked extensible (FLUX 3, official announcement)."
/>

Self-Flow is BFL's method for aligning generation and understanding inside that one backbone, and the one
quantitative claim they put behind it is that unifying the two lifts *both* at once. Their ablation
reports lower generation error (Fréchet distance) per modality against a flow-matching baseline, and —
more interestingly — faster and higher-climbing success on downstream robot-control tasks when the
backbone is finetuned:

<Figure
  src="/articles/flux-3/fig3.png"
  alt="Two-panel chart. Left: generation error (Fréchet distance) for video, image and audio, Self-Flow versus Flow Matching, each normalized to FM=100; Self-Flow is lower on all three (66.3 vs 72.9 video, 3.69 vs 4.04 image, 149.8 vs 153 audio). Right: robot-control success rate over training steps, Self-Flow climbing to 47% versus 35% for flow matching, marked 2x faster learning."
  caption="Self-Flow vs. Flow Matching: lower generation error across all three modalities, and ~2× faster / higher robot-control success after finetuning (FLUX 3, official announcement). Vendor-reported, normalized to FM = 100."
/>

Read that right panel carefully, because it is the real bet: the same weights that generate video are a
**dynamics-aware prior** for physical control. That is the bridge from "content tool" to "world model,"
and it is the part most worth being skeptical of until there is a paper.

## What it actually does: video, with sound

The headline capability in Early Access is video. FLUX 3 generates up to **20 seconds in a single pass**,
and — the part competitors mostly don't have — every clip comes with **native audio**, generated jointly
rather than dubbed on afterward. The capability list is broad: text-to-video, image-to-video (animate a
still or use images as visual references), video-to-video (carry a character from a reference clip into a
new scene), keyframe-to-video for controlled transitions, multilingual dialogue, and *agentic chaining*
of clips into multi-shot sequences minutes long with consistent characters. Here is a representative shot
from BFL's own reel — a single continuous take of a galloping horse, the kind of coherent physical motion
the "world model" framing is really about:

<Video
  src="/articles/flux-3/flux3-video"
  poster="/articles/flux-3/flux3-video-poster.jpg"
  alt="A dappled grey horse galloping across a green plain under a dark stormy sky, with motion blur and debris blowing through the air."
  caption="A ~4s excerpt from BFL's FLUX 3 reel (muted/looped here; the source clips carry native audio). Text-to-video, 4K source (FLUX 3, official announcement)."
/>

<Callout type="note">
The clip is muted and trimmed to keep the page light; the point it carries is temporal coherence — the
horse's gait, mane, and the blown debris stay physically consistent across the shot. BFL's full reel runs
image, video, and audio together; native sound is one of the model's stronger claims.
</Callout>

## The numbers — and exactly what they are

For the preliminary evaluation, BFL generated 10-second text-to-video clips at 720p with audio and ran
pairwise human-preference comparisons against a spread of current video models. These are the results
they published — read as "share of comparisons where a rater preferred FLUX 3 over the named model":

<BenchBars
  title="FLUX 3 text-to-video — human-preference win rate vs. each model (%)"
  unit="%"
  max={100}
  bars={[
    { label: "Luma Ray 3.2", value: 93, highlight: true },
    { label: "Runway Gen-4.5", value: 77, highlight: true },
    { label: "Grok Imagine Video", value: 69 },
    { label: "Kling v3 Pro", value: 60 },
    { label: "Happy Horse v1", value: 59 },
    { label: "Happy Horse 1.1", value: 57 },
    { label: "Seedance 2.0", value: 52 },
    { label: "Gemini Omni Flash", value: 52 },
  ]}
/>

<Callout type="warn">
Hold these loosely. **50% is a tie**, not a loss — so the 52% against Seedance 2.0 and Gemini Omni Flash
is essentially even, while the 93% against Luma Ray 3.2 is a rout. The two highlighted bars (Runway,
Luma) are the comparisons BFL leads with in its post; I highlighted *their* emphasis, not mine. Every
number here is **vendor-reported**, from BFL's own harness, on short 720p clips, for a model BFL calls
"still in development" — there is no independent third-party evaluation yet, and the Grok figure is quoted
by BFL as "up to 69%." This is a preview signal, not a settled ranking.
</Callout>

## Image and action

Image generation and editing are coming a little behind video (Early Access "in the following weeks").
BFL says even mid-training FLUX 3 is a clear step over earlier FLUX on complex-prompt handling and
high-accuracy multilingual **text rendering** — the two things that have defined the modern image race.
The sample grid spans photographic, product, painterly, and graphic styles:

<Figure
  src="/articles/flux-3/fig4.jpg"
  alt="A grid of eight FLUX 3 image samples: pink smoke in a petri dish, a blue-framed chair with a red seat, molten lava pouring over rock, a painterly stool in a sunlit corner, a minimalist lighthouse at night, a tulip frozen in an ice block, a close-up of an octopus eye, and a black car on a worn asphalt lot."
  caption="FLUX 3 image samples across photographic, product, painterly and graphic styles (FLUX 3, official announcement)."
/>

The most unusual branch is **action**. FLUX 3's world understanding is meant to extend to predicting what
happens next — and BFL takes two routes to it: native action prediction folded into the model, and using
the pretrained video backbone as a dynamics-aware foundation that specialized robot-control models finetune
from with little task-specific data. The first partner is [mimic robotics](https://bfl.ai/blog/flux-3),
with whom BFL built **FLUX-mimic**, a video-action model for dexterous manipulation reportedly tested on
production tasks at Audi. The bet, again, is that content creation and physical AI run on the *same*
foundation — the claim the right-hand panel of the Self-Flow chart is quietly staking out.

## The variants, and what "open" means this time

Everything ships from one underlying multimodal flow-matching model, rolled out in phases behind
Early Access gates for safety testing:

| Model | Covers | Access | Status (Jul 2026) |
|---|---|---|---|
| **FLUX 3 Video** | video + audio, gen & edit | API + private weights | Early Access (now) |
| **FLUX-mimic / FLUX 3 Action** | action prediction | research & commercial partners | rolling out (mimic robotics) |
| **FLUX 3 Image** | image, gen & edit | API + private weights | "in the following weeks" |
| **FLUX 3 Dev** | image + video + audio + action backbone | **open weights** | promised, not yet released |

That last row is the one to watch. FLUX.1 and FLUX.2 earned their standing partly because BFL shipped
open `dev` weights the community could actually run; FLUX 3 Dev promises the same for a *multimodal*
backbone — but as of the announcement it is a promise, and the near-term reality is API and private-weight
access. "Open" is on the roadmap, not on the table yet.

## The take

FLUX 3 is the most ambitious repositioning in the open-ish image world this year: from a best-in-class
image model to a single flow-matching backbone that treats image, video, audio, and action as one
learning problem. The mechanism is sound and well-motivated — joint attention over a unified token sequence
is the honest way to let modalities constrain each other, and rectified flow is what makes generating 20
seconds of it tractable. The evidence is thinner than the ambition: preliminary vendor evals on short
clips, a Self-Flow ablation without a paper behind it, an open release that is still a promise, and the
boldest claim — that a video generator is also a robot-control prior — resting on one chart. If it holds
up, "image model" will look like a strangely narrow way to have described what BFL was building. Worth
watching the Dev weights and the tech report; until then, admire the direction and keep the caveats.

---

*Source: [FLUX 3 — Real World Models](https://bfl.ai/blog/flux-3) (Black Forest Labs, 2026-07-23) and
[Self-Flow](https://bfl.ai/research/self-flow). Architecture, Self-Flow, sample, and benchmark figures are
BFL's own, shown for commentary; all evaluations are vendor-reported and preliminary. The flow-matching
and joint-attention interactives are mine. Related: [Mage-Flow](/articles/mage-flow) on the MMDiT backbone
and few-step Turbo sampling.*
