text model · Mistral · macOS
Can I run Magistral Small on Apple M1 (8GB)?
No. Magistral Small needs ~16 GB even at Q4_K_M, but Apple M1 (8GB) only has ~5.5 GB usable.
Needs ~16 GB even at Q4_K_M, but only ~5.5 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 10.5 GB: Magistral Small needs roughly 16 GB at Q4_K_M and Apple M1 (8GB) leaves only about 5.5 GB usable for a model. The lightest tracked hardware that runs Magistral Small is the Apple M4 (24GB) at 24 GB. See Magistral Small on Apple M4 (24GB).
- Q4_K_M needed
- ~16 GB
- Usable on device
- ~5.5 GB
- Device memory
- 8 GB
Which quant fits
- Parameters
- 24B
- Q4_K_M size
- 14 GB
- Q8_0 size
- 25 GB
- Context
- 40k
- Ollama tag
- magistral:24b
- Memory
- 8 GB unified
- Usable for weights
- ~5.5 GB
- Power draw
- ~39 W
- Best runtime
- Ollama (llama.cpp Metal backend)
What you can run instead
Run Magistral Small on other hardware
FAQ
Can Apple M1 (8GB) run Magistral Small?
No. Magistral Small needs ~16 GB even at Q4_K_M, but Apple M1 (8GB) only has ~5.5 GB usable.
How much memory does Magistral Small need?
Apple M1 (8GB) does not have enough memory. At Q4_K_M the weights are ~14 GB; with KV cache and runtime overhead, budget ~16 GB at a 4k context.
What is the best tool to run Magistral Small on macOS?
LM Studio for a simple setup; mlx-lm for the most speed. vLLM is NOT a Mac tool, it is a CUDA/Linux serving engine. Unified memory is not a fixed VRAM slice; ~70% is usable for weights.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/magistral-small/apple-m1-8gb) Sources
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.