text model · Mistral · macOS

Can I run Devstral 2 123B on Apple M5 Max (128GB)?

Compatibility verdict VRAM threshold engine

Yes, it runs usable speed ~7 tok/s est.

Yes. Devstral 2 123B runs on Apple M5 Max (128GB) at Q4_K_M (~73.3 GB of ~96 GB usable).

Needs ~73.3 GB Device usable ~96 GB

Runs at Q4_K_M using ~73.3 GB of ~96 GB usable.

That figure is at a 4k context and moves about ±15% as context length changes. Apple M5 Max (128GB) leaves ~22.7 GB of headroom.

Q4_K_M needed: ~73.3 GB
Usable on device: ~96 GB
Device memory: 128 GB
Best quant: Q4_K_M

Share on X Share on Reddit

Which quant fits

Quant ladder vs ~96 GB usable

Q2_K

~55 GB

Q3_K_M

~63.6 GB

Q4_K_M

~73.3 GB

Q5_K_M

~91.1 GB

Q6_K

~104.4 GB

Q8_0

~127.2 GB

FP16

~253.6 GB

The line marks Apple M5 Max (128GB)'s ~96 GB budget; rungs past it are too large.

Run it

Install commands macOS

Pick your tool. All 3 load the same Q4_K_M weights.

Ollama

$ ollama run devstral-2:123b

llama.cpp

$ llama-cli -hf unsloth/Devstral-2-123B-Instruct-2512-GGUF:Q4_K_M

LM Studio

$ lms get unsloth/Devstral-2-123B-Instruct-2512-GGUF

Model Mistral

Parameters: 123B
Q4_K_M size: 69.75 GB
Q8_0 size: 123.73 GB
Context: 256k
Ollama tag: devstral-2:123b

Full Devstral 2 123B requirements →

Device macOS

Memory: 128 GB unified
Usable for weights: ~96 GB
Best runtime: MLX direct / Ollama (MLX backend)

Best models for Apple M5 Max (128GB) →

You could also run

Run Devstral 2 123B on other hardware

Apple M4 Max (128GB)AMD Ryzen AI Halo (128GB)Apple M3 Ultra (256GB)

FAQ

Can Apple M5 Max (128GB) run Devstral 2 123B?

Yes. Devstral 2 123B runs on Apple M5 Max (128GB) at Q4_K_M (~73.3 GB of ~96 GB usable).

How much memory does Devstral 2 123B need?

Apple M5 Max (128GB) has room to spare. At Q4_K_M the weights are ~69.75 GB; with KV cache and runtime overhead, budget ~73.3 GB at a 4k context.

What is the best tool to run Devstral 2 123B 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.

Markdown

[![Devstral 2 123B on Apple M5 Max (128GB)](https://localmodel.run/badge/devstral-2-123b/apple-m5-max-128gb.svg)](https://localmodel.run/can-i-run/devstral-2-123b/apple-m5-max-128gb)

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.