How to Deploy gpt-oss 120B Locally
gpt-oss 120B is OpenAI's large open-weight MoE, with 116.8B parameters but only 5.1B used per token, so it runs fast on machines with lots of memory. At 4-bit with 8K it takes about 64 GB, so a 128GB machine holds it entirely, at about 52 to 54 tokens/s; with just one ordinary graphics card, it still runs if you keep the experts in system RAM. OpenAI says a single 80GB H100 is enough.
gpt-oss 120B details
- Min VRAM at 4-bit65 GB · 8K
- Parameters116.8B
- Active params5.1B
- Max context128K
- Architecture
- MoE
- Experts offloaded
- 4 GB VRAM + 62 GB RAM
- License
- Apache-2.0
- Launch date
- Aug 5, 2025
- Vendor
- OpenAI
- Hugging Face repo
- openai/gpt-oss-120b
- GGUF repo
- unsloth/gpt-oss-120b-GGUF
- MLX repo (Apple)
- mlx-community/gpt-oss-120b-MXFP4-Q8
- Ollama tag
- gpt-oss:120b
- Layers
- 36
- Hidden size
- 2,880
- KV heads
- 8
- Head dim
- 64
How much VRAM does gpt-oss 120B need for local deployment?
| Quantization | WeightsGB | 8K contextGB | 32K contextGB | 128K context (max)GB |
|---|---|---|---|---|
| 1-bit | 29.4est. | 30.8 | 31.7 | 35.4 |
| 2-bit | 46.6est. | 48 | 48.9 | 52.5 |
| 3-bit | 62.6GGUF | 64 | 64.9 | 68.5 |
| 4-bit | 62.8GGUF | 64.2 | 65.1 | 68.7 |
| 5-bit | 62.9GGUF | 64.3 | 65.2 | 68.8 |
| 8-bit | 63.4GGUF | 64.8 | 65.7 | 69.3 |
| BF16/FP16 | 65.4GGUF | 66.8 | 67.7 | 71.3 |
Full calculation rules are on the Methodology page.
Can a single GPU run gpt-oss 120B?
No consumer GPU can; it takes a workstation or data center card, or a big unified-memory machine. The RTX PRO 6000 holds 4-bit with the full context window to spare, at about 147 tokens/s, and the 80GB A100 and 72GB RTX PRO 5000 fit it too. Don't count on a smaller quant to squeeze it onto a lesser card: the model ships in a 4-bit format, so files from 2-bit to 8-bit are nearly the same size, and the 48GB RTX A6000 still can't fit it. Among all-in-one machines, the 96GB Mac Studio M5 Ultra does about 129 tokens/s and the 128GB DGX Spark about 54, because with only about 5B parameters used per token, there's little data to read and modest bandwidth goes a long way.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 63.2 | 128K |
| Instinct MI21064 GB | $4,99411 listings | 155.3 | 128K |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 142.5 | 128K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 107 | 128K |
| $8,24022 listings | 66 | 128K | |
| $10,7223 listings | 146.6 | 128K | |
| $18,99912 listings | 162 | 128K | |
| $22,50011 listings | 159 | 128K | |
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 122.2 | 128K |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 51.5 | 128K |
| Instinct MI21064 GB | $4,99411 listings | 142.8 | 128K |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 128.7 | 128K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 92.2 | 128K |
| $8,24022 listings | 54 | 128K | |
| $10,7223 listings | 133.2 | 128K | |
| $18,99912 listings | 150.4 | 128K | |
| $22,50011 listings | 147 | 128K | |
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 107.5 | 128K |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 51.1 | 128K |
| Instinct MI21064 GB | $4,99411 listings | 142.4 | 112K |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 128.2 | 128K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 91.7 | 128K |
| $8,24022 listings | 53.6 | 128K | |
| $10,7223 listings | 132.8 | 128K | |
| $18,99912 listings | 150 | 128K | |
| $22,50011 listings | 146.5 | 128K | |
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 107 | 128K |
Only common GPUs and systems are listed, one set for models under 50B and another for larger ones, sorted by price from low to high.
How many GPUs do you need to run gpt-oss 120B?
A pair of 48GB RTX A6000 cards is all it takes, running 4-bit at about 97 tokens/s. 24GB cards need four: the model plus 32K of context comes to about 65 GB, more than two of them can hold, and four RTX 3090s do about 107 tokens/s. The 32GB RTX 5090 also starts at four. Dropping to 2-bit won't save a card, since every quant is about the same size. One caveat: vLLM's gpt-oss recipe currently lists data center parts such as the H100, B200 and MI300, with support for GeForce cards and the A6000 still in progress. On those cards, splitting the layers across GPUs with llama.cpp is the safer route.
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 2 cards | $1,790 | 64 GB | 117.5 | 500 W | |
| 2 cards | $3,700 | 64 GB | 96.7 | 460 W | |
| Radeon RX 7900 XTX24 GB per card | 4 cards | $5,000 | 96 GB | 120.9 | 1,420 W |
| 4 cards | $7,196 | 96 GB | 119.6 | 1,400 W | |
| 2 cards | $9,798 | 96 GB | 109.1 | 600 W | |
| 4 cards | $15,032 | 96 GB | 123.4 | 1,800 W | |
| 2 cards | $16,790 | 64 GB | 151.2 | 1,150 W | |
| 2 cards | No price | 96 GB | 123.4 | 900 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 cards | $3,580 | 128 GB | 104.9 | 1,000 W | |
| Radeon RX 7900 XTX24 GB per card | 4 cards | $5,000 | 96 GB | 108.3 | 1,420 W |
| 4 cards | $7,196 | 96 GB | 107 | 1,400 W | |
| 4 cards | $7,400 | 128 GB | 84.4 | 920 W | |
| 2 cards | $9,798 | 96 GB | 96.5 | 600 W | |
| Instinct MI21064 GB per card | 2 cards | $9,988 | 128 GB | 136 | 600 W |
| 4 cards | $15,032 | 96 GB | 110.9 | 1,800 W | |
| 4 cards | $33,580 | 128 GB | 140.3 | 2,300 W | |
| 2 cards | No price | 96 GB | 110.9 | 900 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 cards | $3,580 | 128 GB | 104.5 | 1,000 W | |
| Radeon RX 7900 XTX24 GB per card | 4 cards | $5,000 | 96 GB | 107.9 | 1,420 W |
| 4 cards | $7,196 | 96 GB | 106.6 | 1,400 W | |
| 4 cards | $7,400 | 128 GB | 84 | 920 W | |
| 2 cards | $9,798 | 96 GB | 96.1 | 600 W | |
| Instinct MI21064 GB per card | 2 cards | $9,988 | 128 GB | 135.6 | 600 W |
| 4 cards | $15,032 | 96 GB | 110.5 | 1,800 W | |
| 4 cards | $33,580 | 128 GB | 139.9 | 2,300 W | |
| 2 cards | No price | 96 GB | 110.5 | 900 W |
Full calculation rules are on the Methodology page.
What PC or server build do you need to run gpt-oss 120B locally?
This model uses only 5.1B parameters per token, so very little expert data has to be read from system RAM, which makes expert offloading its most practical way to run. At 4-bit, a 16GB Tesla V100 with a dual-channel DDR5 desktop does about 36 tokens/s, and with DDR4 about 21; a used 8-channel DDR4 server with an RTX 3090 does about 59. In llama.cpp, --cpu-moe puts all the experts in system RAM, while --n-cpu-moe N moves only the first N layers; if you have VRAM to spare, lower N for more speed.
Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Single EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
FlagshipGeForce RTX 5070 + Desktop DDR5
Home PCTesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Single EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
Flagship2 × GeForce RTX 5070 + Desktop DDR5
Home PCTesla V100 32GB + Dual Xeon E5 DDR4
Budget2 × GeForce RTX 3090 + Single EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
FlagshipDetailed calculation rules are on the Methodology page.
As an eBay Partner, VRAMGlass may be compensated if you buy through the eBay links on this page. The price you pay stays the same.
What to know before running gpt-oss 120B locally
Just use the original precision
Its experts already come in a 4-bit format (MXFP4), so every GGUF quant is almost the same size; even the FP16 one is only about 65 GB, the same as the original. There's no point stepping down a level to save two or three GB. Unsloth recommends at least 66 GB of VRAM and RAM combined to get above 6 tokens per second.
Weaker in Chinese, strong at code and reasoning
Qwen used gpt-oss 120B as a comparison point on the Qwen3.5 9B model card. On the Chinese benchmark C-Eval it scores only 76.2, below the 9B Qwen3.5 (88.2), but on the coding benchmark LiveCodeBench v6 it scores 82.7, the highest in that comparison table. If your use is mainly in Chinese, test it on your own tasks before deploying.
Reasoning effort and tools
Like the 20B, it has three levels, low, medium and high, set in the system prompt (for example “Reasoning: high”). It was trained with browser and Python tool calling, and adding
--tool-call-parser openai--enable-auto-tool-choicein vLLM hooks up function calling. Sampling parameters are the same as for the 20B:temperature1.0 andtop_p1.0.If it fits, run the full 128K
The full 128K takes only about 4.5 GB more than 8K (68.7 vs. 64.2 GB at 4-bit), so any device that holds it can go straight to 128K, with no trade-off between quantization and context. The reason is that half its layers only look at the most recent 128 tokens, and their cache doesn't grow with context.
Launch commands
Ollama
- Windows
- macOS
- Linux
ollama run gpt-oss:120bllama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/gpt-oss-120b-GGUF:Q4_K_M -c 8192Short on VRAM? Add --cpu-moe to keep the routed experts in system RAM (about 62 GB needed).
llama-server -hf unsloth/gpt-oss-120b-GGUF:Q4_K_M -c 8192 -ngl 99 \ --cpu-moe
vLLM
- Linux
- NVIDIA
- AMD
vllm serve openai/gpt-oss-120bMLX
- Apple Silicon
On a Mac, pip install mlx-lm first; this command downloads the MLX weights from Hugging Face and starts an OpenAI-compatible server.
mlx_lm.server --model mlx-community/gpt-oss-120b-MXFP4-Q8File names follow that week's model-library snapshot; the definitions are in the methodology. Methodology
Other models in the gpt-oss family
| Model | Total params | Active params | 4-bit size |
|---|---|---|---|
| gpt-oss 20BMoE | 20.9B | 3.6B | 11.6 GB |
| gpt-oss Safeguard 20BMoE | 20.9B | 3.6B | 11.6 GB |