gpt-oss 20B and 120B: VRAM, Ollama tags and hardware
gpt-oss:20b is a 13.8 GB download that fits a 16 GB graphics card; gpt-oss:120b is 65.4 GB and needs a single 80 GB GPU or a Mac with 96 GB or more of unified memory. Both are OpenAI's open-weight mixture-of-experts reasoning models from August 2025, released under Apache 2.0 with their expert weights already in 4-bit MXFP4.
Overview
gpt-oss is a pair of open-weight reasoning models from OpenAI, published with a model card on 5 August 2025 under the Apache 2.0 licence. Anyone can download, modify and deploy the weights, including commercially; the training data and code are not released.
The family is gpt-oss-120b (116.8B total parameters, 5.1B active per token, 36 layers) and gpt-oss-20b (20.9B total, 3.6B active, 24 layers). Both use a Mixture of Experts design, a 128K context and the same 201,088-token tokenizer, and both let you set the reasoning effort to low, medium or high in the system prompt.
gpt-oss-20b
- 21B total params, 3.6B active/token
- 13.8 GB on Ollama; fits a 16 GB GPU
- The practical local option
- MMLU 85.3, SWE-Bench Verified 60.7 (OpenAI card)
- 128K context window
gpt-oss-120b
- 117B total params, 5.1B active/token
- 65.4 GB on Ollama; one 80 GB GPU
- OpenAI: surpasses o3-mini, approaches o4-mini
- 97.9% on AIME 2025 with tools (competition math)
- 128K context window
MoE Architecture and MXFP4
gpt-oss uses a Mixture of Experts (MoE) Transformer. These are the details from OpenAI's model card and the released config.json files:
Technical Specifications
The MoE design means the model activates only a fraction of its parameters per token: gpt-oss-120b uses 5.1B of its 116.8B parameters, about 4.4%. Every expert still has to sit in memory, which is why the 120b needs 80 GB even though only a few billion parameters are active at a time. Because generation speed for MoE models depends on how experts are routed and placed, this page gives no tokens-per-second figure.
The other unusual choice is the format. OpenAI post-trained the expert weights, over 90% of the parameters, directly in MXFP4, a 4-bit floating-point format with shared scales. The released checkpoints are 60.8 GiB (120b) and 12.8 GiB (20b), already the size of a typical 4-bit quantisation, and OpenAI ran all its evaluations on these weights. In practice that means there is no larger “full-quality” build to download and little to gain from quantising further.
The alternating dense and banded attention follows GPT-3's approach: half the layers only look back 128 tokens, which keeps the KV cache small. Even counting every layer at full length, the cache is at most 49 KB per token for the 20b and 74 KB for the 120b, so the full 128K context adds at most 6.4 GB and 9.7 GB.
Benchmarks (gpt-oss-120b)
120B vs 20B Comparison
| Benchmark | gpt-oss-120b | gpt-oss-20b |
|---|---|---|
| MMLU | 90.0 | 85.3 |
| GPQA Diamond (no tools) | 80.1 | 71.5 |
| AIME 2025 (with tools) | 97.9 | 98.7 |
| SWE-bench Verified | 62.4 | 60.7 |
| Tau-Bench Retail (function calling) | 67.8 | 54.8 |
Note: 20b edges out 120b on AIME 2025 with tools (98.7 vs 97.9); without tools the order flips (92.5 vs 91.7). All figures at reasoning level high. Source: arXiv 2508.10925, Table 3.
Quick Start with Ollama
Ollama publishes two local tags: gpt-oss:20b (13.8 GB; gpt-oss and gpt-oss:latest point to the same file) and gpt-oss:120b (65.4 GB). Both are the MXFP4 weights; there are no Q4_K_M, Q8_0 or fp16 tags. The -cloud variants run on Ollama's servers, not your machine.
Use via OpenAI-Compatible API
Ollama exposes a Chat Completions API compatible with the OpenAI SDK:
from openai import OpenAI
client = OpenAI(
base_url="http://localhost:11434/v1",
api_key="ollama" # required but unused
)
response = client.chat.completions.create(
model="gpt-oss:20b",
messages=[
{"role": "system", "content": "Reasoning: medium"},
{"role": "user", "content": "Explain MoE architectures"}
]
)
print(response.choices[0].message.content)Use with Open WebUI
For a ChatGPT-like interface, pair gpt-oss with Open WebUI:
# Start Ollama with gpt-oss ollama serve & ollama pull gpt-oss:20b # Launch Open WebUI docker run -d -p 3000:8080 \ --add-host=host.docker.internal:host-gateway \ -e OLLAMA_BASE_URL=http://host.docker.internal:11434 \ ghcr.io/open-webui/open-webui:main
Hardware Requirements
gpt-oss-20b needs about 15 GB with an 8K context (13.8 GB file + up to 0.4 GB of KV cache + ~1 GB of buffers); gpt-oss-120b needs about 67 GB (65.4 GB + up to 0.6 GB + ~1 GB). The table shows what that means for common GPUs and unified-memory machines. It is arithmetic from the file sizes, not a measurement.
| Hardware | gpt-oss-20b (13.8 GB) | gpt-oss-120b (65.4 GB) |
|---|---|---|
| 12 GB GPU (RTX 3060 12GB, RTX 4070) | Partial CPU offload only | No |
| 16 GB GPU (RTX 4060 Ti 16GB, 4080, 5070 Ti, 5080) | Yes, ~15 GB at 8K; 32K is tight | No |
| 24 GB GPU (RTX 3090, 4090) | Yes, full 128K context (~21 GB) | No |
| 32 GB GPU (RTX 5090) | Yes, with room to spare | No (partial CPU offload only) |
| 2x 24 GB GPUs (48 GB) | Yes | No, 65.4 GB does not fit 48 GB |
| 80 GB GPU (H100, A100 80GB) | Yes | Yes, ~67 GB at 8K; full 128K under 80 GB |
| Mac, 16 GB unified memory | Borderline: macOS reserves part of RAM for the system | No |
| Mac or mini-PC, 32-64 GB unified memory | Yes | No |
| Mac or mini-PC, 96-128 GB unified memory | Yes | Yes |
gpt-oss-20b
gpt-oss-120b
Download Options (20B and 120B)
| Build | Size | Format | Runs in |
|---|---|---|---|
| gpt-oss:20b | 13.8 GB | MXFP4 (native) | Ollama |
| gpt-oss-20b-MXFP4.gguf | 12.1 GB | MXFP4 GGUF | llama.cpp, LM Studio |
| gpt-oss:120b | 65.4 GB | MXFP4 (native) | Ollama |
| gpt-oss-120b-MXFP4.gguf | 63.4 GB | MXFP4 GGUF | llama.cpp, LM Studio |
GGUF sizes from the ggml-org/gpt-oss-20b-GGUF and gpt-oss-120b-GGUF repositories. Because the experts are already 4-bit, these are the full-quality builds. See our quantization guide for what the formats mean.
vs Other Models
All of these are open-weight and locally runnable on the right hardware. Scores are each developer's own and come from different setups, so treat them as rough positioning.
| Model | Parameters | Ollama download | What holds it | Published score | Licence |
|---|---|---|---|---|---|
| gpt-oss-120b | 117B total, 5.1B active (MoE) | 65.4 GB (gpt-oss:120b) | One 80 GB GPU, or 96 GB+ unified memory | MMLU 90.0 (OpenAI card) | Apache 2.0 |
| gpt-oss-20b | 21B total, 3.6B active (MoE) | 13.8 GB (gpt-oss:20b) | One 16 GB GPU | MMLU 85.3 (OpenAI card) | Apache 2.0 |
| Llama 3.3 70B | 70B dense | 42.5 GB (llama3.3:70b) | Two 24 GB GPUs or a 64 GB Mac | MMLU 86.0, 0-shot CoT (Meta card) | Llama 3.3 Community |
| DeepSeek V3 | 671B total, 37B active (MoE) | 404.4 GB (deepseek-v3) | Multi-GPU server or 512 GB unified memory | MMLU 88.5 (DeepSeek card) | MIT code, DeepSeek model licence |
| Qwen 2.5 72B | 72B dense | 47.4 GB (qwen2.5:72b) | More than 48 GB, or a 64 GB Mac | MMLU-Pro 71.1 (Qwen blog) | Qwen licence |
When to Choose gpt-oss
Best Use Cases
Local AI Development
The 20b runs on a 16 GB GPU and Ollama exposes it through an OpenAI-compatible API, so code written against it moves to a hosted API with a base-URL change.
Competition Math & Reasoning
97.9 on AIME 2025 with tools (92.5 without) at the high reasoning level, per OpenAI. Raise the reasoning level for multi-step problems and lower it for quick answers.
Agentic Workflows
OpenAI trained both models for function calling, browsing and Python tool use (Tau-Bench Retail 67.8 for the 120b). That suits local AI agent frameworks like CrewAI and LangGraph running fully offline.
Code Generation
SWE-bench Verified 62.4 (120b) and 60.7 (20b) in OpenAI's card. Pair it with Continue.dev for a free, private coding assistant.
Privacy-Sensitive Applications
Apache 2.0 license + local execution means zero data leaves your machine, which helps when compliance rules keep data on-premises.
Edge & Workstations
The 20b is the smallest gpt-oss: 13.8 GB, so it suits laptops and desktops with 16 GB GPUs or 24 GB+ of unified memory. It is too large for phones.
Advanced Setup
Custom Modelfile
# gpt-oss Modelfile for Ollama FROM gpt-oss:20b # 32K context adds at most ~1.6 GB of KV cache on the 20b PARAMETER num_ctx 32768 # Reasoning effort is set in the system prompt SYSTEM """Reasoning: high You are an expert software engineer. Write clean, well-documented code. When you're unsure, say so rather than guessing."""
# Build and run the custom model ollama create my-gpt-oss -f Modelfile ollama run my-gpt-oss
Running the 120B
gpt-oss-120b is built to fit one 80 GB GPU. On a machine with less VRAM, Ollama will place what it can on the GPU and the rest in system RAM, which works but is much slower. Check the split with ollama ps:
ollama run gpt-oss:120b # in another terminal: PROCESSOR should read 100% GPU ollama ps
With Agents SDK
gpt-oss supports tool calling, making it compatible with the OpenAI Agents SDK:
from agents import Agent, Runner, OpenAIChatCompletionsModel
from openai import AsyncOpenAI
client = AsyncOpenAI(
base_url="http://localhost:11434/v1",
api_key="ollama"
)
agent = Agent(
name="local-agent",
model=OpenAIChatCompletionsModel(model="gpt-oss:20b", openai_client=client),
instructions="You are a helpful research assistant."
)
result = Runner.run_sync(agent, "Summarize the key points of MoE models")
print(result.final_output)Sources
- gpt-oss-120b & gpt-oss-20b Model Card (arXiv 2508.10925) — Architecture, parameter counts, MXFP4, benchmark tables
- OpenAI: Introducing gpt-oss — Official announcement
- Hugging Face: openai/gpt-oss-120b and openai/gpt-oss-20b — Weights, config and hardware notes
- GitHub: openai/gpt-oss — Official repository
- Ollama: gpt-oss tags — Download sizes (read from the registry on 2 November 2026)
Frequently Asked Questions
How much VRAM does gpt-oss-20b need?
The Ollama build (gpt-oss:20b) is a 13.8 GB file. With an 8K context and about 1 GB of buffers it needs roughly 15 GB, so it fits a 16 GB graphics card, and a 24 GB card holds it with the full 128K context (at most 6.4 GB of KV cache). OpenAI's own wording is that it runs "on systems with as little as 16GB memory". A 12 GB card runs it only with part of the model in system RAM.
How much VRAM does gpt-oss-120b need?
The Ollama build (gpt-oss:120b) is 65.4 GB. OpenAI designed it to fit a single 80 GB GPU such as an NVIDIA H100 or AMD MI300X, and with at most 9.7 GB of KV cache even the full 128K context stays under 80 GB. Two 24 GB consumer cards (48 GB) cannot hold it; Macs and mini-PCs with 96 GB or 128 GB of unified memory can.
What are the gpt-oss Ollama tags?
gpt-oss:20b (13.8 GB; also gpt-oss and gpt-oss:latest) and gpt-oss:120b (65.4 GB). Both are the MXFP4 weights OpenAI released; there are no Q4_K_M, Q8_0 or fp16 tags. gpt-oss:20b-cloud and gpt-oss:120b-cloud also exist, but those run on Ollama's servers rather than your machine.
What is MXFP4 and why does it matter?
MXFP4 is a 4-bit floating-point format with shared scales. OpenAI post-trained the mixture-of-experts weights, which are over 90% of the parameters, directly in MXFP4 at 4.25 bits per parameter. That is why the release is already as small as a typical 4-bit quantisation, and why quantising it further saves very little.
Is gpt-oss open source?
The weights are released under Apache 2.0, a permissive licence that allows commercial use, modification and redistribution. The training data and training code are not released, so "open-weight" is the more precise term, and it is the one OpenAI uses.
How does gpt-oss compare with Llama 3.3 70B?
They are different shapes. gpt-oss-120b is a 117B mixture-of-experts model with 5.1B active parameters per token, a 65.4 GB download; Llama 3.3 70B is a dense 70B, a 42.5 GB download. OpenAI reports MMLU 90.0 for gpt-oss-120b and Meta reports 86.0 for Llama 3.3 70B, from different evaluation setups. The practical difference is hardware: Llama 3.3 70B fits two 24 GB cards, gpt-oss-120b does not, while gpt-oss-20b fits a single 16 GB card.
Does gpt-oss support images?
No. The model card describes a text-only training set, and both models take and produce text only.
How do I change the reasoning level?
Put "Reasoning: low", "Reasoning: medium" or "Reasoning: high" in the system prompt. Higher levels produce longer chains of thought and score higher on OpenAI's benchmarks; the scores on this page are at the high level.
Build Real AI on Your Machine
RAG, agents, NLP, vision, and MLOps - chapters across 25 courses that take you from reading about AI to building AI.
Related Guides
Continue your local AI journey with these comprehensive guides
Go from reading about AI to building with AI
25 structured courses. Hands-on projects. Runs on your machine. Start free.

Written by
Barsha Mohapatra
Founder and Editor, Local AI Master · Founder, Little AI Master
Founder of Little AI Master and the editor behind every course and guide on Local AI Master. Years of tutoring students taught her where AI education actually fails.
- PILLARLocal AI Models Directory: Every Model Compared
- DeepSeek V4 Local Setup: 1M Context, MIT (2026)
- models/llama-3-1-8b
- models/deepseek-coder-v2-236b
- MiniMax M3: Open-Weight 1M-Context Frontier Model (2026)
- ShieldGemma 2B: Local Safety Classifier for Content Moderation
- models/llama-3-3-70b
- Phi-3 Mini 3.8B: 69% MMLU on 8GB RAM (Microsoft SLM)
- models/kimi-k3
- models/gemma-2-9b
Grab the AI Starter Kit — career roadmap, cheat sheet, setup guide
No spam. Unsubscribe with one click.
Found your model? Now build something with it.
25 hands-on courses — RAG, agents, fine-tuning — all running locally. First chapter free, no card.