// head_to_head
Qwen3.7 Max vs Qwen3.8 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.
Qwen3.8 27B wins outright — it scores higher and costs less.
Qwen3.8 27B leads by 2.1 points overall while listing 1.9× 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. Qwen3.8 27B also leads on measured cost per point of capability, at $0.0556 per point.
qwen
Qwen3.7 Max
- Blended / 1M
- $2.21
- Context
- 1M
- Released
- May 21, 2026
- Overall score
- 73.1
qwen
Qwen3.8 27B
- Blended / 1M
- $1.14
- Context
- 1M
- Released
- Aug 14, 2026
- Overall score
- 75.3
Specs and pricing
| Metric | Qwen3.7 Max | Qwen3.8 27B |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 73.1 | 75.3win |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0971 | $0.0556win |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $2.21 | $1.14win |
| Input price / 1M | $1.48 | $0.450win |
| Output price / 1M | $4.42 | $3.20win |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.295 | $0.050win |
| Context window | 1M | 1M |
| Max output tokens | 131K | 131K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Qwen3.7 Max on top, Qwen3.8 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 | Qwen3.7 Max | Qwen3.8 27B |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $623.04/mo | $335.20/mo |
| RAG assistant 8K in / 600 out × 100K requests | $973.50/mo | $392.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $873.20/mo | $392.00/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $1747.88/mo | $670.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $3540.00/mo | $1245.00/mo |
Which should you pick?
You are running this at volume
Qwen3.8 27B
Lowest measured cost per point of capability at $0.0556 per point — the gap compounds with every request.
Quality matters more than the bill
Qwen3.8 27B
Highest overall LiveBench score of the two at 75.3.
The workload is coding or agentic work
Qwen3.8 27B
Leads on agentic coding — 61.4 against 43.6.
Qwen3.7 Max vs Qwen3.8 27B FAQ
Which is better, Qwen3.7 Max or Qwen3.8 27B?
Qwen3.8 27B wins outright — it scores higher and costs less. Qwen3.8 27B leads by 2.1 points overall while listing 1.9× 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. Qwen3.8 27B also leads on measured cost per point of capability, at $0.0556 per point.
Is Qwen3.7 Max cheaper than Qwen3.8 27B?
Qwen3.8 27B is cheaper. On a 3:1 input:output blend, Qwen3.7 Max lists at $2.21 per million tokens and Qwen3.8 27B at $1.14 — Qwen3.8 27B is 1.9× cheaper. Input and output are priced separately — Qwen3.7 Max charges $1.48 in and $4.42 out, Qwen3.8 27B charges $0.450 and $3.20 — so the model that looks cheaper flips depending on how output-heavy your workload is.
Qwen3.7 Max vs Qwen3.8 27B: which scores higher on benchmarks?
Qwen3.7 Max scores 73.1 and Qwen3.8 27B scores 75.3 overall on LiveBench, the mean of its seven categories. That is a 2.1-point lead for Qwen3.8 27B. 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, Qwen3.7 Max or Qwen3.8 27B?
Qwen3.8 27B. 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. Qwen3.7 Max works out at $0.0971 per point and Qwen3.8 27B at $0.0556.
Does Qwen3.7 Max or Qwen3.8 27B have a bigger context window?
They are effectively the same — 1M for Qwen3.7 Max and 1M for Qwen3.8 27B.
Do Qwen3.7 Max and Qwen3.8 27B support prompt caching?
Both publish a cached-input rate: $0.295 per million for Qwen3.7 Max and $0.050 for Qwen3.8 27B, against full input rates of $1.48 and $0.450. 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.