Skip to main content

Model comparison

GLM-5 vs GLM-5.2

Updated July 31, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload. This is a same-family comparison, so migration details appear when the source data supports them.

21 confirmed releases in the last 30 daystrack changes
GLM-5

Z.AI

65.2/100

Supported · Public rank #31

90% interval 54.4–76.1

GLM-5.2

Z.AI

62.9/100

Estimated · Public rank #41

90% interval 47.7–78.2

GLM-5 has the higher public score estimate, 65.24 versus 62.94, but the 90% score intervals overlap. Treat that as a lead, not a settled winner.

11 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.

Which one for your work

Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.

  • Agentic work

    Tool use, computer use, and multi-step task completion

    GLM-5.2

    GLM-5.2 leads on the same 1 weighted benchmark row.

    Confidence: limited

  • Long documents

    Prompts that approach the documented context limit

    GLM-5.2

    GLM-5.2 has the larger documented context window.

    Confidence: documented

  • Chat turn cost

    1K fresh input + 500 output tokens

    GLM-5

    GLM-5 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.

    Confidence: listed-rates

Show secondary and unsupported calls
  • Repository review cost

    50K fresh input + 3K output tokens

    GLM-5

    GLM-5 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.

    Confidence: listed-rates

  • Coding work

    Code generation, repair, and software-engineering tasks

    Not enough matched evidence

    The category averages use different weighted benchmark sets, so they are directional rather than like-for-like.

    Confidence: limited

  • Cache-heavy agent loop cost

    200K cached + 20K fresh input + 10K output tokens

    Not enough matched evidence

    The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. GLM-5 does not fit this workload in one request. GLM-5 has no published cached-input rate, so cached tokens use its listed input rate. GLM-5.2 has no published cached-input rate, so cached tokens use its listed input rate.

    Confidence: rate-fallback

What is actually comparable

Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.

Shared results
11
GLM-5 only
25
GLM-5.2 only
7
Like-for-like categories
1 / 8

3 categories use different evidence sets. Those rows remain visible for coverage context but do not name a winner.

Category results, on a stated basis

Each row states whether both averages use the same weighted benchmark set. Directional and not-comparable rows remain visible, but they never receive a winner in this template.

Agentic

Like-for-like
GLM-5
56.2
GLM-5.2
81.0
Weighted basis
1 vs 1 rows
Reading
GLM-5.2 leads

Coding

Directional only
GLM-5
66.3
GLM-5.2
62.1
Weighted basis
3 vs 1 rows
Reading
Directional only

Knowledge

Directional only
GLM-5
66.4
GLM-5.2
59.6
Weighted basis
4 vs 2 rows
Reading
Directional only

Math

Directional only
GLM-5
56.3
GLM-5.2
95.9
Weighted basis
4 vs 2 rows
Reading
Directional only

Reasoning

Not comparable
GLM-5
60.8
GLM-5.2
Not measured
Weighted basis
1 vs 0 rows
Reading
Not comparable

Multilingual

Not comparable
GLM-5
83.1
GLM-5.2
Not measured
Weighted basis
1 vs 0 rows
Reading
Not comparable

Multimodal

Not comparable
GLM-5
Not measured
GLM-5.2
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Instruction following

Not comparable
GLM-5
92.6
GLM-5.2
Not measured
Weighted basis
1 vs 0 rows
Reading
Not comparable

Shape of the matched evidence

Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.

Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.

What each workload costs

Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.

Chat turn

1K fresh input + 500 output tokens

GLM-5
$0.0026
Fits in one request
GLM-5.2
$0.0036
Fits in one request

GLM-5 has the lower modeled cost

Costs use the listed standard API rates.

Repository review

50K fresh input + 3K output tokens

GLM-5
$0.0596
Fits in one request
GLM-5.2
$0.0832
Fits in one request

GLM-5 has the lower modeled cost

Costs use the listed standard API rates.

Cache-heavy agent loop

200K cached + 20K fresh input + 10K output tokens

GLM-5
$0.252
Does not fit in one request
Cached input priced at the published list-input rate
GLM-5.2
$0.352
Fits in one request
Cached input priced at the published list-input rate

