How to Deploy Kimi K2.5 Locally
Kimi K2.5 is a 1T-parameter MoE that Moonshot AI released in January 2026. Compared with K2, it adds image understanding and two modes, thinking and instant, and its expert weights are natively 4-bit. The later K2.6 and K2.7 Code share exactly the same architecture, so for a new deployment, use K2.7 Code for coding and K2.6 if you need instant mode. K2.5's GGUFs also have a catch: the 8-bit quant, at about 1,091 GB, just stores the 4-bit experts in a larger format and is no more accurate than 4-bit.
Kimi K2.5 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
- Jan 27, 2026
- Vendor
- Moonshot AI
- Hugging Face repo
- moonshotai/Kimi-K2.5
- GGUF repo
- unsloth/Kimi-K2.5-GGUF
- NVFP4 repo (Blackwell)
- nvidia/Kimi-K2.5-NVFP4
- MLX repo (Apple)
- mlx-community/Kimi-K2.5
- Layers
- 61
- Hidden size
- 7,168
- KV heads
- 64
- Head dim
- 192
How much VRAM does Kimi K2.5 need for local deployment?
| Quantization | WeightsGB | 8K contextGB | 32K contextGB | 128K contextGB | 256K context (max)GB |
|---|---|---|---|---|---|
| 1-bit | 300.6GGUF | 302.2 | 304 | 310.9 | 320.1 |
| 2-bit | 374.8GGUF | 376.4 | 378.2 | 385.1 | 394.3 |
| 3-bit | 490.4GGUF | 492 | 493.8 | 500.7 | 509.9 |
| 4-bit | 621.2GGUF | 622.8 | 624.6 | 631.5 | 640.7 |
| 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.5?
No. Like K2 it has 1T parameters, and 2-bit is about 375 GB, far beyond any GPU; a 128GB machine holds only about a third of it. The only machine that fits it whole is the 512GB Mac Studio M3 Ultra at 2-bit, and even with the full context you don't have to touch system settings. 4-bit, at about 621 GB, is too much even for that Mac. Without one, it's multiple GPUs or a big-memory server with one GPU. And skip the 8-bit download: the experts ship in 4-bit form, so 8-bit just stores the same data in a bigger file without being any more accurate. Locally, 4-bit is as good as it gets.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 41.2 | 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.5?
It takes eight 96GB RTX PRO 6000 cards: about 70 tokens/s at 2-bit and about 50 at 4-bit. 4-bit is already close to original quality, so there's no point chasing 8-bit. Its 2-bit is over 30 GB larger than K2.6's, and with 32K of context that's just enough to miss on both four 96GB cards and eight 48GB cards, so there's no in-between option with fewer cards. Four networked DGX Spark units can hold 2-bit, but each has limited memory bandwidth, so expect around 15 tokens/s.
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 units | $32,960 | 512 GB | 14.8 | 960 W | |
| Instinct MI21064 GB per card | 8 cards | $39,952 | 512 GB | 66 | 2,400 W |
| 8 cards | $85,776 | 576 GB | 57.4 | 2,400 W | |
| 8 cards | $151,992 | 640 GB | 73.8 | 2,400 W | |
| 8 cards | $180,000 | 768 GB | 70.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.5 locally?
For expert offloading, the only setup that works is a 12-channel DDR5 server with one RTX PRO 6000. 4-bit needs every slot filled for 768GB of RAM, and only about 9 of the 61 layers of experts fit in the 96GB of VRAM, with the rest in RAM, so speed depends mainly on memory bandwidth, at about 26 tokens/s. 2-bit needs only 384GB, and more layers of experts fit in VRAM (about 15), at about 41.
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.5 locally
Skip the 8-bit GGUF
The officially released expert weights are already 4-bit (INT4), and the model was adapted to 4-bit during training (the same approach as K2 Thinking). Unsloth says 4-bit or 5-bit dynamic quants are enough for original-level precision, so for K2.5 run locally, 4-bit is as high as it makes sense to go; 8-bit just stores the same data in a larger format. Starting with K2.6, Unsloth switched to an 8-bit that keeps the INT4 as-is, only about 10 GB larger than 4-bit.
Thinking and instant modes
Use
temperature1.0 for thinking mode and 0.6 for instant mode, withtop_p0.95 for both. When deploying with vLLM or SGLang, pass thinking: false underchat_template_kwargsin the request to switch to instant mode.Local GGUFs are basically text-only
When llama.cpp merged K2.5 support in February 2026, it included preliminary vision code (PR #19170), but Unsloth's K2.5 GGUF repository doesn't include the projector file (mmproj) needed for images; only the GGUFs from K2.6 onward do. Video input, according to Moonshot, is currently available only through its own API.
The template changed on January 29
Two days after release, Moonshot removed a default system prompt that could cause misunderstandings and fixed a typo in the chat template, changing
<|media_start|>to<|media_begin|>. If you're using weights or GGUFs from the earliest conversions, make sure the template is the new one.
Launch commands
llama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/Kimi-K2.5-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.5-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.5 \ --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.5-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.5Ollama
- 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.3 GB | |
| 1,000B | 32B | 583.7 GB | |
| 1,000B | 32B | 583.7 GB | |
| 2,800B | 104B | 1,508.7 GB |