selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

moonshotai logo

Kimi-K3.1-Pro

moonshotai·Instruct·released 2 Nov 2026

kimi-k3.1-pro2.78TMoE1M ctx ≈1701 GB
Your GPU
hf download moonshotai/Kimi-K3.1-Pro
Setup ↓

Kimi K3.1 Pro is an open-weight, natively multimodal agentic model, and our most capable 3T-class model to date. Post-trained from Kimi K3 with large-scale joint reinforcement learning across hundreds of downstream domains, it is the first model in the K3.1 series.

Notify me when

How much VRAM does Kimi-K3.1-Pro need?

At Q4_K_M Kimi-K3.1-Pro needs about 1701 GB with an 8K context (1701 GB at Q4, 5490 GB at full precision). Pick your GPU to see what fits and how fast it runs.

--vram
any
--gpus
--quant

Needs: ≈1701 GB · Q4_K_M · 8K context — Pick a GPU to check the fit.

Change quant, context or KV cache to compare
Advanced: context 8K · KV cache 16-bit
Context
KV cache

Smallest GPU for each quant and context (KV cache 16-bit)

Quantisation8K16K32K64K128K1M
Q3_K_M
Q4_K_M
Q5_K_M
Q6_K
Q8_0
FP16

≤16 GB card24–32 GB48–96 GBmore

QuantisationQualityWeightsKV cacheTotal
Q2_KHeavy lossSmallest, noticeably worse qualityHeavy loss851 GB 52 GB≈947 GB
Q3_K_MNoticeable lossSmall, some quality lossNoticeable loss1265 GB 52 GB≈1382 GB
Q4_K_MrecommendedSmall lossRecommended default for local useSmall loss1570 GB 52 GB≈1701 GB
Q5_K_MNear-losslessNear-lossless for most tasksNear-lossless1842 GB 52 GB≈1986 GB
Q6_KNear-losslessPractically losslessNear-lossless2133 GB 52 GB≈2292 GB
Q8_0LosslessLossless in practice, twice the size of Q4Lossless2751 GB 52 GB≈2941 GB
FP16 / BF16LosslessFull precision, as releasedLossless5178 GB 52 GB≈5490 GB

Estimates for 8K tokens of context: weights + KV cache + runtime overhead. All experts stay in memory, but only the active ones are read per token. Speed assumes memory-bound decoding at your GPU’s bandwidth. Pick a GPU above and the fit column checks every row against it.

How to pick a quant

Take the biggest quant that fits with room left for context. Q4_K_M is the usual sweet spot. Below Q4 quality drops fast, above Q6 you mostly pay memory for nothing. Big models (70B+, large MoE) tolerate low quants better than small ones.

  • LosslessF16, Q8_0
  • Near-losslessQ6_K, Q5_K_M
  • Small lossQ5_K_S, Q4_K_M, IQ4_NL, IQ4_XS, Q4_K_S
  • Noticeable lossQ4_0, Q3_K_L, Q3_K_M, IQ3_M
  • Heavy lossIQ3_XXS, Q3_K_S, IQ2_M, Q2_K

Typical quality loss, not measured per model. Tiers come from KL divergence against FP16 on Llama 3 8B: llama.cpp perplexity README: LLaMA 3 8B scoreboard (KLD and ΔPPL vs FP16, Wikitext-2); llama.cpp quantize tool: ΔPPL per quant type @ Llama-3-8B

How much context fits?

Model quant
KV cache

At 8K context, Q4_K_M needs ≈1701 GB(1570 GB weights + 52 GB KV cache + 79 GB overhead). Pick a GPU above to see how much context fits.

02000400060008000100001K2K4K8K16K32K64K128K256K512K1MGB

Weights + overheadKV cache

Speed vs quality per quant

Smaller quants run faster and fit in less memory, but lose quality.

Q2_KQ3_K_MQ4_K_MQ5_K_MQ6_KQ8_0F16

Fits in VRAMTight fitCPU offload✕ won't runQuality is typical KL divergence vs FP16, not measured for this model.

Real-world speed of Kimi-K3.1-Pro

Tokens per second measured by people running it at home. A GPU shows a median once 3 reports agree on the same setup. Reports far from our estimate wait for a review. Measure yours with llama-bench →

No medians yet. Be one of the first 3 to report a setup.

All reports

Run Kimi-K3.1-Pro locally

These commands load the original weights from Hugging Face.

Ask about an imagedocs
python
from transformers import pipeline

