RigBaseBuildsGPUsCan it run?GuidesBest rig for…By budgetRent before you buySubmit a buildNewsletterAdvertise

Apple M5 Max for local LLMs

13 measured results from 2 builds, each linked to its source.

Memoryunified memory: 36–128 GB in our builds
Memory bandwidthnot listed
Typical EU pricenot tracked yet

All builds with the Apple M5 Max

BuildGPU(s)Memory GB (total)Results
MacBook Pro M5 Max 128 GB: Qwen3.6 35B-A3B at 271 tok/s (mlx-serve + MTP), Gemma 4 26B-A4B at 166Apple M5 Max (unified)1285
Mac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXApple M5 Max (unified)368

All measured results

(MTP, DFlash, DSpark and similar draft-and-verify methods give much higher tok/s on predictable text and are not comparable 1:1 with plain decode)

ModelBuildRan onQuantEnginetok/sDetails
Gemma 4 26B-A4BMacBook Pro M5 Max 128 GB: Qwen3.6 35B-A3B at 271 tok/s (mlx-serve + MTP), Gemma 4 26B-A4B at 166mixed / see build4-bit MLX (QAT)Rapid-MLX 0.16.1 + DFlash166⚡ spec-decode (DFlash)
Qwen3.5 9BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXRapid-MLX 0.16.1 (MTP)115.5⚡ spec-decode (MTP)
Qwen3.5 9BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXoMLX 0.7.078.0
Qwen3.6 35B-A3BMacBook Pro M5 Max 128 GB: Qwen3.6 35B-A3B at 271 tok/s (mlx-serve + MTP), Gemma 4 26B-A4B at 166mixed / see build4-bit MLX (mlx-serve build)mlx-serve 26.10.2 + MTP271⚡ spec-decode (MTP)
Qwen3.6 35B-A3BMacBook Pro M5 Max 128 GB: Qwen3.6 35B-A3B at 271 tok/s (mlx-serve + MTP), Gemma 4 26B-A4B at 166mixed / see build4-bit MLXRapid-MLX 0.16.1 + MTP240⚡ spec-decode (MTP)
Qwen3.6 35B-A3BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXRapid-MLX 0.16.1 (MTP)173.4⚡ spec-decode (MTP)
Qwen3.6 35B-A3BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXoMLX 0.7.0145.8
Qwen3.6 35B-A3BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXLM Studio (MLX)124.5
Qwen3.6 35B-A3BMacBook Pro M5 Max 128 GB: Qwen3.6 35B-A3B at 271 tok/s (mlx-serve + MTP), Gemma 4 26B-A4B at 166mixed / see build4-bit MLXmlx_lm.server 0.32.2107
Qwen3.8 27BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXRapid-MLX 0.16.1 (MTP)37.9⚡ spec-decode (MTP)
Qwen3.8 27BMacBook Pro M5 Max 128 GB: Qwen3.6 35B-A3B at 271 tok/s (mlx-serve + MTP), Gemma 4 26B-A4B at 166mixed / see build4-bit MLXsame server, no speculation31
Qwen3.8 27BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXLM Studio (MLX)26.0
Qwen3.8 27BMac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLXmixed / see build4-bit MLXoMLX 0.7.025.3

All Apple M5 Max builds: see also all GPUs · best LLMs by memory size · download the dataset.

FAQ

How fast is the Apple M5 Max for local LLMs?

The fastest plain-decode result we have is 145.8 tok/s on Qwen3.6 35B-A3B (4-bit MLX, oMLX 0.7.0) in Mac Studio M5 Max 36 GB: Qwen3.6 35B-A3B at 173 tok/s (Rapid-MLX), 146 on oMLX. Speed depends heavily on the model, quant and engine, so compare like with like in the table. RigBase lists 13 measured results from 2 builds.

How much memory does the Apple M5 Max have?

unified memory: 36–128 GB in our builds.

Which models have been measured on the Apple M5 Max?

Gemma 4 26B-A4B, Qwen3.5 9B, Qwen3.6 35B-A3B, Qwen3.8 27B.

Where do these numbers come from?

Every row links to a build page with its original public source (benchmark logs, READMEs, forum posts). RigBase does not re-run the benchmarks. Results marked ⚡ use speculative decoding and are not comparable 1:1 with plain decode.

Not enough VRAM? Rent before you buy. Run Apple M5 Max-class models on a rented 24–96 GB cloud GPU by the hour and see the real speed before spending €1,000+. Try it on Runpod
Referral link: if you sign up with Google and add $10, Runpod gives you and RigBase bonus credit (terms). It never affects our data.