Kimi K3.1 Pro has 2780.1B parameters (106B 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 $51.60 per hour. It reads text, images and video, calls tools and has a reasoning mode.
Weights plus the KV cache of one request (BF16 cache) and the model's fixed recurrent state, in GiB. Add 1 to 3 GiB for the inference engine itself.
Weights format
Weights only
+ 8K context
+ 32K context
+ 128K context
+ 1M context
NVFP4 (native)
1454
1455
1455
1458
1481
BF16 / FP16
5178
5179
5180
5182
5206
FP8 / INT8
2591
2592
2593
2595
2619
4-bit (GGUF Q4_K_M)
1563
1564
1565
1567
1591
How many GPUs to run Kimi K3.1 Pro
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
NVFP4 (native)
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
Not on this GPU
> 128
> 128
96 (several machines)
GeForce RTX 5090 32 GB
Not on this GPU
> 128
96 (several machines)
64 (several machines)
RTX PRO 6000 Blackwell 96 GB
Not on this GPU
64 (several machines)
32 (several machines)
24 (several machines)
Mac M5 Max 128 GB 96 GB usable
Not on this GPU
64 (several machines)
32 (several machines)
24 (several machines)
Ryzen AI Max+ 395 128 GB 96 GB usable
Not on this GPU
64 (several machines)
32 (several machines)
24 (several machines)
DGX Spark (GB10) 128 GB
Not on this GPU
48 (several machines)
24 (several machines)
16 (several machines)
NVIDIA H100 80 GB
Not on this GPU
96 (several servers)
48 (several servers)
24 (several servers)
NVIDIA H200 141 GB
Not on this GPU
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)
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size. Not on this GPU: the official NVFP4 weights do not run there (llama.cpp needs a GGUF version, and vLLM needs a GPU with FP4 support).
Cheapest way to run Kimi K3.1 Pro today
For each GPU: the fewest cards that fit Kimi K3.1 Pro with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-11-05).
On-demand prices from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, 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.
The repository sets no sampling defaults: these are OpenRouter's defaults for Kimi K3.1 Pro.
Setting
Value
Top-p
0.95
With llama.cpp, pass them yourself: --top-p 0.95
Reasoning. Has a reasoning mode. Reasoning tokens take context and KV cache like any other token: leave room for them.
KV cache: how memory grows with context
Architecture: 93 layers · MLA (512 + 64 latent) on 24 · 69 Kimi Delta Attention. 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 106B 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.1 Pro VRAM FAQ
How much VRAM does Kimi K3.1 Pro 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 NVFP4 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.1 Pro run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 96 RTX 4090s, spread over several machines. In 4-bit it needs 24 H100 GPUs, across several servers.
Can Kimi K3.1 Pro run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 64 RTX 5090s, spread over several machines.
Can Kimi K3.1 Pro run on a Mac?
No single Mac holds it, even in 4-bit: it needs 1564 GiB with an 8K-token context, and the largest Mac (512 GB) gives its GPU about 384 GB.
Can Kimi K3.1 Pro run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
No. Even in 4-bit it needs 16 DGX Spark units or 24 Ryzen AI Max+ 395 machines (128 GB), linked over the network.
What is the cheapest way to run Kimi K3.1 Pro?
On 2026-11-05, the cheapest on-demand setup is 6 × AMD MI355X / MI350X (288 GB) with NVFP4 weights on Oracle Cloud, at $51.60 per hour (about $37,668.00 per month). Next: 7 × NVIDIA B300 / GB300 (288 GB) with NVFP4 weights on Scaleway, at $59.15 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Kimi K3.1 Pro need?
With one request and an 8K-token context: 96 in BF16, 48 in FP8 and 24 in 4-bit (vLLM, 90% of memory usable). Above 8 GPUs, that means several servers. Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Can Kimi K3.1 Pro read images?
Yes. Kimi K3.1 Pro reads text, images and video. Images add tokens to the context, so they also add KV cache.
Does Kimi K3.1 Pro support tool calling?
Yes, Kimi K3.1 Pro supports tool (function) calling: it can ask your application to run a function and use the result.
Does Kimi K3.1 Pro have a thinking mode?
Has a reasoning mode. Reasoning tokens count toward the context and the KV cache.
What temperature should I use with Kimi K3.1 Pro?
The repository sets no defaults; OpenRouter uses top-p 0.95.
Kimi K3.1 Pro 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-1-pro.json.
[](https://studiotvai.com/vram-requirements/kimi-k3-1-pro)
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.