How to Deploy Kimi K2 Locally
Kimi K2 is Moonshot AI's 1T-parameter MoE, and the version on this site is 0905 from September 2025: instant chat only, with no thinking, and text only. At 4-bit it is about 621 GB, far beyond any single GPU or 128GB machine. For a new deployment, look at the later versions instead: for coding and agents, use K2.7 Code, whose official weights are already 4-bit, so quantization adds almost no extra loss. K2's official weights are FP8, so squeezing them to 4-bit is genuinely lossy.
Kimi K2 details
- Min VRAM at 4-bit623 GB · 8K
- Parameters1,000B
- Active params32B
- Max context256K
- Architecture
- MoE
- Experts offloaded
- 10 GB VRAM + 615 GB RAM
- License
- Modified MIT
- Launch date
- Sep 3, 2025
- Vendor
- Moonshot AI
- Hugging Face repo
- moonshotai/Kimi-K2-Instruct-0905
- GGUF repo
- unsloth/Kimi-K2-Instruct-0905-GGUF
- MLX repo (Apple)
- mlx-community/Kimi-K2-Instruct-0905-mlx-3bit
- Revision
- 0905
- Layers
- 61
- Hidden size
- 7,168
- KV heads
- 64
- Head dim
- 192
How much VRAM does Kimi K2 need for local deployment?
| Quantization | WeightsGB | 8K contextGB | 32K contextGB | 128K contextGB | 256K context (max)GB |
|---|---|---|---|---|---|
| 1-bit | 304.8GGUF | 306.4 | 308.2 | 315.1 | 324.3 |
| 2-bit | 383.6GGUF | 385.2 | 387 | 393.9 | 403.1 |
| 3-bit | 452.4GGUF | 454 | 455.8 | 462.7 | 471.9 |
| 4-bit | 621.3GGUF | 622.9 | 624.7 | 631.6 | 640.8 |
| 5-bit | 728.7GGUF | 730.3 | 732.1 | 739 | 748.2 |
| 8-bit | 1,091.1GGUF | 1,092.7 | 1,094.5 | 1,101.4 | 1,110.6 |
| 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?
No. Single GPUs and 128GB machines are nowhere close: even at 2-bit, 1T parameters come to about 384 GB. The only machine that holds 2-bit is the 512GB Mac Studio M3 Ultra, and it's pressed right up against the three-quarters of memory macOS lets the GPU use by default, so raise that limit first. The more common route is a server with 384GB of RAM and one RTX PRO 6000, with most experts in system memory, which runs 2-bit at around 40 tokens/s. Also note that K2's official weights are 8-bit, so both 2-bit and 4-bit are genuinely lossy, unlike later versions.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 40.5 | 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?
You need eight 96GB RTX PRO 6000 cards: about 69 tokens/s at 2-bit and about 50 at 4-bit. K2's 2-bit is noticeably bigger than K2.6's, so with 32K of context it just misses on four 96GB cards and on eight 48GB cards, leaving no smaller option. Four networked DGX Sparks can hold 2-bit, but only manage about 14 tokens/s. If four 96GB cards are what you have, K2.6 is the better pick: same 1T architecture, its 2-bit fits on four cards, and its instant mode is the closest match to how K2 is used.
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 units | $32,960 | 512 GB | 14.5 | 960 W | |
| Instinct MI21064 GB per card | 8 cards | $39,952 | 512 GB | 65.1 | 2,400 W |
| 8 cards | $85,776 | 576 GB | 56.5 | 2,400 W | |
| 8 cards | $151,992 | 640 GB | 72.8 | 2,400 W | |
| 8 cards | $180,000 | 768 GB | 69.2 | 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 | 26.2 | 960 W |
| 8 cards | $180,000 | 768 GB | 50 | 4,800 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| Mac Studio M3 Ultra 512GB512 GB per unit | 4 units | $91,600 | 2,048 GB | 16.1 | 1,920 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 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 41 tokens/s, and 4-bit, which needs every slot filled for 768GB, about 26. KTransformers, recommended on the model card, is built specifically for this kind of inference split between CPU and GPU.
GeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Dual EPYC DDR5
Flagship2 × RTX PRO 6000 + Dual EPYC DDR5
Giant modelsTesla V100 32GB + Dual Xeon E5 8-GPU server
Budget- PSU
- Built-in 4 × 1,600 W
- Included
GeForce RTX 5090 + Dual EPYC DDR5
Flagship4 × RTX PRO 6000 + Dual EPYC DDR5
Giant modelsGeForce RTX 5090 + Dual EPYC DDR5
Flagship8 × RTX PRO 6000 + Dual EPYC DDR5 8-GPU server
Giant models- PSU
- Built-in 4 × 3,000 W
- Included
Detailed 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 locally
Which version to deploy now
For coding and agents, go straight to K2.7 Code: the same 1T architecture, with official weights that are natively 4-bit (INT4), so quantization adds almost no extra loss. For instant answers without thinking, the instant mode of K2.6 is the closest to how K2 is used. The main reason to keep K2 is that your existing workflows and prompts were tuned for it.
Where to get GGUFs
The llama-server command on this page uses Unsloth's 0905 GGUF (unsloth/Kimi-K2-Instruct-0905-GGUF), available from 1-bit to 8-bit, and llama.cpp runs it directly. Moonshot's recommended engines are vLLM, SGLang, KTransformers and TensorRT-LLM.
What 0905 improves over the original
In Moonshot's tests, SWE-bench Verified for coding rose from 65.8 on the 0711 version to 69.2, and Terminal-Bench for terminal tasks from 37.5 to 44.5; front-end code is more polished and practical, and context doubled from 128K to 256K.
Sampling parameters
Moonshot recommends
temperature0.6; for the system prompt, the default line given on the model card is fine.License
A modified MIT license with just one extra clause: commercial products with more than 100 million monthly active users or very high monthly revenue must prominently display “Kimi K2” in their interface. K2.5 through K2.7 Code keep the same terms, with the displayed name changed to each version's own.
Launch commands
llama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/Kimi-K2-Instruct-0905-GGUF:Q4_K_M -c 8192Short on VRAM? Add --cpu-moe to keep the routed experts in system RAM (about 615 GB needed).
llama-server -hf unsloth/Kimi-K2-Instruct-0905-GGUF:Q4_K_M -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-Instruct-0905 \ --port 8000 \ --served-model-name kimi-k2 \ --trust-remote-code \ --tensor-parallel-size 16 \ --enable-auto-tool-choice \ --tool-call-parser kimi_k2
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-Instruct-0905-mlx-3bitOllama
- Windows
- macOS
- Linux
The Ollama library has no official tag for it yet.
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.2 GB | |
| 1,000B | 32B | 583.7 GB | |
| 1,000B | 32B | 583.7 GB | |
| 2,800B | 104B | 1,508.7 GB |