ALITEQ.

the biggest open AI model ever drops this week. you can download all 1.4 terabytes you just can't run it

Kimi K3's open weights land July 27. It's genuinely great and genuinely free. It also needs about 1.4TB of memory to load, which means the download is the easy part. Here's the real hardware math — and the far smaller model that gets you most of the way.

Lena FischerUpdated 1h ago9 min read
Kimi K3 'Open Frontier Intelligence' announcement page from Moonshot AI

On July 27, Moonshot AI does something remarkable: it hands the entire world the weights to Kimi K3, a 2.8-trillion-parameter model that just took the number-one spot on the Frontend Code Arena leaderboard — ahead of Claude Fable 5, GPT-5.6 Sol and GLM-5.2. Free to download, open to run, yours to keep. There's just one catch, and it's a big one: the download is about 1.4 terabytes, and loading it needs roughly that much fast memory. 'Open weights' does not mean 'runs on your machine.' It means you can watch the file finish downloading and then discover you have nowhere to put it. Let me show you exactly why, and what you can actually do about it.

Does it fit? — Kimi K3 at MXFP4 needs ≈1,400GB
Kimi K3 (MXFP4) needs ≈1400 GB
RTX 5090 (32GB)32 GBover 1368 GB
Mac Studio (512GB)512 GBover 888 GB
8× H100 (640GB)640 GBover 760 GB
8× B200 (1,440GB)1440 GBfits
Not a typo. Even a maxed 512GB Mac Studio and eight H100s fall short — you need a full 8×B200 datacenter node just to load the weights.

The MoE trap that fools everyone

Here's the mistake I see constantly. People hear 'Kimi K3 only activates ~50 billion parameters per token' — because it's a Mixture-of-Experts model using 16 of its 896 experts at a time — and conclude they only need enough memory for 50B parameters, which sounds almost reasonable. That's wrong, and it's the single most important thing to understand about running big MoE models. Mixture-of-Experts reduces how much compute each token needs, not how much memory the model occupies. The router can send the next token to any of the 896 experts, so all of them have to be resident in fast memory, ready. You don't get to load a tenth of the model. You load all 2.8 trillion parameters or it doesn't run.

So the memory math is unforgiving. Per the technical breakdown, Moonshot trained K3 with MXFP4 weights from the fine-tuning stage — not a crude after-the-fact compression — which gets the full weights down to about 1.4TB. At FP16 it would be 5.6TB. Even the aggressively-quantized 1.4TB figure is more memory than exists in any workstation you can buy. The good news, such as it is: the ~50B active parameters mean that if you can fit it, it runs faster than a 2.8T dense model would. The bad news is the 'if.'

Kimi K3 by the numbers

0.0T

total parameters

largest open model ever

0 GB

weights at MXFP4

~5.6TB at FP16

0B

active per token

16 of 896 experts — but all must load

Two NVIDIA graphics cards on a dark surface
A pair of consumer GPUs holds ~48GB. Kimi K3 needs roughly thirty times that — the gap isn't closable at home. · Unsplash

So who is the open release actually for?

If almost nobody can run it locally, why open-weight a 2.8T model at all? Because 'open weights' serves people who aren't running it on a desk. Research labs studying frontier architectures like Kimi's Delta Attention and Attention Residuals. Companies that will host it on their own datacenter hardware, free of Moonshot's API terms and pricing. Cloud providers who'll offer it. And the distillation ecosystem — smaller, runnable models trained to imitate K3's behaviour, which is where most of us will actually feel its influence. The open release is a gift to the ecosystem, not to your GPU. It also, pointedly, works around US compute-export limits by letting the weights travel where the chips can't.

What you can actually run at home

Here's the payoff, because 'you can't run it' is a useless place to stop. The gap between a 2.8T frontier model and what runs on a single good GPU is smaller than the headline numbers suggest — for most real work, anyway. A Qwen3-32B-class model on a single 24GB card handles coding, analysis and chat at a level that was frontier-grade a year ago. If you want to push toward the big leagues, Llama 70B on a dual-GPU build or a big Mac is the realistic ceiling for serious home setups. And renting a datacenter GPU by the hour is how you'd touch anything K3-sized without owning a server room.

Frontier model vs what you can run at home

Parameters

Kimi K3
2.8T (MoE)
Runnable at home
8B–70B

Memory needed

Kimi K3
~1,400 GB
Runnable at home
12–48 GB

Hardware

Kimi K3
8×B200 datacenter node
Runnable at home
1–2 consumer GPUs or a Mac

How you access it

Kimi K3
API / hosted / distills
Runnable at home
Download and run

Good enough for most work?

Kimi K3
Overkill locally
Runnable at home
Yes

The questions people actually ask

Can I run Kimi K3 on a single RTX 5090?
No — not remotely. The 5090's 32GB holds about 2% of Kimi K3's ~1,400GB of MXFP4 weights. There's no quantization or offloading trick that closes a gap that large; you'd be trying to fit a terabyte-plus model into 32GB. The 5090 is an excellent card for 32B-class models that fit its memory. Kimi K3 is a datacenter workload, full stop.
It's Mixture-of-Experts and only uses 50B parameters per token — doesn't that help?
It helps with speed, not with whether it fits. MoE means each token only runs through ~50B of the 2.8T parameters, so compute per token is manageable. But the router can pick any of the 896 experts for the next token, so all 2.8T parameters must be loaded in memory simultaneously. MoE reduces compute, never the memory footprint — that's the single most common misunderstanding about models like this.
What's MXFP4 and why does it matter here?
MXFP4 is a 4-bit floating-point format Moonshot used for K3's weights, trained in from the fine-tuning stage rather than bolted on afterward — which preserves quality better than crude post-training quantization. It's why the weights are 'only' ~1.4TB instead of ~5.6TB at FP16. It's genuinely impressive engineering; it just isn't enough to bring a 2.8T model into consumer reach. 4 bits per parameter times 2.8 trillion is still 1.4TB.
If I can't run it, why should I care about the open release?
Because you'll benefit from it indirectly and soon. Open weights let the whole ecosystem build on K3 — hosted APIs at lower prices, cloud offerings, and especially smaller distilled models that inherit some of its capability and do run on normal hardware. Frontier open releases raise the floor for everyone, including people who never touch the original weights. That's the real story of a 2.8T open model.

Kimi K3's open-weight drop is a genuine milestone — the largest open model ever, free to the world — and also a perfect illustration of the gap between 'open' and 'runnable.' If you want the frontier, you'll reach it through the API, a host, or the distilled models that follow. If you want something on your own hardware today, size a runnable model to your GPU in our VRAM calculator and start with what fits in 24GB. And if you're curious why K3 kept introducing itself as Claude, that's a different — and genuinely interesting — story.

AI & Local Compute Editor

Lena Fischer

Lena runs more GPUs at home than she'll admit to and has quantized more models than she's finished reading about. She writes about running AI on your own hardware — what actually fits, what's genuinely fast, and what the polished cloud demos quietly leave out.

The Aliteq brief

The tech worth knowing — hardware, AI, gaming, deals. No spam, unsubscribe anytime.

Keep reading