Methodology

How scoring works

A score is only worth something if you can see how it was made. This page explains every step, first in plain words, then in full detail.

Version 2.3 · Sep 26, 2026 · 40 of 100 models scored. The rest stay blank until there’s enough evidence.

The short version

Think of it as a report card

  1. 01

    Every kind of model gets its own report card

    You wouldn’t grade a fish on climbing trees. Image models are graded on things like picture quality and following instructions; chat models on reasoning, accuracy, and speed. Each category has its own subjects.

  2. 02

    Each subject gets a mark from 0 to 10

    Reasoning: 9. Accuracy: 8. Writing: 7. Every mark comes from a public measurement or a published checklist, never from a gut feeling.

  3. 03

    Some subjects count more than others

    For a chat model, reasoning counts for 45% of the final grade and writing for 15%. The weight of every subject is shown next to it (w45, w15).

  4. 04

    Price isn’t one of the subjects

    What a model costs doesn’t change what it can do, so price and availability are measured and shown on every card but kept out of the grade. Otherwise a cheap model would outrank a stronger one in a ranking that claims to say which is better.

  5. 05

    A mark says how sure we are

    Where a source publishes a margin of error, we take the cautious end of it, and a model tested only a few hundred times doesn’t get a mark at all. Two models whose margins overlap are shown as tied, because the evidence can’t separate them.

  6. 06

    The final score is a weighted average

    Strong marks in heavy subjects pull the score up more than strong marks in light ones. That’s the number in the corner of a card, like 8.2/10.

  7. 07

    No final grade without enough homework

    A model needs marks covering at least 80% of what counts before it gets a final score, so one lucky subject can’t make it look amazing.

  8. 08

    Nobody can buy a grade

    Companies don’t pay to be listed or scored, and they don’t see scores before they’re published. If a number is wrong, the fix is better evidence, not a phone call.

In detail · step 1

Where each mark comes from

Every criterion is scored with one of three rules. The rule used, the source, and the date appear next to each mark on the model’s page, so any number can be checked.

Rule A · Benchmark results

Percent scores map straight to marks

When a public benchmark reports a percentage, the mark is that percentage divided by ten. 72% becomes 7.2. The mark doesn’t move when other models are added.

SWE-bench Verified: 75.6% → 7.6

Rule B · Measured quantities

Placed on a fixed, published scale

Arena ratings, price, and context length are placed between a floor that scores 0 and a ceiling that scores 10, both published below and fixed. Where the source gives a confidence interval, the mark uses its low end. Nothing depends on which other models we happen to list.

Rating 1,450 on the 700–1,550 scale → 8.8

Rule C · Judgement criteria

A published checklist

Things like licensing or data controls can’t be benchmarked, so each gets a five-item checklist worth two points per item. Each checklist is published on this page before any model is marked against it.

4 of 5 checklist items met → 8.0

  • Each model is scored on one named version, shown on its page, together with the exact leaderboard entry behind each mark.
  • Cost uses a blended price: 3 parts input to 1 part output, per million tokens.
  • Rule B marks are absolute. A model’s mark changes only when its own measurement changes, never because another model was added to or removed from the directory.
  • A human-preference rating built on fewer than 500 votes is treated as unmeasured rather than as a weak result.
  • Where a model has several tested settings, we credit the strongest result we can be confident in: the highest lower bound, not the highest headline figure.
  • If there’s no trustworthy source for a criterion, it stays empty (shown as “—”). We never estimate or fill gaps.
  • Vendor marketing claims are never used as evidence. Independent measurements and published benchmark results are.
In detail · the scales

Every Rule B scale, published

Each scale was set on Sep 20, 2026 from the leaderboard’s own published spread: the floor is its lowest listed rating and the ceiling its highest, rounded outward to the nearest 50. They are fixed. Changing one means a new entry in the changelog at the bottom of this page, and every score recomputed.

