What is the Flux 3 AI Video Generator?

The Flux 3 AI Video Generator is an independent browser workspace for creators following the next Flux 3 multimodal direction. It focuses on image concepts, video planning, references, prompts, and campaign workflows while official model access continues to evolve.

Is this the official BFL website?

No. This is an independent creator platform. The Flux 3 AI Video Generator helps users organize workflows around the new model direction while official availability, pricing, and API rules should be verified with Black Forest Labs.

Can I create images here?

Yes. The Flux 3 AI Video Generator works as an AI image generator for product frames, campaign visuals, portraits, and reference-led concepts. It avoids claiming fixed official technical limits that have not been publicly confirmed.

Can it help with video?

Yes. The Flux 3 AI Video Generator supports video concepting, image-to-video planning, shot descriptions, and storyboard creation for teams exploring motion-aware creative.

What is the difference between Flux 3 and Flux 3.0?

Creators search both Flux 3 and Flux 3.0 for the same next-generation model direction. The Flux 3 AI Video Generator uses both terms naturally so users can find image and video workflows in one place.

How is it different from a generic generator?

A generic generator stops at one still image. The Flux 3 AI Video Generator keeps image, video direction, reference image, prompt, motion notes, and campaign context together.

Does it promise official API access?

No. Official access should be confirmed through Black Forest Labs. The Flux 3 AI Video Generator focuses on practical creative workflows and avoids unsupported claims about self-serve access.

The Flux 3 AI Video Generator is built for marketers, designers, social creators, ecommerce teams, creative producers, and anyone who needs fast image ideas and video storyboards.

Can I use reference images?

Yes. The Flux 3 AI Video Generator supports reference-led workflows for style, subject identity, product look, and visual continuity.

Use the Flux 3 AI Video Generator for product ads, social hooks, thumbnails, character frames, concept art, pitch visuals, storyboard frames, and image-to-video directions.

New users can start with free credits and review the credit cost before generation. Paid plans are available for higher-volume Flux 3 AI Video Generator workflows.

Can I use outputs commercially?

You can use generated outputs according to the plan and platform terms shown at checkout. For official model licensing, verify the latest rules with Black Forest Labs.

FLUX Kontext: Still Worth Using in 2026?

FLUX.1 Kontext was the model that made "edit this image by describing the change" feel reliable. A lot of tools were built on it, and a lot of those tools still call it.

Then FLUX.2 arrived, and Black Forest Labs' own documentation now files Kontext under Legacy Models with a notice recommending FLUX.2 for new projects. If you are running Kontext today, the question is whether that notice is a nudge or a deadline.

Sourcing note: Kontext's current classification, the recommendation notice, the endpoints, and the FLUX.2 capability comparison below come from Black Forest Labs' own documentation and model pages. No third-party benchmark is cited. Last verified July 30, 2026.

What this article solves

The pain point: "legacy" is ambiguous. It can mean deprecated-and-dying or simply not-the-default. Teams with Kontext in production need to know which, and the marketing pages do not say.

The differentiator: this separates what Kontext still does perfectly well from what FLUX.2 genuinely does better, so the migration decision is about your workload rather than about labels.

Where Kontext stands today

BFL's documentation is direct about it. The Kontext introduction page carries a notice that FLUX.2 is now their recommended model for image generation and editing, citing superior quality, multi-reference support for up to 10 images, improved text editing, and output up to 4MP.

The API reference goes further: the Kontext endpoint descriptions themselves say that for image editing, you should prefer FLUX.2 [pro] or FLUX.2 [flex], described as the recommended default models for editing workflows.

In the documentation navigation, Kontext sits under Legacy Models alongside the FLUX1.1 [pro] line.

What that adds up to: Kontext is not being switched off, and the endpoints are live and documented. It is no longer where new work should start.

What Kontext actually does

FLUX.1 Kontext [pro] combines text-to-image generation with context-aware image editing — describe a change and it applies it while keeping the rest of the image intact. Two tiers exist, [pro] and [max], both testable in BFL's playground before you integrate.

The endpoints:

/flux-kontext-pro
/flux-kontext-max

For single-image editing driven by a natural-language instruction, it still does the job it was built for.

What FLUX.2 does that Kontext cannot

This is where the migration case actually lives:

