Kimi K3 has 2779.9B parameters (104B active per token). In BF16 its weights alone take 5178 GiB; quantized to 4-bit, about 1563 GiB. Each 32K-token request adds 0.84 GiB of KV cache. Cheapest way to run it today: 6 × AMD MI355X / MI350X (288 GB) at $32.94 per hour.
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run Kimi K3
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
MXFP4 (native)
BF16 / FP16
FP8 / INT8
4-bit (GGUF Q4_K_M)
GeForce RTX 4090 24 GB
96 (several servers)
> 128
> 128
96 (several servers)
GeForce RTX 5090 32 GB
64 (several servers)
> 128
96 (several servers)
64 (several servers)
RTX PRO 6000 Blackwell 96 GB
24 (several servers)
64 (several servers)
32 (several servers)
24 (several servers)
Mac M5 Max 128 GB 96 GB usable
24 (several servers)
64 (several servers)
32 (several servers)
24 (several servers)
NVIDIA H100 80 GB
24 (several servers)
96 (several servers)
48 (several servers)
24 (several servers)
NVIDIA H200 141 GB
16 (several servers)
48 (several servers)
24 (several servers)
16 (several servers)
NVIDIA B200 (HGX) 180 GB
16 (several servers)
48 (several servers)
24 (several servers)
16 (several servers)
Cheapest way to run Kimi K3 today
For each GPU: the fewest cards that fit Kimi K3 with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-10).
On-demand prices from RunPod, Vast.ai, Verda and Azure, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
KV cache: how memory grows with context
Architecture: MoE 896 experts · MLA on 24 of 93 layers · 69 Kimi Delta Attention layers (~430 MiB state per sequence). Its KV cache is 3.9× smaller than if every layer used full attention, because only 24 of its 93 layers keep a KV cache; the others hold a small fixed-size state. Only 104B parameters are active per token, but all 2780B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.21 GiB
0.11 GiB
32K tokens
0.84 GiB
0.42 GiB
128K tokens
3.38 GiB
1.69 GiB
1M tokens
27.0 GiB
13.5 GiB
Plus 429 MiB of recurrent state per request, whatever the context.
Kimi K3 VRAM FAQ
How much VRAM does Kimi K3 need?
In BF16 the weights alone take 5178 GiB (5560 GB). In FP8 that is 2591 GiB, and about 1563 GiB with 4-bit quantization (Q4_K_M); the official MXFP4 checkpoint is 1454 GiB. Each request then adds KV cache: 0.21 GiB at 8K tokens and 0.84 GiB at 32K (BF16 cache).
Can Kimi K3 run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 96 (several servers) RTX 4090s. In 4-bit it needs 24 (several servers) H100 GPUs.
What is the cheapest way to run Kimi K3?
On 2026-10-10, the cheapest on-demand setup is 6 × AMD MI355X / MI350X (288 GB) with MXFP4 weights on RunPod, at $32.94 per hour (about $24,046.20 per month). Next: 6 × NVIDIA B300 / GB300 (288 GB) with MXFP4 weights on RunPod, at $53.94 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Kimi K3 need?
With one request and an 8K-token context: 96 (several servers) in BF16, 48 (several servers) in FP8 and 24 (several servers) in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Kimi K3 VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/kimi-k3.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.