← All modelsMODEL CHECK

Can I run Devstral 24B?

Devstral 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 24B is Mistral AI's coding specialist, built for people who want a capable local agent for software work rather than a general chat companion. At 24B dense parameters it is not a lightweight: the 4-bit quant lands around 14.6 GB and the model needs roughly 24 GB of RAM minimum to run comfortably. That puts it out of reach of a 12 GB card like an RTX 3060, where it simply does not fit. The natural home is a 24 GB GPU such as an RTX 4090, or an Apple Silicon Mac with plenty of unified memory. If you are short on space, the 2-bit build drops to about 10.1 GB.

In daily coding use on an RTX 4090 you can expect around 59 tokens per second at 4-bit, quick enough that generated code streams smoothly while you read it. On an Apple M-series Max it settles closer to 24 tokens per second, still perfectly usable for interactive work, and CPU-only on DDR5 falls to roughly 4 tokens per second, which is patience territory. The 128K context window is genuinely large, but it is not free: filling it pushes total memory to about 42.1 GB, well past the model's resting footprint, so keep working context modest unless you have the headroom to spare.

Against its stablemates, Devstral 24B is the heavyweight: Mistral 7B and Mistral Nemo 12B are far lighter and aimed at general chat, so they will run on hardware Devstral cannot touch but generally trail it on actual coding tasks. The closer comparison is Gemma 4 26B A4B, a similarly sized model that also handles coding alongside chat, reasoning, and vision, and tends to be the more versatile generalist if you want one model for everything. Devstral's standout trait is its narrow focus on code, and the Apache 2.0 license means you can use it freely, including in commercial production.

Specifications

Parameters24B
Context window128K tokens
ProviderMistral AI
LicenseApache 2.0
Released2025-05
Best forCoding

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.3510.1 GB16 GBNoticeable loss
Q4_K_MRecommended4.8514.6 GB24 GBRecommended
Q5_K_M5.6517.0 GB24 GBHigh
Q8_08.525.5 GB48 GBNear-original
F161648.0 GB64 GBOriginal

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

ContextKV 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

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/sWon't fit in VRAM
NVIDIA RTX 4090 24GB1008 GB/s~59 tok/s
Apple M-series (base)100 GB/s~6 tok/s
Apple M-series Pro270 GB/s~16 tok/s
Apple M-series Max410 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

Frequently asked questions