Can I run GPT-OSS 120B?
GPT-OSS 120B by OpenAI needs around 96 GB of RAM at the recommended 4-bit quantization (70.8 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~113 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
GPT-OSS 120B is OpenAI's big open-weight release for people who want a frontier-style chat and reasoning model running entirely on their own hardware. It is a mixture-of-experts design, so even though the full model is 116.8B parameters, only about 5.1B are active per token. That is the trick that keeps it fast for its size, but do not let it fool you on memory: you still have to hold the whole thing in RAM. At a 4-bit quant that is roughly 71 GB, and you want around 96 GB of system memory to run it comfortably. This is not a laptop-GPU model.
In practice that means an RTX 3060 or even a 4090 simply will not fit it, so the realistic homes are a high-memory Apple Silicon machine or a big-RAM CPU box. On an M-series Max you can expect around 113 tokens per second, which feels genuinely snappy for a model this large. On CPU with DDR5 you drop to about 16 tokens per second, usable for batch work but slow for interactive chat. The 128K context window is generous, but filling it pushes total memory to roughly 127 GB at max context, so plan for headroom rather than treating that ceiling as your normal working size.
Against its peers, GPT-OSS 120B leans hard toward chat and reasoning rather than coding or vision, so something like Mistral Small 4 119B generally gives you more range if you need code or image input in the same footprint. Its own little sibling, GPT-OSS 20B, is the one to reach for when 96 GB of RAM is out of the question. The standout here is the license: Apache 2.0 means you can use it commercially and in production with no provider strings attached, which is rare at this capability tier and a real reason to pick it.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 48.9 GB | 64 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 70.8 GB | 96 GB | Recommended |
| Q5_K_M | 5.65 | 82.5 GB | 128 GB | High |
| Q8_0 | 8.5 | 124.1 GB | 192 GB | Near-original |
| F16 | 16 | 233.6 GB | 256 GB | Original |
Sizes are estimates from parameter count Γ bits per weight; real GGUF builds vary slightly. Β· Data updated: 2026-06-11 Β· How we calculate these numbers β
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~1.8 GB | ~72.6 GB |
| 8K tokens | ~3.5 GB | ~74.3 GB |
| 32K tokens | ~14.0 GB | ~84.8 GB |
| 128K tokens | ~56.1 GB | ~126.9 GB |
The KV cache grows with context length β a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | Won't fit in VRAM |
| Apple M-series (base) | 100 GB/s | ~27 tok/s |
| Apple M-series Pro | 270 GB/s | ~74 tok/s |
| Apple M-series Max | 410 GB/s | ~113 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~16 tok/s |
Token generation is memory-bandwidth bound: tok/s β bandwidth Γ 0.85 Γ· model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama β one command and you're chatting:
ollama run gpt-oss:120bSources & downloads