MeasurementScores 0Scores 10Shape
LMArena text (hard prompts)7001,550even
LMArena text (creative writing)7501,550even
LMArena WebDev1,0501,800even
LMArena text-to-image8501,450even
LMArena text-to-image (text rendering)8501,500even
LMArena text-to-image (commercial design)8501,450even
LMArena image edit9501,550even
LMArena text-to-video1,0001,550even
LMArena image-to-video9501,500even
LMArena text (non-English prompts)7501,550even
Blended price per 1M tokens$30$0.05×10 steps
Context window (tokens)8,1921,048,576×10 steps

“Even” means equal steps: halfway between the floor and the ceiling scores 5. “×10 steps” means each tenfold change moves the mark by the same amount, which is how price and context windows actually vary — the gap between $0.10 and $1 matters as much as the gap between $1 and $10. A measurement beyond either end is clamped, so nothing scores below 0 or above 10.

In detail · the reasoning

Why this isn’t just a leaderboard

Public leaderboards are the raw material here, and they’re credited on every mark. Four deliberate choices separate a score on this site from a position on any one of them.

More than one kind of evidence

Human preference tells you what people liked. It doesn’t tell you whether the answer was true, or whether the code ran. A score here combines preference votes with task success on real GitHub issues and measured factual consistency, because no single signal covers what a model is for.

The cautious end of the evidence

A rating is an estimate with a margin of error, and that margin is wider for a model tested a few hundred times than one tested fifty thousand times. Marks use the low end of the published interval, so being barely tested can’t look like being good, and a rating below 500 votes isn’t used at all.

Ties are called ties

When two models’ intervals overlap, the evidence cannot separate them, so the leaderboard marks them as statistically tied instead of presenting an order that’s really noise.

Capability and price kept apart

Cheap and good are different claims. Both are measured here, and both are shown on every model’s page, but only capability decides the ranking — so the board answers one question at a time.

None of this makes a score the last word. Every leaderboard behind it measures what it can measure, on the prompts it happens to collect, at one moment in time. What this method adds is that each number is traceable to a dated, public source, computed by published rules, and honest about how firm it is.

In detail · the sources

Every source we use

All independent, all public. Their data is copied into a dated snapshot, so scores only change when the snapshot is refreshed, and the date shows on every mark.

LMArena ↗data as of Nov 2, 2026

Human-preference ratings from blind, side-by-side votes: text (hard prompts, creative writing), web development, text-to-image, image editing, text-to-video, and image-to-video. Its English and non-English categories split the same votes by the language of the prompt; they feed the multilingual board rather than any score.

Arenas published 2026-09-13 to 2026-11-02

SWE-bench Verified ↗data as of Feb 26, 2026

Share of real GitHub issues resolved. Only runs using the same open harness (mini-SWE-agent) are counted, so results are comparable.

OpenRouter ↗data as of Nov 4, 2026

List prices, context windows, supported features, and the number of independent providers serving each model.

Arabic ability

The sources above are run in English, so they say nothing about how well a model handles Arabic. These two do, and they are the only current Arabic leaderboards that publish results in a form anyone can read back and check. They feed the Arabic leaderboard on the home page, not the directory’s scores: a model’s place there is a separate measurement against a different field of models, and neither number should be read as the other.

The home page shows both boards per model and one combined figure. They aren’t simply averaged: the scales aren’t interchangeable, and across the 25 models both boards have run the agreement is moderate rather than tight (r = 0.67). So a line is fitted on exactly those 25 models — AraGen ≈ -0.169 + 0.795 × OALL — an OALL result is converted into AraGen’s terms carrying ±2.2 marks of error at 95%, and the two figures are combined by weighting each by how firm it is. A model only one board has measured therefore carries a wide band and, under the low-end rule above, is marked low and ties with much of the table. That is the evidence speaking, not a fault in the table.

AraGen v3 ↗data as of Apr 4, 2026

Free-form Arabic answers scored on six qualities — correctness, completeness, conciseness, helpfulness, honesty and harmlessness — by a judge model (claude-sonnet-4-20250514), published with a bootstrap 95% interval. 67 models measured.

The average of seven native Arabic benchmarks — AlGhafa, ArabicMMLU, EXAMS, MadinahQA, AraTrust, ALRAGE, ArbMMLU-HT — run zero-shot through LightEval. 163 models measured.

