GLM-5.3-Flash beats Qwen3.8-Flash-Next on coding and costs less to rent: $0.075 per million input tokens on promo through September 9, versus roughly $0.15 on Qwen’s hosted Flash tier. Qwen wins on agentic work and activates 6B parameters against GLM’s 18B, so it is the better model to own. Rent GLM. Self-host Qwen.
Two Chinese labs shipped a frontier-adjacent open-weight model on the same day. August 26, 2026: Z.ai released GLM-5.3-Flash, Alibaba released Qwen3.8-Flash-Next. Same week, same price bracket, and — as we will get to — very nearly the same architecture.
This is the comparison that matters for anyone paying an API bill this quarter. Here is what the numbers actually say.
What are GLM-5.3-Flash and Qwen3.8-Flash-Next?
Both are sparse mixture-of-experts models built for cheap, long-context, agentic work. GLM-5.3-Flash is the multimodal one with a 1M-token window and an MIT license. Qwen3.8-Flash-Next is a preview of the Qwen4 architecture that activates only 6B parameters per token. Both released August 26, 2026.
GLM-5.3-Flash: 320B total, 18B active, MIT
Z.ai’s model carries 320B total parameters with 18B active per token, across 45 layers — 34 linear, 11 full attention — trained on a 30T-token corpus, per LLM-Stats’ launch breakdown.
It handles text, image and video. The context window is 1,048,576 input tokens with 131,072 output tokens. The license is MIT — the most permissive terms of any model at this capability tier.
Z.ai claims a 3x attention compute reduction and 4.4x KV cache savings versus the full GLM-5.3.
Qwen3.8-Flash-Next: 6B active, Qwen4 preview
Alibaba’s model is 125B in the main body plus a 51B n-gram table and a 4B multi-token-prediction head — roughly 180B stored — but only 6B parameters fire per token. It needs one-ninth the compute of Qwen3.7-Plus.
Native context is 262,144 tokens, extensible to 1M with YaRN. The license is Qwen Community 1.0, not MIT. Alibaba reports up to 7.6x prefill and 4.9x decoding speedups at 1M tokens.
How much does each model cost per million tokens?
GLM-5.3-Flash is cheaper to rent, and it is not close during the promo. Z.ai lists $0.15 input, $0.03 cached input, $0.50 output per million tokens, with 50% off through September 9, 2026. Qwen3.8-Flash-Next has no first-party hosted list price at all — it shipped as weights only.
| Spec | GLM-5.3-Flash | Qwen3.8-Flash-Next |
|---|---|---|
| Released | Aug 26, 2026 | Aug 26, 2026 |
| Total / active params | 320B / 18B | ~180B stored / 6B |
| Native context | 1,048,576 tokens | 262,144 (1M via YaRN) |
| Modalities | Text, image, video | Text, vision |
| License | MIT | Qwen Community 1.0 |
| List input / output | $0.15 / $0.50 | No first-party rate |
| Promo input / output | $0.075 / $0.25 (to Sep 9) | — |
| Cached input | $0.03 | Not published |
| Nearest hosted sibling | — | Qwen3.8-Flash: $0.16 / $0.47 |
What that gap costs on a real workload
Run 100M input and 20M output tokens a month — a mid-sized coding agent deployment. On GLM’s promo rate that is $7.50 plus $5.00, or $12.50. On Qwen3.8-Flash’s QwenCloud rate of $0.16 / $0.47, it is $16.00 plus $9.40, or $25.40.
Roughly 2x. Both are rounding errors next to Qwen3.8-Max at $2.00 / $6.00 input-output — the Flash tier undercuts it by more than 10x on input, as DataCamp documented.
Caching is where GLM pulls further ahead. At $0.03 per million cached input tokens, a repeated 500K-token repo context costs 1.5 cents to re-read. We covered the same dynamic in our breakdown of the cheapest 1M context model.
Which is better for coding, GLM-5.3-Flash or Qwen3.8-Flash-Next?
GLM-5.3-Flash wins coding. It scores 63.4 on DeepSWE 1.1 against Qwen’s 58.7, and BenchLM ranks it #13 of 146 on coding versus Qwen at #28. Qwen wins the agentic category decisively — #7 of 140 against GLM’s #36 — so the answer depends on whether your job is writing code or running tools.
The benchmark split
| Benchmark | GLM-5.3-Flash | Qwen3.8-Flash-Next |
|---|---|---|
| DeepSWE 1.1 | 63.4 | 58.7 |
| SWE-bench Pro | Not published | 62.5 |
| Toolathlon | 78.4 | Behind GLM |
| Terminal Bench 2.1 | 84.3 | Not published |
| AutomationBench | 48.8 | Not published |
| GPQA Diamond | Not published | 91.7 |
| LiveCodeBench v6 | Not published | 91.9 |
| CharXiv-R | 89.4% | 90.6% |
| Agents’ Last Exam | Behind Qwen | 24.3 pass@1 |
| BenchLM overall | 61.3 (#58/228) | 61.3 (#57/228) |
| LLM-Stats score | 51.6 (#11) | 50.5 (#14) |
Note the dead heat at the top line: both land on 61.3/100 at BenchLM, one rank apart. The aggregate hides the split underneath it.
Where Qwen actually wins
Qwen’s agentic numbers are the story. SWE-bench Pro 62.5 against Claude Opus 4.6 Max’s 53.4. CoWorkBench 73.9 against 68.2. JobBench 55.7 against 36.6 — a 19-point gap over a frontier closed model.
It also takes instruction following, ranking #10 of 42 at 91.2. GLM is not measured on that axis.
Reasoning is Qwen’s weak spot: 35.9 on Humanity’s Last Exam versus Opus’s 40.0. GLM wins the head-to-head on HLE and NL2Repo, per LLM-Stats’ comparison page.
Why did two rival labs ship the same architecture?
Because the efficiency math has one answer right now. MarkTechPost’s teardown found both models independently adopted four identical design choices — and the convergence is the real news, more than either model’s scorecard.
The four shared choices
- 3:1 linear attention ratio. Three cheap linear layers per full attention layer, compressing history into fixed recurrent states.
- 4x context compression with sparse attention capped at exactly 2,048 tokens via a learned indexer. Both picked the same number.
- Four gated residual streams replacing the single-stream transformer, controlled by data-dependent gates.
- Muon optimizer, with fused matrices split before orthogonalization during training.
Where they split: RoPE versus NoPE
GLM dropped rotary position embeddings entirely, relying on linear layers for implicit position. Qwen kept RoPE — after finding that NoPE models “often failed to stop generating” during post-training alignment.
That is a genuinely useful negative result: a failure mode invisible in pre-training metrics. Not everyone is convinced either way. MiniMax’s ablations found linear attention harms multi-hop reasoning, and M3 uses sparse softmax only.
Is self-hosting cheaper than the API?
For GLM-5.3-Flash, no. The FP8 checkpoint is about 306 GiB of weights needing roughly 386 GiB of VRAM — a minimum 8-GPU Hopper node. Two H200s at 282 GiB combined do not fit. For Qwen3.8-Flash-Next at 6B active, the answer flips: fewer active parameters means far cheaper serving at scale.
The GLM hardware ladder, per LumaDock’s deployment guide:
- BF16: ~772 GiB VRAM. Multi-node territory.
- FP8: ~306 GiB weights, ~386 GiB recommended. 8-GPU Hopper node.
- 4-bit GGUF: ~160 GB before overhead. Two to four GPUs, with quality trade-offs.
- 1-bit to 3-bit (Unsloth): 100–128 GB combined RAM/VRAM. Mac Studio or DGX class.
LumaDock’s verdict is blunt: an 8-GPU node costs more per day than most teams spend on the API per month. At $12.50 a month for our example workload, that is not a close call.
Qwen is the opposite trade. Six billion active parameters is what makes it cheap to serve — the same argument we ran through on Qwen3.8-Max open weights versus API. The catch is the license: Qwen Community 1.0, not MIT. Read it before you build a product on it.
Which model should you pick?
Pick by workload, not by leaderboard. GLM for code generation, multimodal input and anything cost-sensitive you plan to rent. Qwen for tool-calling agents, instruction-heavy pipelines and any deployment you intend to own outright.
| Use case | Pick | Why |
|---|---|---|
| Code generation / repo refactors | GLM-5.3-Flash | DeepSWE 63.4 vs 58.7; coding #13 vs #28 |
| Tool-calling agents | Qwen3.8-Flash-Next | Agentic #7/140; JobBench 55.7 |
| Document / video understanding | GLM-5.3-Flash | Multimodal #7/35; video support |
| Long-context RAG | GLM-5.3-Flash | 1M native; $0.03 cached input |
| On-prem / air-gapped | Qwen3.8-Flash-Next | 6B active; runs on far less iron |
| Commercial product, license risk | GLM-5.3-Flash | MIT beats Qwen Community 1.0 |
| Lowest cost per token today | GLM-5.3-Flash | $0.075 / $0.25 through Sep 9 |
| Structured output pipelines | Qwen3.8-Flash-Next | Instruction following #10/42, 91.2 |
Frequently asked questions
Is GLM-5.3-Flash really MIT licensed?
Yes. Z.ai released it under MIT, which permits commercial use, modification and redistribution without a revenue threshold. Qwen3.8-Flash-Next ships under Qwen Community License 1.0, which carries its own conditions.
When does the GLM-5.3-Flash promo price end?
September 9, 2026. After that, input goes from $0.075 to $0.15 and output from $0.25 to $0.50 per million tokens — a doubling. Budget for it now.
Can I get Qwen3.8-Flash-Next through an API?
Not at a first-party list price. It shipped as open weights on Hugging Face. The nearest hosted option is Qwen3.8-Flash on QwenCloud at $0.16 input / $0.47 output; OpenRouter lists a comparable Flash tier at $0.15 / $0.47.
Which has the bigger context window?
GLM-5.3-Flash, at 1,048,576 tokens native. Qwen3.8-Flash-Next is 262,144 native and reaches 1M only with YaRN extension.
Is either one faster?
BenchLM clocks Qwen3.8-Flash-Next at 73 tokens per second with 30.22s first-token latency; GLM is listed as not measured. Alibaba separately reports up to 7.6x prefill and 4.9x decoding speedups at 1M tokens.
How do these compare to Western frontier models?
On agentic coding, favorably. Qwen’s SWE-bench Pro 62.5 beats Claude Opus 4.6 Max’s 53.4. On broad reasoning they still trail — Qwen’s HLE 35.9 versus Opus’s 40.0.
What hardware do I need to run GLM-5.3-Flash locally?
An 8-GPU Hopper node for FP8. Community 1-bit to 3-bit GGUF builds run on 100–128 GB of combined RAM/VRAM, with real quality loss.
The bottom line
Rent GLM-5.3-Flash. Own Qwen3.8-Flash-Next.
If you are buying tokens, GLM wins on price, coding accuracy, context length and license, and the $0.03 cached-input rate makes long-context agents genuinely cheap. Move before September 9 and lock in your usage patterns while the promo lasts.
If you are standing up your own inference, Qwen’s 6B active footprint is the decisive number. Eighteen billion active parameters is three times the serving cost per token, and at scale that swamps a leaderboard gap of five DeepSWE points.
The one scenario where you should not pick either: a commercial product where license terms carry legal weight and you cannot accept Qwen Community 1.0. There, GLM’s MIT license ends the argument by itself. For a wider look at coding agents, see our comparison of Claude Code vs Codex CLI and GLM-5.3 vs DeepSeek V4 Pro.
Sources
- MarkTechPost — GLM-5.3-Flash vs Qwen3.8-Flash-Next architecture convergence
- LLM-Stats — GLM-5.3-Flash launch analysis
- LLM-Stats — Qwen3.8-Flash-Next launch analysis
- LLM-Stats — head-to-head comparison
- BenchLM — Qwen3.8-Flash-Next scorecard
- DataCamp — Qwen3.8-Flash-Next features, benchmarks and pricing
- LumaDock — GLM-5.3-Flash hardware and deployment guide
- OpenRouter — Qwen3.8 Flash vs GLM 5.3 Flash pricing
