Skip to main content
Radar

Provider changes are easy to miss. Radar watches releases, pricing, deprecations, and incidents at the source.Provider changes are easy to miss.

See Radar
BenchLM
Advertise

Model comparison

GLM-4.7 vs GLM-5.1

Updated August 7, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.

GLM-4.7

Z.AI

60.4/100

Supported · Public rank #48

90% interval 46.8–74.0

GLM-5.1

Z.AI

66.9/100

Supported · Public rank #22

90% interval 57.1–76.7

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

7 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.1

    GLM-5.1 leads on the same 2 weighted benchmark rows.

    Confidence: limited

  • Long documents

    Prompts that approach the documented context limit

    GLM-5.1

    GLM-5.1 has the larger documented context window.

    Confidence: documented

Show secondary and unsupported calls

  • 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

  • Chat turn cost

    1K fresh input + 500 output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates

  • 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-4.7 does not fit this workload in one request. GLM-5.1 does not fit this workload in one request. GLM-5.1 has no published cached-input rate, so cached tokens use its listed input rate. GLM-4.7 has no comparable published API token rate.

    Confidence: rate-fallback

  • Repository review cost

    50K fresh input + 3K output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates

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
7
GLM-4.7 only
6
GLM-5.1 only
13
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-4.7
45.7
GLM-5.1
65.4
Weighted basis
2 vs 2 rows
Reading
GLM-5.1 leads

Coding

Directional only
GLM-4.7
75.4
GLM-5.1
61.3
Weighted basis
3 vs 2 rows
Reading
Directional only

Knowledge

Directional only
GLM-4.7
51.8
GLM-5.1
52.3
Weighted basis
3 vs 1 rows
Reading
Directional only

Math

Directional only
GLM-4.7
1.8
GLM-5.1
62.0
Weighted basis
2 vs 4 rows
Reading
Directional only

Reasoning

Not comparable
GLM-4.7
Not measured
GLM-5.1
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Multilingual

Not comparable
GLM-4.7
Not measured
GLM-5.1
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Multimodal

Not comparable
GLM-4.7
Not measured
GLM-5.1
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Instruction following

Not comparable
GLM-4.7
Not measured
GLM-5.1
Not measured
Weighted basis
0 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-4.7
Self-hosted; infrastructure cost varies
Fits in one request
GLM-5.1
$0.0036
Fits in one request

GLM-4.7 has no comparable published API token rate.

Repository review

50K fresh input + 3K output tokens

GLM-4.7
Self-hosted; infrastructure cost varies
Fits in one request
GLM-5.1
$0.0832
Fits in one request

GLM-4.7 has no comparable published API token rate.

Cache-heavy agent loop

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

GLM-4.7
Self-hosted; infrastructure cost varies
Does not fit in one request
Cached-input rate unavailable
GLM-5.1
$0.352
Does not fit in one request
Cached input priced at the published list-input rate

GLM-4.7 does not fit this workload in one request. GLM-5.1 does not fit this workload in one request. GLM-5.1 has no published cached-input rate, so cached tokens use its listed input rate. GLM-4.7 has no comparable published API token 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-4.7

200K

GLM-5.1

203K

API model ID

GLM-4.7

Not sourced

GLM-5.1

Not sourced

Cached-input rate

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

GLM-4.7

No comparable hosted API rate

GLM-5.1

Not published

Documented inputs

GLM-4.7

Not sourced

GLM-5.1

Not sourced

Documented outputs

GLM-4.7

Not sourced

GLM-5.1

Not sourced

Provider availability

GLM-4.7

Not sourced

GLM-5.1

Not sourced

Reasoning profile

GLM-4.7

Reasoning

GLM-5.1

Reasoning

Weight access

GLM-4.7

Open Weight

GLM-5.1

Open Weight

License

GLM-4.7

Open Weight

GLM-5.1

Open Weight

Release date

GLM-4.7

2025-10-01

GLM-5.1

2026-04-07

If you already use one of these models
Deployment change
Both entries list Z.AI as the provider. Confirm endpoint, model ID, limits, and feature support before switching.
Quality signal
GLM-5.1 has the higher public score estimate, 66.9 versus 60.44, but the 90% score intervals overlap.
Workload cost
A complete comparable API-rate estimate is not available for both models.
Context tradeoff
GLM-5.1 has the larger documented window (203K).

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

Self-host vs API cost

