Home  /  Blog  /  LiveBench explained
Benchmark explainer

LiveBench explained: the contamination-free benchmark that anchors our League Score.

LiveBench explained in plain terms: a benchmark built so its questions cannot leak into training data, scored across seven task suites. Here is what a LiveBench score measures, how the overall number is calculated, and how we turn it into the largest single component of the League Score.

By AI Pro League · Published

LiveBench explained — AI Pro League benchmark explainer

LiveBench carries 40% of the League Score on this site — more than any other single component — because it is the broadest general-capability test we track. It is also the benchmark whose headline number moves most often: our own roundup of the biggest AI model ranking changes traced the League’s largest one-day fall to a single LiveBench re-measurement. This explainer uses our own LiveBench leaderboard as the worked example throughout.

What LiveBench measures

LiveBench describes itself, on livebench.ai, as “a challenging, contamination-free long-horizon AI benchmark”. Contamination is the problem it is built to solve: a fixed test published once can end up inside a model’s training data, after which the score measures memorisation as much as capability. LiveBench instead scores models across seven task suites — agentic work, design, coding, browser use, data analysis, research and reasoning — so the overall number reflects long, multi-step tasks rather than short quiz questions alone.

How a LiveBench score is calculated

On LiveBench itself, the overall score is a weighted mean of the suites a model has a score in: the agentic suite counts double, design and coding count one and a half times, and the remaining suites count once. Our League Score then normalises that raw overall across the field we track — today the recorded range runs from 38.7 to 85.7 — and weights the result at 40%. The worked example, from the top of our table:

From raw score to League component (top 3, as recorded)
ModelRaw scoreNormalised (0–100)
Claude Fable 5.185.7(85.7 − 38.7) / (85.7 − 38.7) × 100 = 100.0
GPT-6 Astra85.6(85.6 − 38.7) / (85.7 − 38.7) × 100 = 99.8
Claude Opus 5.585.1(85.1 − 38.7) / (85.7 − 38.7) × 100 = 98.7

Because normalisation is relative to the field, a model’s component can move when a rival is re-measured, even if its own raw score never changed — exactly what happened across the table on October 26. Full method: how the League Score is built.

What a good LiveBench score looks like

31 of the 59 models in our database carry a recorded LiveBench score. The field is wide: the median recorded score is 69.8, the floor is 38.7 and the ceiling is 85.7. The top of the table:

Top 5 on our LiveBench leaderboard
#ModelMakerScoreMeasured
1Claude Fable 5.1Anthropic85.7Oct 26, 2026
2GPT-6 AstraOpenAI85.6Oct 26, 2026
3Claude Opus 5.5Anthropic85.1Oct 26, 2026
4GPT-6.1 SolOpenAI84.1Oct 26, 2026
5Claude Opus 5Anthropic82.1Oct 14, 2026

The full table, with a source link on every row, is the LiveBench leaderboard. The shortlist it feeds is our best AI chatbots page, and the standings it drives are the AI model rankings.

Why LiveBench scores move — and when to distrust a gap

A contamination-free benchmark has to keep its questions fresh, which means the test itself changes over time: a score recorded in one month is not measured against exactly the same question set as a score recorded later. That is why our table carries a measured date on every row, and why a re-measurement can drop a model sharply — on October 26 one model’s recorded score fell from 74.8 to 63.0 without the model itself changing at all. Treat small gaps between models measured on different dates as directional, not decisive.

The limits to keep in mind

For the companion tests, start with our explainers of GPQA Diamond and SWE-bench Verified, or the wider guide to AI benchmarks explained.