How much VRAM does GPT OSS 20B need?
GPT OSS · 21B params MoE · updated 2026-08-25
Headline answer
At bf16, reference 8K context, batch size 1: 46.3GB of VRAM. The smallest fitting configuration is 1× H100 PCIe 80GB.
VRAM by quantization
| Dtype | VRAM | Fits on |
|---|---|---|
| bf16 | 46.3GB | 1× H100 PCIe 80GB |
| fp8 | 25.7GB | 1× RTX 5000 Ada 32GB |
| awq | 16.9GB | 1× L4 24GB |
| nvfp4 | 17.8GB | 1× L4 24GB |
Context length sensitivity
Same model, same bf16 dtype, batch size 1 — VRAM at longer context windows.
| Context | VRAM (bf16) |
|---|---|
| 8K | 46.3GB |
| 32K | 46.9GB |
| 128K | 49.3GB |
Model facts
About GPT OSS 20B
Running a GPT OSS 20B in bf16 at a reference 8K context and batch size 1 takes 46.3GB of VRAM — a number our calculator derives from the model's published architecture (layer count, hidden size, attention heads), not a rough rule of thumb. GPT OSS 20B is a GPT OSS model with 21B total parameters, with only 3.6B active per token via mixture-of-experts routing, and at this batch size that VRAM figure is dominated by the weights themselves, with KV cache and framework overhead adding a smaller but still meaningful slice on top. Which GPU you actually need depends heavily on quantization: bf16 is the reference precision with no quality loss, but fp8 roughly halves the weight footprint, AWQ (weight-only int4) goes further still, and — on Blackwell hardware — NVFP4 offers a similar 4-bit footprint with hardware-native throughput. At bf16, the smallest configuration that fits this model is 1× H100 PCIe 80GB; the dtype table above shows exactly how that changes as you quantize down, including whether a smaller or cheaper GPU becomes viable. Context length is the other lever: KV cache grows roughly linearly with how many tokens you keep resident, so a deployment serving long documents or long conversations needs meaningfully more headroom than this 8K reference number suggests — see the context-sensitivity table for how VRAM scales at 32K and 128K where this model's native context allows it. If you're sizing a real deployment rather than just checking whether a model fits, feed these same architecture numbers into the full calculator to model your actual concurrency and serving framework.
Frequently asked questions
How much VRAM does GPT OSS 20B need?
At bf16, reference 8K context and batch size 1, GPT OSS 20B needs 46.3GB of VRAM. The smallest fitting configuration we find is 1× H100 PCIe 80GB.
How many parameters does GPT OSS 20B have?
GPT OSS 20B has 21B total parameters, with 3.6B active per token via mixture-of-experts routing.
Does quantization reduce GPT OSS 20B's VRAM requirement?
Yes — switching from bf16 to fp8 brings the total down to 25.7GB, and weight-only int4 formats (AWQ, NVFP4) go further still. See the per-dtype table above for exact numbers.
Where do these VRAM numbers come from?
They're computed by the same calculator engine behind our interactive GPU calculator, from the model's published architecture (layers, hidden size, attention heads, KV cache config) — not a generic per-parameter estimate.
Methodology: VRAM figures are computed by the same calculator engine behind our interactive GPU calculator, from GPT OSS 20B's published architecture (layer count, hidden size, attention heads, KV cache configuration) — not a generic per-parameter estimate. Reference scenario: batch size 1, vLLM framework, fp16 KV cache. Page last updated 2026-08-25. These are engineering estimates, not a guarantee — always validate against your actual serving framework and workload before committing to hardware.
Size a full deployment — concurrency, framework, quantization — in the calculator →