DeepSeek V4.1 Flash vs V4 Pro: Which to Use in 2026

DeepSeek’s cheaper model now beats its flagship — and that flips the usual advice on its head. If you call the DeepSeek API, the default choice in November 2026 is V4.1 Flash, not V4 Pro. Flash costs $0.30 per million input tokens and $1.20 per million output tokens at peak rates, against $1.32 and $3.96 for Pro, and on Artificial Analysis’s Intelligence Index v5 it scores 33 to Pro’s 23. It also reads images, which Pro cannot do at all. The only reason to pay for Pro now is a narrow one: hallucination-sensitive factual recall, where the bigger model still leads.

That is a strange sentence to write about a model family, because it inverts how model tiers normally work. The “Pro” tier is supposed to be the smart one and the “Flash” tier the cheap one you accept as a downgrade. DeepSeek broke that pattern in September 2026, then doubled down on it with an October update — and then, in a move that confused everyone, briefly told developers Pro was being retired, then changed its mind. If you build anything on DeepSeek — a coding agent, a customer-support bot, a content pipeline — this is the guide that sorts out which model to actually call, what it really costs once peak hours and caching enter the picture, and the one trap that can still silently bill you at Pro prices.

What happened: the flagship got demoted by its own little brother

DeepSeek’s V4 family arrived in two waves. V4 Pro, the 1.6-trillion-parameter flagship, reached general availability on August 13, 2026. Then on September 10, 2026, DeepSeek shipped V4.1 Flash — a smaller, faster model built on a new causal encoder-decoder architecture — and said plainly in its launch post that it beat V4 Pro on performance, cost, speed, and total runtime in tests run by several parties. On October 17, DeepSeek shipped a further update, V4.1-Flash-1017, behind the same API name (deepseek-flash) at the same prices.

The launch announcement also said V4 Pro was being phased out: from September 14, requests to deepseek-v4-pro would be routed to V4.1 Flash and billed at Flash rates, until a V4.1 Pro shipped at some undetermined date. The next day, DeepSeek backed off. Multiple trackers confirmed the reroute was cancelled before the deadline, and as of late October the live pricing page still lists V4 Pro as its own separately priced model. Treat Pro as continuing, not retired, until DeepSeek says otherwise — but do not treat the launch post’s “phased out” language as current either. The company’s own pages disagree with each other on this point, which is exactly why you should verify the model ID your calls actually hit, a point I come back to below.

The community reaction was immediate and, frankly, amused. On r/LocalLLaMA, the Hugging Face release thread for V4.1 Flash drew 1,121 upvotes and 317 comments, and a follow-up thread titled “DeepSeek V4.1 Flash (1017) Now Leads Open-Weight Models” drew 789 upvotes and 165 comments, according to community tracking reported by aicomparison.ai. The argument in those threads was not about whether Flash was good — it was about the parameter count, with one poster reading the safetensors files and finding roughly 552B in the main model plus about 197B of optional engram parameters. If you plan to self-host, budget for the larger number.

The two models side by side

Here is the comparison that matters, with every figure checked against DeepSeek’s own pricing page, the Hugging Face model cards, and Artificial Analysis as of November 2026.

Two things in that table deserve a pause. First, the size gap is enormous — Pro activates roughly three to six times as many parameters per token — and yet it scores lower on the independent index. That is the whole story of this release: architecture and post-training beat raw scale here. Second, Flash is the only one of the two that accepts images. If your workflow involves screenshots, documents, or photos, Pro is not even an option.

One honest caveat on the benchmark numbers: Artificial Analysis moved to version 5 of its index at the end of October 2026, re-weighting the basket toward private test sets, and scores fell across the board — open-weight models lost the most ground. The September build of Flash scored 39 on the older v4.3.2 index; the October update scores 33 on v5. Those are different rulers, not a model getting worse. What is stable across both versions is the ordering: Flash ahead of Pro by a wide margin.

The price table, including the parts people miss

