Training Compute-Optimal Large Language Models asks how to split a fixed compute budget between model size and training data. To answer it, the authors train over 400 models from 70 million to over 16 billion parameters on 5 to 500 billion tokens, and fit the compute-optimal frontier three independent ways: an envelope of lowest losses at fixed model sizes, IsoFLOP profiles that vary model size at fixed compute, and a parametric loss fit of cross-entropy as a function of parameters and tokens. All three agree that current large models are significantly undertrained, and that the optimal choice scales parameters and tokens equally — for every doubling of model size, the number of training tokens should also double. To test the prediction they train Chinchilla, a 70B-parameter model on 1.4T tokens using the same compute budget as Gopher.
The equal-scaling prediction holds: at one quarter of Gopher’s parameters, Chinchilla uniformly beats Gopher (280B), GPT-3 (175B), Jurassic-1 (178B), and Megatron-Turing NLG (530B), reaching 67.6% on MMLU against Gopher’s 60.0% while using far less compute for fine-tuning and inference. The paper’s own caveats: only two comparable large-scale runs validate the laws, the frontier is assumed to be a power law, and the runs trained on less than one epoch of data. A 2026 reality check on that last point: this is a training-compute-optimal recipe, not a deployment-optimal one — since inference cost dominates what labs actually pay, frontier systems have since deliberately overtrained well past the Chinchilla point, so read it as a training-time law rather than a serving-time budget. Trajectories are schematic; numbers are paper-report. This site does not host the PDF.
teaching explainer · Hoffmann et al. · arXiv 2203.15556 · arXiv:2203.15556 · NeurIPS 2022 · DeepMind · traces are schematic; numbers marked paper-report come from the paper tables
0overview
core: for a fixed training compute budget, current large language models are significantly undertrained — their size was scaled up while the number of training tokens stayed roughly constant. Training over 400 models, Hoffmann et al. find the compute-optimal frontier scales parameters and tokens equally. The test model, Chinchilla (70B parameters, 1.4T tokens, same compute as Gopher), beats Gopher (280B), GPT-3 (175B) and MT-NLG (530B).
The diagnosis
GPT-3-style scaling grows parameters while holding tokens nearly fixed. That is the wrong side of the trade-off — the models are too big for their data.
The law
For every doubling of model size, double the training tokens. Three independent methods converge on the same frontier.
The proof
Chinchilla uses the same compute as Gopher, is 4× smaller, and wins on downstream tasks — 67.6% MMLU vs Gopher's 60.0%.
Five panes: the undertraining problem, the three ways to find the frontier, the 400-model experiment and Chinchilla itself, the downstream results, and the paper's own limits plus a 2026 reality check.
primer — what you need before you start
the task. Training a language model costs compute. Given a fixed compute budget, you must decide how to split it between making the model bigger (more parameters) and showing it more data (more training tokens). This paper answers which split gives the lowest final loss.
how it was done before. Kaplan et al. (2020) fitted scaling laws and concluded you should grow the model much faster than the data. That advice made GPT-3 (175B params, ~300B tokens) and Gopher (280B params, 300B tokens) — big models trained on relatively little data. This paper revisits that conclusion with a cleaner experimental design and finds the opposite.
glossary — terms you will see.
parameters (N) — the model's weights; how "big" it is.
tokens (D) — how much text the model was trained on.
compute (C) — total FLOPs spent training; roughly .
loss — how surprised the model is by the next token (cross-entropy); lower means better predictions. This is the number every scaling law here fits.
compute-optimal — the N / D split that gives the lowest loss for a given C.
IsoFLOP — fixing compute and sweeping model size to find the best loss.
undertrained — a model too large for the amount of data it saw.
MMLU — a 57-subject knowledge benchmark used to compare models.
symbol table — what the letters mean.
— number of parameters.
— number of training tokens.
— training compute, .
— final validation cross-entropy loss; fitted as a floor plus one term falling with and one falling with (full form in the approaches pane).
— irreducible entropy: the loss floor no model can pass.
tone legend — what the [brackets] mean.
[obs] observation / setup [app] an approach to the frontier
[law] scaling law / formula [tbl] experiment / table numbers
[res] headline result [limit] limitation
[eq] equation [take] key takeaway
[sys] system / meta [2026] site-editorial reality check
Six panes cover, in pedagogical order: the undertraining problem; three independent ways to locate the compute-optimal frontier; the 400-model experiment and Chinchilla itself; the downstream results; and the paper's limits with a 2026 reality check. Each pane ends with key takeaways so you can stop after any section and still know what you learned.
1undertraining
point: the era's dominant recipe scaled parameters and held training data roughly constant. The result: current large models are significantly undertrained — too big for the data they saw. The paper's framing: given a compute budget, the size and the number of tokens are a trade-off, and everyone was on the wrong side of it.
The diagnosis is not about quality of data or architecture. It is about the allocation of a fixed compute budget between two quantities — model size and training tokens — and that prior work had systematically over-spent on the first.
observation the trade-off the diagnosis
2three approaches
point: the authors locate the compute-optimal frontier three independent ways. Approach 1 fixes model sizes and varies tokens, taking the lowest-loss envelope. Approach 2 is IsoFLOP: fix compute, sweep model size, keep the lowest loss. Approach 3 fits a parametric loss function of parameters and tokens and optimizes it under a FLOP constraint. All three agree.
The three methods are deliberately different — an envelope of runs, a set of fixed-compute sweeps, and a closed-form fit — so their agreement is strong evidence, not an artifact of one method.
an approach fitted law the conclusion
3the experiment
point: over 400 models, from 70 million to over 16 billion parameters, trained on 5 to 500 billion tokens, map out the loss surface. At Gopher's compute budget — the same number of FLOPs — the compute-optimal model is Chinchilla: 70B parameters on 1.4T tokens. The recipe generalizes: roughly 20 tokens per parameter.
The compute-optimal pairings show that as compute grows, both parameters and tokens grow together, with tokens slightly outpacing parameters in raw count.
table / data setup the law
4results
point: the equal-scaling prediction holds. At one quarter of Gopher's parameters, Chinchilla uniformly and significantly outperforms Gopher (280B), GPT-3 (175B), Jurassic-1 (178B), and Megatron-Turing NLG (530B) across downstream evaluation tasks — while using far less compute for fine-tuning and inference. MMLU: 67.6% against Gopher's 60.0%.
The payoff is not just accuracy. A smaller, better-trained model is cheaper to serve: less memory, less latency, less inference cost for the same or better quality.
Chinchilla baselines numbers
5limits + 2026 reality
point: the paper is honest about its footing. Only two comparable large-scale runs (Gopher, Chinchilla) validate the laws. The frontier is assumed to be a power law, though the authors note some concavity. And the scaling runs all trained on less than one epoch of data.
The 2026 reality check that follows is this site's own editorial note, added at the request of the site owner — it is analysis written in 2026, not a claim from Hoffmann et al.
limit 2026 reality check
Schematic traces are teaching schematics. Numbers reported: Hoffmann et al., Training Compute-Optimal Large Language Models, NeurIPS 2022, arXiv:2203.15556. The limits-section 2026 reality check is site-editorial analysis, not from the paper. This site does not host the PDF.