Check my GPU

LLMs ·

Kimi K3 (2.8T)

Parameters
2,780B (104.0B active)
Architecture
Mixture of experts
Max context
1,024K tokens
License
kimi-k3
Released
2026-07

How to run it

Ollama

Ollama offers this only as a cloud model (it runs on Ollama’s servers, not your machine). To run it locally, use the GGUF files below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

huggingface.co/unsloth/Kimi-K3-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Kimi-K3-GGUF

Original weights · Hugging Face

Full-precision files from Moonshot AI, for fine-tuning, vLLM, Transformers.

huggingface.co/moonshotai/Kimi-K3 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Moonshot AI. The weights themselves download from Hugging Face.

github.com/MoonshotAI/Kimi-K3 (opens in a new tab)

git clone https://github.com/MoonshotAI/Kimi-K3

Links checked 5 days ago against Hugging Face, Ollama and GitHub.

Memory needed

Weights plus KV cache and runtime overhead. Leave a little extra free for the operating system and other apps.

KV cache: hybrid linear attention: about 1 in 4 layers keeps a latent (MLA) cache; active parameters as published.

Quantization Quality Weights Total at 8K context Total at 32K context Download
Q2_K Low 1,112 GB 1,113 GB 1,113 GB GGUF (UD-Q2_K_XL) · folder (opens in a new tab)
Q3_K_M Low 1,362 GB 1,363 GB 1,364 GB GGUF files (opens in a new tab)
Q4_K_M Good 1,696 GB 1,697 GB 1,697 GB GGUF (UD-Q4_K_XL) · folder (opens in a new tab)
Q5_K_M High 1,974 GB 1,975 GB 1,975 GB GGUF files (opens in a new tab)
Q6_K High 2,280 GB 2,280 GB 2,281 GB GGUF files (opens in a new tab)
Q8_0 Very high 2,947 GB 2,948 GB 2,948 GB GGUF (UD-Q8_K_XL) · folder (opens in a new tab)
F16 Full 5,560 GB 5,561 GB 5,561 GB Original weights (opens in a new tab)

Best hardware for Kimi K3 (2.8T)

None of the popular GPUs or Macs in our catalog can run this model. It needs datacenter hardware or several GPUs.

Check it on your own hardware

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.