Kimi-K2-Thinking VRAM & Memory Requirements
Specific checkpoints with sourced architecture and weight files. GGUF Q4_K_M (Unsloth): 579.24 GiB–680.01 GiB at 8,192 tokens, 1 sequence, FP16 KV, llama.cpp.
This result is an estimate, not a measured trace.Not verifiedFile-backed weights
Publisher and provenance
- PublisherMoonshot AI
- Hugging Face
moonshotai/Kimi-K2-Thinking - Revision
a51ccc050d73dab088bf7b0e2dd9b30ae85a4e55 - Total parameters1,026,408,240,256
- Active parametersUnknown / not independently sourced
- Layers61
- Query heads64
- KV heads64 (mla)
- Head dimension112
- Recorded context capability262,144
- Completenesspartial · partial
Active parameters describe tokens' routed compute, not the full resident model weight footprint. Full-resident weight estimates use total parameters.
Memory layers in this estimate
Artifact bytes, raw KV, engine extras, and total demand are separate. This is not a runtime trace.
- Weight artifact
- 578.58 GiB (621,245,226,208 bytes)
- Raw KV cache
- 0.54 GiB (575,668,224 bytes)
- Engine extras / workspace
- 0.13 GiB–100.89 GiB
- Total estimated demand
- 579.24 GiB–680.01 GiB
Published artifacts
| Quantization | Selected files | Bytes | Engine | Evidence |
|---|---|---|---|---|
| BF16 safetensors bf16 | 594,205,920,512 (553.40 GiB / 594.21 GB) | vllm, sglang, unspecified | file-metadata | |
| GGUF Q4_K_M (Unsloth) gguf-q4_k_m | 621,245,226,208 (578.58 GiB / 621.25 GB) | llama.cpp, ollama, unspecified | file-metadata | |
| GGUF Q5_K_M (Unsloth) gguf-q5_k_m | 728,735,735,328 (678.69 GiB / 728.74 GB) | llama.cpp, ollama, unspecified | file-metadata | |
| GGUF Q6_K (Unsloth) gguf-q6_k | 842,909,134,624 (785.02 GiB / 842.91 GB) | llama.cpp, ollama, unspecified | file-metadata | |
| GGUF Q8_0 (Unsloth) gguf-q8_0 | 1,091,053,887,872 (1,016.12 GiB / 1,091.05 GB) | llama.cpp, ollama, unspecified | file-metadata | |
| INT4 theoretical | No published file | 513,204,120,128 (theoretical) | — | theoretical |
Memory by quantization and context
Concurrent sequences = 1. KV defaults to FP16. The range includes documented runtime extras for the listed engine. These figures use the same core as the interactive calculator.
| Quantization | 2,048 tokens | 8,192 tokens | 32,768 tokens |
|---|---|---|---|
| BF16 safetensors | 554.16 GiB–639.46 GiB | 554.56 GiB–640.01 GiB | 556.17 GiB–642.20 GiB |
| GGUF Q4_K_M (Unsloth) | 578.84 GiB–679.43 GiB | 579.24 GiB–680.01 GiB | 580.85 GiB–682.28 GiB |
| GGUF Q5_K_M (Unsloth) | 678.95 GiB–796.86 GiB | 679.35 GiB–797.43 GiB | 680.96 GiB–799.71 GiB |
| GGUF Q6_K (Unsloth) | 785.28 GiB–921.58 GiB | 785.68 GiB–922.16 GiB | 787.29 GiB–924.44 GiB |
| GGUF Q8_0 (Unsloth) | 1,016.38 GiB–1,192.67 GiB | 1,016.78 GiB–1,193.25 GiB | 1,018.39 GiB–1,195.52 GiB |
| INT4 theoretical Theoretical rows are not downloadable artifacts. | 478.22 GiB–616.37 GiB | 478.62 GiB–616.94 GiB | 480.23 GiB–619.22 GiB |
Raw KV contribution
Related pages
Sources
- Kimi-K2-Thinking model card
- config.json — revision a51ccc050d73dab088bf7b0e2dd9b30ae85a4e55
- safetensors index — metadata.total_size=594205920512
- Artifact repo unsloth/Kimi-K2-Thinking-GGUF
Assumptions that affect this result
- Requested context is within the recorded native window of 262144 tokens.
- Full-resident weight estimates use total parameters, including inactive MoE experts.
- Activated parameter count is unknown / not independently sourced. Active parameters describe routed compute, not the full resident model weight footprint.
- Weight bytes come from the selected weight files only, not from every file in the repository.
- Download file size is not peak GPU memory. Runtime layout, allocator padding, and KV are extra.
- Weight bytes come from 13 published safetensors shards totaling 621245226208 bytes.
- Context budget is the number of cached tokens per sequence (prompt plus reserved generation).
- Concurrent sequences share one model replica; weights are not multiplied by sequence count.
Calculator
Loading catalog snapshot…
Search or pick a catalog checkpoint to see memory demand.
Search or pick a catalog checkpoint to see memory demand.