GLM-5 does not fit this workload in one request. GLM-5 has no published cached-input rate, so cached tokens use its listed input rate. GLM-5.2 has no published cached-input rate, so cached tokens use its listed input rate.

Specification differences

Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.

Context window

Maximum documented context; output-token limits may be lower.

GLM-5

200K

GLM-5.2

1M

API model ID

GLM-5

Not sourced

GLM-5.2

Not sourced

Cached-input rate

A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.

GLM-5

Not published

GLM-5.2

Not published

Documented inputs

GLM-5

Not sourced

GLM-5.2

Not sourced

Documented outputs

GLM-5

Not sourced

GLM-5.2

Not sourced

Provider availability

GLM-5

Not sourced

GLM-5.2

Not sourced

Reasoning profile

GLM-5

Non-Reasoning

GLM-5.2

Reasoning

Weight access

GLM-5

Open Weight

GLM-5.2

Open Weight

License

GLM-5

Open Weight

GLM-5.2

Open Weight

Release date

GLM-5

2026-03-01

GLM-5.2

2026-06-16

If you are choosing between sibling variants
Deployment change
Both entries list Z.AI as the provider. Confirm endpoint, model ID, limits, and feature support before switching.
Quality signal
GLM-5 has the higher public score estimate, 65.24 versus 62.94, but the 90% score intervals overlap.
Workload cost
Repository review: $0.0596 vs $0.0832. Cache-heavy agent loop: $0.252 vs $0.352.
Context tradeoff
GLM-5.2 has the larger documented window (1M).

Run the same representative tasks against both endpoints before changing production traffic.

Benchmark evidence

The full public result ledger is available for audit without forcing a wide desktop table onto a phone.

Browse raw public benchmark evidence43 rows

Agentic

  • Terminal-Bench 2.0

    GLM-556.2%
    Source
    GLM-5.281%
    Source

    GLM-5.2 leads this result

  • Claw-Eval

    GLM-557.7%
    Source
    GLM-5.2

    Not directly comparable

  • QwenClawBench

    GLM-554.1%
    Source
    GLM-5.2

    Not directly comparable

  • τ³-bench results

    GLM-565.6%
    Source
    GLM-5.2

    Not directly comparable

  • DeepPlanning

    GLM-514.6%
    Source
    GLM-5.2

    Not directly comparable

  • Toolathlon

    GLM-538%
    Source
    GLM-5.248.2%
    Source

    GLM-5.2 leads this result

  • MCP Atlas

    GLM-531.1%
    Source
    GLM-5.276.8%
    Source

    GLM-5.2 leads this result

  • MCP-Tasks

    GLM-560.8%
    Source
    GLM-5.2

    Not directly comparable

  • WideResearch

    GLM-569.8%
    Source
    GLM-5.2

    Not directly comparable

  • CyberGym

    GLM-543.2%
    Source
    GLM-5.2

    Not directly comparable

  • Gert Labs

    GLM-550.99%
    Source
    GLM-5.2

    Not directly comparable

  • ResearchClawBench

    GLM-5
    GLM-5.220.7%
    Source

    Not directly comparable

Coding

  • SWE-bench Verified

    GLM-577.8%
    Source
    GLM-5.2

    Not directly comparable

  • SWE-bench Verified*

    GLM-572.8%
    Source
    GLM-5.2

    Not directly comparable

  • SWE-bench Pro

    GLM-555.1%
    Source
    GLM-5.262.1%
    Source

    GLM-5.2 leads this result

  • SWE Multilingual

    GLM-573.3%
    Source
    GLM-5.2

    Not directly comparable

  • SWE-Rebench

    GLM-562.8%
    Source
    GLM-5.2

    Not directly comparable

  • React Native Evals

    GLM-574.8%
    Source
    GLM-5.2

    Not directly comparable

  • NL2Repo

    GLM-5
    GLM-5.248.9%
    Source

    Not directly comparable

  • Terminal-Bench 2.0

    GLM-5
    GLM-5.281.0%
    Source

    Not directly comparable

  • ProgramBench

    GLM-5
    GLM-5.263.7%
    Source

    Not directly comparable

  • cursorBench32

    GLM-5
    GLM-5.255.0%
    Source

    Not directly comparable

