DeepSeek V4.1 Flash 资讯汇编DeepSeek V4.1 Flash: Everything Confirmed, Reported, and Rumored

Original official notice (posted verbatim by Juejin, the most reliable passage):

Collected: night of 2026-09-09 (the model has not been officially released yet)

Status: beta build deepseek-v4.1-flash-expires-on-0910 running, expiring September 10; release version planned for around September 10

Three credibility tiers: 【officially confirmed】 (verifiable on the official site / public docs) | 【platform-notice relay】 (logged-in notice, relayed verbatim by media) | 【community/unverified】

Original archives: 调研-v41flash-官方信源.md, 调研-v41flash-社区与媒体.md

0. The Whole Story in Three Sentences

1. This isn't just a price cut — it's a new model launch. V4.1 Flash is slated to go live around September 10, and the company says it comprehensively surpasses V4 Pro in performance, cost, speed, and total elapsed time.
2. The wildest part is the auto-routing. After V4.1 Flash goes live and before V4.1 Pro launches, API requests aimed at V4 Pro will all be switched to V4.1 Flash and billed at Flash's lower rates — users don't change a line of code, the model gets stronger and the money gets smaller.
3. The 12:00 repricing on September 10 clears the way for the new model. Cache-hit input drops 60% (¥0.05→¥0.02), misses drop 33%, output drops 11%.

2. Key Facts at a Glance

Original official notice (posted verbatim by Juejin, the most reliable passage):

"DeepSeek plans to officially release the V4.1 Flash model around September 10, 2026, Beijing time. After extensive internal and external testing, V4.1 Flash has comprehensively surpassed V4 Pro across every metric, including performance, cost, speed, and total elapsed time. In the spirit of an attitude of responsibility toward users, after V4.1 Flash officially goes live and before V4.1 Pro launches, we will route all requests to V4 Pro to V4.1 Flash and bill them at V4.1 Flash rates. If you find any problems in comparative testing between V4 Pro and V4.1 Flash, please report them to us promptly. Thank you for your support!"

3. Pricing Comparison (yuan / million tokens)

Peak/off-peak rules unchanged【officially confirmed】: peak = Monday–Friday 9:00–12:00 and 14:00–18:00; peak price = off-peak price ×2. For comparison, V4-Pro's current prices: cache hit / miss / output = 0.15 / 4.5 / 13.5 (off-peak), peak 0.30 / 9.0 / 27.0.

Mind the framing: only the cache-hit tier drops 60%. That was also the headline framing of yesterday's news flash, and it needs to be spelled out in the piece.

4. V4 Pro Auto-Routing (the Most Newsworthy Point This Time)

• Policy: after V4.1 Flash goes live and before V4.1 Pro launches, all API requests aimed at V4 Pro are routed to V4.1 Flash and billed at Flash rates
• User side: no code changes required (server-side routing)
• Boundaries: interim period only; what happens after V4.1 Pro launches is unstated
• Official reason: "an attitude of responsibility toward users"
• Risk note: the policy appears on no public documentation page, only in a logged-in notice

