on

Can the Raspberry Pi 5 (4 GB) run StableLM 2 Zephyr 1.6B?

7Basic quality (D) · 7 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well

Runs well. At Q2_K it needs about 2.3 GB of 2.8 GB usable, with an estimated speed of 17.5 tok/s.

Best quant
Q2_K
Generation speed
17.5 tok/s
Prompt processing
54.9 tok/s
First token (1K prompt)
18.7 s
Largest safe context
4K

Best app to run it on the Raspberry Pi 5 (4 GB)

On Linux on ARM boards

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

  • One command with Ollama’s own build of this model.
  • Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run stablelm2:1.6b-zephyr-q2_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • llama.cpp Usually the first to support new model architectures.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download StableLM 2 Zephyr 1.6B

Recommended for the Raspberry Pi 5 (4 GB): Q2_K. 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 stablelm2:1.6b-zephyr-q2_K

Quantized files · GGUF

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

huggingface.co/stabilityai/stablelm-2-zephyr-1_6b (opens in a new tab)

ollama run hf.co/stabilityai/stablelm-2-zephyr-1_6b

Original weights · Hugging Face

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

huggingface.co/stabilityai/stablelm-2-zephyr-1_6b (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 7Basic quality (D) · 7 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_K, 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 Runs well
How well it runs on the Raspberry Pi 5 (4 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.3.2 / 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.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.9.9 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score53.1 / 100

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

Every quantization on the Raspberry Pi 5 (4 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 2.3 GB 2.8 GB 17.5 tok/s Runs well 7Basic quality (D) · 7 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking.
Q3_K_M 2.4 GB 2.8 GB 13.8 tok/s Runs welltight fit 8Basic quality (D) · 8 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking.
Q4_K_M 2.6 GB 2.8 GB 10.7 tok/s Runs welltight fit 9Basic quality (D) · 9 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q4_0) (opens in a new tab)
Q5_K_M 2.8 GB 2.8 GB 8.8 tok/s Slowtight fit 9Basic quality (D) · 9 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 3.0 GB 2.8 GB 6.3 tok/s Slowover memory limit 9Basic quality (D) · 9 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 35/100 (quality, fit, speed and memory use) sets the ranking.
Q8_0 3.4 GB 2.8 GB 4.6 tok/s Slowfar over memory limit 10Basic quality (D) · 10 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 28/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 4.9 GB 2.8 GB — Won't run 10Basic quality (D) · 10 of 100: how capable the model is at F16, whatever it runs on. Match score 1/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

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

Other hardware that runs it

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?