gpt-oss-120b
openai/gpt-oss-120bgpt-oss-120b at Q4_K_M is exactly 62,768,723,552 bytes (58.46 GiB / 62.77 GB) — an effective 4.170 bits per weight, not the nominal 4. Its KV cache at 32K is 1.15 GiB, not the 2.25 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| Q3_K_S2 shards | 58.27 GiB | 62,563,621,472 | 4.157 | — | unsloth |
| Q2_K2 shards | 58.27 GiB | 62,570,256,992 | 4.157 | — | unsloth |
| Q4_02 shards | 58.32 GiB | 62,620,023,392 | 4.160 | — | unsloth |
| Q3_K_M2 shards | 58.33 GiB | 62,626,843,232 | 4.161 | — | unsloth |
| Q4_12 shards | 58.41 GiB | 62,715,938,912 | 4.167 | — | unsloth |
| Q4_K_S2 shards | 58.45 GiB | 62,759,138,912 | 4.170 | — | unsloth |
| Q4_K_M2 shards | 58.46 GiB | 62,768,723,552 | 4.170 | — | unsloth |
| Q2_K_L2 shards | 58.54 GiB | 62,859,823,712 | 4.176 | — | unsloth |
| Q5_K_S2 shards | 58.56 GiB | 62,881,227,872 | 4.178 | — | unsloth |
| Q5_K_M2 shards | 58.57 GiB | 62,889,522,272 | 4.178 | — | unsloth |
| Q6_K2 shards | 58.94 GiB | 63,284,496,960 | 4.205 | — | unsloth |
| MXFP42 shards | 59.03 GiB | 63,387,345,440 | 4.211 | — | lmstudio-community |
| MXFP4 | 59.03 GiB | 63,387,346,208 | 4.211 | — | ggml-org |
| Q8_02 shards | 59.03 GiB | 63,387,347,520 | 4.211 | — | unsloth |
| F16 | 60.88 GiB | 65,369,017,728 | 4.343 | 687 | unsloth |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.17 GiB | 0.28 GiB | 1.68× | 18 / 18 / 0 |
| 8,192 | 0.31 GiB | 0.56 GiB | 1.83× | 18 / 18 / 0 |
| 16,384 | 0.59 GiB | 1.13 GiB | 1.91× | 18 / 18 / 0 |
| 32,768 | 1.15 GiB | 2.25 GiB | 1.95× | 18 / 18 / 0 |
| 65,536 | 2.28 GiB | 4.50 GiB | 1.98× | 18 / 18 / 0 |
| 131,072 | 4.53 GiB | 9.00 GiB | 1.99× | 18 / 18 / 0 |
18 of 36 layers cache only a 128-token window rather than the full context, on a period of . Figures assume the default configuration; --swa-full disables the saving entirely.
Compare with
Will it run on your card?
Why other calculators give a different number
A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 63.08 GiB. The real file is 58.46 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 2.25 GiB at 32K context where the real figure is 1.15 GiB, because most of this model's layers cache a fixed window rather than the whole context.
Architecture
Questions people ask
- How much VRAM does gpt-oss-120b need?
- Q4_K_M is exactly 62,768,723,552 bytes (58.46 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
- How large is gpt-oss-120b's KV cache?
- 1.15 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
- Is gpt-oss-120b a mixture-of-experts model?
- Yes — 128 experts, 4 routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.
- Which quantization of gpt-oss-120b 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.