pipe = pipeline("image-text-to-text", model="moonshotai/Kimi-K3.1-Pro", dtype="auto", device_map="auto")
messages = [
    {
        "role": "user",
        "content": [
            {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/bee.jpg"},
            {"type": "text", "text": "Describe this image."},
        ],
    }
]
out = pipe(text=messages, max_new_tokens=256)
print(out[0]["generated_text"][-1]["content"])

Install Transformers

Benchmarks

BenchmarkScoreRankSourceDate
GPQA Diamond94.2%#2 / 104 self-reportedNov 2026
Humanity's Last Exam51.1%#7 / 63 self-reportedNov 2026
MMMU-Pro84.1%#1 / 25 self-reportedNov 2026

Self-reported scores come from the model card and are not independently verified. Rank is among all models with a score on that benchmark.

Quantised versions and downloads

About Kimi-K3.1-Pro

Kimi K3.1 Pro is an open-weight, natively multimodal agentic model, and our most capable 3T-class model to date. Post-trained from Kimi K3 with large-scale joint reinforcement learning across hundreds of downstream domains, it is the first model in the K3.1 series. With a 1-million-token context window, Kimi K3.1 Pro delivers substantial improvements in coding, 3D creation, financial research, factual accuracy, and other agentic capabilities. Architecture Mixture-of-Experts (MoE) Total Parameters 2.8T Activated Parameters 104B Number of Layers 93 Number of Dense Layers 1 Attention-Layer Composition 69 KDA + 24 Gated DSA * Attention Hidden Dimension 7168 Number of Attention Heads 96 DSA Index Head Dimension 128 DSA Index Number of Heads 32 DSA Index Top-K 2048 Latent MoE Dimension 3584 MoE Hidden Dimension (per Expert) 3072 Number of Experts 896 Selected Experts per Token 16 Number of Shared Experts 2 Vocabulary Size 160K Context Length 1048576 Attention Mechanism KDA & Gated DSA Activation Function SiTU-GLU Vision Encoder MoonViT-V2 Parameters of Vision Encoder 401M Quantization MXFP4 weights / MXFP8 activations (quantization-aware training) Modality Text, Image * Compared with Kimi K3, we replace the full-attention Gated MLA layers with Gated DeepSeek Sparse Attention (Gated DSA) layers for more efficient long-context modeling.

Full model card on Hugging Face →

Alternatives to Kimi-K3.1-Pro

All alternatives →
moonshotai logo

Kimi-K3

moonshotai·Vision

≈1701 GB

Kimi K3 is an open-weight, native multimodal agentic model and our most capable model to date. It is a 2.8T-parameter model built on Kimi Delta Attention (KDA) and Attention Residuals (AttnRes), with native vision capabilities and a 1-million-token context window.

2.78T1M ctx kimi-k3
765.8KJun 2026ollama
meituan-longcat logo

LongCat-2.5

meituan-longcat·Vision

≈1070 GB

LongCat-2.5 is a native multimodal MoE model for long-horizon agentic tasks, with 1.6 trillion total parameters and approximately 48 billion activated per token.

1.78T512K ctx MIT
2.5KNov 2026
thinkingmachines logo

Inkling

thinkingmachines·Vision

≈567 GB

Inkling is a general-purpose multimodal model that accepts text, image and audio inputs and generates text outputs. It is intended for use in English and other languages, and across multiple coding languages.

952BA18.1B1M ctx Apache 2.0
1.4MJul 2026gguf
moonshotai logo

Kimi-K2.7-Code

moonshotai·Vision

≈632 GB

Kimi K2.7 Code is a coding-focused agentic model built upon Kimi K2.6. With substantial improvements on real-world long-horizon coding tasks, it strengthens end-to-end task completion across complex software engineering workflows while improving token efficiency, reducing thinking-token usage by…

1.03TA33.3B256K ctx modified-mit
321.9KJun 2026ollama
deepseek-ai logo

DeepSeek-V4.1-Flash

deepseek-ai·Vision

≈454 GB

We introduce DeepSeek-V4.1-Flash, a multimodal Mixture-of-Experts (MoE) model with 552B backbone parameters and support for contexts of up to one million tokens. The model natively processes images and text, and generates text autoregressively.

763BA188B1M ctx MIT
1.5MSept 2026gguf
moonshotai logo

Kimi-K2.6

moonshotai·Vision

≈632 GB

Kimi K2.6 is an open-source, native multimodal agentic model that advances practical capabilities in long-horizon coding, coding-driven design, proactive autonomous execution, and swarm-based task orchestration.

1.03TA33.3B256K ctx modified-mit
202.3KApr 2026ollama

Kimi-K3.1-Pro FAQ

How much VRAM does Kimi-K3.1-Pro need?
About 1701 GB at Q4_K_M with an 8K context. Q8_0 needs about 2941 GB and full precision about 5490 GB. Longer contexts need more memory for the KV cache.
Can Kimi-K3.1-Pro run on a consumer GPU?
Not comfortably on a single one: it needs about 1701 GB at Q4. Split it over several GPUs, use a large unified-memory machine, or offload part of it to system RAM.
Can I use Kimi-K3.1-Pro commercially?
Unclear. It is released under kimi-k3.1-pro. Custom licence: read the model card before using it commercially. Check the licence on the model card before using it in a product.
What is the context length of Kimi-K3.1-Pro?
1,048,576 tokens (1M). The full window needs far more memory than an 8K context.
How do I run Kimi-K3.1-Pro locally?
It runs with Transformers. Each has copy-paste examples in its docs.

Data from Hugging Face, the model card and public leaderboards. Memory and speed figures are estimates; real numbers depend on the runtime, context length and drivers. Always check the licence yourself before commercial use.