Kimi K3 · Lesson 1 of 14
A 2.8-trillion-parameter model that runs 104 billion parameters at a time. One diagram explains where every innovation in the report belongs.
By the end of this lesson you should be able to draw the repeating block of Kimi K3 on a whiteboard and say what each piece is for. That drawing is the map for everything that follows. Every named innovation in the technical report sits somewhere on it.
Open-weight models had stalled around the 1-trillion-parameter mark while proprietary labs kept going. The Kimi team's argument is that the open ecosystem was scaling the wrong axis: lots of work on reasoning and reinforcement learning, applied to pretrained foundations that all sat at roughly the same size.1 K3 pushes both at once: a 2.8T foundation and a million-token context with heavy RL on top.
The headline number: 2.78 trillion total parameters, 104.2 billion activated per token. Understanding that gap is the first real concept, and everything else depends on it.
So K3 costs about as much compute per token as a 104B dense model, while carrying the stored knowledge of something 27 times larger. The tradeoff is memory and networking: you have to hold all 2.78T parameters somewhere, and route tokens to the right experts across many accelerators. This is why the launch post recommends supernode configurations with 64 or more accelerators.
2
Any MoE report gives you both numbers. The ratio between them is the single most useful thing on a config table: it tells you whether the model is expensive to run (activated) or expensive to host (total). K3 is deliberately cheap to run and expensive to host.
The report organises the whole architecture around one idea, stated in its own words: K3 is designed to scale information flow along three complementary dimensions: sequence length, network depth, and model width.
1
This framing is worth adopting, because it makes each component's job predictable before you know how it works. A token in a transformer needs to gather information from three places: other tokens, earlier layers, and its own channels. K3 has one named innovation for each.
Two more components sit outside this scheme. MoonViT-V2 is the vision encoder at the input, making K3 natively multimodal rather than a language model with images bolted on (Lesson 8). Per-Head Muon is the optimiser. It sits outside the network proper, but it is part of why training a 2.8T model at this shape works at all (Lesson 9).
Now the drawing that matters. K3's backbone is 93 layers, built from a block that repeats. Each block contains four attention layers in a fixed pattern, and every attention layer is followed by its own MoE feed-forward network.
Zoom out one level and that block sits in the middle of a short pipeline. Images and text both become token sequences before the backbone sees them, which is what natively multimodal means in practice.
Check the arithmetic, because it is a good habit with config tables: 23 blocks × (3 KDA + 1 MLA) = 92 layers, plus the one trailing Gated MLA = 93. That gives 69 KDA and 24 MLA, matching the report's table exactly.1
Only a quarter of K3's attention layers do the expensive thing. The other three quarters use a mechanism whose cost grows linearly with sequence length instead of quadratically, which is what makes a million-token context affordable. Lesson 2 is entirely about how that works.
The report's Table 1 compares K3 against its predecessor K2 directly. This is the densest single page of information in the paper, so it is worth learning to read.
| Property | Kimi K2 | Kimi K3 | What it tells you |
|---|---|---|---|
| Total parameters | 1.04T | 2.78T | Hosting cost ↑167% |
| Activated parameters | 32.6B | 104.2B | Compute per token ↑220% |
| Layers | 61 | 93 | Depth ↑52% |
| Hidden dimension | 7,168 | 7,168 | Unchanged — growth went elsewhere |
| Routed experts | 384 | 896 | Specialisation capacity ↑133% |
| Experts active / token | 8 | 16 | Combinations per token ↑100% |
| Shared experts | 1 | 2 | Always-on capacity |
| Latent MoE dimension | — | 3,584 | New: experts work at half width |
| Attention heads | 64 | 96 | Parallel read channels ↑50% |
| Attention mechanism | MLA | Hybrid KDA–MLA | New: the 3:1 pattern |
| Activation function | SwiGLU | SiTU-GLU | New: bounded, for low precision |
| Training context length | 128K | 1M | 8× |
| Vocabulary size | 160K | 160K | Unchanged |
| Vision encoder | — | 401M, 27 layers | New: native multimodal |
Two things stand out once you know what to look for.
First, the hidden dimension did not move. K2 and K3 both work in 7,168 channels. All the width growth went into the expert pool, not the residual stream. That is a deliberate choice about where capacity is cheap.
Second, most of the interesting entries are new mechanisms, not larger numbers. Hybrid attention, latent experts, a different activation function. The report attributes the combined effect of these to a 2.5× improvement in overall scaling efficiency over Kimi K2
1, meaning K3 reaches a given validation loss for roughly 40% of the training compute K2 needed.
The 2.5× figure comes from the authors fitting scaling-law curves on their own held-out validation data. No independent replication exists. It is a reasonable claim from a credible team, and it is also exactly the sort of number a lab has every incentive to present favourably. Cite it as "the report claims," not "K3 is 2.5× more efficient."
Answer from memory before scrolling back up. Getting one wrong is more useful than getting it right, because it marks what to reread.
A lab announces a 900B-parameter MoE with 40B activated. What does the gap tell you?
Total parameters set hosting cost, activated parameters set per-token compute. This is why K3 wants 64+ accelerators despite being compute-cheap for its size.
In one K3 block, what is the ratio of KDA layers to Gated MLA layers?
3:1, repeated through the backbone, with one extra Gated MLA at the very end so the final layer always performs global attention.
K3 grew from K2 on almost every axis. Which listed property stayed identical?
Hidden dimension held at 7,168 and vocabulary at 160K. Width grew through the expert pool instead of the residual stream, a bet that capacity is cheaper to add sparsely than densely.
Lesson 2 opens the box on Kimi Delta Attention, the mechanism in three quarters of K3's attention layers. The core idea is a shift in how a model remembers: instead of keeping every past token and re-reading them all, KDA maintains a fixed-size memory it continuously fades and overwrites. That change is what makes a million-token context something you can afford.