Reasoning

  • LongBench v2

    GLM-560.8%
    Source
    GLM-5.2

    Not directly comparable

  • AI-Needle

    GLM-563.3%
    Source
    GLM-5.2

    Not directly comparable

  • CritPt

    GLM-5
    GLM-5.220.9%
    Source

    Not directly comparable

Knowledge

  • GPQA

    GLM-586%
    Source
    GLM-5.291.2%
    Source

    GLM-5.2 leads this result

  • GPQA-D

    GLM-586.0%
    Source
    GLM-5.291.2%
    Source

    GLM-5.2 leads this result

  • SuperGPQA

    GLM-566.8%
    Source
    GLM-5.2

    Not directly comparable

  • MMLU-Pro

    GLM-585.7%
    Source
    GLM-5.2

    Not directly comparable

  • MMLU-Pro (Arcee)

    GLM-585.8%
    Source
    GLM-5.2

    Not directly comparable

  • HLE

    GLM-550.4%
    Source
    GLM-5.254.7%
    Source

    GLM-5.2 leads this result

  • HLE w/o tools

    GLM-5
    GLM-5.240.5%
    Source

    Not directly comparable

Math

  • AIME26

    GLM-595.8%
    Source
    GLM-5.299.2%
    Source

    GLM-5.2 leads this result

  • AIME25 (Arcee)

    GLM-593.3%
    Source
    GLM-5.2

    Not directly comparable

  • HMMT Feb 2025

    GLM-597.5%
    Source
    GLM-5.2

    Not directly comparable

  • HMMT Nov 2025

    GLM-596.9%
    Source
    GLM-5.294.4%
    Source

    GLM-5 leads this result

  • HMMT Feb 2026

    GLM-586.4%
    Source
    GLM-5.292.5%
    Source

    GLM-5.2 leads this result

  • MMAnswerBench

    GLM-582.5%
    Source
    GLM-5.291.0%
    Source

    GLM-5.2 leads this result

  • FrontierMath v2 (Tiers 1-3)

    GLM-516.434%
    Source
    GLM-5.2

    Not directly comparable

  • FrontierMath v2 (Tier 4)

    GLM-52.100%
    Source
    GLM-5.2

    Not directly comparable

Multilingual

  • MMLU-ProX

    GLM-583.1%
    Source
    GLM-5.2

    Not directly comparable

  • NOVA-63

    GLM-555.1%
    Source
    GLM-5.2

    Not directly comparable

Instruction following

  • IFEval

    GLM-592.6%
    Source
    GLM-5.2

    Not directly comparable

Frequently asked questions

Which is better, GLM-5 or GLM-5.2?

GLM-5 has the higher public score estimate, 65.24 versus 62.94, but the 90% score intervals overlap. The higher estimate is not a decisive winner because the uncertainty ranges overlap.

Which is better for coding, GLM-5 or GLM-5.2?

The current coding averages use different weighted benchmark sets, so BenchLM does not name a winner from them. Read the shared benchmark rows directly and test the models on the same task set.

Which is better for agentic tasks, GLM-5 or GLM-5.2?

GLM-5.2 leads the like-for-like agentic tasks comparison across 1 shared weighted benchmark row.

Which costs less, GLM-5 or GLM-5.2?

For the stated presets, chat costs $0.0026 on GLM-5 and $0.0036 on GLM-5.2; repository review costs $0.0596 and $0.0832; the cache-heavy agent loop costs $0.252 and $0.352. GLM-5 does not fit this workload in one request. GLM-5 has no published cached-input rate, so cached tokens use its listed input rate. GLM-5.2 has no published cached-input rate, so cached tokens use its listed input rate.

Which has the larger context window, GLM-5 or GLM-5.2?

GLM-5.2 has the larger documented context window: 1M, compared with 200K.

Related comparisons

Last updated July 31, 2026

Watch GLM-5 vs GLM-5.2

One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.

Read a sample issue

Join 2,000+ readers.