FitLLM

Can I run Laguna XS 2.1 on a M5 Pro 48GB Mac?

⚠️ Tight — it just fits — at 8-bit

Computed with the open FitLLM engine — accurate per-layer KV-cache modeling, not a naive estimate. Updated 2026-08-24.

Memory breakdown (8-bit, F16 KV, 33K context)

Model weights31.1 GB
KV cache1.3 GB
Runtime + macOS12.9 GB
Total used45.4 / 48 GB
Free2.6 GB

Max context at 8-bit: does not fit. Unified memory is shared by the OS — FitLLM leaves ~20% headroom.

Every quantization on M5 Pro 48GB

QuantWeightsFits (KV F16)Used @32K
4bit15.6 GB✅ up to 175K ctx27.9 / 48 GB
8bit31.1 GB⚠️ won't fit45.4 / 48 GB
16bit62.3 GB❌ won't fit80.3 / 48 GB

Lower quants free memory at some output-quality cost — 4-bit is the common sweet spot for local use.

▶ Open the interactive calculator (this exact setup)

Embed this verdict

Live badge for your README or model card — recomputed by the engine, never stale:

[![fits: Laguna XS 2.1 on M5 Pro 48GB Mac](https://img.shields.io/endpoint?url=https%3A%2F%2Ffitllm.run%2Fapi%2Fbadge%3Fmodel%3DLaguna%2520XS%25202.1%26ram%3D48%26quant%3D8)](https://fitllm.run/can-i-run/laguna-xs-2-1-on-m5-pro-48gb)

fit badge preview ← renders like this, live.

Or from your terminal (exit 0/1 — works as a pre-download guard):

npx fitllm "Laguna XS 2.1" --mac 48

Why most calculators get this wrong

Laguna XS 2.1 interleaves sliding-window (local) and global attention 5:1. The local layers cap their KV cache at the 512-token window, and the global layers use a different head shape (head_dim 128 vs 128). A naive "all layers × full context × one head_dim" formula over-counts KV cache by several times.

Other options

same Mac Models that fit in 48GB: gpt-oss-20b, Qwen 3.6 27B, Gemma 4 e2b, Gemma 4 e4b, Gemma 4 12b, Gemma 4 26b A4B, Llama-3.2-3B-Instruct, Llama-3.1-8B-Instruct, MiniCPM5-1B, Qwen3-0.6B, Qwen3-1.7B, Llama-3.2-1B-Instruct, Gemma-3-1B-it, Qwen 3.8 27B.

Reproduce it

Open math: fitllm-engine (MIT), from official config.json.

All numbers are computed by the open-source fitllm-engine (MIT) from official model config.json values — reproduce or audit them yourself. Estimates; real usage varies with runtime (llama.cpp / MLX / Ollama), driver and display. Found a mismatch? Report it. · FitLLM home