MiniMax H3 (33B, video + audio) on Raspberry Pi 5 (4 GB)

Can the Raspberry Pi 5 (4 GB) run MiniMax H3 (33B, video + audio)?

No, it doesn’t fit

No. MiniMax H3 (33B, video + audio) needs about 19.6 GB even at Q4 GGUF; the Raspberry Pi 5 (4 GB) has 2.8 GB usable.

Download MiniMax H3 (33B, video + audio)

Recommended: q4_gguf. Every other precision has its own download link in the table below.

Quantized files · GGUF for ComfyUI

Smaller GGUF versions for ComfyUI (with the ComfyUI-GGUF node). No sign-in needed; the model’s license still applies.

Download the q4_gguf (Q4_K_M) file (opens in a new tab)

huggingface.co/unsloth/MiniMax-H3-GGUF (opens in a new tab)

Original weights · Hugging Face

Full-precision files from MiniMax, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/MiniMaxAI/MiniMax-H3 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/MiniMax-AI/MiniMax-H3 (opens in a new tab)

git clone https://github.com/MiniMax-AI/MiniMax-H3

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

How it’s rated

Quality 83Great quality (A) · 83 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4 GGUF, 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 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.	11.3 / 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 score	11.3 / 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 precision on the Raspberry Pi 5 (4 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	29.5 GB	2.8 GB	—	—	Won't run	90Excellent quality (A+) · 90 of 100: how capable the model is at FP16, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	22.4 GB	2.8 GB	—	—	Won't run	88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q8 GGUF`	22.9 GB	2.8 GB	—	—	Won't run	89Excellent quality (A+) · 89 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	19.6 GB	2.8 GB	—	—	Won't run	83Great quality (A) · 83 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)

Hardware that can run it

88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP8 · 11.4 min · Runs well
90Excellent quality (A+) · 90 of 100: how capable the model is at FP16, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA B200 FP16 · 10.6 min · Runs well
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GH200 Grace Hopper (96 GB GPU) FP8 · 10.9 min · Runs well
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 80GB SXM FP8 · 10.9 min · Runs well
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H800 80GB SXM FP8 · 10.9 min · Runs well
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 NVL FP8 · 11.8 min · Runs well

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

35Basic quality (D) · 35 of 100: how capable the model is at FP16, whatever it runs on. Match score 43/100 (quality, fit, speed and memory use) sets the ranking. AnimateDiff v3 (SD 1.5) FP16 · 78.8 min

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.