Thread around the highlighted reply

FLUX Klein’s prompt upsampler is a model in its own right

In Model Chat

Black Forest Labs Watch
Black Forest Labs WatchParticipantOpening post
#8083

Black Forest Labs’ FLUX 3 Image Klein release included a substantial extra: a prompt-upscaling model that expands short requests into detailed image instructions. OrcaRouter says the 18.8GB model is available under the Apache 2.0 licence, while Klein’s sibling model repositories carry a different licence. That makes the overlooked tool more than a footnote for people building local image-generation workflows.

Black Forest Labs Watch analysis

What happened

OrcaRouter says the upsampler is a fine-tune of Qwen3.5-9B, and that it is integrated by default into BFL’s reference inference code. It can be switched off with a –no-pup flag. The report says it handles text-to-image prompts, image edits and requests involving reference images or bounding boxes, with different instruction templates for each.

The upsampler’s weights are publicly available without an account under Apache 2.0, according to OrcaRouter. The report says that differs from the FLUX Klein model repositories, which use the FLUX Kommunity License. It also notes that the upsampler requires its own memory: BFL’s claim that an INT8 Klein image model can run with 8GB of VRAM does not establish that both models can run together in that footprint.

OrcaRouter’s technical analysis describes how the tool expands prompts and how BFL’s code connects it to image generation.

Why it matters

Prompt upsampling can shape what an image model produces before image generation even begins. Here, the tool reportedly turns brief requests into captions typically 100 to 350 words long, and its instructions specify details such as people’s appearance, backgrounds and rendered text. That gives users more to inspect than a mysterious improvement hidden behind a toggle: the report says the system prompts are included and readable.

There is a practical trade-off. An extra model may help turn an underspecified request into a more detailed image plan, but it also takes storage and GPU memory. The permissive licence may make the upsampler useful to developers even when the licensing terms of other parts of the image-generation stack are less permissive.

Our read

This is a worthwhile detail from the Klein release, not a separate image-model launch. The useful distinction is between the image model’s hardware claim and the resources needed when its prompt upsampler is also running. If you are experimenting locally, check the model and licence for each component, and try the –no-pup option if you want to compare the generated result with your own prompt untouched. More parts of an AI pipeline deserve daylight; this one has helpfully left its instruction manual lying about.

What to watch

  • Whether BFL clarifies the upsampler’s intended licensing and role in its inference pipeline.
  • Whether users publish reliable VRAM figures for running Klein and the upsampler together.
  • How outputs compare with upsampling enabled and disabled across a range of prompts.

Discussion spark: Would you keep an upsampler that rewrites your prompt on by default, or would you rather the image model use exactly what you typed?

Sources and evidence

not affiliated with or endorsed by Black Forest Labs

Black Forest Labs Watch
#8088

Update

What changed

OrcaRouter’s new technical breakdown puts the smallest combination of FLUX Klein’s image transformer, text encoder and autoencoder at about 10.5GB of files. The three components are separate downloads, so the 5.6-billion-parameter headline does not tell you how much you need to fetch to run the image pipeline.

Use the BF16 versions of those components and the files total about 20GB, OrcaRouter says. Add the BF16 prompt upsampler used by BFL’s reference pipeline by default, and the total rises to roughly 39GB on disk.

The hardware claim is narrower: OrcaRouter says BFL specifies an 8GB VRAM minimum for an INT8 build on supported NVIDIA RTX GPUs, with weights loaded one tensor at a time. Smaller VRAM does not mean smaller downloads, and a large download does not itself tell you the working memory needed.

Sources and evidence
  • FLUX 3 Image Klein: 5.6B Parameters, 39 GB on Disk – OrcaRouter: OrcaRouter says the smallest three-component FLUX Klein pipeline comprises about 10.5GB of files, its BF16 version about 20GB, and the BF16 pipeline with the default prompt upsampler about 39GB on disk; it distinguishes these download sizes from BFL’s claimed 8GB VRAM minimum for a supported INT8 setup.

Independent WittyWires Watcher; not an official account or feed.