Deployability checklist (Rule C)

Two points per item, checked against OpenRouter’s data.

  1. 1Weights can be downloaded and self-hosted
  2. 2Served by at least 2 independent providers
  3. 3Served by at least 4 independent providers
  4. 4Supports tool calling
  5. 5Supports structured (JSON) outputs
In detail · step 2

The maths, with a worked example

Here is an example language model. It isn’t a real model; the marks are made up to show the calculation. The numbers below are computed by the same code that scores the directory.

CriterionMarkWeightMark × weight
Reasoning945405
Accuracy820160
Writing715105
Long context620120
Total100790
Overall score

790 ÷ 100 = 7.9

Add up each mark multiplied by its weight, then divide by the total weight. Rounded to one decimal place, only at the end. Price and availability aren’t in this table: they’re measured and shown on the model’s page, but they don’t count toward the score.

If only some marks exist

With only Reasoning and Writing marked, the evidence covers 60% of the weight, below the 80% bar. So there’s no overall score, and the card says “in assessment” instead. Once a model clears the bar, the average uses only the marks that exist and their weights.

In detail · step 3

What we promise, and what we refuse to do

We always

  • Show the source and date for every mark.
  • Publish the rubric and weights before scoring against them.
  • Score every model in a category with the same rules and sources.
  • Recalculate every score whenever a weight or rule changes, and date the change.
  • Correct a score when better evidence appears, whoever points it out, and date the correction.

We never

  • Accept payment for listings, scores, or placement.
  • Let a vendor review or approve a score before it’s published.
  • Use marketing claims or unpublished results as evidence.
  • Estimate a mark we can’t measure, or tweak a score by hand.
  • Compare models across categories. An 8 for images and an 8 for code mean different things.
Good to know

Things on the site that look like scores, but aren’t

Adoption shares

How much each use case is used, from the Anthropic Economic Index. It measures what people ask AI to do, not which model answered, and popular isn’t the same as good — so usage never counts towards a model’s score.

See the use cases

Country adoption

A country’s share of worldwide usage, and its usage per person, from the same index. They describe where AI is used, not how good any model is in that country.

See the map
Every report card

Every report card, and what each subject is worth

Weights are relative within a rubric and shown as a share of the total. They are fixed before scoring; if one changes, every affected score is recalculated and the change is logged below.

Language Models

Criterion · measured byWeight
Reasoning
Preferred by people on hard, multi-step prompts.
Rule BLMArena text arena, hard prompts
45%
Accuracy
Sticks to the facts it was given, with few hallucinations.
Rule AVectara hallucination leaderboard, factual consistency rate
20%
Writing
Preferred by people for creative and long-form writing.
Rule BLMArena text arena, creative writing
15%
Long context
How much text it can take in at once.
Rule BOpenRouter, context window
20%
Cost efficiency
Price per token; cheaper is better.
Rule BOpenRouter, blended price per token
shown, not scored
Deployability
Open weights, choice of hosts, and integration features.
Rule CDeployability checklist (OpenRouter data)
shown, not scored

Coding & Agentic

Criterion · measured byWeight
Code quality
Share of real GitHub issues it resolves on its own.
Rule ASWE-bench Verified, % resolved (mini-SWE-agent harness)
45%
Web development
Preferred by people for building working web apps.
Rule BLMArena WebDev arena
40%
Codebase context
How much code it can take in at once.
Rule BOpenRouter, context window
15%
Cost efficiency
Price per token; cheaper is better.
Rule BOpenRouter, blended price per token
shown, not scored

Image Generation

Criterion · measured byWeight
Image quality
Preferred by people across all kinds of image prompts.
Rule BLMArena text-to-image arena
40%
Text rendering
Preferred by people for images that contain text.
Rule BLMArena text-to-image, text rendering
20%
Commercial design
Preferred by people for ads, product shots, and branding.
Rule BLMArena text-to-image, commercial design
20%
Editing
Preferred by people for editing existing images.
Rule BLMArena image-edit arena
20%

Video Generation