DeepSeek bills on a peak/off-peak split that took effect August 16, 2026. Peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday to Friday, excluding Chinese public holidays. Off-peak is exactly half of peak on every line. For a US-based builder, that timing is generous: peak hours fall overnight and early morning in the US, so most American daytime traffic bills at the cheaper off-peak rate.

The ratio is stable: Pro output costs 3.3 times Flash output at both peak and off-peak. And the cache-hit line is where the real money hides. A cache-hit input token on Flash costs $0.003 off-peak — one fiftieth of a fresh input token. If your agent reuses long system prompts or re-reads the same codebase across turns, most of your input tokens can bill at that near-zero rate. The same trick exists on Pro, but at $0.022 it is seven times more expensive.

DeepSeek also sets different concurrency limits per model: 500 concurrent requests for V4 Pro, 2,500 for V4.1 Flash, according to current pricing trackers. For a high-volume agent loop, that is a practical difference, not just a price one.

What it actually costs: three worked examples

Sticker prices per million tokens are abstract. Here is what real workloads cost, using off-peak rates (the rate most US daytime traffic gets) and the cache-miss input price, since that is the conservative assumption.

A 60-turn coding session. Suppose each turn sends a 20,000-token context and gets back 2,000 tokens. That is 1.2M input tokens and 120,000 output tokens. On Flash: $0.18 input + $0.072 output = about $0.25. On Pro: $0.79 input + $0.24 output = about $1.03. Same session, four times the price — and the independent index says the cheaper one scores higher. With an 80% cache-hit rate on the repeated context, the Flash session drops to roughly $0.13, because the cached input bills at $0.003 per million instead of $0.15.

A support bot doing 10,000 chats a month. Each chat: 3,000 input tokens, 500 output tokens. Monthly volume: 30M input, 5M output. Flash off-peak: $4.50 + $3.00 = $7.50 a month. Pro off-peak: $19.80 + $9.90 = $29.70. The gap is $22 a month at this volume — small in absolute terms, but it scales linearly, and at 100,000 chats it is $222 a month for a model that scores lower.

A document pipeline processing 100M tokens a month. This is where the choice becomes a budget line. Flash off-peak: $15 input per million means $1,500, plus output. Pro: $66 per million input, or $6,600. The $5,100 monthly difference buys a lot of evaluation work — which is exactly what you should spend some of it on, because the right test is your own workload, not a public benchmark.

For context on how cheap this is against the closed frontier: Flash’s $0.30/$1.20 peak rates run roughly a twentieth of Claude Opus 5.5’s pricing and about a twelfth of Kimi K3.1 Pro’s, according to price comparisons published at launch. I have not verified Opus’s current price in this run, so treat that as the launch-week comparison, not a live quote. The point that is verifiable right now is the internal one: Flash is a third of Pro’s price and beats it on the independent index.

If you want the broader pricing context — DeepSeek raised some prices in October, and several other labs moved theirs the same month — the site’s earlier guide to the October AI API price increases covers the GLM and DeepSeek changes that set the stage for this release.

The benchmarks: DeepSeek’s numbers vs the independent ones

DeepSeek’s own launch table puts V4.1 Flash ahead of V4 Pro on every agentic coding, cyber, and tool-use row it reports. The headline vendor figures are Terminal-Bench 2.1 at 90.6, DeepSWE at 74.2 (77 after the October 1017 update), and CyberGym at 88.1. Treat those as vendor results: DeepSeek ran them, and independent testers had not published their own V4.1 Flash measurements on launch day.

The independent check that does exist is Artificial Analysis. On Index v5, Flash 1017 scores 33 and V4 Pro 0813 scores 23, with Flash’s cost per index task at $0.60 against Pro’s $1.77. For scale, the best proprietary models score up to 59 on the same index, and Kimi K3.1 Pro — the current open-weight leader — scores 46. Flash is not close to the frontier, and nobody should pretend it is. What it is, is the best value in the open-weight tier: the top-scoring model with downloadable weights at roughly a third of the cost per task of its own flagship.

