FLUX.1 Kontext
Use the legacy route when reproducing an older task or validating a migration.
- Feature-flagged availability
- Legacy endpoint recorded
- No claim that it is FLUX.2
Generation comparison
FLUX Kontext vs FLUX.2: What Changed?
FLUX.1 Kontext remains available as a legacy rollback option, while FLUX.2 becomes the primary matrix for generation, editing, flexible output and multi-reference composition.
@image1 + @image2Auto · FLUX.2
FLUX.2 workspace
Use the current model family for new production work.
- Pro, Max, Flex and Klein
- Auto and flexible aspect ratios
- One to four numbered references
Safe migration
A model change should not erase the creative decisions behind a result.
- History keeps exact model IDs
- Old selections map to a supported option
- Branch before changing direction
Built for iterative visual work
Every successful result can become the source of a new edit. FluxContext keeps the prompt, model, output dimensions, seed, and parent task relationship so you can return to a prior node and create another branch.
Open the workspace