DeepSeek V4 Full Release (July 2026): Pricing, Benchmarks & How It Stacks Up Against GPT-5.6
TL;DR: After three months of waiting, DeepSeek V4 GA (full release) went live on July 20, 2026. The GA build adds targeted gains in Agent workflows, math reasoning, and code generation, and introduces peak-valley pricing for the first time — a signal that DeepSeek is moving from near-free usage toward disciplined commercial operations.
For AI developers, indie builders, and enterprise engineers, this article answers three questions: ① the full preview-to-GA timeline and architecture innovations (CSA+HCA, mHC, Muon); ② complete benchmarks including SWE-bench Verified 80.6%, plus head-to-head comparison with GPT-5.6 and Claude Fable 5; ③ how peak-valley billing saves money, and the API migration guide you must finish before July 24 when deepseek-chat and deepseek-reasoner are permanently retired.
01 What Happened Between the V4 Preview and GA Release?
Core pain points developers face right now:
- Legacy endpoints are expiring:
deepseek-chatanddeepseek-reasonershut down permanently on July 24. Production code that has not migrated will break. - Peak-valley billing complexity: GA introduces time-of-day pricing. Weekday peak hours double rates; batch jobs without scheduling will silently cost more.
- Closed-source flagship cost pressure: Claude Fable 5 output runs $50/M; GPT-5.6 Sol output is roughly $15/M. High-frequency Agent calls make bills hard to absorb.
- Long-context deployment friction: many models advertise 1M tokens, but KV Cache memory makes real deployment expensive.
| Date | Event |
|---|---|
| 2026-04-24 | V4 preview released and open-sourced (MIT), including V4-Pro (1.6T) and V4-Flash (284B) |
| 2026-05 | Production-tuned V4-Flash and V4-Pro builds shipped; API officially available |
| 2026-06 | V4-Pro output price permanently cut 75% (to $0.87/M tokens) |
| 2026-06-29 | Email to all API users announcing mid-July GA and first disclosure of peak-valley pricing |
| 2026-07-19 | Multiple developers received GA gray-release access; media reported "full release as soon as tomorrow" |
| 2026-07-20 | GA official release (publication date of this article) |
| 2026-07-24 | Legacy model names deepseek-chat and deepseek-reasoner permanently retired |
One-line takeaway: the preview was already strong; GA adds targeted Agent, math, and code gains on top, paired with a formal commercial billing system.
02 How Does DeepSeek V4 Architecture Make 1M Context Practical?
| Spec | V4-Pro | V4-Flash |
|---|---|---|
| Total parameters | 1.6 trillion (1.6T) | 284 billion (284B) |
| Active parameters per token | 49 billion (49B) | 13 billion (13B) |
| Transformer layers | 61 | 43 |
| Context window | 1,000,000 tokens | 1,000,000 tokens |
| Max output | 384K tokens | 384K tokens |
| Precision | FP4 (expert weights) + FP8 (remainder) | FP4 + FP8 mixed |
| Pretraining data | 33T+ tokens | 32T+ tokens |
| License | MIT | MIT |
Hybrid attention (CSA + HCA)
DeepSeek V4 drops the Multi-head Latent Attention (MLA) used in V2/V3 in favor of a hybrid of two new attention mechanisms:
- Compressed Sparse Attention (CSA): KV sequences are compressed 4× via Softmax-gated pooling; an FP4 "lightning indexer" performs top-k sparse selection (Pro selects top-1024, Flash top-512); a sliding window keeps the most recent 128 tokens. At 1M context, inference FLOPs are only 27% of V3.2.
- Heavily Compressed Attention (HCA): tokens are compressed 128× then processed with global dense attention to capture long-range dependencies; Flash uses HCA in the first 2 layers, then alternates CSA/HCA; Pro follows a similar pattern.
Net effect: at 1M tokens, KV Cache memory is only 10% of V3.2 (V4-Flash drops to 7%).
Manifold-Constrained Hyper-Connections (mHC)
An upgrade over standard residual connections: four-channel residual streams mixed through matrices satisfying doubly-stochastic constraints (Birkhoff polytope), keeping signal stable across 61 layers.
Muon optimizer
Training uses the Muon optimizer (not AdamW), applying Newton-Schulz orthogonalization to gradients for faster convergence and more stable training.
| Mode | Behavior | Best for |
|---|---|---|
| Non-think | No chain-of-thought; fastest response | Simple Q&A, routing |
| Think High | Explicit reasoning (<redacted_thinking> tags) | Medium-complexity tasks, code debugging |
| Think Max | Maximum reasoning effort; requires 384K+ context | Complex math, long-chain Agents |
Official recommended sampling: temperature=1.0, top_p=1.0 (all modes). For local deployment, see the ds4 high-memory Mac inference guide.
03 What Do DeepSeek V4 Benchmarks Show?
| Benchmark | DeepSeek V4-Pro | Claude Fable 5 | GPT-5.6 Ultra | Claude Opus 4.8 |
|---|---|---|---|---|
| SWE-bench Verified | 80.6% | 96.0% | Not separately published | ~69% |
| SWE-bench Pro | 55.4% | 80.3% | 78.1% | 69.2% |
| LiveCodeBench (Pass@1) | 93.5% | 88.1% | 87.4% | 83.2% |
| Codeforces Elo | 3,206 | — | — | — |
| Terminal-Bench 2.1 | 83.9% | 88.0% | 85.1% | 82.7% |
SWE-bench Verified measures real GitHub bug fixes. 80.6% is the current open-model high score, tied with Gemini 3.1 Pro. SWE-bench Pro is stricter; Claude Fable 5 leads at 80.3%.
Value comparison (Artificial Analysis):
- Claude Fable 5: Strategy & Ops index tasks cost $3.48 per run, score 50
- DeepSeek V4-Pro: same task class costs $0.03 per run, score 38
- DeepSeek V4-Flash: all six index task types stay below $0.04 per run
Fable 5 costs 116× more than V4-Pro while scoring only ~12 points higher (~31%). For most production workloads, V4-Pro value is unmatched.
04 DeepSeek V4 vs GPT-5.6 and Claude Fable 5: How Does Peak-Valley Pricing Work?
| Dimension | DeepSeek V4-Pro | GPT-5.6 Sol | Claude Fable 5 |
|---|---|---|---|
| Open source / self-hostable | MIT, yes | Closed | Closed |
| Context window | 1M tokens | Not disclosed | 1M tokens |
| Coding capability | Very strong (near Fable 5) | Very strong | Strongest |
| API output price (off-peak) | $0.87/M | ~$15/M | $50/M |
| Peak output price | $1.74/M | — | — |
| Data privacy | Private deployment possible | — | — |
Scenario selection: tight budget / high call volume / private deployment → V4-Pro or V4-Flash; peak coding capability → Claude Fable 5; complex algorithms + math reasoning → GPT-5.6 Sol / Ultra; massive log processing → V4-Flash (cache-hit input as low as $0.0028/M).
| Model | Billing item | Off-peak | Peak |
|---|---|---|---|
| V4-Pro | Input (cache hit) | ¥0.025 / $0.0035 / 1M | 2× |
| Input (cache miss) | ¥3.00 / $0.435 / 1M | ¥6.00 / $0.87 | |
| Output | ¥6.00 / $0.87 / 1M | ¥12.00 / $1.74 | |
| V4-Flash | Input (cache hit) | ¥0.02 / $0.0028 / 1M | 2× |
| Input (cache miss) | ¥1.00 / $0.14 / 1M | ¥2.00 / $0.28 | |
| Output | ¥2.00 / $0.28 / 1M | ¥4.00 / $0.56 |
Peak hours (Beijing time): weekdays 09:00–12:00 and 14:00–18:00. Cost-saving tactics: schedule non-real-time jobs off-peak; use Prompt Cache aggressively; route simple tasks to V4-Flash; DeepSeek promises 24-hour email notice before any billing change. Even at peak, V4-Pro output at $1.74/M is still 8.6× cheaper than Claude Opus 4.8 ($15/M).
05 deepseek-chat Is Going Away: How Do You Migrate Before July 24?
Critical deadline: legacy model names deepseek-chat and deepseek-reasoner stop responding permanently at 2026-07-24 15:59 UTC (July 24, 23:59 Beijing time).
| Legacy model | New model | Notes |
|---|---|---|
deepseek-chat | deepseek-v4-flash (non-think mode) | Fast; good for lightweight tasks |
deepseek-reasoner | deepseek-v4-flash (think mode) | Or upgrade to deepseek-v4-pro |
Six steps to complete migration:
- Search your entire codebase for every reference to
deepseek-chatanddeepseek-reasoner. - Choose replacement strategy: lightweight chat →
deepseek-v4-flash; complex reasoning →deepseek-v4-prowith Think High/Max. - Update OpenAI SDK calls: change only the
modelparameter; keepbase_urlathttps://api.deepseek.com. - Configure thinking mode: former reasoner users enable thinking via
extra_body; Think Max requires 384K+ context. - Validate in staging: run core use cases in pre-production before July 24; confirm latency and cost.
- Monitor peak-valley bills: after migration, schedule batch jobs by Beijing time and maximize cache hits to cut input cost.
client.chat.completions.create(model="deepseek-chat", messages=[...])
client.chat.completions.create(
model="deepseek-v4-pro",
messages=[...],
extra_body={"thinking": {"type": "enabled", "budget_tokens": 8000}}
)
V4 supports both OpenAI ChatCompletions and Anthropic Messages formats. With the Anthropic SDK, update only the model parameter; base_url="https://api.deepseek.com" stays the same.
Citeable hard data (DeepSeek official, 2026-07-20):
- SWE-bench Verified: 80.6% — highest open-model score, tied with Gemini 3.1 Pro
- KV Cache efficiency: at 1M context, only 10% of V3.2 memory (Flash 7%)
- Value ratio: V4-Pro $0.03 vs Fable 5 $3.48 per task — 116× cost gap
- Peak output price: V4-Pro $1.74/M, still 8.6× cheaper than Opus 4.8
- Migration deadline: 2026-07-24 23:59 Beijing time — legacy endpoints permanently retired
- Sources: DeepSeek official docs, arXiv:2606.19348, HuggingFace, Artificial Analysis
06 Is the GA Release Worth It? Summary and Production Close
DeepSeek V4 GA is one of the most important milestones in open models for 2026. Its value is not whether it beats Claude Fable 5 or GPT-5.6 today (not yet), but delivering the strongest open-model performance at one-tenth to one-hundredth the cost of closed flagships.
Best fit: enterprises that cannot send data offshore, budget-constrained indie developers, Agent engineers who need 1M-token context, and AI product teams chasing extreme value. Peak-valley billing adds cost complexity, but pricing remains highly competitive — DeepSeek's shift from "price disruptor" to "rules-based commercial platform" is a maturity signal, not a retreat.
If you still call deepseek-chat, finish API migration before July 24 or your service will break.
API-only access gets you onto V4 quickly, but three hidden costs remain: 1M-context Agents OOM on shared VPS hosts, batch inference during peak hours lacks stable scheduling infrastructure, and local MIT-weight inference needs high unified-memory hardware. For production DeepSeek Agent pipelines, ds4 local inference, or long-context MCP servers running 7×24, JEXCLOUD multi-region bare-metal Mac nodes are the better fit: dedicated Apple Silicon unified memory, no oversubscription jitter, launchd-resident gateways, 120-second delivery. See nodes and pricing on the JEXCLOUD pricing page.