Total parameters
2.8T tells you Kimi K3 is frontier-scale and far beyond ordinary single-GPU local models.
Model size
Kimi K3 size explained: 2.8T total parameters, 104B activated parameters, 896 experts, 1M context, and what size means in practice.
| Metric | Value | Meaning |
|---|---|---|
| Total parameters | 2.8T | Full model scale |
| Activated parameters | 104B | Approximate active compute per token |
| Experts | 896 total, 16 selected per token | Sparse MoE routing |
| Context length | 1,048,576 tokens | Long-context ceiling listed in official materials |
| Quantization | MXFP4 weights and MXFP8 activations | Serving format details that affect memory math |
Kimi K3 is listed by Moonshot as a 2.8T-parameter Mixture-of-Experts model with 104B activated parameters per token, 896 experts, 16 selected experts per token, and a 1,048,576-token context length.
The important part is that active parameters do not make the full checkpoint small. For self-hosting, the full weights still need to be stored and served across a large accelerator setup.
Use this section to keep the next step practical before you touch accounts, files, infrastructure, or hardware.
| Check | Look for | Why it matters |
|---|---|---|
| Read the official source | Start with the model card, help center, docs, or official product page before trusting summaries. | Model names, limits, and prices change. |
| Name the path | Decide whether you need a hosted app, API call, local client, or full self-managed deployment. | Different paths have different costs and account boundaries. |
| Check the boundary | Keep login, payment, API keys, private files, and account settings on the official surface. | A public guide should help you choose, not handle sensitive actions. |
| Keep evidence | Save the source link, date, version, and practical next step that shaped your decision. | This makes later review easier for a team. |
2.8T tells you Kimi K3 is frontier-scale and far beyond ordinary single-GPU local models.
104B active parameters per token helps explain MoE efficiency but does not eliminate the need to store the full expert set.
1M context supports very long inputs when the product surface and plan allow it, but it should still be prepared carefully.
2.8T Full model scale
104B Approximate active compute per token
896 total, 16 selected per token Sparse MoE routing
1,048,576 tokens Long-context ceiling listed in official materials
MXFP4 weights and MXFP8 activations Serving format details that affect memory math
Yes, official Kimi K3 materials list 2.8T total parameters.
No. The full weights still need to be stored and served.
Long context increases cache and memory pressure during real use.