Can I run DeepSeek-V3.2 on a Apple M5 Max?
Not at these settings. No indexed quantization of DeepSeek-V3.2 fits Apple M5 Max at any context we compute, with q4_0 KV. The smallest shipped quantization is 138.82 GiB in weights alone, against 44.64 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| BF16 | 1250.09 GiB | 1250.8 | 1250.9 | 1251.0 | 1251.3 | 1251.9 | 1253.1 |
| Q8_0 | 664.30 GiB | 665.0 | 665.1 | 665.2 | 665.5 | 666.1 | 667.3 |
| Q6_K | 513.45 GiB | 514.2 | 514.2 | 514.4 | 514.7 | 515.3 | 516.5 |
| Q5_K_M | 443.46 GiB | 444.2 | 444.2 | 444.4 | 444.7 | 445.3 | 446.5 |
| Q5_K_S | 430.86 GiB | 431.6 | 431.6 | 431.8 | 432.1 | 432.7 | 433.9 |
| Q4_1 | 391.87 GiB | 392.6 | 392.7 | 392.8 | 393.1 | 393.7 | 394.9 |
| Q4_K_M | 377.56 GiB | 378.3 | 378.3 | 378.5 | 378.8 | 379.4 | 380.6 |
| Q4_K_S | 354.89 GiB | 355.6 | 355.7 | 355.8 | 356.1 | 356.7 | 357.9 |
| Q4_0 | 353.99 GiB | 354.7 | 354.8 | 354.9 | 355.2 | 355.8 | 357.0 |
| IQ4_NL | 353.10 GiB | 353.8 | 353.9 | 354.0 | 354.3 | 354.9 | 356.1 |
| IQ4_XS | 333.74 GiB | 334.4 | 334.5 | 334.7 | 335.0 | 335.6 | 336.8 |
| Q3_K_M | 298.24 GiB | 298.9 | 299.0 | 299.2 | 299.5 | 300.1 | 301.3 |
| Q3_K_S | 270.50 GiB | 271.2 | 271.3 | 271.4 | 271.7 | 272.3 | 273.5 |
| UD-IQ3_XXS | 254.37 GiB | 255.1 | 255.2 | 255.3 | 255.6 | 256.2 | 257.4 |
| Q2_K_L | 228.72 GiB | 229.4 | 229.5 | 229.6 | 229.9 | 230.6 | 231.8 |
| Q2_K | 228.51 GiB | 229.2 | 229.3 | 229.4 | 229.7 | 230.3 | 231.6 |
| UD-IQ2_M | 212.44 GiB | 213.1 | 213.2 | 213.4 | 213.7 | 214.3 | 215.5 |
| UD-IQ2_XXS | 202.22 GiB | 202.9 | 203.0 | 203.1 | 203.4 | 204.1 | 205.3 |
| UD-IQ1_M | 185.62 GiB | 186.3 | 186.4 | 186.6 | 186.9 | 187.5 | 188.7 |
| UD-IQ1_S | 171.48 GiB | 172.2 | 172.3 | 172.4 | 172.7 | 173.3 | 174.5 |
| IQ2_XXS | 162.59 GiB | 163.3 | 163.4 | 163.5 | 163.8 | 164.4 | 165.6 |
| UD-TQ1_0 | 150.20 GiB | 150.9 | 151.0 | 151.1 | 151.4 | 152.0 | 153.2 |
| IQ1_M | 138.82 GiB | 139.5 | 139.6 | 139.8 | 140.1 | 140.7 | 141.9 |
Figures are GiB of total memory: weights plus KV cache plus compute buffer and backend overhead. Weights and KV are near-exact; the overhead term is modeled. Hover any cell for the breakdown.
Why other calculators disagree
A parameters × bits ÷ 8 estimate ignores two things that dominate at long context. First, the weights themselves are not the nominal rate — quantizations are mixtures, so the real file is consistently larger than the label implies. Second, this model uses latent attention and allocates no V cache at all, so any formula reading num_key_value_heads overstates its cache by more than an order of magnitude.