Emergent Abilities & Scaling Laws
In 2020, researchers at OpenAI plotted the loss of language models against the compute used to train them. The points fell almost perfectly on a straight line in log-log space. This held across seven orders of magnitude. This was strange — nothing about neural networks obviously guarantees such regularity. Yet the discovery let engineers predict the performance of a model costing tens of millions of dollars. They could do this using only experiments run on a laptop. That predictive power reshaped how the entire field allocates money, chips, and data. The concrete motivating problem is deceptively simple. Given a fixed budget of compute, how should one split it? The split is between model size and training data. The goal is the best possible model. Get this wrong and you waste months of GPU time. You might end up with a model too big for the data it sees. Or one too small to use the data efficiently. Scaling laws answer this question quantitatively. They turn what used to be guesswork into an optimization problem with a closed-form-ish solution. Alongside this predictability sits a puzzle. Some capabilities, like multi-step arithmetic or chain-of-thought reasoning, do not improve smoothly as models grow. They stay near zero for a long stretch of scale. Then they rise sharply once a threshold is crossed. These are called emergent abilities. They complicate the otherwise clean picture that scaling laws paint. A model's loss may scale smoothly. Meanwhile, its downstream task accuracy jumps discontinuously — a distinction this article makes precise. This article builds the mathematics of scaling laws from first principles. It works through the compute-optimal training recipe (the "Chinchilla" analysis). It explains what emergent abilities are. It also covers the debate over whether they are real phenomena or measurement artifacts. Both ideas are connected to the practical business of deciding how to spend a training budget. It assumes familiarity with the Transformer Architecture and Language Model Pretraining. It sets up the ground for later discussions of In-Context Learning and Mixture-of-Experts models. Both of these are direct consequences of what happens when models are scaled up.
- Test loss of language models follows a power law in parameters , data , and compute , holding across many orders of magnitude.
- Power laws let practitioners predict a large model's loss from small-scale experiments, guiding budget allocation before expensive runs.
- The compute-optimal ("Chinchilla") analysis shows model size and data size should scale roughly equally with compute — most earlier large models were undertrained.
- Emergent abilities are capabilities that appear discontinuously at scale on some metrics, while the underlying loss improves smoothly.
- Much of the sharpness of "emergence" is a property of the metric (e.g., exact-match accuracy) rather than the model — smoother metrics reveal gradual improvement.
- These ideas directly motivate In-Context Learning and Mixture-of-Experts architectures, which try to buy capability more cheaply than dense scaling alone.
Language model loss decreases as a smooth, predictable power law in scale, but the downstream skills built on that loss can appear to switch on abruptly, because discrete evaluation metrics amplify small, continuous improvements into visible jumps.
The idea
A scaling law is an empirical relationship, of power-law form, between a language model's test loss and the resources used to produce it: the number of trainable parameters , the size of the training dataset (in tokens), and the total training compute (in floating-point operations). The canonical form, per parameter or per fixed pair with the other held effectively unconstrained, is
where are constants fit from data and the exponents are small positive numbers (empirically around – depending on the study and architecture family). The loss is cross-entropy on held-out text, and it decreases as any one resource grows while the others are not the bottleneck. Crucially the relationship is linear in log-log space: is approximately affine in . This is what makes the law useful — a line fit to small-scale runs extrapolates to scales orders of magnitude larger.
Compute-optimal scaling asks a sharper question: given a fixed compute budget , how should you split it between and to minimize loss, rather than simply asking what loss a given or achieves in isolation? Since compute for training a dense Transformer is well approximated by (roughly, 2 FLOPs per parameter per forward pass, times 3 for forward + backward, times tokens seen), there is a genuine trade-off: doubling at fixed halves the usable . The optimal split is itself a power law, and with , and the Chinchilla study found — parameters and data should grow at roughly the same rate, contrary to earlier practice (e.g., GPT-3) which scaled parameters much faster than data.
Emergent abilities are a separate but related phenomenon. They refer to capabilities — such as multi-step arithmetic, unit conversion in word problems, or successful chain-of-thought reasoning — that are not present (near-random performance) in a family of models below some scale threshold, and then appear with a sharp, seemingly discontinuous rise above that threshold, on a specific benchmark's accuracy metric. This is qualitatively different from a smooth power-law improvement in loss; the same underlying smooth improvement in log-likelihood of the correct answer can look like an on/off switch when the evaluation metric is something binary like exact-match accuracy, because exact-match requires every token in a multi-step answer to be correct simultaneously.
How it works
Step 1: Fit the scaling law from small-scale runs. Train a family of models at varying (holding large enough not to bottleneck) and record final test loss. Similarly vary at large fixed . Fit a line in log-log space by least squares.
Step 2: Determine the compute-optimal frontier (IsoFLOP method). For a range of fixed compute budgets , train many models with different pairs satisfying , and record the loss for each. For each budget, the pair achieving minimum loss traces out the optimal allocation curve. Fit power laws and to these minima.
Step 3: Extrapolate to the target budget. Given a real budget (e.g., a planned production training run), plug into the fitted and to decide model size and dataset size before spending the money on the full run.
Step 4: Evaluate for emergence separately. Scaling laws describe loss. To check whether a task is emergent, evaluate the same model family on downstream benchmarks, plotting task accuracy (or another metric) against scale. Compare with a smoother metric (log-likelihood of the correct token sequence, or partial-credit scoring) on the same task — this reveals whether the jump is intrinsic or metric-induced. ```
# Pseudocode: fitting a scaling law and finding the compute-optimal frontier function FIT_POWER_LAW(x_values, y_values):
# y = A x^(-alpha) <=> log(y) = log(A) - alpha log(x) log_x = [log(x) for x in x_values] log_y = [log(y) for y in y_values] (slope, intercept) = LEAST_SQUARES_LINE(log_x, log_y) alpha = -slope A = exp(intercept) return (A, alpha) function ISO_FLOP_SEARCH(compute_budgets, candidate_ratios):
# candidate_ratios: list of N/D splits to try at each fixed C optimal_points = [] for C in compute_budgets: best_loss = INFINITY best_N, best_D = None, None for ratio in candidate_ratios:
# solve N, D from C = 6ND and N/D = ratio N = sqrt(C ratio / 6) D = sqrt(C / (6 ratio)) model = TRAIN_MODEL(params=N, tokens=D, budget=C) loss = EVALUATE(model, held_out_set) if loss < best_loss: best_loss = loss best_N, best_D = N, D optimal_points.append((C, best_N, best_D, best_loss)) return optimal_points function DERIVE_ALLOCATION_LAW(optimal_points): Cs = [p.C for p in optimal_points] Ns = [p.N for p in optimal_points] Ds = [p.D for p in optimal_points] (A_N, a) = FIT_POWER_LAW(Cs, Ns) # N_opt(C) = A_N C^a (A_D, b) = FIT_POWER_LAW(Cs, Ds) # D_opt(C) = A_D C^b return (A_N, a, A_D, b) function PLAN_TRAINING_RUN(target_compute, A_N, a, A_D, b): N_opt = A_N (target_compute ^ a) D_opt = A_D (target_compute ^ b) return (N_opt, D_opt) function CHECK_EMERGENCE(model_family, task, scales): hard_metric_curve = [] # e.g. exact-match accuracy soft_metric_curve = [] # e.g. avg log-likelihood of correct answer for scale in scales: model = model_family[scale] hard_metric_curve.append(EVAL_EXACT_MATCH(model, task)) soft_metric_curve.append(EVAL_LOG_LIKELIHOOD(model, task))
# emergence is "real" only if the smooth metric also shows
# a sharp change in slope, not just the hard metric return (hard_metric_curve, soft_metric_curve) ```
Complexity & correctness
Fitting cost. Fitting a scaling law itself is cheap: it is ordinary least squares on points, where is the number of small-scale training runs — time and space, negligible next to training cost. The expensive part is generating the data points, since each point requires an actual training run. This is the entire economic argument for scaling laws: instead of training full-scale candidate models to pick the best configuration ( full-scale runs, potentially catastrophic in cost), you train small models and extrapolate, turning an search into for one confirmatory large run.
Compute-optimal derivation, sketched. Given the constraint and an additive loss model motivated by empirical fits,
(an irreducible entropy term plus separate parameter- and data-limited error terms), minimize subject to using a Lagrange multiplier. Substituting :
Differentiating with respect to and setting to zero:
Solving for gives , and correspondingly — a genuine power law in , confirming the empirical form used in Step 2/3 above. When empirical fits give , the exponents both come out near , which is the Chinchilla finding: split growth roughly evenly between model size and data size. This is a real optimization result, not just curve-fitting folklore: it follows from minimizing a convex (in , for reasonable exponent ranges) loss surface under a linear compute constraint.
Honesty about the model's limits. The additive two-term loss form is an empirical approximation, not a law of nature; it can break down when data is repeated (multiple epochs), when architecture changes qualitatively (e.g., mixture-of-experts routing, which decouples parameter count from FLOPs — foreshadowing Mixture-of-Experts), or at extremes of scale where new bottlenecks (data quality, tokenizer effects) dominate. The power law is a strong empirical regularity across many studied ranges, not a proven theorem.
Emergent abilities: correctness of the "mirage" explanation. Consider a task scored by exact-match over an answer of length tokens, where each token's probability of being correct scales smoothly with as with smoothly. The probability the entire sequence is correct is approximately
for small . Because of the exponent , even a smooth, gradual decrease in per-token error produces a sharply nonlinear rise in : the metric stays near zero while , then rises quickly once drops below roughly . This is a mathematically rigorous demonstration that discontinuous-looking metrics can arise from perfectly smooth underlying quantities — it does not prove all emergent abilities are mirages, but it proves the mirage explanation is a valid and sufficient mechanism for at least some observed cases, which is why choosing evaluation metrics carefully is essential to correctly characterizing what "emerges."
Worked example
Suppose (illustrative numbers, in the style of published scaling studies) small-scale experiments give the fitted per-token-error model where is parameters in billions, and a benchmark requires correct tokens in a row for an exact-match to count as correct.
| (billions) | interpretation | |||
|---|---|---|---|---|
| 0.1 | 20(0.1) ≈ 23.9 | 191 | ≈ 0 | far below threshold |
| 1 | 20(1) = 20.0 | 160 | ≈ 0 | still ≈ 0 |
| 10 | 20(10) ≈ 16.7 | 134 | ≈ 0 | ≈ 0, deceptively flat |
| 100 | 20(100) ≈ 13.9 | 111 | ≈ 0 | still ≈ 0 |
| 400 | 20(400) ≈ 12.1 | 97 | ≈ 0 | close, but not yet |
| 800 | 20(800) ≈ 11.5 | 92 | ≈ 0 | — |
For this metric to leave the "essentially zero" region, must drop from the hundreds down to order 1 — that is, must fall below about . Solving :
This corresponds to on the order of — absurdly large — which illustrates the actual mechanism: a benchmark can require combinatorially small per-token error before exact-match rises above zero at all, and then it rises over a comparatively narrow band of scale once that threshold is neared. Real published emergent-ability curves (e.g., for arithmetic or multi-step reasoning benchmarks) show exactly this signature — flat-at-zero for many orders of magnitude, then a rise within roughly one order of magnitude of scale, consistent with a smoothly improving raised to a power . Choosing a partial-credit metric (e.g., token-level accuracy or log-likelihood, rather than exact-match) on the same checkpoints, in published studies, reveals a smooth curve throughout — no "emergence" appears, only the same underlying signal viewed through a metric that does not exponentiate error into invisibility. A second, complementary trace: compute-optimal allocation. Suppose small-scale IsoFLOP sweeps yield fitted exponents , for the loss model above. Then
If a lab plans a increase in compute over its last well-fit run (which used B parameters and B tokens, roughly consistent with FLOPs), the model predicts
Notice both roughly triple rather than one scaling ten-fold and the other staying flat — this is the core Chinchilla lesson: earlier practice that scaled parameters much faster than tokens (fixing dataset size while growing by –) was leaving loss improvements on the table that could have come from more data at a smaller model size, for the same compute cost.
Common pitfalls & traps
| Pitfall | Why it happens | Consequence |
|---|---|---|
| Treating loss-scaling laws as guarantees for downstream task performance | Loss is an aggregate over all next-token predictions, not a proxy for any one skill | A model can have "on-track" loss yet fail badly on a specific benchmark |
| Ignoring data quality/repetition when extrapolating | Power laws are fit assuming roughly unique, high-quality tokens | Repeating data (multiple epochs) yields diminishing returns not captured by the naive law |
| Attributing "emergence" solely to the model, ignoring the metric | Exact-match and similar all-or-nothing metrics exponentiate small per-token errors | Overclaiming a qualitative capability jump when the underlying signal is smooth |
| Using small-scale fits far outside their fitted range | Power laws are local empirical fits, not universal physical constants | Extrapolation error compounds silently at extreme scales |
| Confusing compute-optimal (lowest loss for a budget) with deployment-optimal (lowest inference cost for a quality target) | Chinchilla optimizes training compute only | Production systems often intentionally overtrain smaller models to save inference cost, deviating from the training-compute-optimal point |
Pioneers & history
Origins · 1 minJared Kaplan and how this was discovered
Kaplan, trained in theoretical physics, brought a physicist's instinct for finding simple power-law regularities in noisy systems to neural network research. His 2020 paper with collaborators at OpenAI established the empirical scaling-law framework that reframed language model training as a predictable optimization problem rather than trial-and-error engineering.
Where this matters
Scaling laws are now load-bearing infrastructure for the economics of frontier AI labs. Before committing tens of millions of dollars to a training run, teams fit scaling laws on a ladder of smaller models to choose architecture hyperparameters, dataset size, and stopping points, essentially replacing expensive full-scale hyperparameter search with cheap extrapolation. The Chinchilla-style compute-optimal recipe directly influenced the design of later production models, which shifted toward much larger training datasets relative to parameter count compared to earlier scaling-heavy designs. Inference cost considerations push real deployed systems to deliberately deviate from pure training-compute optimality, training smaller models on more tokens than the "optimal" point suggests, because inference happens far more often than training and a smaller model is cheaper to serve at scale. The emergent-abilities debate shapes how capability evaluations and safety audits are designed: if a jump in a benchmark score could be a metric artifact, evaluators are pushed toward multiple complementary metrics (log-likelihood, calibration, partial credit) rather than trusting a single exact-match number, especially when trying to anticipate dangerous capabilities before they become fully reliable. Both threads — predictable scaling of loss and unpredictable-looking scaling of specific skills — motivate architectural responses covered in related articles: In-Context Learning emerges as a byproduct of scale and is itself studied through the same emergent-versus-smooth lens, while Mixture-of-Experts architectures attempt to decouple total parameter count from per-token compute cost, changing the very compute-accounting () that the classical scaling laws assume, and requiring the laws to be refit for that architecture family.
Ask the tutor: If I only have compute to train three small model checkpoints, how should I choose their sizes to get a reliable scaling-law fit?
Are scaling laws the same thing as emergent abilities?
No. Scaling laws describe how test loss — an aggregate, smooth quantity — changes with parameters, data, and compute, typically following a power law. Emergent abilities describe how specific downstream task metrics, often binary ones like exact-match accuracy, can appear to switch on sharply at some scale threshold. The two are related because emergent abilities are built on top of the same underlying smooth loss improvements that scaling laws describe; the apparent discontinuity often comes from how the task is scored, not from a genuinely different underlying learning process. Understanding both together is important: scaling laws let you predict compute needs, while the emergence discussion warns you not to over-trust any single benchmark curve as evidence of a qualitatively new capability.
Why do power laws work so well for describing language model loss, when neural networks are so complex?
There isn't a fully rigorous first-principles derivation, but several partial explanations exist. One view treats data as effectively fractal or having heavy-tailed statistics, so a model's ability to fit increasingly rare patterns scales as a power law in its capacity. Another draws analogies to statistical learning theory, where generalization error often scales as a power law in dataset size for a fixed model class. Empirically, the regularity holds robustly across architectures, dataset compositions, and many orders of magnitude, which is itself strong evidence even without a complete theoretical proof. It should be treated as an extremely reliable empirical regularity within studied ranges, not a theorem.
What exactly did the Chinchilla paper change about how models are trained?
Before Chinchilla, common practice scaled parameter count much faster than training tokens as compute budgets grew, following the original Kaplan et al. scaling curves, which under-emphasized data scaling relative to what a rigorous constrained optimization implied. The Chinchilla analysis (Hoffmann et al., 2022) ran systematic IsoFLOP sweeps and found that, for a fixed compute budget, loss is minimized when parameters and training tokens scale at roughly equal rates. This implied that many contemporary large models were significantly oversized relative to their training data, and that a smaller model trained on more tokens would achieve lower loss for the same compute cost. Subsequent large models shifted toward substantially larger token counts relative to parameter count as a direct result.
Do emergent abilities disappear entirely once you switch to a smoother metric?
Not always, but often the sharpness does. Research following the initial emergent-abilities reports showed that for several benchmarks, switching from exact-match to a continuous measure — such as average token-level log-likelihood of the correct answer, or a partial-credit scoring scheme — turned an apparently sudden jump into a smooth, gradual curve across the same range of model scales. This does not prove every claimed emergent ability is purely a metric artifact; some capabilities plausibly do depend on crossing a genuine functional threshold (for instance, needing enough working-memory-like capacity to hold intermediate reasoning steps). The honest conclusion is that metric choice must be scrutinized before concluding a capability "emerged," rather than assuming all discontinuities are equally meaningful.
How are scaling laws used to decide the size of a real production model before training it?
Labs train a "scaling ladder" of much smaller models, typically spanning several orders of magnitude in compute, varying model size and data size systematically (the IsoFLOP method). They fit power laws to the resulting loss values, extract the compute-optimal allocation curve for and , and then extrapolate that curve to the target compute budget for the planned full-scale run. This lets teams choose parameter count, dataset size, and often learning rate schedules with reasonable confidence before spending the bulk of the budget, though extrapolation always carries risk if the target scale is far beyond the fitted range or if architectural choices change the compute-accounting assumptions.
Does mixture-of-experts change how scaling laws apply?
Yes, substantially. Standard scaling laws assume a dense model where every parameter participates in every forward pass, making total parameters a good proxy for compute per token. In a Mixture-of-Experts model, only a subset of experts activates per token, so total parameter count and per-token compute are decoupled — a model can have far more total parameters than its effective FLOPs-per-token would suggest under the dense formula . This means scaling laws for mixture-of-experts architectures must be refit using effective active parameters rather than total parameters, and the compute-optimal frontier looks different, generally favoring larger total capacity than a dense model at the same training compute cost.
What is the relationship between scaling laws and in-context learning?
In-context learning — a model performing a new task from a few examples in its prompt, without gradient updates — is itself an ability whose strength scales with model size, and it is one of the most-cited examples in emergent-abilities discussions. Some studies find in-context learning improves smoothly with scale on some tasks and jumps sharply on others, mirroring the general emergent-versus-smooth distinction. This makes in-context learning a natural next topic once scaling laws and emergent abilities are understood, since it sits at the intersection of both: a capability that scaling laws help predict in aggregate, but whose task-specific manifestation can look emergent depending on how it is measured.