Launch

Launch pricing: up to 74% below on-demand, fixed for your term — ends Oct 31, 2026 · 17d left Launch pricing ends Oct 31 · 17d left

See pricing

OpenAI · 20.9B parameters · 3.6B active

gpt-oss-20b: GPU memory requirements and which GPU to rent

OpenAI's smaller open-weight model: 21 billion parameters with 3.6 billion active, shipped with its experts in MXFP4 — about 13 GB as released, so it runs on a single 24 GB GPU.

  • Weights at FP821 GB42 GB at 16-bit · 11 GB at 4-bit
  • FP8, 8k context, 1 sequence23 GBweights + KV cache + runtime
  • Suggested here1× RTX 5090$279 a month · dedicated

Inference

How much GPU memory gpt-oss-20b needs to serve

Total memory for one sequence at each context length, and for 16 concurrent sequences at 8k — weights, KV cache at 16-bit and runtime overhead included.

Weights precisionWeights4k context32k context128k context8k × 16 sequencesSuggested here, 8k
16-bit (BF16 / FP16) 42 GB 45 GB 46 GB 48 GB 48 GB 1× L40S · $429/mo
8-bit (FP8 / INT8) 21 GB 23 GB 24 GB 26 GB 27 GB 1× RTX 5090 · $279/mo
4-bit (GPTQ, AWQ, Q4) 11 GB 14 GB 14 GB 17 GB 17 GB 1× L4 · $169/mo

GB are 109 bytes. Context lengths are shown for scale where the model supports them; an FP8 KV cache halves the cache part of each figure. As a mixture of experts, every expert stays resident, so memory follows the total parameter count, not the active one. Released in MXFP4: about 13 GB of weights as shipped.

Hardware

GPU servers that run gpt-oss-20b

For FP8 inference with an 8k context and one sequence: the configurations we would suggest, in order — one large card ahead of several small ones.

Fine-tuning gpt-oss-20b

Memory for a 2k-token sequence and a micro-batch of 4, with gradient checkpointing. Full fine-tuning keeps gradients and Adam states for every parameter; LoRA and QLoRA train small adapters on a frozen base.

MethodMemorySuggested here
QLoRA, 4-bit base 17 GB 1× L4 · $169/mo
LoRA, 16-bit base 48 GB 1× A100 · $649/mo
Full fine-tune, mixed precision 340 GB 4× RTX PRO 6000 · $2,996/mo

Architecture at a glance

Parameters20.9B3.6B active per token
Layers24hidden size 2,880
KV cache0.03 GBper 1,000 tokens at 16-bit

Released in MXFP4: about 13 GB of weights as shipped. Figures from the model's published configuration; method on the calculator page.

gpt-oss-20b hardware: questions answered

How much VRAM does gpt-oss-20b need?

For the weights alone: about 42 GB at 16-bit, 21 GB at FP8 and 11 GB at 4-bit. Serving it at FP8 with an 8k-token context and one sequence takes about 23 GB in total once the KV cache and the runtime are counted; long contexts and many concurrent users add the KV cache on top — about 0.03 GB per 1,000 tokens at 16-bit.

Can gpt-oss-20b run on a single GPU?

Yes, at FP8 with a moderate context: one NVIDIA RTX 5090 (32 GB GDDR7) holds it, for $279 a month here. Longer contexts or more concurrent users may need a larger card or a second GPU.

What is the cheapest GPU setup to run gpt-oss-20b?

For FP8 inference with an 8k context and one sequence, the configuration we would suggest is 1× RTX 5090 · $279/mo; at 4-bit, 1× L4 · $169/mo. Suggestions favour one large card over several small ones: splitting a model across PCIe cards costs speed.

How much GPU memory do I need to fine-tune gpt-oss-20b?

With a 2k-token sequence and a micro-batch of 4: about 17 GB for QLoRA on a 4-bit base, 48 GB for LoRA on a 16-bit base, and 340 GB for a full fine-tune with Adam in mixed precision. Gradient checkpointing is assumed; sharding the optimizer across GPUs spreads the full fine-tune over several cards.

Run gpt-oss-20b on 1× RTX 5090 for $279 a month

Dedicated, single-tenant and live in under 10 minutes — with vLLM, the Hugging Face stack or Ollama preinstalled if you want. Paid in BTC, ETH or USDT, with no KYC.