Mage-VL-Cowork 4.7B on Raspberry Pi 5 (16 GB)

Can the Raspberry Pi 5 (16 GB) run Mage-VL-Cowork 4.7B?

Yes, but slowly

Slow. At Q5_K_M it needs about 6.3 GB of 13.6 GB usable, with an estimated speed of 3.0 tok/s.

Best quant: Q5_K_M
Generation speed: 3.0 tok/s
Prompt processing: 19.0 tok/s
First token (1K prompt): 53.9 s
Largest safe context: 32K

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

On Linux on ARM boards

Docker Model Runner

Command line + local API · runs on llama.cpp, vLLM

Handy if you already work in Docker.

docker model run hf.co/microsoft/Mage-VL-Cowork

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 Mage-VL-Cowork 4.7B

Original weights · Hugging Face

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

huggingface.co/microsoft/Mage-VL-Cowork (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/microsoft/Mage (opens in a new tab)

Microsoft’s Mage repo; the mage_vl_cowork folder has the agent harness and evaluation code.

git clone https://github.com/microsoft/Mage

Links checked 5 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 58Good quality (B) · 58 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q5_K_M, 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 Slow: How well it runs on the Raspberry Pi 5 (16 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.	26.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.	4.1 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	10.6 / 15
Match score	66.0 / 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 (16 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	4.8 GB	13.6 GB	6.1 tok/s	Slow	42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q3_K_M`	5.2 GB	13.6 GB	4.8 tok/s	Slow	50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q4_K_M`	5.8 GB	13.6 GB	3.7 tok/s	Slow	57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q5_K_M`	6.3 GB	13.6 GB	3.0 tok/s	Slow	58Good quality (B) · 58 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q6_K`	6.8 GB	13.6 GB	2.6 tok/s	Very slow	59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q8_0`	7.9 GB	13.6 GB	1.9 tok/s	Very slow	60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`F16`	12.4 GB	13.6 GB	0.9 tok/s	Very slowtight fit	60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

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

Other hardware that runs it

60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER F16 · 40.8 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER F16 · 44.7 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti F16 · 54.4 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 F16 · 58.3 tok/s · Runs great
59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 Q6_K · 48.9 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 Q8_0 · 45.9 tok/s · Runs great

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.