Kimi K3 vs K2.7: Is the Upgrade Worth It for Coding?

Last updated: August 1, 2026

What Changed on August 1, 2026#

Kimi K2.7-Code arrived as a focused, efficient coding model. A month later, Kimi K3 changed the shape of the comparison. It is much larger, natively multimodal, holds up to 1 million tokens, and is designed for long agent runs that mix terminals, screenshots, research, and code. Two things landed since the original July 17 version of this post:

• K3's weights shipped on July 27 as promised - the 2.8T-parameter model (104B active) is on Hugging Face in native MXFP4 4-bit form with the MoonEP inference stack open sourced alongside it. The open-weights reality is now known, and it is datacenter-scale: roughly 1.5TB of VRAM at native MXFP4, with a 2-bit quant at about 1TB. See the K3 weights analysis and the access guide with verified prices.
• Third-party hosting routes opened up. Beyond Moonshot's API at $3/$15, K3 is now served on Together, Fireworks, Modal, SiliconFlow, and OpenRouter with a $0.30 cache-read rate, per the open-weights showdown.

That does not make K2.7 obsolete. For many coding tasks, the older model is still the more economical tool.

Kimi K3 vs K2.7 at a glance#

Prices were checked July 17, 2026 and re-verified August 1, 2026. K3 costs more than three times as much on uncached input and nearly four times as much on output through Moonshot's API.

Choose K3 for visual and repository-scale work#

K3's clearest advantage is not a few points on a code benchmark. It is the ability to keep vision inside the engineering loop.

For frontend work, game development, CAD, and browser automation, a model that can inspect its own output can catch problems that terminal-only feedback misses. Moonshot's examples show K3 generating interactive 3D experiences, capturing live screenshots, and refining the result. That workflow is materially different from asking a text-only model to infer a visual defect from a DOM tree.

The 1M-token window also gives K3 room for large repositories, long test histories, design references, and research material. If your agent repeatedly loses earlier decisions or requires aggressive context pruning, K3 is worth testing.

Keep K2.7 for bounded coding tasks#

K2.7 remains a good fit for code generation, bug fixes, refactors, and terminal tasks where the relevant context fits inside 256K. It is cheaper, its weights have been available for months, and the ecosystem has documented deployment paths.

The pricing gap compounds quickly. One million input tokens plus 100,000 output tokens costs about $1.35 on K2.7 at Moonshot's listed rates. The same uncached workload costs about $4.50 on K3. If the larger model does not improve completion quality enough to avoid retries or human intervention, the upgrade is wasted spend.

K2.7 also remains the safer self-hosting choice today. K3's weights are out, but the footprint answers the infrastructure question with a number most teams cannot meet: 1.5TB of VRAM at native MXFP4 is roughly 8x B200-class GPUs at the limit, and realistically 16x once you account for context and throughput. Individual developers and most startups are priced out; this is a cloud-provider or well-funded-lab deployment.

Benchmark claims need the same caution for both#

Moonshot reports that K3 performs competitively with its strongest comparison model on several kernel-optimization tasks. The numbers now include a widely cited one: Terminal-Bench 2.1 at 88.3 - the top score among open models - plus agent benchmark scores (MCPMark-Verified 94.5, ProgramBench 77.8, SWE-Marathon 42.0) that land at or above the closed frontier on most axes. These are useful signals, but the maker-reported figures deserve the same caution as any launch data. K3 does not report SWE-bench Verified, so that cluster is a gap in every public comparison.

K2.7's launch had the same limitation: impressive maker-reported improvements with incomplete independent coverage. The responsible comparison is a task suite built from your own repository:

1. Select 20 representative issues across debugging, refactoring, tests, and UI work.
2. Give both models the same tools and time limits.
3. Measure accepted patches, wall time, token cost, test pass rate, and human corrections.
4. Run visual tasks separately so K3's native vision has a fair chance to matter.

One blended score hides the reason you would pay for K3.

A practical routing strategy#

Use K2.7 as the default worker for bounded, text-first coding. Escalate to K3 when the task crosses one of three thresholds:

• The relevant working set does not fit comfortably inside 256K.
• Success depends on screenshots, diagrams, video frames, or other visual evidence.
• The agent must sustain a multi-hour loop across research, code, execution, and evaluation.

This keeps K3's higher price attached to the workloads that can benefit from its architecture. It also avoids turning a model launch into an all-or-nothing migration. On the API side, the $0.30 cache-read rate makes repeated-context agent loops on K3 noticeably cheaper than the uncached numbers suggest - worth modeling against your real prompt churn before the routing decision.

When to wait#

Wait if you need self-hosting on anything below server-class hardware, stable low-latency serving from a managed provider, or independently verified benchmarks. The K3 technical report and serving guidance have now landed, and they confirm the datacenter footprint. For most teams, K3 should enter the routing table before it replaces anything. Let measured task outcomes decide whether it earns more traffic.

FAQ#

Is Kimi K3 replacing K2.7-Code?#

K3 is the new flagship, but K2.7 remains useful for cheaper, bounded coding tasks and for teams that need downloadable weights that fit on manageable hardware. K3's 2.8T weights are open, but self-hosting them is a datacenter project (~1.5TB VRAM at native MXFP4).

Does Kimi K3 have a larger context window?#

Yes. K3 supports 1 million tokens compared with K2.7-Code's 256K window.

Is Kimi K3 cheaper than K2.7?#

No. At Moonshot's pricing, K3 costs $3/M uncached input and $15/M output. K2.7 costs $0.95/M input and $4/M output. Third-party K3 routes (Together, Fireworks, Modal, SiliconFlow, OpenRouter) list the same $3/$15 with a $0.30 cache-read rate.

Which model is better for frontend coding?#

K3 has the stronger capability mix because it can inspect screenshots and keep vision inside the coding loop. K2.7 can still handle ordinary component work when visual evaluation happens through a human or separate browser tool.

Is Kimi K3 open weights?#

Yes, with a license. Moonshot released the 2.8T K3 weights on Hugging Face on July 27, 2026 under a custom Kimi K3 License: free for most use, with a separate commercial agreement required for model-as-a-service businesses above $20M aggregate revenue over any 12 consecutive months. The MoonEP inference stack and AgentEnv eval environment are open sourced too.

Official Sources#

Sources#

• Kimi K3 official launch post - fetched July 17, 2026, re-verified July 31, 2026
• Kimi K3 API quickstart - fetched July 17, 2026
• Kimi K3 weights on Hugging Face - 2.8T MXFP4 release, license terms, 2-bit quant (verified July 31, 2026)
• Kimi K2.7-Code developer guide - reviewed July 17, 2026
• Kimi API platform - fetched July 17, 2026

Continue Reading#

• Kimi K3 Weights Land on HuggingFace - the 2.8T open release, benchmarks, licensing terms
• Where to Access Kimi K3 - every provider route with verified prices
• Kimi K3 Developer Guide - the model itself, in depth
• Open-Weights Coding Showdown - K3 vs GLM-5.2 vs DeepSeek V4 vs Qwen3
• Model Routing Recipes to Cut AI Spend - tiering K3 with cheaper workers