How to Deploy Kimi K2.6 Locally
Kimi K2.6 is a 1T-parameter MoE that Moonshot AI released in April 2026, with exactly the same architecture as K2.5. What it improves is long-running coding, building interfaces from design mockups and multi-agent collaboration. K2.7 Code, released in June, is a coding-focused version built on top of it, so use K2.7 Code for coding; for instant mode or general tasks beyond coding, K2.6 is still the newest choice in the K2 series.
Kimi K2.6 details
- Min VRAM at 4-bit586 GB · 8K
- Parameters1,000B
- Active params32B
- Max context256K
- Architecture
- MoE
- Experts offloaded
- 10 GB VRAM + 578 GB RAM
- License
- Modified MIT
- Launch date
- Apr 20, 2026
- Vendor
- Moonshot AI
- Hugging Face repo
- moonshotai/Kimi-K2.6
- GGUF repo
- unsloth/Kimi-K2.6-GGUF
- NVFP4 repo (Blackwell)
- nvidia/Kimi-K2.6-NVFP4
- MLX repo (Apple)
- mlx-community/Kimi-K2.6-mlx-DQ3_K_M-q8
- Layers
- 61
- Hidden size
- 7,168
- KV heads
- 64
- Head dim
- 192
How much VRAM does Kimi K2.6 need for local deployment?
| Quantization | WeightsGB | 8K contextGB | 32K contextGB | 128K contextGB | 256K context (max)GB |
|---|---|---|---|---|---|
| 1-bit | 252est. | 253.6 | 255.4 | 262.3 | 271.5 |
| 2-bit | 340.5GGUF | 342.1 | 343.9 | 350.8 | 360 |
| 3-bit | 514.5est. | 516.1 | 517.9 | 524.8 | 534 |
| 4-bit | 583.7GGUF | 585.3 | 587.1 | 594 | 603.2 |
| 5-bit | — | — | — | — | — |
| 8-bit | 594.5GGUF | 596.1 | 597.9 | 604.8 | 614 |
| BF16/FP16 | 2,053.2GGUF | 2,054.8 | 2,056.6 | 2,063.5 | 2,072.7 |
Full calculation rules are on the Methodology page.
Can a single GPU run Kimi K2.6?
No single GPU can hold it, and only one machine on its own manages it: the 512GB Mac Studio M3 Ultra at 2-bit. Squeezed to 2-bit, 1T parameters come to about 341 GB, a notch smaller than K2.5, so the Mac holds it without any system tweaks and still has room for the full context. Each token uses only 32B of those parameters, so generation on the Mac isn't as slow as the size suggests. 4-bit, at about 584 GB, is too big for the Mac; that means eight 96GB cards, or a server with 768GB of RAM plus one GPU and the experts in system memory.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 44.4 | 256K |
Only common GPUs and systems are listed, one set for models under 50B and another for larger ones, sorted by price from low to high.
How many GPUs do you need to run Kimi K2.6?
Four 96GB RTX PRO 6000 cards at 2-bit are the most compact setup, at about 74 tokens/s. Eight 48GB RTX A6000s have the same total VRAM and also hold 2-bit, at roughly half the speed. 4-bit means doubling to eight RTX PRO 6000s, and at that point just use 8-bit: the official experts are already 4-bit, 8-bit keeps them untouched and counts as lossless, the file is only 11 GB larger, and both run at just over 50 tokens/s. Four networked DGX Spark units can run 2-bit too, but only in the mid-teens.
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 units | $32,960 | 512 GB | 16.1 | 960 W | |
| 8 cards | $39,192 | 384 GB | 39.8 | 2,400 W | |
| Instinct MI21064 GB per card | 8 cards | $39,952 | 512 GB | 70.1 | 2,400 W |
| 8 cards | $85,776 | 576 GB | 61.1 | 2,400 W | |
| 4 cards | $90,000 | 384 GB | 74.3 | 2,400 W | |
| 8 cards | $151,992 | 640 GB | 78.1 | 2,400 W | |
| 8 cards | No price | 384 GB | 49.4 | 3,600 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| Mac Studio M3 Ultra 512GB512 GB per unit | 2 units | $45,800 | 1,024 GB | 27.6 | 960 W |
| 8 cards | $151,992 | 640 GB | 55.4 | 2,400 W | |
| 8 cards | $180,000 | 768 GB | 52.3 | 4,800 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| Mac Studio M3 Ultra 512GB512 GB per unit | 2 units | $45,800 | 1,024 GB | 27.2 | 960 W |
| 8 cards | $151,992 | 640 GB | 54.7 | 2,400 W | |
| 8 cards | $180,000 | 768 GB | 51.6 | 4,800 W |
Mac Studios link up over Thunderbolt 5 and run with MLX or exo; vLLM doesn't support them. Full calculation rules are on the Methodology page.
What PC or server build do you need to run Kimi K2.6 locally?
For expert offloading, the only setup that works is a 12-channel DDR5 server with one RTX PRO 6000: 2-bit with 384GB of RAM does about 46 tokens/s, while 4-bit and 8-bit both need every slot filled for 768GB and both do about 27. Here 8-bit is no slower than 4-bit, so if you have the memory, go straight to lossless 8-bit.
GeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Dual EPYC DDR5
Flagship2 × RTX PRO 6000 + Dual EPYC DDR5
Giant models4 × Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 5090 + Dual EPYC DDR5
Flagship4 × RTX PRO 6000 + Dual EPYC DDR5
Giant models4 × Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 5090 + Dual EPYC DDR5
Flagship4 × RTX PRO 6000 + Dual EPYC DDR5
Giant modelsDetailed calculation rules are on the Methodology page.
As an eBay Partner, VRAMGlass may be compensated if you buy through the eBay links on this page. The price you pay stays the same.
What to know before running Kimi K2.6 locally
Only three quantization levels
Unsloth has released only three: 2-bit (about 341 GB), 4-bit (about 584 GB) and 8-bit (about 595 GB). The 8-bit keeps the 4-bit experts as-is and uses BF16 for the rest, so it counts as lossless; 4-bit just compresses the rest further to 8-bit, and its difference from 8-bit is negligible (perplexity 1.8420 vs. 1.8419). Unsloth recommends 2-bit as the balance point between size and quality.
Thinking, instant and preserve_thinking
Sampling parameters carry over from K2.5:
temperature1.0 for thinking mode and 0.6 for instant mode, withtop_p0.95. Switching to instant mode works the same way, by turning off thinking underchat_template_kwargs. The newpreserve_thinkingoption is off by default; turning it on keeps all thinking content across multi-turn conversations, and Moonshot recommends enabling it only for coding agents running in thinking mode.Images
Starting with K2.6, Unsloth's GGUFs include the projector file (mmproj) for images, so adding
--mmprojin llama.cpp lets you input images and use its vision capabilities locally too.vLLM requirements
The vLLM recipe requires 0.25 or later. The official original (INT4) was validated on eight H200s, and the recipe puts the requirement at about 640 GB of VRAM in total; on B300 you can switch to the NVFP4 version, where four cards are enough.
Context
Native context is 256K, and it's light on VRAM: at 4-bit, going from 8K to 256K adds only about 18 GB. Unsloth recommends a default of 98,304 (about 96K).
Launch commands
llama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/Kimi-K2.6-GGUF:UD-Q4_K_XL -c 8192Short on VRAM? Add --cpu-moe to keep the routed experts in system RAM (about 578 GB needed).
llama-server -hf unsloth/Kimi-K2.6-GGUF:UD-Q4_K_XL -c 8192 -ngl 99 \ --cpu-moe
vLLM
- Linux
- NVIDIA
Follow the deployment guide to prepare the required runtime and hardware.
vllm serve moonshotai/Kimi-K2.6 \ --trust-remote-code \ --tensor-parallel-size 8 \ --tool-call-parser kimi_k2 \ --enable-auto-tool-choice \ --reasoning-parser kimi_k2 \ --speculative-config '{"model":"lightseekorg/kimi-k2.6-eagle3-mla","method":"eagle3","num_speculative_tokens":3}' \ --mm-encoder-tp-mode data
MLX
- Apple Silicon
On a Mac, pip install mlx-lm first; this command downloads the MLX weights from Hugging Face and starts an OpenAI-compatible server.
mlx_lm.server --model mlx-community/Kimi-K2.6-mlx-DQ3_K_M-q8Ollama
- Windows
- macOS
- Linux
Ollama only has a cloud version, kimi-k2.6:cloud, which runs on Ollama's servers rather than on your machine.
File names follow that week's model-library snapshot; the definitions are in the methodology. Methodology
Other models in the Kimi family
| Model | Total params | Active params | 4-bit size |
|---|---|---|---|
| 49.1B | 3B | 30.1 GB | |
| 1,000B | 32B | 621.3 GB | |
| 1,000B | 32B | 621.2 GB | |
| 1,000B | 32B | 583.7 GB | |
| 2,800B | 104B | 1,508.7 GB |