Devstral Small 2505 on Apple M3 Pro (36 GB)

Can the Apple M3 Pro (36 GB) run Devstral Small 2505?

Yes, it runs well

Runs well. At Q2_K it needs about 13.3 GB of 24.1 GB usable, with an estimated speed of 11.0 tok/s.

Best quant: Q2_K
Generation speed: 11.0 tok/s
Prompt processing: 195 tok/s
First token (1K prompt): 5.3 s
Largest safe context: 72K

Best app to run it on the Apple M3 Pro (36 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX · use the MLX build

Runs the MLX build, typically up to 10% faster than GGUF for a model with 23.6B active parameters on Apple silicon.
Point-and-click: search, download and chat in one window.

Open Devstral Small 2505 in LM Studio

Ollama One command with Ollama’s own build of this model.
llama.cpp Usually the first to support new model architectures.

Want an agent? Devstral Small 2505 supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

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 Devstral Small 2505

Recommended for the Apple M3 Pro (36 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 devstral:24b

Quantized files · GGUF

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

Download the Q2_K file (opens in a new tab)

huggingface.co/unsloth/Devstral-Small-2505-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Devstral-Small-2505-GGUF:Q2_K

Original weights · Hugging Face

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

huggingface.co/mistralai/Devstral-Small-2505 (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 66/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 Apple M3 Pro (36 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.	20.8 / 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.	7.9 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	12.7 / 15
Match score	66.4 / 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 Apple M3 Pro (36 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	13.3 GB	24.1 GB	11.0 tok/s	Runs well	46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	15.4 GB	24.1 GB	8.7 tok/s	Slow	55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	18.2 GB	24.1 GB	6.7 tok/s	Slow	62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	20.6 GB	24.1 GB	5.6 tok/s	Slowtight fit	64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	23.2 GB	24.1 GB	4.7 tok/s	Slowtight fit	65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	28.9 GB	24.1 GB	2.9 tok/s	Very slowfar over GPU memory limit	66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	51.0 GB	24.1 GB	—	Won't run	66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) 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

65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q6_K · 64.8 tok/s · Runs great
64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 Q5_K_M · 40.3 tok/s · Runs great
64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 Q5_K_M · 43.4 tok/s · Runs great
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX Q4_K_M · 43.1 tok/s · Runs great
55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER Q3_K_M · 45.2 tok/s · Runs well (tight fit)
55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER Q3_K_M · 49.6 tok/s · Runs well (tight fit)

Quick answers

How much memory does Devstral Small 2505 need on the M3 Pro 36GB?

At Q2_K it needs about 13.3 GB. The M3 Pro 36GB has 24.1 GB usable.

How fast is Devstral Small 2505 on the M3 Pro 36GB?

About 11.0 tok/s at Q2_K, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Devstral Small 2505 should I use on the M3 Pro 36GB?

Q2_K. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

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.