Choose the unified-memory configuration, estimate room for your model, then inspect speed and whole-machine price evidence.
Current generation. Selected published configurations, not an exhaustive Apple configurator. SSD, display, thermal design and GPU-core variants must be matched separately.
Apple chip
M5 Max
GPU cores
4018 CPU cores
Unified memory
48 / 64 / 128 GB
Memory bandwidth
614 GB/s
Which models fit this Mac?
36 GiB model/runtime budget after 12 GiB system allowance.
The allowance is editable. Lowering it does not raise macOS’s actual Metal working-set limit. Four sample models, Q4_K_M weights, FP16 KV, one request and 2 GiB runtime reserve. Models above 70B are not assessed here.
We do not infer tok/s from memory size, bandwidth, GPU core count or Neural Engine TOPS. The capacity models above have not been benchmarked by us on this Mac.
Changing the memory/context selector changes estimates only. Published references keep their own model, quantization and scope; no exact-configuration speed is implied.
Whole-Mac purchase references.
No exact configured purchase quote collected. Confirm the GPU cores, memory, SSD, seller, condition, tax and stock before comparing prices.
For the GGUF files used in this estimate, llama.cpp provides a Metal backend on Apple Silicon. Download the exact model artifact linked in the capacity cards, set an explicit context, and confirm GPU/Metal execution and actual memory use in the runtime logs. This page does not claim a tested installation on this machine.
MLX is another Apple Silicon runtime path. Its model checkpoints, quantization and memory allocations differ; the GGUF estimates above are not measurements of an MLX checkpoint. Recheck the chosen artifact rather than carrying over a GGUF file size.
Apple designs the integrated GPU in this M5 Max system. Unified memory is shared with the CPU and system; it is not dedicated VRAM. GPU core count and selected memory options come from the linked specification.
These Macs contain an integrated Apple GPU. CPU, GPU, macOS and other apps share one memory pool. We reserve 25% (at least 4 GiB) for the system and other apps, then add exact Q4_K_M weight-file bytes, FP16 KV cache and 2 GiB for the inference runtime. The system allowance is our editable planning assumption, not a measured free-memory value or a universal macOS GPU limit.
Nominal Apple GB labels are treated as GiB for this scenario. Context includes input and output tokens; one request, weights kept in memory. Passing the estimate is a shortlist, not a verified deployment. The four-model sample stops at 70B; a 70B result is not a ceiling on a large Mac.
Actual Metal working-set limits, prefill workspace, app usage, runtime allocations and model support may change the result. Swapping to SSD can make a model load while becoming too slow for the intended task. Memory bandwidth alone cannot establish output speed.
Files, architecture & formula
KV bytes = 2 × layers × KV heads × head dimension × context × 2 bytes. 1 GiB = 2³⁰ bytes. Capacity uses the same four pinned GGUF profiles as our GPU catalog.