Criterion · measured byWeight
Text-to-video
Preferred by people for video made from a written prompt.
Rule BLMArena text-to-video arena
60%
Image-to-video
Preferred by people for video made from a starting image.
Rule BLMArena image-to-video arena
40%

Audio, Voice & Music

Criterion · measured byWeight
Output quality
Naturalness, fidelity, and musicality — or transcription accuracy.
Not scored yet: no independent source
35%
Control
Steering of voice, emotion, structure, or style.
Not scored yet: no independent source
20%
Language coverage
Breadth and quality across languages and accents.
Not scored yet: no independent source
15%
Latency
Fast enough for real-time or high-volume use.
Not scored yet: no independent source
10%
Licensing & safety
Commercial rights and consent safeguards.
Not scored yet: no independent source
10%
Cost efficiency
Price per minute or per track.
Not scored yet: no independent source
10%

Search & Enterprise

Criterion · measured byWeight
Answer grounding
Accurate answers anchored in retrieved sources.
Not scored yet: no independent source
30%
Citations
Clear, checkable references back to sources.
Not scored yet: no independent source
20%
Integrations
Connectors to company data, clouds, and tools.
Not scored yet: no independent source
20%
Governance
Permissions, audit, data residency, and admin controls.
Not scored yet: no independent source
15%
Cost efficiency
Predictable pricing at organisational scale.
Not scored yet: no independent source
15%
Changelog

Every change to the method

If a rule or weight changes, it’s listed here with its date, and every affected score is recalculated.

  1. v2.3Sep 26, 2026The two Arabic boards were merged into one table with a single combined figure, after being shown as separate tabs. Both boards’ own results stay visible on every row, because they disagree about some models and the disagreement is the finding. The combination fits a line between the two scales on the models both have run and weights each figure by how firm it is, so a converted result moves the answer least; the conversion’s error is carried into the band, which is why models known through one board alone are marked low and tie with much of the table.
  2. v2.2Sep 26, 2026A multilingual board was added to the home page, built on LMArena’s non-English category: the same blind votes as the text arena, split by the language of the prompt. Each model is shown with its place on the English board beside it, and the site states both places without turning the difference between them into a claim — in a field of 400 models the ratings around any place sit inside one another’s confidence bands, so a move of even twenty places usually can’t be told apart from noise. The non-English arena’s scale is published with the others below. No score changed: this board sits beside the directory’s scores rather than feeding them.
  3. v2.1Sep 26, 2026Arabic ability became measurable. Two independent Arabic leaderboards — AraGen, which has a judge model score free-form Arabic answers on six qualities, and the Open Arabic LLM Leaderboard, which averages seven native Arabic benchmarks — now publish results in a machine-readable form, so the site reads them directly and ranks the Arab world’s models on them. Marks follow Rule A, the low end of the published interval where there is one. No existing score changed: these boards are shown beside the directory, not folded into it, because they measure something different against a different field of models.
  4. v2.0Sep 20, 2026Three changes, after the old method produced rankings that didn’t survive scrutiny. (1) Rule B no longer ranks a model against the others in the directory; it places the measurement on a fixed, published scale, so gaps reflect real differences, leading a category no longer means an automatic 10, and adding a model doesn’t move everyone else’s marks. (2) Where a source publishes a confidence interval, the mark uses the low end of it, a rating from fewer than 500 votes is treated as unmeasured, and every score carries a band; models whose bands overlap share a rank. (3) Price and availability are still measured and shown, but no longer count toward the score, which now measures capability only. Every score on the site changed.
  5. v1.2Sep 19, 2026Coverage bar raised from 60% to 80%. A model now needs marks covering at least 80% of its rubric’s weight before it gets an overall score, so models with big gaps can’t outrank fully measured ones. Models below the bar keep their individual marks and show as in assessment.
  6. v1.1Sep 19, 2026Rubrics revised before any scores were published so that every criterion has exactly one independent source. Criteria with no independent source yet (speed, image prompt adherence, video motion, and others) were removed until one exists. Audio, search, and enterprise tools stay unscored for the same reason. First scores published.
  7. v1.0Sep 19, 2026Methodology published: rubrics, three marking rules, weighted average, 60% coverage bar.