Update 2026.10

Mac mini M5 Pro 24GB Integrated memory 24GB · Usable space for model: approximately 20GB

The base-memory M5 Pro configuration prioritizes high bandwidth and is currently sold for fast 12B-class model use.

Speed and memory for the same model

Mac mini M5 Pro 24GB · Qwen3.8 27B · local LLM speed and memory: Prompt processing · prefill 351–631 tok/s · Token generation · decode 13.9–15.4 tok/s; Required 17.56GB / Usable 20GB unified memory
4,096 input tokens · single request · prompt cache off

Hardware core specifications

Available memory
20GB
Memory bandwidth
307GB/s
Estimated sustained LLM load
About 92W
Korean price range (KRW)
299 × KRW 10,000–299 × KRW 10,000

Who it fits

  • Utilizes 20GB of available memory
  • Quiet finished product composition
  • K2 Horizon MoVA 36B-A4B-level local inference

Skip it if

Since the operating system and KV cache use the same memory, headroom quickly decreases for long contexts or models above 20B.

Recommended format for each device 4K input

The model you will experience with this equipment

K2 Horizon 0.9B

Required 1.03GB · spare time

MLX 4-bit

Decode

417.1 ~ 463.4 tok/s

First token

0.62 to 1.3 seconds

K2 Horizon MoVA 36B-A4B

recommended

Required 21.94GB · tight

MLX 4-bit

Decode

23.4 ~ 36.4 tok/s

First token

3.9 to 8.8 seconds

Actual speed varies with runtime version, cooling, context length and quantization file.

On sales pages, look at memory before chips.

The model and speed assumptions above change if the product is not the 24GB configuration.

Frequently asked questions

What LLM can be run on the Mac mini M5 Pro 24GB?
K2 Horizon 0.9B, K2 Horizon MoVA 36B-A4B and others with a 4K input and the recommended format. Required memory varies by model and context length.
What is the local LLM power of the Mac mini M5 Pro 24GB?
Sustained load is about 92 W, with an actual range of 62–128 W.
Are the displayed token speeds ground truth?
This is a range aligned to collected benchmark measurements under the same conditions. Combinations without a matching measurement are estimated from the nearest result and vary with runtime, cooling, quantization file and context length.