At current prices, for the same request switching from V4 Pro to V4.1 Flash (assuming the new prices match Flash's), the output tier drops from ¥13.5 to ¥4 and missed input from ¥4.5 to ¥1 — that's why "upgrade + price cut" happen at the same time.

5. Community Tests: One Consistent Direction vs. Dissenting Voices

The Consistent Direction: It Really Is Faster

The speed numbers are scattered wildly and none are official; when citing them you must include "who tested it and in what scenario":

The safe way to write it: say only that "the community broadly reports it's noticeably faster than V4-Flash"; any specific number must carry its source and scenario, plus a note that the differences come from peak/off-peak hours, task length, and test method.

Dissenting Voices (Must Include — Don't Cherry-Pick Only the Good News)

1. "It's actually more expensive than the previous generation" (one individual's 14 task tests, ~300 million tokens): for the same three-level mini game, V4.1 took 34.5 minutes end to end vs 30.5 minutes for V4 — fast tokens ≠ fast delivery; the generation time saved was eaten by tool-call verification (18.7 minutes waiting on tools vs 6.6 minutes)
2. Yicai (9/8): developers reported "¥10 in 5 minutes" and "dozens of yuan gone in an instant," and it withheld judgment on "lower cost," speculating that faster = more tokens swallowed per unit of time
3. Overthinking / breakdowns (r/LocalLLaMA): frequent failures under heavy load, failed file edits, 4M tokens and still no finished Frogger game; the Seven Wonders benchmark took 2 hours and cost $2.60 (competitors take about 30 minutes)
4. Self-identity confusion: asked "who are you," it said it was Claude — taken as evidence it "isn't being treated as a release version"
5. Uneven abilities: general web tasks ("browser operating system") fall flat, desktop resource loading misbehaves; rocket-simulation physics still trails top competitors
6. Beta nature: a Bilibili review notes video isn't supported yet and only images were tested; some third-party integrations haven't caught up and even report no image support at all

Positive Cases (Usable)

• 3D "S-shaped path parking": V4.1 finished in about 25.4 seconds with zero collisions; V4 took 11 minutes 27 seconds and rendered the main view upside down
• Small shop task (Node.js + shopping cart + coupon codes + idempotent checkout): V4.1 took 1 minute 41 seconds, V4 took 5 minutes 54 seconds
• One community coding comparison: V4.1 total 18 minutes 49 seconds / 11.59M tokens, vs Vision-Exp 30 minutes 11 seconds / 20.31M tokens (38% faster, 43% fewer tokens) — though note that V4.1 left some tasks unfinished
• No multimodal hallucination: the blogger "Xiangyang Qiaomu" (向阳乔木) posted a suit photo and the model answered "pinstripe suit"; zooming in confirmed it was right

6. How the Media Are Reading It

Consensus: almost uniformly read as a dimensional-strike play — "use Flash's price and speed to replace Pro's capability" — compounded by a simultaneous price cut, a rare "upgrade and price cut at once" strategy.

How each outlet frames it:

Point of divergence: centered on "whether costs really drop" — Yicai and individual testers withhold judgment.

7. Timeline (Verified)

Note: this price cut comes less than a month after the major price hike on August 13.

8. DSH Ecosystem Reaction (What We're Watching)

• NetEase Youdao LobsterAI announced on September 8 that it was the first to integrate the V4.1 Flash beta, the fastest mover in the ecosystem
• We found no DSH official support specifically for deepseek-v4.1-flash, and no dedicated "dsh-web Liang God mode flash" move either. Existing DSH / Liang God mode materials all center on V4 Flash and V4 Pro
• DSH's default channel mechanism (under the V4-native protocol, deepseek-v4-flash as the default high-throughput channel, auto-escalating to deepseek-v4-pro on hard problems) means: once V4.1 Flash ships, both the default channel and the escalation path may change with it — this is the point DSH users should really care about
• The official awesome-deepseek-agent already covers routing configuration for 20 tools (Claude Code, Cline, Codex, OpenCode, Roo, and others)
• We found no dedicated discussion threads about V4.1 Flash in the Claude Code / Cline / Roo communities

9. IPO and Capital Moves (All "Media Reports, Not Officially Confirmed")

Reuters on 9/9, citing two people familiar with the matter: DeepSeek has engaged CITIC Securities to prepare a STAR Market IPO and hopes to start the process this year; listing timing, fundraising size, and offering valuation are all undecided; neither DeepSeek nor CITIC Securities responded to requests for comment.

Other outlets' accounts (none officially confirmed):

• Current valuation around ¥500 billion; post-listing market cap could land in the ¥1.5–2.5 trillion range
• Opened financing for the first time in April; the first round closed in June, raising over ¥50 billion at a post-money valuation above ¥350 billion (Liang Wenfeng personally about ¥20 billion, Tencent ¥10 billion, the CATL ecosystem ¥5 billion, JD.com / NetEase / IDG ¥3 billion each)
• Second round launched in mid-July, pre-money valuation rising to ¥500 billion, cumulative fundraising across both rounds above ¥100 billion
• Revenue of about ¥475 million and a net loss of ¥715 million in the first seven months of 2026 (The Information / Bloomberg)

Writing advice: this item has nothing to do with the model itself and is entirely unconfirmed officially. If you mention it in a post, you must write "according to Reuters" and "not officially confirmed," and do not draw a causal link to the model release.

10. Sourcing Advice for Writing

Safe to write

• The new Flash price sheet effective 12:00 on September 10, the reductions, and the peak/off-peak rules (backed by an official notice + current published rates for comparison)
• The V4 Pro auto-routing policy (notice text available; note "the official notice says")
• The official "comprehensively surpasses V4 Pro" phrasing (label it as the official line; don't restate it as your own assessment)
• Beta details: 20 concurrency cap, expires 9/10, change the model name and it works

Handle with care

• Write the launch timing as "around September 10," not "released at 12:00 on September 10" (12:00 is the repricing time, not the release time)
• Speed numbers: must be "community test + who tested + what scenario," and note that the numbers range from 200 to 600
• "Lower cost": the official line conflicts with some developers' experience — give both sides
• Specs (context / output / concurrency): the company hasn't said, so don't fill them in

Must not write

• Treating "Liang Wenfeng's return/comeback" as fact ("Saint Liang is back" can only be relayed as a community joke)
• Writing the IPO as a done deal
• Treating community benchmark runs as official benchmarks
• Conflating the beta build (20 concurrency, offline 9/10) with the release version

One reminder: yesterday's news flash covered only the price cut and missed the bigger news of the new model launch and auto-routing. Before 12:00 on September 10, it's worth publishing a follow-up, or at least adding it in the comments on the original piece or a later push — otherwise readers will think this was just an ordinary price cut.

Appendix: Main Source List

Official: api-docs.deepseek.com (pricing page / changelog / news260813), platform.deepseek.com (logged-in notices) Media relays: Juejin (verbatim notice text), Shanghai Securities News, ITHome, Yicai, Qianjiang Evening News · Chao News, Zhidx, Huxiu, CNYES, KOCPC, STAR Market Daily, Reuters Community: SMZDM, Weibo long-form posts, APPSO, Zhihu, Xiaohongshu, Bilibili, X (@riba2534, @MiaAI_lab), Reddit r/LocalLLaMA (relayed by AGI Hunt), Rare Earth Juejin, CSDN, 8news.ai, Geeky Gadgets, FrontierNews, GPT Proto