on

Can the Raspberry Pi 4 (2 GB) run gpt-oss 20B?

70Great quality (A) · 70 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.

No, it doesn’t fit

No. gpt-oss 20B needs about 12.8 GB even at MXFP4; the Raspberry Pi 4 (2 GB) has 1.2 GB usable.

Download gpt-oss 20B

Recommended: MXFP4. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run gpt-oss:20b

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the MXFP4 file (opens in a new tab)

huggingface.co/ggml-org/gpt-oss-20b-GGUF (opens in a new tab)

ollama run hf.co/ggml-org/gpt-oss-20b-GGUF:MXFP4

Original weights · Hugging Face

Full-precision files from OpenAI, for fine-tuning, vLLM, Transformers.

huggingface.co/openai/gpt-oss-20b (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from OpenAI. The weights themselves download from Hugging Face.

github.com/openai/gpt-oss (opens in a new tab)

git clone https://github.com/openai/gpt-oss

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 70Great quality (A) · 70 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at MXFP4, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Won't run
How well it runs on the Raspberry Pi 4 (2 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.9.5 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.0.0 / 15
Match score9.5 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every quantization on the Raspberry Pi 4 (2 GB)

Quant Memory needed Available Speed Runs Quality Download
MXFP4 12.8 GB 1.2 GB — Won't run 70Great quality (A) · 70 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)
F16 42.7 GB 1.2 GB — Won't run 70Great quality (A) · 70 of 100: how capable the model is at F16, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Hardware that can run it

Models that do run on the Raspberry Pi 4 (2 GB)

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?