Can I run DeepSeek-Prover-V2-671B on a Apple M5 Max?
Not at these settings. No indexed quantization of DeepSeek-Prover-V2-671B fits Apple M5 Max at any context we compute, with q8_0 KV. The smallest shipped quantization is 172.10 GiB in weights alone, against 89.28 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.9 | 1251.0 | 1251.3 | 1251.9 | 1253.0 | 1255.3 |
| Q8_0 | 664.30 GiB | 665.1 | 665.2 | 665.5 | 666.1 | 667.2 | 669.5 |
| Q6_K | 513.09 GiB | 513.9 | 514.0 | 514.3 | 514.9 | 516.0 | 518.3 |
| Q5_K_M | 442.78 GiB | 443.5 | 443.7 | 444.0 | 444.5 | 445.7 | 448.0 |
| Q5_K_S | 394.82 GiB | 395.6 | 395.7 | 396.0 | 396.6 | 397.7 | 400.0 |
| Q4_1 | 391.10 GiB | 391.9 | 392.0 | 392.3 | 392.9 | 394.0 | 396.3 |
| Q4_K_M | 376.71 GiB | 377.5 | 377.6 | 377.9 | 378.5 | 379.6 | 381.9 |
| Q4_K_S | 353.96 GiB | 354.7 | 354.9 | 355.2 | 355.7 | 356.9 | 359.1 |
| Q4_0 | 353.24 GiB | 354.0 | 354.2 | 354.4 | 355.0 | 356.1 | 358.4 |
| IQ4_NL | 352.16 GiB | 352.9 | 353.1 | 353.4 | 353.9 | 355.1 | 357.3 |
| IQ4_XS | 332.72 GiB | 333.5 | 333.6 | 333.9 | 334.5 | 335.6 | 337.9 |
| Q3_K_M | 297.40 GiB | 298.2 | 298.3 | 298.6 | 299.2 | 300.3 | 302.6 |
| Q3_K_S | 269.35 GiB | 270.1 | 270.3 | 270.6 | 271.1 | 272.3 | 274.5 |
| UD-IQ3_XXS | 253.67 GiB | 254.4 | 254.6 | 254.9 | 255.4 | 256.6 | 258.9 |
| Q2_K_L | 227.64 GiB | 228.4 | 228.6 | 228.8 | 229.4 | 230.6 | 232.8 |
| Q2_K | 227.44 GiB | 228.2 | 228.4 | 228.6 | 229.2 | 230.3 | 232.6 |
| UD-IQ2_M | 212.09 GiB | 212.9 | 213.0 | 213.3 | 213.9 | 215.0 | 217.3 |
| UD-IQ2_XXS | 201.13 GiB | 201.9 | 202.0 | 202.3 | 202.9 | 204.0 | 206.3 |
| UD-IQ1_M | 186.06 GiB | 186.8 | 187.0 | 187.3 | 187.8 | 189.0 | 191.2 |
| UD-IQ1_S | 172.10 GiB | 172.9 | 173.0 | 173.3 | 173.9 | 175.0 | 177.3 |
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.