FLUX 3

Overview

One model trained across image, video, and audio. Video with synchronized sound, live now.

One model, multiple modalities

FLUX 3 generates video with synchronized audio: from a text prompt, from pinned keyframes, or continuing an existing clip. More modalities ship on the same request shape as they land.

Up to 20 seconds at FHD (1920 × 1088 for 16:9), 24 fps, in a single request.
Multilingual speech with strong lipsync, plus effects and ambience, generated with the frames.
Multiple scenes and camera angles in one generation. Shots hold together across cuts.
Stylistic range beyond cinematic: animation, motion design, stylized artistic looks.
Accurate text and typography rendered inside the scene.

FLUX 3 is a preview model. Video editing and Omni Reference with images and videos will be available soon.

Modes

Every request names a mode. The mode is how you tell FLUX 3 what you’re starting from, and it decides what the model does with your media: start a clip from words alone, build one around images you pin, or carry an existing clip forward.There are three:

Text to Video (t2v) starts from nothing but your prompt.
Image to Video (i2v) starts from your images. They become frames of the clip itself.
Video Continuation (v2v) starts from a clip you already have and keeps it going.

All three run on the same flux-3-video endpoint, and the rest of the request looks identical. To show how they connect, everything below is one scene passed through the whole API: the first request generates a clip, and every request after it runs on that clip’s own frames. Each tab shows the request we sent and the video that came back.

Text to Video
Image to Video
Video Continuation

Describe the shot. t2v turns the prompt into a clip, sound included. This is the request that started the scene:

curl -X POST https://api.bfl.ai/v1/flux-3-video \
  -H "x-key: $BFL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "t2v",
    "prompt": "she takes his hand and pulls him laughing through the lantern-lit alley, the camera chasing them, paper lanterns swaying overhead, their footsteps and laughter echoing off the walls",
    "duration": 8
  }'

The clip this request returned. The next two tabs build on it.

There is no separate start-frame field: keyframes is how you hand i2v images, and one image is the start frame. We extracted the opening frame of the clip in the first tab and pinned it, with a new camera direction:

curl -X POST https://api.bfl.ai/v1/flux-3-video \
  -H "x-key: $BFL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "i2v",
    "prompt": "from this frame the camera rises slowly above the alley as they rush away beneath the lanterns, their laughter fading into the night",
    "keyframes": "data:image/png;base64,<opening frame>"
  }'

Same first frame, different film: the pinned image opens the clip exactly, then the prompt takes over.

More images, more control: two pin the start and end frames, up to ten storyboard the clip, and [seconds, image] pairs pin each one to an exact moment. Here the hero clip’s first and last frames are pinned at 0 and 8 seconds and the model finds its own path between them:

curl -X POST https://api.bfl.ai/v1/flux-3-video \
  -H "x-key: $BFL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "i2v",
    "prompt": "they sprint the length of the lantern-lit alley, lanterns blurring past, footsteps quick on the wet stones",
    "keyframes": [[0, "data:image/png;base64,<first frame>"], [8, "data:image/png;base64,<last frame>"]],
    "duration": 8
  }'

Both pins hit exactly; the sprint in between is the model’s.

v2v picks up where your clip ends. Momentum, framing, and scene logic carry into the new footage. We sent the first tab’s clip as start_video and asked for the scene’s next beat:

curl -X POST https://api.bfl.ai/v1/flux-3-video \
  -H "x-key: $BFL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "v2v",
    "prompt": "they burst out of the alley into a crowded night market, drums and street chatter swelling, she pulls him into the lantern light",
    "start_video": "data:video/mp4;base64,<the clip from the first tab>",
    "duration": 8
  }'

The same couple, out of the alley and into the market: continuation keeps the scene’s logic and sound.

Everything else is optional. Set any field explicitly and it is used exactly; leave it out and the default takes over:

aspect_ratio and duration default to auto and fit themselves to the content.
resolution defaults to hd; fhd finishes the result at a higher resolution via the video upsampler.
generate_audio defaults to true.

The full field list, constraints, and dimensions live in the API reference.

Draft mode

Iterate in draft, commit once. Drafts generate faster and cost about a third of a full render, so you can explore variants freely and only pay full price for the shot you keep.

draft: true returns a fast preview instead of a full render, plus a draft_cache bundle in the result.
mode: "draft_enhance" renders the preview you picked at full quality: send its bundle as draft_cache and the original generation is reproduced. Same shot, same seed, nothing re-interpreted.

Here is the same prompt run through all three paths:Each fresh submit is its own generation, so the direct full render can interpret the shot differently from the draft you liked. Enhancing keeps it:

Draft preview

Enhanced: the draft’s shot, full quality

Direct full render: its own take

1 — Draft
2 — Enhance the one you picked

curl -X POST https://api.bfl.ai/v1/flux-3-video \
  -H "x-key: $BFL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "t2v",
    "prompt": "a fox running through dawn mist",
    "draft": true
  }'

Download the winning preview’s draft_cache URL from its result, then send the bundle back:

curl -X POST https://api.bfl.ai/v1/flux-3-video \
  -H "x-key: $BFL_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"mode\": \"draft_enhance\",
    \"draft_cache\": \"$(base64 -i draft_cache.bin)\"
  }"

Limits and constraints are in the API reference.

Specifications

Mode	You send	Length	Full render	Draft
Text to Video	a prompt	5–20 s	$0.17/s hd, $0.29/s fhd	$0.06/s
Image to Video	a prompt + 1–10 images	5–20 s	$0.17/s hd, $0.29/s fhd	$0.06/s
Video Continuation	a prompt + your clip	5–15 s	$0.43/s hd, $0.54/s fhd	$0.12/s

Every mode outputs 24 fps at hd or fhd, in aspect ratios 21:9, 2:1, 16:9, 4:3, 1:1, 3:4, and 9:16. Drafts render at hd.

What it can do

Start in ten seconds

FLUX 3 is asynchronous. You submit a request and get back an id and a polling_url; then you poll that URL until the job turns Ready and returns your result. Here is the full round trip, text to video with audio.

Result URLs are signed and expire about 2 hours after the job finishes. Download the video promptly once the status is Ready.

Getting started

Quickstart

Create an account, add credits, and make your first FLUX 3 call.

Try in Playground

Test FLUX 3 in your browser. No setup required.

Video

Generate from text, animate stills, pin keyframes, continue clips, all with audio.

API reference

The full flux-3-video request contract: modes, fields, constraints.

Get Started

Account Management

FLUX 3

FLUX.2

FLUX Tools

API Integration

Training

Legacy Models

FLUX 3

Overview

One model, multiple modalities

Modes

Draft mode

Specifications

What it can do

Start in ten seconds

Getting started

Quickstart

Try in Playground

Video

API reference

​Overview

​One model, multiple modalities

​Modes

​Draft mode

​Specifications

​What it can do

​Start in ten seconds

​Getting started

Quickstart

Try in Playground

Video

API reference

Overview

One model, multiple modalities

Modes

Draft mode

Specifications

What it can do

Start in ten seconds

Getting started