DeepSeek V4 Flash Review: How Far a 300B Model Can Actually Go
A hands-on DeepSeek V4 Flash review covering reasoning parity with the 1.6T Pro preview, agentic coding gains, harness quirks, long-context limits, and real API cost.
Every lab that ships a 300B-class model is publishing an opinion about what that size is for.
MiniMax got there first and treated it as a daily driver for light work.
Hunyuan aimed higher, arguing 300B is enough to carry most engineering tasks that aren't especially complex.
OpenAI handed its small Luna model to an AI to self-iterate on, using the size class as a proving ground;
the results so far have been underwhelming. DeepSeek's answer with V4 Flash is that none of these are the ceiling — that 300B can do difficult reasoning and complex development at the same time.
The short version of this DeepSeek V4 Flash review: it mostly holds up.
On reasoning, Flash matches DeepSeek's own 1.6T Pro preview at the top end and beats it on consistency. The price is roughly 50% higher token consumption, which is what the post-training buys. On agentic coding it clears Pro preview outright and lands at the lower edge of what I'd call genuinely production-usable.
Logic Benchmark Results
Scores below follow the methodology of the July 2026 LLM logic capability benchmark, sorted by median score in descending order.
Three things about reading it. The table shows only comparable models rather than the full ranking, so treat it as a set of head-to-head pairings, not a leaderboard. Entries in red were run in reasoning mode (slow thinking); black entries are the same models in non-reasoning mode (fast thinking). The complete and continuously updated ranking lives at https://llm2014.github.io/llm_benchmark/.
Agentic Coding
Test setup follows the V3 agentic coding evaluation.
Flash's coding ability is uneven, and it splits along two axes: programming language and harness.
Like most Chinese models, Flash is strongest where the training corpus and training methods are most mature — frontend work. Its finished frontend output trades wins with GLM-5.2, a model close to three times its size. Move to Rust or Swift and the curve falls off a cliff. Flash broadly understands what needs to happen; it just doesn't hold the details the way it does in frontend. That's still a long way from the Pro and Flash previews, which frequently couldn't establish what needed doing or how to proceed at all.
Claude Code vs Codex
The harness gap comes down to default settings and toolchains rather than anything about the model itself.
Claude Code's default single-response length cap works against Flash. Like the preview, Flash wants to reason the whole thing through before touching a file, and during the planning stage of a complex project a single thinking pass can run to 50K tokens. Codex has the opposite problem. It iterates on itself often enough that Flash's tool-use efficiency there is poor, taking 30–40% more steps to finish the same task.
Final output quality between the two ends up close. DeepSeek's own harness, due shortly, should close both the configuration mismatch and the tool-familiarity gap — at minimum it won't be the thing holding the model back.
Frontend Quality Without Vision
Flash still has no vision capability, which makes its aesthetic jump harder to explain. Preview-era UI came out at demo quality: fine for a screenshot, not something anyone would ship. Release-version output sits close to production grade across spacing, color, proportion, and interaction detail. It volunteers page transitions and icon micro-animations without being asked, which even some higher-tier models don't bother with.
The ceiling is still visible. Flash ranks below the leading frontier models on UI work, and the gap widens as soon as you leave the web. Anything involving 3D modeling or animation exposes undertrained territory — exactly where large frontier models keep their advantage.
How Flash Verifies Its Own Work
The self-testing behavior is the most interesting thing in this release, and it follows directly from having no eyes.
Beyond conventional test cases, Flash converts screenshots into ASCII character maps so it can reason indirectly about what is on screen. For animation, it writes automated interaction sequences that reproduce a complex scene, then reads frame-by-frame state values to decide whether the motion is behaving correctly. Both approaches work in practice.
On one Godot project, Flash located and fixed nearly every functional bug on its own; what remained was interaction polish and performance tuning.
Building a text channel to the visual state is a reasonable workaround for a blind model. More importantly, it means verification is part of Flash's working loop rather than something bolted on at the end.
Reasoning: Where Flash Beats a Model Five Times Its Size
Not a clean sweep. Flash's advantage over Pro preview concentrates in meta-capabilities that generalize out of coding and writing training — instruction following and text manipulation above all.
July's new question set included items with unusually heavy text-processing demands. Pro preview scored very low there, in line with most Chinese models. Flash jumped to the top of that group, level with GPT-5.6 Luna. On constraint-satisfaction problems the two trade wins at a similar ceiling.
Hallucination and Long-Context Behavior
Context hallucination is meaningfully suppressed. Across very long inputs, Flash holds onto detail better than Pro preview — first tier, though not the top of it.
In coding the improvement is easier to pin down. Flash doesn't start dropping the original instruction requirements until context passes roughly 400K, later than either the Pro or Flash preview managed.
Token Efficiency and What It Actually Costs
Flash averages about 24% more tokens per turn than Pro preview, but that average hides a lopsided distribution. On instruction-following tasks Flash is more efficient, sometimes down to half of Pro's usage. On some simple coding tasks its raw instinct is better, so it spends slightly less. Everywhere else it spends more.
Iteration is the bigger cost driver. On complex agentic tasks Flash runs more turns, and cache reads for the same task come in 2.7–5x higher than Pro. Priced at API rates, that erodes most of the headline discount: Flash lands only about 30% cheaper than Pro preview.
Anyone routing through a third-party API should check cache pricing and hit rate before assuming savings. Without DeepSeek's native cache efficiency, Flash's cost advantage disappears entirely.
The Note
For a team that controls its own release cadence, timing was never the question. Whether the thing is finished is the question.
If DeepSeek intends to lead rather than follow, it can't ship warmed-over versions of other people's ideas. North America's frontier labs spent three years in unmapped territory with no one to learn from; they had no choice but to trust themselves. DeepSeek works from the same premise. In their view there are no rivals — only the far end of the map.
Top comments (0)