FitLLM

The best GPU or Mac to run gpt-oss-120b locally

❌ No listed GPU runs gpt-oss-120b at ~4-bit with 8K context

Computed with the open FitLLM engine — accurate per-layer KV-cache modeling, not a naive estimate. Updated 2026-07-10.

Ranked by memory size (a proxy for cost and availability), not price. Every figure is computed by the engine — these are a floor, not a guarantee; leave headroom for your runtime and OS.

Smallest GPU / Mac that fits, by setup

~4-bit ≈ Q4_K_M (GGUF, llama.cpp) on GPU / 4-bit (MLX) on Mac · ~8-bit ≈ Q8_0 / 8-bit · KV cache F16 · "full" = the model's max context (131K).

SetupSmallest GPUSmallest Mac
~4-bit · 8K ctx🔴M5 Max 128GB · 69.6/128 GB
~4-bit · full (131K)🔴M5 Max 128GB · 78.1/128 GB
~8-bit · 33K ctx🔴🔴
~8-bit · full (131K)🔴🔴

Every GPU and Mac, ranked by memory

HardwareMemoryMax context (~4-bit)Used @8K
RTX 3060 12GB12 GB❌ won't fit77.2 / 12 GB
RTX 4080 SUPER16 GB❌ won't fit77.2 / 16 GB
RTX 508016 GB❌ won't fit77.2 / 16 GB
RTX 309024 GB❌ won't fit77.2 / 24 GB
RTX 409024 GB❌ won't fit77.2 / 24 GB
RTX 509032 GB❌ won't fit77.2 / 32 GB
M5 Pro 48GB48 GB❌ won't fit69.6 / 48 GB
M5 Max 64GB64 GB❌ won't fit69.6 / 64 GB
M5 Max 128GB128 GB✅ up to 131K69.6 / 128 GB

Why bigger isn't always needed — and smaller sometimes won't fit

gpt-oss-120b interleaves sliding-window (local) and global attention 5:1. The local layers cap their KV cache at the 128-token window, and the global layers use a different head shape (head_dim 64 vs 64). A naive "all layers × full context × one head_dim" formula over-counts KV cache by several times. So gpt-oss-120b has no single fixed memory requirement — it shifts with quantization and context. See the full breakdown.

▶ Open the interactive calculator

All numbers are computed by the open-source fitllm-engine (MIT) from official model config.json values — reproduce or audit them yourself. Estimates; real usage varies with runtime (llama.cpp / MLX / Ollama), driver and display. Found a mismatch? Report it. · FitLLM home