Kimi K3 Open Weights
July 27 Release: 2.8 Trillion Parameters — Can Closed-Source Premium Hold?

Five days until July 27, 2026: Moonshot AI will publish the full 2.8 trillion-parameter Kimi K3 weights on Hugging Face under a Modified MIT license — the world's first 3T-class open-weights model. Bottom line first: K3 is not a "Fable 5 killer." It ranks third on overall intelligence, but delivers near-frontier capability at roughly one-third the cost, plus two things closed models cannot offer — downloadable weights and a 1 million token context window. This guide covers the July 16 API launch vs July 27 weight release timeline, specs and benchmark tables, API pricing and cache-adjusted costs, the open weights vs open source distinction, 1.4 TB self-deployment reality, a six-step release-day checklist, industry significance, and FAQ — for developers tracking K3 weight downloads, local deployment feasibility, and whether closed-source premium pricing still holds.

01

Kimi K3 Release Timeline: API Launch vs Open Weights — Two Dates, Don't Mix Them Up

The most common search confusion: "K3 is already usable — what's launching on July 27?" Answer: July 16 brought the API and Kimi product suite. July 27 is when downloadable full model weights and the technical report go public.

DateEvent
2026-07-16Kimi K3 goes live via API, Kimi App, Kimi Work, and Kimi Code; Artificial Analysis publishes independent benchmarks the same day
2026-07-17World AI Conference (WAIC) opens in Shanghai; Xinhua frames K3 as a "national milestone"
2026-07-27Full weight download on Hugging Face (Modified MIT license) + technical report (architecture, training, evaluation details)

Kimi K3 Core Specs at a Glance

SpecDetail
Total parameters2.8 trillion (2.8T) — largest open-weights model to date
ArchitectureSparse MoE: Stable LatentMoE, 896 experts with 16 activated per token
AttentionKimi Delta Attention (KDA) + Attention Residuals (AttnRes) + Gated MLA
Context1,048,576 tokens (~1 million)
ModalitiesNative vision (text + image; video supported in product); text output
Weight formatMXFP4 weights + MXFP8 activations (4-bit quantization near training precision)
Scaling efficiency~2.5x improvement over K2 at equal compute
Training stabilityQuantile Balancing, Per-Head Muon optimizer, SiTU activation
Long-context decodeKDA delivers up to 6.3x decode speedup at 1M token context

K3 is not a "Fable 5 killer" — overall intelligence still ranks third. But at roughly one-third the cost it reaches near-frontier capability, with two things closed models cannot give you: open weights and a 1 million token context window.

Why the July 27 Weight Release Matters Now

  1. 01

    Data residency: Strict compliance scenarios require weights on-premises, not API calls

  2. 02

    Fine-tuning: Continued training on proprietary data requires full weights

  3. 03

    Massive call volume: At extreme scale, self-hosted hardware may beat API costs

  4. 04

    Ecosystem alignment: vLLM support for KDA and prefix caching lands with the weights

  5. 05

    Quantization follow-up: Expect Ollama and GGUF builds, as with the K2 series

  6. 06

    License verification: Read the Modified MIT text on release day — do not assume terms early

02

Kimi K3 Benchmarks: Where It Beats Claude Fable 5 and GPT-5.6 — and Where It Doesn't

Artificial Analysis Intelligence Index (independent review, July 16) ranks overall capability:

ModelAA Intelligence IndexRank
Claude Fable 559.9#1
GPT-5.6 Sol58.9#2
Kimi K357.1#3 / 189

Benchmarks Where K3 Leads or Ties

  • Frontend Code Arena: #1 — blind tests show developers prefer its UI code over Fable and Sol
  • Automation Bench, SpreadsheetBench 2: #1
  • BrowseComp: 91.2 (#1; with 1M context and no compression strategy, 90.4+)
  • SWE Marathon (extended coding sessions): 42.0 — well ahead (GPT-5.5 / GLM-5.2 collapse to teens here)
  • Terminal Bench 2.1: 88.3 — essentially tied with GPT-5.6 Sol at 88.8
  • Program Bench: 77.8 — slightly ahead of Sol at 77.6
  • FrontierSWE: 81.2 — well above Sol's 71.3 (but behind Fable 5's 86.6)

Areas Where K3 Still Trails

  • GDPval v2 Elo: 1668–1687 vs Fable 5's 1760 and Sol's 1748 — long-horizon judgment remains Fable's domain
  • DeepSWE: 67.5 vs Sol's 73.0
  • Hallucination rate: Up from K2.6 (Moonshot acknowledges); Reddit users report more hallucinations than top closed models in self-hosted apps
  • Conversation polish and stability: Single-session variance still lags Fable 5 / Sol
info

Moonshot's unusually honest stance: The company openly admits overall performance still trails Fable 5 and GPT-5.6 Sol, and lists known weaknesses — sensitivity to harness-returned reasoning content, over-eagerness on ambiguous intent. Each model used its own inference harness; independent third-party reproduction is ongoing.

03

Kimi K3 API Pricing: Sticker Price vs Real Cost After Cache Hits

ItemPrice (per million tokens)
Input (cache miss)$3.00
Input (cache hit, automatic caching)$0.30
Output$15.00

K3 pricing deliberately aligns with Western frontier tiers — a quality play, not a race to the bottom. It is the highest API pricing among Chinese LLM vendors, yet still well below Claude Opus 4.8 per-task cost.

Artificial Analysis measured a per-task cost of $0.94: 9.4% below GPT-5.6 Sol and 65.8% below Claude Fable 5. Coding workloads reportedly hit cache rates above 90%, so real bills sit far below sticker price.

