What is FLUX 3? The family map: image, video, audio, action
BFL's docs describe FLUX 3 as one family covering image, video with synchronized audio, audio and action. Which pieces have open weights and which do not.

FLUX 3 is Black Forest Labs' unified model family. Its documentation lists four modalities: image, video with synchronized audio, audio, and action. The open weights the docs point to are the earlier FLUX.2 [klein] and [dev] models on Hugging Face, while FLUX 3 Action is a separate open-weights release.
The family at a glance
The BFL documentation describes FLUX 3 as a single family rather than a set of unrelated products, and lists an MCP integration alongside the API. A September 23 post introduces FLUX 3 Action as a 7B open-weights World Action Model.
| Piece | What the sources say | Open weights stated? |
|---|---|---|
| FLUX 3 image | Part of the unified family | Not stated |
| FLUX 3 video | Video with synchronized audio | Not stated |
| FLUX 3 audio | Part of the unified family | Not stated |
| FLUX 3 Action | 7B World Action Model | Yes, open weights |
| FLUX.2 [klein] and [dev] | Earlier generation | Yes, on Hugging Face |
How to read the open-weights column
Where the sources say nothing, the table says not stated. That is not a claim that weights are closed; it means the pages read on October 3, 2026 do not list them. Before you plan a local deployment of any FLUX 3 piece, look for the weights file and the license on the model's own page rather than inferring from the family name.
The Action model is the clearest example of how the family differs from the image models. BFL reports 42.2 percent on RoboLab-120 against 36.8 percent for Cosmos 3 Nano, which is a robotics benchmark. It is not an image or video generator, so it does not help with creative work.
Which piece matters for video makers
For image and video production, the relevant modalities are image and video with audio. A hosted API is the usual way to reach them. On Sume, GET /v1/images/models lists the image models you can call, and each entry publishes its parameters, so you can see whether a given FLUX model is available and which inputs it accepts without relying on a vendor's family page.
A model's presence on a vendor's documentation page and its presence in a particular catalog are separate facts. Always check the catalog you will call.
curl "https://api.sume.com/v1/images/models" \
-H "Authorization: Bearer $SUME_API_KEY"Takeaway
Treat FLUX 3 as a family name, not a license. Confirm modality, availability and weights for the specific model you plan to use.
Sources
Related posts
More in Models
- An OpenRouter-compatible video API: sume/auto or a pinned model
Sume's POST /v1/videos follows OpenRouter's video generation API field for field. Let sume/auto pick the model, or pin a catalog id like seedance-2.5.
- Image generation API with reference images: POST /v1/images
Send a prompt plus public HTTPS reference images to Sume's POST /v1/images. Pin a catalog model or send sume/auto; the catalog lists each model's limits.
- Video 1.0 and Image 1.0 are retiring soon: move to sume/auto
Sume Video 1.0 and Image 1.0 are retiring soon and already run as aliases for the Auto path. New integrations call /v1/videos or /v1/images with sume/auto.
- Music generation API: the Sume Music Router with Lyria 3.5
Sume's Music Router turns a text prompt into a track via POST /v1/music-router/generate. sume/music-auto picks the engine, Lyria 3.5 today.
Written by Sume