// head_to_head
DeepSeek V4 Flash 0423 vs Qwen3.6 27B
Published LiveBench scores across all seven categories, live list pricing, context windows, and the measured cost of a point of capability — for both models, side by side.
DeepSeek V4 Flash 0423 wins outright — it scores higher and costs less.
DeepSeek V4 Flash 0423 leads by 1.5 points overall while listing 8.3× cheaper per blended million tokens. There is no trade-off to reason about here; the only reason to pick the other is a constraint this table does not show, like an existing contract, a region, or a provider you are already on. DeepSeek V4 Flash 0423 also leads on measured cost per point of capability, at $0.0083 per point.
deepseek
DeepSeek V4 Flash 0423
- Blended / 1M
- $0.111
- Context
- 1.0M
- Released
- Apr 24, 2026
- Overall score
- 65.5
qwen
Qwen3.6 27B
- Blended / 1M
- $0.915
- Context
- 262K
- Released
- Apr 27, 2026
- Overall score
- 64.0
Specs and pricing
| Metric | DeepSeek V4 Flash 0423 | Qwen3.6 27B |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 65.5win | 64.0 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0083win | $0.1074 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.111win | $0.915 |
| Input price / 1M | $0.089win | $0.320 |
| Output price / 1M | $0.177win | $2.70 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.018win | $0.150 |
| Context window | 1.0Mwin | 262K |
| Max output tokens | 384Kwin | 262K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — DeepSeek V4 Flash 0423 on top, Qwen3.6 27B below, both out of 100.
What each one costs to run
Per-token prices are hard to feel. These are monthly list costs for both models across five workload shapes, using each provider's published cached-input rate where there is one.
| Workload | DeepSeek V4 Flash 0423 | Qwen3.6 27B |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $30.34/mo | $280.56/mo |
| RAG assistant 8K in / 600 out × 100K requests | $53.16/mo | $350.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $45.37/mo | $376.80/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $98.35/mo | $514.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $203.79/mo | $985.00/mo |
Which should you pick?
You are running this at volume
DeepSeek V4 Flash 0423
Lowest measured cost per point of capability at $0.0083 per point — the gap compounds with every request.
Quality matters more than the bill
DeepSeek V4 Flash 0423
Highest overall LiveBench score of the two at 65.5.
The workload is coding or agentic work
Qwen3.6 27B
Leads on agentic coding — 39.3 against 37.6.
You need to fit large documents in one call
DeepSeek V4 Flash 0423
Wider context window — 1.0M against 262K.
DeepSeek V4 Flash 0423 vs Qwen3.6 27B FAQ
Which is better, DeepSeek V4 Flash 0423 or Qwen3.6 27B?
DeepSeek V4 Flash 0423 wins outright — it scores higher and costs less. DeepSeek V4 Flash 0423 leads by 1.5 points overall while listing 8.3× cheaper per blended million tokens. There is no trade-off to reason about here; the only reason to pick the other is a constraint this table does not show, like an existing contract, a region, or a provider you are already on. DeepSeek V4 Flash 0423 also leads on measured cost per point of capability, at $0.0083 per point.
Is DeepSeek V4 Flash 0423 cheaper than Qwen3.6 27B?
DeepSeek V4 Flash 0423 is cheaper. On a 3:1 input:output blend, DeepSeek V4 Flash 0423 lists at $0.111 per million tokens and Qwen3.6 27B at $0.915 — DeepSeek V4 Flash 0423 is 8.3× cheaper. Input and output are priced separately — DeepSeek V4 Flash 0423 charges $0.089 in and $0.177 out, Qwen3.6 27B charges $0.320 and $2.70 — so the model that looks cheaper flips depending on how output-heavy your workload is.
DeepSeek V4 Flash 0423 vs Qwen3.6 27B: which scores higher on benchmarks?
DeepSeek V4 Flash 0423 scores 65.5 and Qwen3.6 27B scores 64.0 overall on LiveBench, the mean of its seven categories. That is a 1.5-point lead for DeepSeek V4 Flash 0423. Category scores differ from the overall figure — a model can lead on reasoning and trail on coding, which the per-category table above breaks out.
Which gives better value for money, DeepSeek V4 Flash 0423 or Qwen3.6 27B?
DeepSeek V4 Flash 0423. Cost per point divides the measured dollars LiveBench spent running the benchmark by the score it earned, so it captures something token pricing misses: a reasoning model can emit many times more tokens than its per-token rate suggests. DeepSeek V4 Flash 0423 works out at $0.0083 per point and Qwen3.6 27B at $0.1074.
Does DeepSeek V4 Flash 0423 or Qwen3.6 27B have a bigger context window?
DeepSeek V4 Flash 0423 has the larger context window: 1.0M for DeepSeek V4 Flash 0423 against 262K for Qwen3.6 27B. Note that a window you can fill is not a window you should fill — retrieval quality usually degrades well before the limit, and you pay for every token you put in it.
Do DeepSeek V4 Flash 0423 and Qwen3.6 27B support prompt caching?
Both publish a cached-input rate: $0.018 per million for DeepSeek V4 Flash 0423 and $0.150 for Qwen3.6 27B, against full input rates of $0.089 and $0.320. On a workload with a long stable prefix — a system prompt, a tool schema, a retrieved corpus — that changes the economics more than the headline price does.
Related comparisons
How these numbers are produced
- Price — provider list price from OpenRouter, refreshed every 15 minutes. “Blended” is a 3:1 input:output mix.
- Scores — LiveBench release 2026-06-25, using their own category map. Each model shows its strongest published run. A blank means “not evaluated”, never “bad”.
- Cost per point — the measured dollars LiveBench spent on the run, divided by the score it earned.
- “Win” — awarded only past a threshold: one full point on a benchmark score, 10% on a price, 25% on a context window. Anything tighter reports as a tie, because effort settings alone move a LiveBench score by more than that.
Published benchmarks rank models on someone else's tasks. Before committing, see LLM & agent evaluation for building an eval on your own.