FLUX.1 Kontext [dev]

Closed weights Black Forest Labs 12B parameters May 2025

No estimate

No hardware requirements for this model

The weights for this model have not been published, so it cannot be downloaded or run on your own hardware at any size. It is reachable only through its provider, and no graphics card changes that.

On record

Full specification

Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.

Origin

Who built this model, where, and when it was published.

Organisation
Black Forest Labs
Organisation type
Industry
Country
Germany
Published
29 May 2025
Authors
Stephen Batifol, Andreas Blattmann, Frederic Boesel, Saksham Consul, Cyril Diagne, Tim Dockhorn, Jack English, Zion English, Patrick Esser, Sumith Kulal, Kyle Lacey, Yam Levi, Cheng Li, Dominik Lorenz, Jonas Müller, Dustin Podell, Robin Rombach, Harry Saini, Axel Sauer, Luke Smith

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Image generation, Vision
Task
Image generation, Text-to-image, Image captioning
Base model
Flux.1 [pro]

Size

How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.

Parameters
12B

12B

Training data
tokens

Availability

Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.

Weights
Closed — provider access only
Model access
Unreleased
Training code
Unreleased

We open FLUX.1 Kontext [dev] in a private beta release, for research usage and safety testing. Please contact us at [email protected] if you’re interested.

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Confident

Sources

Where this record came from and when it was last checked.

Reference
Introducing FLUX.1 Kontext and the BFL Playground
Last updated
28 November 2025

What the numbers mean

Where it came from

FLUX.1 Kontext [dev] was published by Black Forest Labs, in Germany, in May 2025. industry is the category the publisher falls under.

It works in Image generation, Vision, and is recorded as doing image generation, Text-to-image, Image captioning.

Its starting point was Flux.1 [pro] — most models at this scale are adapted from an existing base rather than built from nothing.

Its weights were never published, so it can only be reached through its provider. No graphics card changes that.

Answers

FLUX.1 Kontext [dev] — common questions

01

What GPU do I need to run FLUX.1 Kontext [dev]?

None. FLUX.1 Kontext [dev] is a closed model — its weights were never published, so it cannot be downloaded or run on your own hardware at any price. It is reachable only through its provider.

02

Is FLUX.1 Kontext [dev] open source?

No. FLUX.1 Kontext [dev] has not had its weights published, so it exists only as a service controlled by its owner.

03

How many parameters does FLUX.1 Kontext [dev] have?

FLUX.1 Kontext [dev] has 12B parameters. 12B. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.

04

Who created FLUX.1 Kontext [dev]?

FLUX.1 Kontext [dev] was published by Black Forest Labs, based in Germany, categorised as industry.

05

When was FLUX.1 Kontext [dev] released?

FLUX.1 Kontext [dev] was published in May 2025.

06

What is FLUX.1 Kontext [dev] used for?

FLUX.1 Kontext [dev] works in Image generation, Vision, and is recorded as handling image generation, Text-to-image, Image captioning. These are the areas it was designed around; they describe intent rather than a hard boundary.

Source

Original publication

Record last updated 28 November 2025

The other direction

Looking at it from the other side?

This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.