Can I run Devstral Small 2 24B?
Devstral Small 2 24B by Mistral AI needs around 24 GB of RAM at the recommended 4-bit quantization (14.6 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~24 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
Devstral Small 2 is Mistral's 24B coding model, and the name undersells how much machine it asks for. At a 4-bit quant it lands around 14.6 GB of weights, so the 12 GB cards most people own are out: on an RTX 3060 it simply does not fit. You realistically want 24 GB of memory to run it comfortably, which in practice means a 24 GB GPU like a 4090 or an Apple Silicon Mac with at least 24 GB of unified memory. If you drop to a 2-bit quant it shrinks to about 10.1 GB, but that is a steep quality tradeoff for a model whose whole point is careful code generation.
On a 4090 you can expect around 59 tokens per second at 4-bit, which is genuinely pleasant for an agentic coding loop where it reads files, plans, and edits. On an M-series Max it settles closer to 24 tok/s, still usable for interactive work but you feel it on longer generations. The headline 256K context is real and useful for feeding it whole repositories, but be honest about the cost: even at 128K the fact sheet puts total memory near 42.1 GB, well past a single 24 GB card. Treat the big context as something you reach for deliberately, not a default you leave open.
Against its siblings, Devstral is the serious-work pick: Mistral 7B and Mistral Nemo 12B are lighter and easier to host but generally weaker on multi-step coding tasks, while Gemma 4 26B A4B is the closest peer for coding and reasoning and worth a side-by-side if you have the memory. What makes Devstral stand out is that it was built for agentic, tool-using code editing rather than one-shot chat, and that focus shows in how it follows a plan across files. The license is Apache 2.0, so you can use it commercially and in production without restrictions, which is rare for a model this capable.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 10.1 GB | 16 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 14.6 GB | 24 GB | Recommended |
| Q5_K_M | 5.65 | 17.0 GB | 24 GB | High |
| Q8_0 | 8.5 | 25.5 GB | 48 GB | Near-original |
| F16 | 16 | 48.0 GB | 64 GB | Original |
Sizes are estimates from parameter count Γ bits per weight; real GGUF builds vary slightly. Β· Data updated: 2026-06-11 Β· How we calculate these numbers β
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~0.9 GB | ~15.5 GB |
| 8K tokens | ~1.7 GB | ~16.3 GB |
| 32K tokens | ~6.9 GB | ~21.5 GB |
| 128K tokens | ~27.5 GB | ~42.1 GB |
The KV cache grows with context length β a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~59 tok/s |
| Apple M-series (base) | 100 GB/s | ~6 tok/s |
| Apple M-series Pro | 270 GB/s | ~16 tok/s |
| Apple M-series Max | 410 GB/s | ~24 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~4 tok/s |
Token generation is memory-bandwidth bound: tok/s β bandwidth Γ 0.85 Γ· model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama β one command and you're chatting:
ollama run devstral-small-2:24b