There is one axis where Pro still leads, and DeepSeek’s own model-card comparisons show it: knowledge tests. On SimpleQA-Verified, a factual-recall benchmark, V4 Pro’s base model scores 55.2 against V4.1 Flash’s 42.3. That gap is the reason Pro still exists. If your workload is hallucination-sensitive factual recall — answering questions from memory where a wrong fact is worse than a slow answer — Pro is the safer call. Everything else, Flash wins or ties.

The API ID trap: verify which model your calls actually hit

This is the most practical section of this article, and the one most likely to save you money. DeepSeek has changed model routing twice in three months, and the model ID in your code is not a guarantee of which weights answer.

First, the old Flash model (deepseek-v4-flash, the July 31 build) was retired on September 10, 2026. If your code still references it, check what it resolves to — the old ID was temporarily routed to V4.1 Flash, and retired IDs have a habit of eventually failing outright.

Second, the September 14 reroute of deepseek-v4-pro to Flash was announced, then cancelled. The pricing page still lists Pro separately, and community trackers confirmed in October that Pro requests still reach Pro weights and bill at Pro rates. But the episode proves DeepSeek is willing to reroute a pinned ID, so the only safe move is to verify: run a probe request and check the response, or check your usage dashboard for which model actually billed. If you pinned Pro because you wanted Pro’s factual recall, a silent reroute to Flash would have changed your product’s behavior without changing your code.

Third, V4.1 Pro does not exist yet as a callable model. DeepSeek named it in the September announcement as the future model that would end the Flash reroute, and community trackers reported a deepseek-v4.1-pro slug in per-account early access from late September, but as of early November there is no model card, no Hugging Face upload, and no price sheet. Any benchmark score circulating for V4.1 Pro today is unverified. Do not build a roadmap around it.

The off-peak scheduling trick

Peak hours are 01:00–04:00 and 06:00–10:00 UTC on weekdays. In US Eastern time, that is 9:00 PM–midnight and 2:00–6:00 AM during standard time; in Pacific time, 6:00–9:00 PM and 11:00 PM–2:00 AM. Most American business-hours traffic falls outside peak windows entirely, which means most US builders already get off-peak pricing by default. The scheduling trick matters most for batch work: if you have a nightly job — a document pipeline, a bulk classification run, a weekly report generator — schedule it for the weekend, when every hour is off-peak, or for weekday afternoons in US time. The saving is a clean 50% on every token, with no code change beyond a cron schedule.

One more pricing detail worth knowing: DeepSeek lists no batch API discount, unlike some competitors. The off-peak window is the discount. Plan around it.

Self-hosting: the MIT license is real, the download is not small

Both models ship MIT-licensed open weights on Hugging Face, which is the part of this story that matters most for builders who want to own their stack. Flash’s repository is about 510 GB across 48 safetensors shards; the model card states 552B parameters, while the safetensors index totals closer to 763B including the engram component. Pro is larger still at 1.6T parameters. You will need serious GPU hardware to run either at usable speed — this is not a laptop model — but the license means you can run it in your own cloud, fine-tune it, and ship it in a product without a per-token bill.

That openness is also why the community tracks this family so closely. Kimi K3.1 Pro, the current open-weight benchmark leader, is API-first with closed weights; DeepSeek remains the best-scoring family you can actually download. The site’s guide to Kimi K3.1 Pro’s weights, license, and VRAM requirements covers the other side of that comparison if you are choosing between the two.

One caution for US businesses: on October 20, 2026, the Federal Register published a Department of Homeland Security order telling federal civilian agencies to remove DeepSeek products and third-party products built with DeepSeek implementations. That order applies to federal agencies, not to private companies, but if you sell into government or regulated industries, check your customers’ policies before building on DeepSeek. For everyone else, it is a compliance footnote, not a blocker.

