FLUX 3 Image Klein is an open-weight image model, not a chat LLM. The distilled BF16 generator file is 11.1 GB, the FP8 variant 6.3 GB and the NVFP4 variant 5.3 GB; the text encoder (8.9 GB in two shards) and VAE (0.3 GB) load on top. Black Forest Labs says an INT8 build runs on GeForce RTX cards with as little as 8 GB of VRAM, but the file listing we checked on 16 October 2026 does not contain an INT8 filename.

So the 8 GB figure depends on that INT8 build. The files you can download now are bigger: the BF16 generator, text encoder and VAE add up to about 20.3 GB, before any working memory. We haven’t measured a Klein run on any GPU.

Key specs

Spec Value Source
Release 15 October 2026 BFL blog, release notes
Tasks Text-to-image, editing, up to 10 reference images, bounding boxes, native 4K output Blog
Parameters 5.6B for the image generator, text encoder not counted (blog). Safetensors metadata: distilled 5,548,681,984; base 5,538,458,368 Blog; HF API
Steps Distilled: 16 steps, CFG 1. Base: 50 steps, CFG 3.5 Release notes
Resolution 768sq to 4k Release notes
License FLUX Kommunity License; free commercial use under $5M annual revenue Blog
API id flux-3-image-klein (distilled) Blog
Weights Hugging Face, gated. Distilled revision 1755314e2216, base revision f66af34f9c15 HF API, checked 2026-10-16

GB here means 10⁹ bytes and GiB means 2³⁰ bytes. GPU sizes on this site are in GiB; see why file size isn’t the VRAM you need.

Weight files (checked 16 October 2026)

The distilled repo has the generator twice: as a single file and as a two-shard transformer. Those are two copies of the same thing, so don’t add them together. The text encoder is separate. ae.safetensors and vae/diffusion_pytorch_model.safetensors differ by 2,264 bytes, so both are listed.

File Bytes GB GiB
Distilled model.safetensors 11,097,404,512 11.097 10.335
Distilled transformer shard 1 of 2 9,907,529,352 9.908 9.227
Distilled transformer shard 2 of 2 1,189,878,064 1.190 1.108
Text encoder shard 1 of 2 4,967,229,296 4.967 4.626
Text encoder shard 2 of 2 3,908,490,048 3.908 3.640
Text encoder, both shards 8,875,719,344 8.876 8.266
vae/diffusion_pytorch_model.safetensors 336,213,556 0.336 0.313
ae.safetensors 336,211,292 0.336 0.313
Distilled variants/fp8r/model.safetensors 6,270,949,144 6.271 5.840
Distilled variants/nvfp4/model.safetensors 5,277,674,144 5.278 4.915

The base repo uses the same text encoder and VAE sizes. Its generator files:

Base file Bytes GB
model.safetensors 11,076,957,072 11.077
variants/fp8r/model.safetensors 6,250,501,712 6.251
variants/nvfp4/model.safetensors 5,257,226,696 5.257

The distilled single-file generator, both text-encoder shards and the VAE file add up to 20,309,337,412 bytes (20.309 GB, 18.914 GiB). That leaves out ae.safetensors, the transformer shards and the FP8/NVFP4 variants. It’s a sum of files, not a measured load; activations and diffusion working memory come on top.

The blog’s 11.2 GB (BF16) and 5.6 GB (FP8) figures are rounded publisher numbers and don’t match the 11.097 GB and 6.271 GB files exactly. No filename containing int8 appeared in the 42-file distilled listing or the 39-file base listing.

What Black Forest Labs says about hardware

The INT8 build runs on GeForce RTX GPUs with as little as 8 GB of VRAM, through ComfyUI or Diffusers. NVIDIA’s timings, as reported in the same post: about 4 seconds per megapixel on an RTX 5090 and under 9 seconds on an RTX 4070 for the distilled INT8 build in ComfyUI, and under 0.6 seconds per megapixel image on GB300 with NVFP4. We haven’t reproduced any of these.

The release notes say both variants run on consumer GPUs down to an RTX 3090. Cards in the classes they name: RTX 4060 8GB (see what fits in 8 GB), RTX 4070 12GB, RTX 3090 24GB and RTX 5090 32GB. None of these pages has a measured Klein run.

The release notes also link a separate ComfyUI weight repo, which we haven’t summed.

API price

Per image, same for text-to-image and editing (release notes, 15 October 2026):

Resolution Price
768sq $0.008
1k $0.009
1.5k $0.011
2k $0.014
4k $0.036

The VRAM calculator and KV cache calculator cover open language models such as Qwen3.8-27B, not diffusion models. Two GPUs don’t pool into one bigger card; see two GPUs and unified memory. File sizes above are from the publisher’s listings, not our measurements. How we calculate.

FAQ

How much VRAM does FLUX 3 Image Klein need?

Black Forest Labs says an INT8 build runs on GeForce RTX GPUs with as little as 8 GB of VRAM. The files you can download today are larger: the BF16 generator is 11,097,404,512 bytes and the FP8 variant 6,270,949,144 bytes, before the text encoder and VAE.

Are the FLUX 3 Image Klein weights open?

Yes. Black Forest Labs released a distilled and a base model on 15 October 2026 under the FLUX Kommunity License, which allows free commercial use for individuals and companies with under $5 million in annual revenue. The Hugging Face repos are gated.

What does the FLUX 3 Image Klein API cost?

Per image, the same for text-to-image and editing: $0.008 at 768sq, $0.009 at 1k, $0.011 at 1.5k, $0.014 at 2k and $0.036 at 4k.

Can I use the VRAM calculator for FLUX 3 Image Klein?

No. The calculator covers open language models. Klein is a diffusion image model, so it has no calculator preset and no KV cache.

Sources last checked 2026-10-16.