Updated 2026-11-20
DeepSeek V4.1 Pro Release Timeline: Official Announcements and Updates
DeepSeek named V4.1 Pro in its September 10, 2026 Flash announcement. The only date it attached to the Pro API in that notice concerned a planned routing change for existing customers. As of November 20, DeepSeek had yet to announce a V4.1 Pro release date.
When did DeepSeek first name V4.1 Pro?
The August release explains why an application could already have a working Pro configuration in September. DeepSeek's September launch post mentioned the successor for the first time. The updated change log explains what happened to existing V4 Pro requests.
| Date in the official record | What happened | What it establishes for Pro |
|---|---|---|
| August 13 | DeepSeek released V4 Pro for general use on the web, in the app and through the API. | The API retained the deepseek-v4-pro ID. This is the V4 generation. |
| September 10 | DeepSeek introduced V4.1 Flash. Its launch notice described a temporary routing plan that would last until V4.1 Pro launched. | DeepSeek named V4.1 Pro as a future model and gave no release date. |
| September 14 (proposed) | The original notice proposed sending V4 Pro requests to Flash starting at 04:00 UTC. The updated change log says V4 Pro service and its billing would continue after September 14. | September 14 belongs to the routing proposal. Existing V4 Pro customers retained a Pro service. |
Which releases reached users in October and November?
On October 17, DeepSeek upgraded V4.1 Flash on the web, in the app and through the API. The Flash-1017 checkpoint kept the deepseek-flash request ID. A release post that mentions V4.1 and carries the October 17 date refers to this Flash update.
On November 13, DeepSeek added application features including file input, web search and URL reading to its existing APIs. The announcement identifies deepseek-flash as the model supporting those features. These notes document a change in what an application can do with Flash.
Where the November 8 web evaluation fits
An independent evaluator reported that the DeepSeek website passed 32 of 50 private agent tasks on all three attempts, up from 24 for the V4-Pro-0813 baseline. The evaluator could observe changes in the answers but could not identify which checkpoint served them. November 8 dates the report of those results.
What was public at the November 20 check?
DeepSeek's official model table still mapped deepseek-v4-pro to V4-Pro-0813. Its public V4 weights collection included V4-Pro-0813 and V4.1-Flash-1017. Neither source listed a V4.1 Pro release.
A dated DeepSeek announcement can establish when access begins and where. A model table can document an API version, while an official model card with downloadable weights can establish an open-weights release. Each can have its own date. For changes after November 20, use the status page, which tracks those channels individually.
FAQ
Does the 0813 suffix give a release date for V4.1 Pro?
0813 identifies the August 13 V4 Pro release. Likewise, 1017 identifies the October 17 V4.1 Flash release. Each suffix belongs to the checkpoint named alongside it.
If a launch starts with a public beta, which date should I use?
Use the date DeepSeek gives for the start of the beta and include its scope, such as invited web users. If API access opens later, cite that announcement separately when documenting an API release date.