Estimates at 50,000 req/day · 1000 tokens/req average.

GLM-4.7
API / mo$0
Self-host / moNot listed
Break-even—
Proprietary model — self-hosting not applicable.
GLM-5.1
API / mo$4,350
Self-host / mo$18,221
Break-even264M/day
Model the full break-even

Benchmark evidence

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

Browse raw public benchmark evidence26 rows

Agentic

  • Terminal-Bench 2.0

    GLM-4.741%
    Source
    GLM-5.163.5%
    Source

    GLM-5.1 leads this result

  • BrowseComp

    GLM-4.752%
    Source
    GLM-5.168%
    Source

    GLM-5.1 leads this result

  • VITA-Bench

    GLM-4.715.5%
    Source
    GLM-5.1—

    Not directly comparable

  • Gert Labs

    Shared source
    GLM-4.739.95%
    GLM-5.160.11%

    GLM-5.1 leads this result

  • τ³-bench results

    GLM-4.7—
    GLM-5.170.6%
    Source

    Not directly comparable

  • MCP Atlas

    GLM-4.7—
    GLM-5.171.8%
    Source

    Not directly comparable

  • CyberGym

    GLM-4.7—
    GLM-5.168.7%
    Source

    Not directly comparable

  • Claw-Eval

    GLM-4.7—
    GLM-5.162.3%
    Source

    Not directly comparable

  • ResearchClawBench

    GLM-4.7—
    GLM-5.118.2%
    Source

    Not directly comparable

Coding

  • SWE-bench Verified

    GLM-4.773.8%
    Source
    GLM-5.1—

    Not directly comparable

  • LiveCodeBench

    GLM-4.784.9%
    Source
    GLM-5.1—

    Not directly comparable

  • SWE-Rebench

    Shared source
    GLM-4.758.7%
    GLM-5.162.7%

    GLM-5.1 leads this result

  • SWE-bench Pro

    GLM-4.7—
    GLM-5.158.4%
    Source

    Not directly comparable

  • NL2Repo

    GLM-4.7—
    GLM-5.142.7%
    Source

    Not directly comparable

  • Vibe Code Bench

    GLM-4.7—
    GLM-5.131.46%
    Source

    Not directly comparable

Knowledge

  • GPQA

    GLM-4.785.7%
    Source
    GLM-5.1—

    Not directly comparable

  • MMLU-Pro

    GLM-4.784.3%
    Source
    GLM-5.1—

    Not directly comparable

  • HLE

    GLM-4.724.8%
    Source
    GLM-5.152.3%
    Source

    GLM-5.1 leads this result

  • GPQA-D

    GLM-4.7—
    GLM-5.186.2%
    Source

    Not directly comparable

Math

  • AIME 2025

    GLM-4.795.7%
    Source
    GLM-5.1—

    Not directly comparable

  • FrontierMath v2 (Tiers 1-3)

    Shared source
    GLM-4.72.439%
    GLM-5.133.448%

    GLM-5.1 leads this result

  • FrontierMath v2 (Tier 4)

    Shared source
    GLM-4.70.000%
    GLM-5.112.500%

    GLM-5.1 leads this result

  • AIME26

    GLM-4.7—
    GLM-5.195.3%
    Source

    Not directly comparable

  • HMMT Nov 2025

    GLM-4.7—
    GLM-5.194.0%
    Source

    Not directly comparable

  • HMMT Feb 2026

    GLM-4.7—
    GLM-5.182.6%
    Source

    Not directly comparable

  • MMAnswerBench

    GLM-4.7—
    GLM-5.183.8%
    Source

    Not directly comparable

Frequently asked questions

Which is better, GLM-4.7 or GLM-5.1?

GLM-5.1 has the higher public score estimate, 66.9 versus 60.44, 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-4.7 or GLM-5.1?

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-4.7 or GLM-5.1?

GLM-5.1 leads the like-for-like agentic tasks comparison across 2 shared weighted benchmark rows.

Which costs less, GLM-4.7 or GLM-5.1?

Both models do not have comparable published API token rates, so this page does not name a universal price winner.

Which has the larger context window, GLM-4.7 or GLM-5.1?

GLM-5.1 has the larger documented context window: 203K, compared with 200K.

Related comparisons

Compare API pricing Read the methodology Open the model selector

Last updated August 7, 2026

Watch GLM-4.7 vs GLM-5.1

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

Read a sample issue

Join 2,000+ readers.