KIMI K3 OPEN
WEIGHTS_
JULY_27.
Direct answer: Moonshot AI will release the full weights of Kimi K3 — a 2.8-trillion-parameter MoE model with a 1M-token context window (1,048,576) — on July 27, 2026, under a Modified MIT license. The API has been live since July 16. This pillar guide covers every material point from our research: two-phase timeline, full spec table, benchmarks vs Claude Fable 5 and GPT-5.6 Sol, API pricing with caching math, open weights vs open source, 1.4TB self-host reality, a July 27 release checklist, industry analysis, and FAQ. For architecture deep-dives see our July 17 K3 review.
30-Second Read
| Headline | World's largest open-weight model at 2.8T · ranks #3 overall · frontier-adjacent at ~1/3 the cost |
| Two dates | Jul 16 API + Kimi stack · Jul 27 full weights + tech report |
| What closed models can't give you | Downloadable weights + 1M context |
| Not a "Fable 5 killer" | AA Index 57.1 · wins frontend/automation/long coding sessions |
| Self-host | ~1.4 TB at 4-bit · 64+ accelerators · API for most teams |
1. Pain Points: Why July 27 Matters
- "API live" ≠ "weights downloadable." K3 has been callable since July 16 via Kimi App, Kimi Work, Kimi Code, and the API — but full weights arrive July 27. That confusion drives the highest pre-release search volume.
- Closed-source premium is under pressure. The open-closed intelligence gap at the frontier has shrunk to roughly 2–3 index points. Vendors can no longer justify premium pricing on capability alone.
- Self-host expectations need honest calibration. r/LocalLLaMA hates "run on your laptop" clickbait. At 1.4 TB (4-bit) and 64+ accelerators, credibility beats hype — and earns backlinks.
2. Kimi K3 Release Date: API Launch vs Open Weights
| Date | Event |
|---|---|
| 2026-07-16 | Kimi K3 via API / full Kimi product stack; Artificial Analysis independent eval same day |
| 2026-07-17 | WAIC Shanghai opens; Xinhua frames K3 as a national milestone |
| 2026-07-27 | Full weight download (Hugging Face, Modified MIT) + technical report |
3. What Is Kimi K3? Key Specs at a Glance
| Spec | Detail |
|---|---|
| Total parameters | 2.8 trillion — largest open-weight model ever |
| Architecture | Sparse MoE: Stable LatentMoE, 16 of 896 experts active per token |
| Attention | Kimi Delta Attention (KDA) + Attention Residuals (AttnRes) + Gated MLA |
| Context | 1,048,576 tokens (1M) |
| Modalities | Native vision (text + image; video in product); text output |
| Weight format | MXFP4 weights + MXFP8 activations (native low-precision training) |
| Scaling efficiency | ~2.5× vs K2 at equal compute (per Moonshot) |
| Training stability | Quantile Balancing, Per-Head Muon optimizer, SiTU activation |
| Long-context decode | KDA up to 6.3× decode speedup at 1M tokens |
4. Kimi K3 Benchmarks vs Claude Fable 5 and GPT-5.6
4.1 Artificial Analysis Intelligence Index
| Model | Score |
|---|---|
| Claude Fable 5 | 59.9 |
| GPT-5.6 Sol | 58.9 |
| Kimi K3 | 57.1 (#3 / 189) |
Moonshot publicly acknowledged trailing Fable 5 and GPT-5.6 Sol at launch — plus known weaknesses (sensitivity to harness-returned reasoning, over-eagerness on ambiguous intent). That honesty survives Reddit scrutiny better than "Claude killer" headlines.
4.2 Where Kimi K3 Wins
| Benchmark | K3 |
|---|---|
| Frontend Code Arena | #1 (blind dev preference over Fable/Sol UI code) |
| Automation Bench / SpreadsheetBench 2 | #1 |
| BrowseComp | 91.2 (#1; 1M context no-compression strategy) |
| SWE Marathon | 42.0 (GPT-5.5 / GLM-5.2 collapse to teens) |
| Terminal Bench 2.1 | 88.3 (near Sol 88.8) |
| Program Bench | 77.8 (edges Sol 77.6) |
| FrontierSWE | 81.2 (beats Sol 71.3; trails Fable 5 86.6) |
4.3 Where It Still Falls Short
- GDPval v2 Elo: 1668–1687 vs Fable 5 1760, Sol 1748 — long-horizon judgment remains Fable territory
- DeepSWE: 67.5 vs Sol 73.0
- Hallucination rate up vs K2.6 (official admission); Reddit reports higher hallucination in self-hosted apps vs top closed models
- Dialog polish and session variance still trail Fable 5 / Sol
Caveat: benchmarks run through different harnesses — always note eval date (Artificial Analysis, July 16, 2026) in your acceptance docs.
5. Kimi K3 API Pricing (and Real Cost With Caching)
| Item | Price (per 1M tokens) |
|---|---|
| Input (cache miss) | $3.00 |
| Input (cache hit, automatic) | $0.30 |
| Output | $15.00 |
Pricing aligns with Western quality tiers — highest among Chinese vendors today, yet still well below Claude Opus 4.8 per-task cost. Artificial Analysis: $0.94 per task — 9.4% below GPT-5.6 Sol, 65.8% below Claude Fable 5. Coding workloads report >90% cache hit rates; surface sticker price overstates real spend.
6. Is Kimi K3 Open Source? Open Weights vs Open Source
Use open weights in titles and H1s — not "open source" alone. K3 releases full downloadable weights under Modified MIT (final LICENSE text confirmed July 27). Training code and datasets are not part of the drop. That distinction targets queries like is kimi k3 open source and kimi k3 open weights without alienating HN readers.
7. Can You Run Kimi K3 Locally? Hardware Requirements
Not on consumer hardware. 4-bit weights ≈ 1.4 TB. Moonshot recommends a 64+ accelerator super-node with expert parallelism + tensor parallelism. Reference: K2.7 Code (1T) needed ~577 GB VRAM at INT4 — K3 is 2.8× that scale.
Self-hosting only makes sense for: strict data residency / air-gap, fine-tuning on proprietary data, or volume where owned clusters beat API spend. Everyone else: API at $3/$15.
8. What Happens on July 27
- Full 2.8T weights on Moonshot's Hugging Face org
- Technical report (architecture, training, eval details)
- vLLM support for KDA / prefix caching ships with weights
- Expect Ollama / GGUF quant builds to follow (as with K2 series)
9. July 27 Release-Day Checklist (5 Steps)
- Verify Hugging Face repo completeness — config, tokenizer, shard index
- Read LICENSE verbatim — Modified MIT terms and restrictions
- Check quant artifacts — MXFP4/NVFP4/GGUF availability
- Validate vLLM / SGLang launch commands and KDA prefix caching
- Confirm minimum hardware and independently re-test 1M context (don't trust harness-only numbers)
10. Five Action Steps Before and After Weights Drop
- Before Jul 27: Baseline your workloads on API — measure cache hit rate on coding tasks.
- Within 2 hours of release: Update pages from "scheduled" to "now available" + HF link — Google re-ranks fast on
kimi k3 download. - Route by workload: K3 for frontend/UI, spreadsheets, SWE Marathon sessions; Fable 5 / Sol for deep reasoning and low-hallucination dialog.
- Self-host gate: No 64-GPU cluster → wait for community GGUF/distills (track Ollama progress from August).
- Multi-vendor stack: LiteLLM / OpenRouter — K3 primary for coding, Fable/Sol reasoning fallback.
11. Why the July 27 Weights Release Matters
① Open-closed gap nearly closed at the frontier — from hundreds of points to ~2–3; premium pricing narrative weakens.
② Geopolitical backdrop: Release timed before WAIC; US briefly pulled Anthropic Fable/Mythos (restored July 1) — "regulators can shut closed models, not published open weights."
③ China's model wave: GLM-5.2, DeepSeek V4 Pro (1.6T), MiniMax — K3 is the peak of this cycle.
④ Moonshot's comeback: Rank fell to #7 domestically after DeepSeek R1 in early 2025; rebuilt via K2 → K2.5 → K3 open-weight strategy.
12. Deep Insight: What K3 Means for Mac Developers
K3 is engineering, not vanity parameter stacking. KDA + Stable LatentMoE make 1M-token workflows operable — Cursor + K3 API for whole-repo analysis and Kimi Code for SWE Marathon-class stress tests are pragmatic today on Mac.
Post-release, expect the DeepSeek playbook: vLLM first → GGUF/Ollama → MLX community quants. Track independent re-tests on r/LocalLLaMA — the "benchmaxxed" debate and open-weight definition fights are part of the signal.
Sources: kimi.com/en/blog/kimi-k3, platform.kimi.ai, Artificial Analysis (Jul 16), VentureBeat, Northflank, atoms.dev / llmrumors, r/LocalLLaMA, Hacker News.
13. FAQ
When will Kimi K3 weights be released? July 27, 2026 on Hugging Face + tech report. API live since July 16.
Is Kimi K3 really open source? Open weights under Modified MIT — not fully open source (no training code/data).
How much does Kimi K3 cost? $3/$0.30/$15 per million tokens; ~$0.94/task measured, 65.8% below Fable 5.
Can I run Kimi K3 on a consumer GPU? No — ~1.4 TB at 4-bit, 64+ accelerators recommended.
Is Kimi K3 better than Claude Fable 5 / GPT-5.6? Overall #3; leads coding/automation benchmarks, trails reasoning polish.
What license does Kimi K3 use? Modified MIT — confirm LICENSE file on release day.
14. Closing: API Anywhere, Agent Stress Tests Belong on a Mac Node
Signing up for Kimi API and switching OpenRouter routes works on Windows or Linux. But Cursor + K3 million-token coding, Kimi Code marathon regressions, and batch 1M-context jobs run smoother on Apple Silicon unified memory + Metal.
Practical split: daily driver on API; offload agent stress tests and long-context batches to a MACGPU remote Mac mini M4 node — on-demand, SSH-isolated. Before weights land July 27, keep agent workloads off your primary machine.