OptionBest forBefore 7/27After 7/27
API ($3/$15)Most developers and enterprisesAvailableStill recommended
Self-deploy (64+ accelerators)Data residency / fine-tuning / extreme volumeWeights not publicOnly three scenarios justify it
Consumer local GPUPersonal experimentsNot viableNot viable — 4-bit ~1.4 TB
04

Is Kimi K3 Open Source? Open Weights vs Open Source Explained

The English community draws a sharp line between open weights (model weights only) and open source (training code and data included). Kimi K3 is the former — on July 27 Moonshot publishes full model weights under a Modified MIT license (exact terms confirmed on release day), not a full-stack open-source release.

What Happens on July 27

  • Full 2.8T weights go live on Moonshot's Hugging Face organization
  • Technical report published simultaneously (architecture, training, evaluation)
  • vLLM support for KDA and prefix caching ships with the weights
  • Expect follow-on Ollama and GGUF quantized builds, as with the K2 series
warning

Self-deployment reality (ignore "run it on your laptop" headlines): 4-bit weights are roughly 1.4 TB. Moonshot recommends a 64+ accelerator supernode with expert parallelism plus tensor parallelism for distributed inference. Reference point: the previous-gen 1T K2.7 Code needed ~577 GB VRAM at INT4; K3 is 2.8x larger. For most people, the API ($3/$15) is the correct answer.

Six-Step Release-Day Checklist

  1. 01

    Verify Hugging Face repo completeness: Check the full file list under Moonshot's HF organization

  2. 02

    Read the LICENSE: Review Modified MIT terms line by line — confirm commercial use and redistribution rules

  3. 03

    Watch for quantized builds: Track official or community MXFP4/NVFP4 packages

  4. 04

    vLLM / SGLang launch commands: Verify official examples for KDA and prefix caching

  5. 05

    Minimum viable hardware: Cross-check distributed inference requirements in the technical report — do not plan around consumer GPUs

  6. 06

    Independent long-context retests: Follow community benchmarks and r/LocalLLaMA reproduction threads

05

Why the July 27 Weight Release Challenges Closed-Source Premium

Four Industry Angles Worth Quoting

  1. 01

    Open vs closed gap nearly closed at the frontier: The intelligence gap shrank from hundreds of points to two or three — closed vendors can no longer justify premium pricing on capability alone

  2. 02

    Geopolitical backdrop: Release timed ahead of WAIC; one month earlier the U.S. briefly delisted Anthropic's Fable/Mythos models (restored July 1) — "regulators can shut down closed models, but not published open weights" is a new argument

  3. 03

    Chinese vendor wave: Z.ai GLM-5.2 (coding at Opus 4.8 level, 1/5 the price), DeepSeek V4 Pro (1.6T), MiniMax, and others — K3 is the peak of this wave

  4. 04

    Moonshot's comeback: Ranked seventh domestically after DeepSeek R1 in early 2025; rebuilt via K2 (Jul 2025) to K2.5 (Jan 2026) to K3 on an open-weights strategy

Key Data Quick Reference

  • Scale: 2.8T total parameters, 896 experts / 16 active, 1M token context (1,048,576)
  • Overall intelligence: AA Index 57.1 / Sol 58.9 / Fable 5 59.9 (#3 of 189)
  • Per-task cost: K3 $0.94 — 65.8% below Fable 5
  • API: $3 input / $0.30 cache hit / $15 output (per million tokens)
  • Self-deploy: ~1.4 TB at 4-bit; 64+ accelerators recommended
  • Coding highlights: Frontend Code Arena #1; SWE Marathon 42.0
  • Known gaps: Moonshot admits overall capability trails Fable 5 / GPT-5.6 Sol; hallucination rate up from K2.6

Sources: Official kimi.com technical blog, platform.kimi.ai; independent review by Artificial Analysis (July 16); coverage from VentureBeat and Northflank; community threads on r/LocalLLaMA and Hacker News. For deeper architecture analysis, see our Kimi K3 deep-dive review.

If you plan to wire K3 into Kimi Code-style long-session agents or iOS CI pipelines after 7/27, running CLI agents on a laptop or unstable Linux VPS often means insufficient memory, dropped sessions, and missing Xcode/Metal toolchains. For production environments that need stable SSH long sessions, DerivedData caching, and iOS CI/CD automation, NodeMini Mac Mini cloud rental is usually the better fit — dedicated nodes with second-level provisioning keep agents and build jobs running on a real Mac. See rental pricing for details.

FAQ

Frequently Asked Questions

Full 2.8T weights are scheduled to go live on Moonshot's Hugging Face organization on July 27, 2026, alongside a technical report. The API and Kimi product suite launched on July 16.

The accurate term is open weights, not fully open source. Overall intelligence favors K3 (2.8T vs DeepSeek V4 Pro 1.6T, 1M vs 128K context), but DeepSeek output costs only $3.48/M — significantly cheaper. Choose DeepSeek for cost sensitivity; choose K3 for long code and document workloads.

Free kimi.com accounts can use K3. API pricing is $3/$15 per 1M tokens, with cache hits at $0.30/M. For stable agent runtime environments, see Mac Mini rental rates.

4-bit weights are roughly 1.4 TB. Moonshot recommends a 64+ accelerator supernode — consumer GPUs cannot host this model. Self-deployment only makes sense for data residency, fine-tuning, or extreme call volume; everyone else should use the API.

Overall intelligence: K3 ranks third (57.1), behind Fable 5 (59.9) and GPT-5.6 Sol (58.9). K3 leads on Frontend Code Arena, SWE Marathon, and BrowseComp. Long-horizon reasoning and hallucination control still trail top closed models. For operational questions, see the help center.

Modified MIT license. Read the full LICENSE file on release day — do not assume terms before July 27.