When Is DeepSeek V5 Coming Out? The Honest 2026 Answer

Short version, because I respect your time: nobody knows, and anyone giving you a hard date is guessing. As of June 2026, there is no DeepSeek V5. No name, no roadmap, no release date, nothing in the official API docs. If you landed here because a thumbnail somewhere promised "V5 DROPS JULY 24," I have some mildly annoying news about where that date actually comes from.

I run DeepSeek in production every day, so this question matters to me beyond idle curiosity. It's the model quietly doing most of the work behind my agent setup, and if a successor is coming I'd like to know whether to plan around it or not. So I went and checked the primary sources instead of trusting the rumour mill. Let me walk you through what's real, what's noise, and what I'd actually watch.

Spoiler: the most repeated "evidence" for an imminent DeepSeek V5 is a misreading of a routine deprecation notice. We'll get to that.

The short answer: no date, and that's okay

DeepSeek has not announced V5. Not a name, not a window, not a teaser. The only models DeepSeek officially lists right now are V4 Pro and V4 Flash. Everything else is people reading tea leaves.

It helps to look at the cadence. DeepSeek shipped V3, then V3.1, then V3.2, then V4, all inside roughly a year. V4 itself only landed on 24 April 2026. That's recent. A clean, ground-up V5 this soon would break the pattern hard. What's far more likely in the near term is a tuned V4.x or a stable V4 release that drops the "Preview" label. Useful, but not the generational leap the hype crowd is promising.

So if your planning depends on V5 arriving by a particular date, build for the world where it doesn't. You'll be right more often.

