// head_to_head
Qwen3 235B A22B 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.
Qwen3 235B A22B is the cheaper of the two; neither can be ranked on quality here.
Qwen3 235B A22B does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
qwen
Qwen3 235B A22B
- Blended / 1M
- $0.796
- Context
- 131K
- Released
- Apr 28, 2025
- Overall score
- Not evaluated
qwen
Qwen3.6 27B
- Blended / 1M
- $0.915
- Context
- 262K
- Released
- Apr 27, 2026
- Overall score
- 64.0
Specs and pricing
| Metric | Qwen3 235B A22B | Qwen3.6 27B |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | — | 64.0 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | — | $0.1074 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.796win | $0.915 |
| Input price / 1M | $0.455 | $0.320win |
| Output price / 1M | $1.82win | $2.70 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | — | $0.150 |
| Context window | 131K | 262Kwin |
| Max output tokens | 8K | 262Kwin |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Qwen3 235B A22B 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 | Qwen3 235B A22B | Qwen3.6 27B |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $254.80/mo | $280.56/mo |
| RAG assistant 8K in / 600 out × 100K requests | $473.20/mo | $350.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $509.60/mo | $376.80/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $591.50/mo | $514.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $1,319/mo | $985.00/mo |
Which should you pick?
You need to fit large documents in one call
Qwen3.6 27B
Wider context window — 262K against 131K.
You are cost-constrained
Qwen3 235B A22B
Cheaper on blended list price at $0.796 per million tokens.
Qwen3 235B A22B vs Qwen3.6 27B FAQ
Which is better, Qwen3 235B A22B or Qwen3.6 27B?
Qwen3 235B A22B is the cheaper of the two; neither can be ranked on quality here. Qwen3 235B A22B does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
Is Qwen3 235B A22B cheaper than Qwen3.6 27B?
Qwen3 235B A22B is cheaper. On a 3:1 input:output blend, Qwen3 235B A22B lists at $0.796 per million tokens and Qwen3.6 27B at $0.915 — Qwen3 235B A22B is 15% cheaper. Input and output are priced separately — Qwen3 235B A22B charges $0.455 in and $1.82 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.
Does Qwen3 235B A22B or Qwen3.6 27B have a bigger context window?
Qwen3.6 27B has the larger context window: 131K for Qwen3 235B A22B 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 Qwen3 235B A22B and Qwen3.6 27B support prompt caching?
Qwen3.6 27B publishes a cached-input rate of $0.150 per million tokens against a full input rate of $0.320. The catalogue lists no separate cached rate for Qwen3 235B A22B, which means the provider does not price it separately here — not that caching is unavailable.
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.