black-forest-labs · image

FLUX.2-klein-9b-kv

black-forest-labs/FLUX.2-klein-9b-kv

FLUX.2-klein-9b-kv at Q4_K_M is exactly 5,716,891,936 bytes (5.32 GiB / 5.72 GB) — an effective 5.038 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
9.1B
Architecture
flux
Context
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K3.33 GiB3,571,505,4403.147QuantStack
Q3_K_S4.15 GiB4,457,552,1603.928QuantStack
Q3_K_M4.25 GiB4,564,506,9124.022QuantStack
Q4_K_S5.23 GiB5,616,228,6404.949QuantStack
Q4_K_M5.32 GiB5,716,891,9365.038QuantStack
Q5_K_S6.25 GiB6,706,747,6805.910QuantStack
Q5_K_M6.35 GiB6,813,702,4326.004QuantStack
Q6_K7.33 GiB7,865,424,1606.931QuantStack
Q8_09.29 GiB9,978,304,8008.793QuantStack

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser16.91 GiB52%no, must be resident
vae0.16 GiB0%no, must be resident
text encoder15.26 GiB47%yes — the usual first VRAM saving
Full pipeline32.32 GiBresident if nothing is offloaded

The parameter count published for a diffusion model describes the denoiser alone. Running it also requires its text encoder and VAE, and the text encoder is often nearly as large as the denoiser — which is why offloading it is the standard first move when you run out of memory. This repository also ships a single-file copy of the denoiser at its root; we count it once, not twice.

We publish component sizes here, not throughput. Community-submitted image-generation rates do exist for many GPUs and we show them on the hardware pages, but they aggregate runs at different resolutions, step counts and settings, so they cannot be attributed to one model. Peak memory during sampling is unmeasured by any public source, and we do not estimate it.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 4.76 GiB. The real file is 5.32 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does FLUX.2-klein-9b-kv need?
Q4_K_M is exactly 5,716,891,936 bytes (5.32 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of FLUX.2-klein-9b-kv should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.