Why everyone thinks DeepSeek V5 is imminent (and why they're wrong)

Here's the load-bearing myth. DeepSeek's API docs note that the model names deepseek-chat and deepseek-reasoner will be discontinued at 15:59 UTC on 24 July 2026. A bunch of posts took "deprecation on July 24" and ran with "new model on July 24." You can see the logic. You can also see why it's wrong if you read one more sentence.

Those two names are legacy aliases. They currently point at V4 Flash, one for non-thinking mode and one for thinking mode. DeepSeek is retiring the old generic names and asking everyone to call the models by their real names instead. The migration is a one-line change: swap your model field to deepseek-v4-flash or deepseek-v4-pro. Your base_url stays the same. Your API key stays the same. That's the whole job.

If you're calling the OpenAI-compatible endpoint, it's literally model: "deepseek-chat" becoming model: "deepseek-v4-flash" and you're done. I migrated my own jobs in about five minutes, and most of that was hunting down where past-me had scattered the string. The point is, nothing about your integration breaks. It just stops accepting an old name.

So this isn't a roadmap leak. It's housekeeping. The 90-day countdown started the day V4 shipped, which is exactly how you'd phase out old aliases after a new generation lands. If DeepSeek were dropping V5 on the 24th, they'd be sending you to call deepseek-v5-something. They're not. They're sending you to V4.

Does this mean V4 Flash is going away?

No, and this is the part the hype posts get backwards. V4 Flash is the destination, not the casualty. The legacy names are being pointed somewhere permanent, and that somewhere is the explicit V4 model IDs. If you've hard-coded deepseek-chat in some script from 2025, sure, go fix that before July. But your actual model isn't disappearing. Nothing about this date implies a new release. It's a rename with a deadline.

What DeepSeek V4 actually is right now: Pro vs Flash

Before we daydream about V5, it's worth being precise about what shipped, because half the articles out there get the basics wrong.

DeepSeek V4 launched as a Preview on 24 April 2026, both variants at once, open-weight on Hugging Face under the MIT license. The two models:

• V4 Pro: a 1.6T-parameter Mixture-of-Experts model with around 49B active parameters per token. This is the premium tier.
• V4 Flash: 284B total, around 13B active. Fast, cheap, the volume workhorse.

Both run a 1M-token context window. Both support thinking and non-thinking modes.

A quick word on why the active-parameter numbers matter, because they're the whole reason Flash is cheap. In a Mixture-of-Experts model, only a slice of the network fires for any given token. Flash carries 284B parameters but only lights up around 13B per token, so you get the breadth of a big model at the inference cost of a small one. That's the trick that lets DeepSeek price Flash the way it does. The 1M context, meanwhile, is genuinely useful for the kind of agent work where you're stuffing in a pile of search results and documents and asking the model to make sense of all of it at once. It's not a gimmick number on a spec sheet, at least not for how I use it.

DeepSeek V4 Pro pricing

The numbers, per million tokens:

Model	Input (cache miss)	Output	Cache-hit input
V4 Flash	$0.14	$0.28	$0.0028
V4 Pro	$0.435	$0.87	$0.003625

One correction worth flagging, since I've seen it repeated: the V4 Pro rate isn't a discount anymore. It started as a 75% promo, then became the permanent list price on 22 May 2026. So $0.435 / $0.87 is just what it costs now. Don't budget for the promo expiring, because it already didn't.

Here's where I'll get personal. V4 Flash is my daily driver. I use it constantly through the OpenCode Go subscription, which at the volume I push feels close to unlimited, and it's the engine behind most of what my Hermes setup does all day. Searching, researching, summarising, analysing, the unglamorous connective tissue of agent work. Flash is genuinely more than enough for all of it, and it's quick enough that I rarely sit there watching a spinner.

What I would not do is write code with Flash. Pro is much better for that, and I get into why in my V4 review. But honestly, even with Pro available, my coding rotation is Opus, GPT-5, Minimax M3, and Kimi 2.7 Code. DeepSeek isn't where I reach first for code. It's where I reach first for cheap, fast, high-volume thinking. Different tool, different job.

DeepSeek V4 Pro vs Claude (and GPT-5)

This is the comparison everyone wants, so let's be honest about it instead of cheerleading.

On a chunk of benchmarks, V4 Pro lands in the neighbourhood of Claude Opus 4.7 and GPT-5.5, and it does it at a fraction of the API cost. That part is real and it's impressive. But "near the frontier on some benchmarks" is not the same as "the frontier." On the hardest reasoning and agentic tasks, the top closed models still tend to edge ahead. If raw capability at any cost is your only metric, DeepSeek probably isn't your answer yet.

Where DeepSeek wins, decisively, is the price-to-performance ratio. That's the actual story, and it's a big one. You can run a lot of competent inference for very little money, which changes what kinds of products and agent loops are even economically viable. I've shipped things with Flash that would've been silly to attempt at Claude prices.

Make it concrete. Picture an agent that does a hundred small research-and-summarise passes a day, each one chewing through a decent slab of context. On Flash, that's pocket change, the kind of bill you forget to look at. Run the same loop on a frontier closed model and suddenly you're doing actual maths before you let it run unattended. The capability gap on that particular task is small to none. The cost gap is enormous. That asymmetry is the entire reason I default to Flash for high-volume agent work, and it's why I think the "vs Claude" framing slightly misses the point. They're not really competing for the same job.

How to compare them without fooling yourself

Vendor benchmark slides are marketing. If you want a read you can trust, lean on standardised harnesses like SWE-bench Pro or DeepSWE that run the same tasks against every model with the same grading. And test on your workload. A model that tops a leaderboard can still fall apart on your specific agent loop, and the only way to know is to run it. I've been burned by trusting a headline number more than once.

The DeepSeek vision API gap, and why agent users are still waiting

Here's a detail that trips people up. DeepSeek does have vision now. It added image recognition to the chat interface and the mobile app back on 29 April 2026, which SCMP wrote up nicely under the headline that the whale can finally see. Upload an image, it understands the image. Good, fast, the works.

The catch, and it's a big one if you build agents: it's chat-only. There's still no vision endpoint in the API. No image content type, nothing you can call programmatically. So for anyone wiring DeepSeek into an automated pipeline, the vision capability may as well not exist. A human can paste a screenshot into the chat box and get a great answer. Your agent, running headless at 2am, cannot. And agents are where vision actually earns its keep: reading a chart, parsing a screenshot, pulling structure out of a scanned document, checking what a UI looks like. All the workflows I'd most want it for live on the API side, behind a door that's still locked.

deepseek vision api: the part that matters for Hermes

This is exactly the gap I keep hitting. Inside Hermes, when something needs eyes, I can't hand it to DeepSeek. I route those tasks through Qwen 3.7 Plus instead, purely because Qwen gives me vision over an API and DeepSeek doesn't. It works, but it's a second model in the stack for one missing feature, and I'd happily collapse it back down to one if I could.

So when I think about what would make DeepSeek's next model actually move the needle for me, "another point on a reasoning benchmark" isn't it. A vision API is.

The funding signal, and when DeepSeek V5 might actually land

There's one piece of news that genuinely changes DeepSeek's trajectory, and it's not a model. It's money.

DeepSeek closed its first ever external funding round in June 2026, roughly $7.4 billion, at a valuation reported in the $55 to $59 billion range. SCMP covered the structure: Tencent led it, the EV battery giant CATL crossed over as a strategic investor (an AI-meets-energy bet that's more interesting than it sounds), and notably, Alibaba and ByteDance sat it out. For a lab that had stayed proudly self-funded, that's a real shift. More capital means more compute, which means more concurrent training runs, which is the kind of thing that eventually produces a V5.

But "eventually" is doing heavy lifting there. None of this comes with a date.

If you want a sane way to track the actual signal instead of the rumours, watch two things: DeepSeek's official Change Log and their Hugging Face org. When a new generation is real, it shows up there first, usually with weights and a paper, not as a leak on social media. Everything upstream of those two sources is speculation dressed up as reporting.

What I want from DeepSeek V5

So, the honest answer to "when is V5 coming out" is: unknown, no date, probably not as soon as the hype says, and the July 24 thing is a red herring. But I'm still genuinely excited for it, so here's my wishlist.

Keep the Flash-tier pricing. Add a real vision API so I can finally drop Qwen 3.7 Plus from my Hermes stack. And push the agent reliability up a notch. Do those three things and V5 becomes close to the perfect agent model for how I actually work, and my default in Hermes the day it ships.

Until then, V4 Flash is doing the job, the date nobody can give you is still nobody's to give, and I'd gently suggest ignoring any headline that claims otherwise. I'll update this post the moment DeepSeek puts something official on the Change Log. Not before.