Does Kimi-K2-Instruct fit in 32GB of VRAM?
Not at these settings. No indexed quantization of Kimi-K2-Instruct fits 32GB card at any context we compute, with q8_0 KV. The smallest shipped quantization is 226.87 GiB in weights alone, against 29.76 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| BF16 | 1912.15 GiB | 1913.2 | 1913.3 | 1913.6 | 1914.2 | 1915.3 | 1917.6 |
| Q8_0 | 1016.12 GiB | 1017.1 | 1017.3 | 1017.6 | 1018.1 | 1019.3 | 1021.6 |
| Q6_K | 784.76 GiB | 785.8 | 785.9 | 786.2 | 786.8 | 787.9 | 790.2 |
| Q5_K_M | 678.33 GiB | 679.3 | 679.5 | 679.8 | 680.3 | 681.5 | 683.8 |
| Q5_K_S | 658.04 GiB | 659.1 | 659.2 | 659.5 | 660.1 | 661.2 | 663.5 |
| Q4_1 | 598.40 GiB | 599.4 | 599.6 | 599.8 | 600.4 | 601.6 | 603.8 |
| Q4_K_M | 578.15 GiB | 579.2 | 579.3 | 579.6 | 580.2 | 581.3 | 583.6 |
| Q4_K_S | 542.73 GiB | 543.7 | 543.9 | 544.2 | 544.7 | 545.9 | 548.2 |
| Q4_0 | 540.74 GiB | 541.8 | 541.9 | 542.2 | 542.8 | 543.9 | 546.2 |
| IQ4_NL | 538.76 GiB | 539.8 | 539.9 | 540.2 | 540.8 | 541.9 | 544.2 |
| IQ4_XS | 508.98 GiB | 510.0 | 510.1 | 510.4 | 511.0 | 512.1 | 514.4 |
| Q3_K_M | 455.77 GiB | 456.8 | 456.9 | 457.2 | 457.8 | 458.9 | 461.2 |
| Q3_K_S | 412.03 GiB | 413.1 | 413.2 | 413.5 | 414.1 | 415.2 | 417.5 |
| UD-IQ3_XXS | 388.01 GiB | 389.0 | 389.2 | 389.5 | 390.0 | 391.2 | 393.4 |
| Q2_K_L | 347.81 GiB | 348.8 | 349.0 | 349.3 | 349.8 | 351.0 | 353.2 |
| Q2_K | 347.55 GiB | 348.6 | 348.7 | 349.0 | 349.6 | 350.7 | 353.0 |
| UD-IQ2_M | 323.27 GiB | 324.3 | 324.4 | 324.7 | 325.3 | 326.4 | 328.7 |
| UD-IQ2_XXS | 306.20 GiB | 307.2 | 307.4 | 307.7 | 308.2 | 309.4 | 311.6 |
| UD-IQ1_M | 283.34 GiB | 284.4 | 284.5 | 284.8 | 285.4 | 286.5 | 288.8 |
| UD-IQ1_S | 260.88 GiB | 261.9 | 262.0 | 262.3 | 262.9 | 264.0 | 266.3 |
| UD-TQ1_0 | 226.87 GiB | 227.9 | 228.0 | 228.3 | 228.9 | 230.0 | 232.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 there are no speeds on this page
A capacity is not a card. Whether a model fits depends only on memory, so every figure above holds for any 32GB accelerator. How fast it runs depends on memory bandwidth, which varies several-fold between cards of the same capacity — so putting a tokens-per-second number here would be inventing one. Pick a specific card from hardware and the speed column appears.
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.