TechCompare LogoTechCompare

How much VRAM does gpt-oss 20B need at Q4_K_M? OpenAI's first open-weight model since GPT-2

gpt-oss 20B at Q4_K_M is the model to download if you've never run a local LLM before in 2026. Apache 2.0, runs on anything, decent reasoning for the size, and OpenAI lineage. Not as strong as Qwen3 30B-A3B at the same memory footprint, but the brand recognition matters and the licensing is the cleanest in the open-weights ecosystem.

gpt-oss 20B at Q4_K_M with native 128K context needs about 19.4 GB of VRAM with all experts resident. It's an MoE with 3.6B active parameters per token, 24 layers, an unusual hidden size of 2944, head_dim 64, and 128K native context. The 20B variant of OpenAI's first Apache 2.0 release is the smallest model in the family and is intentionally sized for laptops and consumer GPUs.

By TechCompare · Updated

Total VRAM required
19.4 GB
gpt-oss 20B (MoE) at Q4_K_M
Weights
11.2 GB
20B params
KV cache
6.4 GB
128K tokens, FP16 KV

Calculator

Estimated VRAM required

19.4 GB

20B params at Q4_K_M, 131,072 token context, batch 1, inference.

Weights
11.2 GB
KV cache
6.4 GB
Overhead
1.8 GB

Estimate accuracy: Weights within ~2%. KV cache within ~5% for standard GQA models, ~10% for MLA or hybrid state estimates. Real VRAM may vary with framework (vLLM vs llama.cpp vs Transformers), Flash Attention, and driver overhead.

Hardware that fits

Apple entries show installed unified memory separately from a model budget based on an 8 GB reserve. That budget is a planning heuristic, not a fixed hardware limit.

RTX 3090
Consumer
24 GB
81% used
RTX 5090
Consumer
32 GB
61% used
A100 40GB
Datacenter
40 GB
49% used
Apple M3 Max 64GB
Unified
~56 GB
35% of estimate

How this is calculated

11.2 GB of weights at Q4_K_M plus a 6.4 GB KV cache (at the full 128K context window) and ~1.8 GB overhead, for about 19.4 GB total.

Verdict

The total stacks to 19.4 GB resident at the full 128K context: 11.2 GB of Q4 weights plus 6.4 GB of FP16 KV cache and 1.8 GB of activation overhead. A 24 GB consumer card (RTX 3090/4090/5090) handles resident mode comfortably. Smaller cards can move expert weights to system RAM, but the host then has to hold them and every token gets slower. Apache 2.0 plus OpenAI lineage is the differentiator against Qwen3 30B-A3B at the same footprint, which is otherwise the stronger-raw-quality alternative.

More gpt-oss scenarios

MiMo-V2.6-Pro at Q4_K_M
Budget a 1.02T expert pool, hybrid attention, and a 1M text context.
View details ➜
MiMo-V2.6-Flash at Q4_K_M
309B total weights and separate global and sliding cache widths.
View details ➜
GLM-5.3-Flash at Q4_K_M
Model the 34 KDA layers, 11 sparse layers, and indexer storage.
View details ➜

Frequently asked questions

What does '3.6B active' actually mean for inference speed?
Per token, the model only computes through 3.6B parameters worth of expert weights even though all 20B must be reachable. That makes each token cheaper to compute than a dense 20B model, but it doesn't shrink memory, because the next token can pick different experts. If expert weights sit in system RAM instead of VRAM, every token gets slower.
Should I pick gpt-oss 20B or Qwen3 30B-A3B?
Qwen3 30B-A3B is generally stronger at the same active footprint (3B active vs 3.6B). gpt-oss has cleaner licensing and OpenAI lineage. Both fit on the same hardware - try whichever fits your stack first.
What GPU do I need to run gpt-oss 20B all-resident?
A GPU with at least 24 GB is the practical target for full resident mode at the 128K native context: 11.2 GB of weights plus 6.4 GB KV cache plus 1.8 GB overhead = roughly 19.4 GB. An RTX 4080 (16 GB) won't quite fit all-resident, while a 24 GB RTX 3090/4090 has useful headroom.
Does the 3.6B active count lower the VRAM math?
No. The 3.6B figure is what each token computes through, not what has to stay loaded. Different tokens pick different experts, so all 20B parameters need a place in fast memory for full speed. Moving expert weights to system RAM cuts VRAM, but the host then has to hold them and every token gets slower.