Which one should you actually use?

The decision is simpler than the model family makes it look.

Use V4.1 Flash if: you are building a coding agent, a support bot, a document pipeline, an extraction or classification job, or anything with images. It is cheaper, faster, higher-scoring on the independent index, and the only one with vision. It is also the default DeepSeek serves to new users, and the concurrency limit is five times higher.

Use V4 Pro if: your workload is hallucination-sensitive factual recall, or your own tests show Flash failing on a specific hard-reasoning task. Do not choose Pro on the assumption that bigger means better — on this family, in November 2026, it does not. Run your own benchmark first: take 50 real examples from your workload, run both models, and score them yourself. The $1.17 per-task difference on the public index is a hint, not a verdict on your data.

Use neither, yet, if: you need a model with a published safety evaluation you can show an enterprise customer, or you need guaranteed uptime with an SLA. DeepSeek’s API has had outages, including one in mid-October, and the open-weight route gives you control but no support line.

And keep an eye on the calendar. The November AI price deadlines guide on this site tracks the introductory-pricing cliffs across Gemini, GPT, and Claude — DeepSeek’s rates have already moved twice since August, and the next move could come from any direction. If V4.1 Pro ships, this whole decision table gets rewritten, and the first thing to check will be whether it actually outscores Flash, or whether DeepSeek has built a flagship that earns its name this time.

Frequently Asked Questions

Is DeepSeek V4.1 Flash really better than V4 Pro?

On the independent Artificial Analysis Intelligence Index v5, yes: Flash 1017 scores 33 and V4 Pro 0813 scores 23, as of November 2026. DeepSeek’s own launch table also puts Flash ahead on agentic coding, cyber, and tool-use benchmarks. The exception is factual recall, where Pro’s base model leads on SimpleQA-Verified (55.2 vs 42.3). “Better” depends on your workload — but for most coding, agent, and extraction work, Flash is the stronger and cheaper model.

How much does DeepSeek V4.1 Flash cost?

At peak hours, $0.30 per million input tokens (cache miss), $0.006 per million on cache hits, and $1.20 per million output tokens. Off-peak rates are exactly half: $0.15, $0.003, and $0.60. Peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday to Friday. V4 Pro costs 4.4 times more on input and 3.3 times more on output at the same hours.

What is the difference between deepseek-flash and deepseek-v4-pro?

deepseek-flash is the API ID for V4.1 Flash, the 552B-parameter model with native image input, released September 10, 2026 and updated October 17. deepseek-v4-pro is the API ID for V4 Pro, the 1.6T-parameter text-only flagship from August 2026. Both have a 1M-token context and MIT-licensed open weights. DeepSeek announced in September that Pro requests would be rerouted to Flash, then cancelled that plan — Pro still serves Pro weights and bills at Pro rates.

Can I use DeepSeek V4.1 Flash for free?

No. DeepSeek’s platform has no free API tier for this model — billing is pay-as-you-go against a topped-up balance. The weights themselves are free to download under the MIT license from Hugging Face, so you can self-host without paying DeepSeek, but you pay for the GPU hardware instead. The repository is about 510 GB.

Should I switch from V4 Pro to V4.1 Flash?

For most workloads, yes — and DeepSeek’s own pricing makes the test cheap. Run 50 real examples from your workload through both models and score them yourself before switching production traffic. If your workload is factual question-answering where a wrong answer is costly, keep Pro or run the comparison with extra care, because Pro still leads on factual-recall benchmarks. And verify the model ID in your code: the retired deepseek-v4-flash ID and the cancelled September reroute mean old configs can behave unexpectedly.

When is DeepSeek V4.1 Pro coming out?

DeepSeek has not announced a date. It named V4.1 Pro in the September 10 announcement as a future model, and community trackers reported early-access sightings from late September, but as of early November 2026 there is no model card, Hugging Face upload, price sheet, or verified benchmark. Do not plan a launch around it until DeepSeek publishes something official.