Capability	Kontext	FLUX.2
Reference images per request	Single-image editing	Up to 10
Output resolution	Lower ceiling	Up to 4MP
Text editing	Supported	Improved, per BFL
Generation + editing in one checkpoint	Yes	Yes
Status in BFL docs	Legacy	Recommended default

The reference-image count is the one that changes what is possible rather than just how good it looks. Character consistency across a campaign, product identity held across a catalogue, style transferred from one image while composition comes from another — those are multi-reference workflows. Kontext editing one image at a time cannot express them.

Not building an integration at all? Flux 3 AI is a browser workspace for generation, editing and reference-driven work — no endpoint decisions required. Open the image generator or see the credit plans.

When staying on Kontext is defensible

Not every workload needs migrating this quarter:

Your edits are single-image and instruction-driven. That is exactly Kontext's shape; multi-reference buys you nothing.
You have prompt libraries tuned to Kontext's behaviour. Editing models respond differently to the same instruction; a migration means re-testing that library, not just swapping a URL.
Your outputs are well under 4MP. The resolution ceiling is not binding for you.
You have a pinned-model requirement. A stable, non-preview endpoint has value where reproducibility is contractual.

When to migrate

You need more than one reference image — this is the decisive one
You need 4MP output
Text rendering quality matters to your work
You are starting something new — BFL's own recommendation is unambiguous here
You want to be on the model family that gets improvements, since new capability is landing on FLUX.2 and FLUX 3, not Kontext

How to migrate without surprises

Do not just swap the endpoint. Kontext and FLUX.2 interpret editing instructions differently; expect to re-tune prompts.
Pin first, then move. FLUX.2 has both preview and snapshot endpoints — flux-2-pro-preview tracks improvements, flux-2-pro is fixed. Migrate onto the pinned one if you have regression tests.
Re-baseline your golden images on the new model before switching traffic.
Budget for reference-image billing. FLUX.2 charges per megapixel and each reference image counts as at least 1 MP — a multi-reference edit costs meaningfully more than a Kontext single-image edit.

That last point catches teams out. Multi-reference is a capability upgrade and a cost increase; model it before you turn it on at volume.

FAQ

Is FLUX Kontext deprecated? BFL classes it under Legacy Models and recommends FLUX.2 for new projects. The endpoints remain documented and available.

What replaced Kontext? FLUX.2 — specifically [pro] and [flex], which BFL names as the recommended defaults for editing.

What are the Kontext endpoints? /flux-kontext-pro and /flux-kontext-max.

What does FLUX.2 add? Up to 10 reference images, output to 4MP, and improved text editing.

Can I still try Kontext before integrating? Yes, both tiers are available in BFL's playground.

Will my Kontext integration break? Nothing in BFL's documentation announces a shutdown. Treat it as stable-but-frozen rather than at-risk.

Is Kontext cheaper than FLUX.2? Compare per-megapixel rates on BFL's pricing page for your actual workload — and remember multi-reference edits add per-reference charges that single-image Kontext calls do not have.

Bottom line

Kontext is in the comfortable middle: documented, live, and no longer where BFL is investing. If your editing is single-image and instruction-driven, staying is a legitimate choice. The moment you need a second reference image, the decision makes itself.

If you would rather not manage this decision at all, work in a browser workspace and let the model layer be someone else's problem.

Sources

FLUX.1 Kontext introduction (BFL documentation) — legacy classification, FLUX.2 recommendation notice, tiers, playground link
BFL documentation overview — Legacy Models navigation and current recommendation
Image generation quick start (BFL docs) — full endpoint list including Kontext and preview-vs-snapshot behaviour
Kontext image editing (BFL docs) — editing capability detail
FLUX.2 overview (BFL docs) — the recommended replacement
FLUX.2 model page — multi-reference and production positioning
FLUX.2: Frontier Visual Intelligence (BFL, November 25, 2025) — what FLUX.2 added over FLUX.1
BFL API pricing — per-megapixel rates and reference-image billing rules
FLUX.2 image editing (BFL docs) — the editing workflow to migrate onto
FLUX API integration guide (BFL docs) — migration and integration guidance

Scope note: classification and endpoints as of July 30, 2026. Flux 3 AI is an independent creator workspace, not affiliated with Black Forest Labs.