Every open model in our directory, ranked by how well it runs on Apple M5 (32GB) at 4-bit. Grades weigh whether the model fits in memory and how fast it should run.
Apple M5 has 32 GB of VRAM, enough to run 230 of the 297 open models we track at 4-bit. The largest that still fits well is minimax-m2.5 (230B), and the top-rated is Holo4-35B-A3B at about 53 tok/s.
230 of 297 models run comfortably on Apple M5.
See full Apple M5 specs and pricingThe top models this device can run at 4-bit, ranked by fit and speed.
| Model | Grade | Speed | VRAM |
|---|---|---|---|
| Holo4-35B-A3BHcompany | SS | 52.9 tok/s | 2.3 GB |
| Mellum2.1JetBrains | AA | 60.9 tok/s | 2.0 GB |
| LFM2.5-8B-A1BLiquid AI | AA | 42.5 tok/s | 2.9 GB |
| Qwen3-30B-A3BAlibaba | AA | 23.0 tok/s | 5.4 GB |
| Gemma 4 E2B ITGoogle | AA | 33.3 tok/s | 3.7 GB |
| Apertus 8BEPFL, ETH Zurich, CSCS | BB | 22.9 tok/s | 5.4 GB |
| AliceAI-Foundation-80B-A3B-Baseyandex | BB | 14.5 tok/s | 8.5 GB |
| BolmoAi2 | BB | 247.3 tok/s | 0.5 GB |
| VibeThinker-3BWeiboAI | BB | 32.4 tok/s | 3.8 GB |
| Llama 3 8B InstructMeta | BB | 21.8 tok/s | 5.7 GB |
| Mixtral 8x7B InstructMistral AI | BB | 10.9 tok/s | 11.4 GB |
| North Mini CodeCohere | BB | 14.7 tok/s | 8.4 GB |
Holo4-35B-A3BHcompany | 35B(3B active) | SS | 52.9 tok/s | 2.3 GB | |
Mellum2.1JetBrains | 12B(2.5B active) | AA | 60.9 tok/s | 2.0 GB | |
LFM2.5-8B-A1BLiquid AI | 8.3B(1.5B active) | AA | 42.5 tok/s | 2.9 GB | |
Qwen3-30B-A3BAlibaba | 30B(3B active) | AA | 23.0 tok/s | 5.4 GB | |
Gemma 4 E2B ITGoogle | 2B | AA | 33.3 tok/s | 3.7 GB | |
Apertus 8BEPFL, ETH Zurich, CSCS | 8B | BB | 22.9 tok/s | 5.4 GB | |
| 81.29B(3B active) | BB | 14.5 tok/s | 8.5 GB | ||
BolmoAi2 | 0B | BB | 247.3 tok/s | 0.5 GB | |
| Ad | |||||
VibeThinker-3BWeiboAI | 3B | BB | 32.4 tok/s | 3.8 GB | |
| 8B | BB | 21.8 tok/s | 5.7 GB | ||
Mixtral 8x7B InstructMistral AI | 46.7B(12.9B active) | BB | 10.9 tok/s | 11.4 GB | |
North Mini CodeCohere | 30B(3B active) | BB | 14.7 tok/s | 8.4 GB | |
Nemotron 3 Nano OmniNVIDIA | 30B(3B active) | BB | 14.5 tok/s | 8.5 GB | |
Qwen3.6 35B-A3BAlibaba | 35B(3B active) | BB | 14.5 tok/s | 8.5 GB | |
Qwen3.5-35B-A3BAlibaba | 35B(3B active) | BB | 14.5 tok/s | 8.5 GB | |
LensVLM-9BApple | 9B | BB | 20.6 tok/s | 6.0 GB | |
| Ad | |||||
| 9B | BB | 20.6 tok/s | 6.0 GB | ||
PersonaPlex 7BNVIDIA | 7B | BB | 25.8 tok/s | 4.8 GB | |
Llama 2 7B ChatMeta | 7B | BB | 25.8 tok/s | 4.8 GB | |
Holo4-27BHcompany | 27B | BB | 7.3 tok/s | 17.0 GB | |
minimax-m2.5MiniMax | 230B(10B active) | BB | 5.4 tok/s | 22.7 GB | |
DiffusionGemma 26B-A4BGoogle | 25.2B(3.8B active) | BB | 11.8 tok/s | 10.5 GB | |
Gemma 4 26B-A4B ITGoogle | 26B(4B active) | BB | 11.2 tok/s | 11.0 GB | |
Xing4.0-29B-A4BChina Telecom AI | 29B(4B active) | BB | 11.0 tok/s | 11.2 GB | |
| Ad | |||||
K2-Horizon-MoVA-36B-A4BInstitute of Foundation Models | 36B(4B active) | BB | 6.3 tok/s | 19.6 GB | |

Model Compatibility
Use the calculator to weigh this device against any other, model by model, with speed and fit scores.
Straight answers to the questions we hear most often.
Can't find what you're looking for? Book a Discovery Call
Holo4-35B-A3B is the highest-rated model that runs on Apple M5 at 4-bit, at about 53 tok/s. In total, Apple M5 can run 230 of the 297 open models we track.
We size each model at 4-bit (Q4_K_M), add the KV cache for its context length and a fixed runtime overhead, then compare that to this device VRAM. Each model is graded on how comfortably it fits and how fast it should run on this card.
It is an estimate of decode speed in tokens per second at 4-bit, based on this device memory bandwidth and each model size. Real speed depends on your runtime, batch size, and context length, so use it to compare models, not as a hard promise.
Lower-bit quantization shrinks a model so more of them fit. These grades already assume 4-bit, which is the common local default. Going below 4-bit can squeeze a larger model in at some quality cost; going above needs more VRAM and may not fit.
Mixture-of-experts models only activate a fraction of their parameters at a time, so their runtime memory is closer to the active size than the headline size. We score fit on the active parameters, which is why some very large models still fit.