GLM 4.6 vs GLM 5
GLM 4.6 and GLM 5 are both text-only models from z-ai with identical 202,752-token context windows, so this comparison is decided by price and capability, not context length. GLM 5 launched five months after GLM 4.6 and costs more per token on both input and output. The question is whether the capability gap justifies the price gap — the Design Arena data says yes for coding and agent tasks.
Spec vs spec
| Spec | GLM 4.6 | GLM 5 |
|---|---|---|
| Context window | 203K | 203K |
| Max output | 131K | — |
| Input modalities | text | text |
| Output modalities | text | text |
| Knowledge cutoff | Mar 31, 2025 | — |
| Released | Sep 30, 2025 | Feb 11, 2026 |
| Reasoning | optional | optional |
Pricing
Per 1M tokens. Provider price plus the flat 3% fee — the sum is what you pay.
z-ai/glm-4.6
Input · 1M tokens
$0.430 + 3%$0.443
Output · 1M tokens
$1.74 + 3%$1.79
Cache read · 1M tokens
$0.080 + 3%$0.082
FEE — FLAT, EVERY MODEL3%
z-ai/glm-5
Input · 1M tokens
$0.600 + 3%$0.618
Output · 1M tokens
$1.92 + 3%$1.98
Cache read · 1M tokens
$0.120 + 3%$0.124
FEE — FLAT, EVERY MODEL3%
One workload, priced on both
10M input + 2M output tokens at each model's price, flat 3% fee included.
z-ai/glm-4.6Cheaper
$8.01
$7.78 provider + 3%
z-ai/glm-5
$10.14
$9.84 provider + 3%
Benchmarks
Design Arena categories where both models have results. Higher Elo and lower rank win.
| GLM 4.6 | GLM 5 | |||
|---|---|---|---|---|
| Category | Elo | Rank | Elo | Rank |
| 3D | 1205 | #42 | 1307 | #15 |
| androidnative | 1097 | #20 | 1244 | #6 |
| Code | 1215 | #47 | 1295 | #16 |
| Data viz | 1208 | #44 | 1269 | #22 |
| Full-stack | 1098 | #22 | 1190 | #13 |
| Game dev | 1215 | #40 | 1299 | #15 |
| godotgamedev | 1219 | #7 | 1237 | #3 |
| Mobile apps | 1186 | #19 | 1222 | #10 |
| SVG | 1167 | #38 | 1225 | #19 |
| UI components | 1214 | #43 | 1287 | #21 |
| Websites | 1217 | #47 | 1290 | #18 |
Head-to-head preference voting. How we filter and rank
Pricing math
GLM 4.6 costs $0.43/M input and $1.74/M output from the provider; on OpenKey that's $0.43 × 1.03 = $0.4429/M input and $1.74 × 1.03 = $1.7922/M output. GLM 5 costs $0.60/M input and $1.92/M output from the provider, or $0.618/M input and $1.9776/M output on OpenKey. GLM 4.6's input price is 72% of GLM 5's (input_price_ratio: 0.72) — a real gap, but not a large absolute one at typical volumes.
For a 10M-input / 2M-output workload: GLM 4.6 runs $7.78 total, GLM 5 runs $9.84. That's a $2.06 difference for that workload — worth noting if you're running this at scale, but small next to the capability gap below.
Coding and agent benchmarks
Across the 11 Design Arena categories both models share, GLM 5 has a higher Elo in all 11. The gaps are largest in agentic categories: androidnative (1244 vs 1097, GLM 5 ranked #6 vs GLM 4.6's #20), mobileapps (1222 vs 1186, rank #10 vs #19), and fullstack (1190 vs 1098, rank #13 vs #22). In pure model-quality categories the gap is smaller but consistent: codecategories (1295 vs 1215), gamedev (1299 vs 1215), website (1290 vs 1217). GLM 4.6 has an artificial_analysis agentic_index of 17.7; no equivalent index is reported for GLM 5, so that comparison isn't available. GLM 5 also enables reasoning by default, which GLM 4.6 does not.
Context and parameters
Both models share the same 202,752-token context window — no advantage either way (context_ratio: 1.0). GLM 4.6 caps completions at 131,072 tokens; GLM 5 doesn't report a max_completion_tokens limit in this data, so don't assume it's unlimited, just undocumented here. GLM 5 supports two extra parameters GLM 4.6 doesn't: `logprobs` and `top_logprobs`, useful if you need token-level probability data for evaluation or guardrail pipelines. Otherwise the parameter sets are nearly identical (tool calling, structured outputs, reasoning toggles, penalties).
When to pick each
Pick GLM 5 by default for anything involving code generation, multi-step agent workflows, or app scaffolding — the Elo gap holds across every shared category, agentic and otherwise. Pick GLM 4.6 when you're running high-volume, less demanding tasks where the 28% lower input cost adds up, or when you don't need default-on reasoning and want a lighter-weight call. Both models are available on OpenKey through one API key, billed at the provider's list price plus a flat 3% fee.
Which model for which job
| Use case | Pick | Why |
|---|---|---|
| Agentic coding (mobile/full-stack apps) | GLM 5 | Leads GLM 4.6 in androidnative (1244 vs 1097), fullstack (1190 vs 1098), and mobileapps (1222 vs 1186) Elo |
| Game dev / Godot workflows | GLM 5 | godotgamedev Elo 1237 (rank #3) vs GLM 4.6's 1219 (rank #7) |
| High-volume batch text generation | GLM 4.6 | Input price is 28% lower ($0.4429/M vs $0.618/M on OpenKey) |
| UI component / website generation | GLM 5 | uicomponent Elo 1287 vs 1214, website Elo 1290 vs 1217 |
| Need token-level probability output | GLM 5 | Only GLM 5 supports `logprobs` and `top_logprobs` parameters |
| Long-context document work | Either | Both share the identical 202,752-token context window |
Questions
- Is GLM 5 worth the extra cost over GLM 4.6?
- For coding and agent tasks, yes. GLM 5 wins all 11 shared Design Arena categories, with a 147-point Elo gap in androidnative (1244 vs 1097). The cost difference on a 10M-input/2M-output workload is $9.84 vs $7.78 — about $2.06 more, which is small relative to the capability gap.
- Do GLM 4.6 and GLM 5 have the same context window?
- Yes, both support 202,752 tokens of context (context_ratio: 1.0). GLM 4.6 caps output at 131,072 tokens; GLM 5's max output isn't documented in the catalog data, so check current provider docs before relying on a specific limit.
- How much more expensive is GLM 5 per token?
- GLM 5's input price is $0.618/M on OpenKey ($0.60 provider price × 1.03) versus GLM 4.6's $0.4429/M ($0.43 × 1.03) — GLM 4.6's input price is 72% of GLM 5's. Output is closer: $1.9776/M vs $1.7922/M.
- Does GLM 5 use reasoning by default?
- Yes — GLM 5 has default_enabled reasoning, while GLM 4.6's reasoning is optional and not mandatory. Both models support the `reasoning` parameter, but GLM 5 turns it on unless you explicitly disable it, which can affect latency and output token counts.