Bring the mental model from Scaled Dot-Product Attention & Transformer Layers; this page will reuse it instead of restarting from zero.
Scaling
Scaling Laws & Emergent Abilities
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.

Concept Structure
Scaling Laws & Emergent Abilities
Start with the picture, metaphor, or geometric mechanism.
Make the objects explicit and connect them with notation.
Mirror the equations with runnable implementation details.
Manipulate the mechanism and watch the idea respond.
Learning map
Scaling Laws & Emergent AbilitiesConceptual Bridge
What should feel connected as you move through this page.
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
The next edge should feel earned: use the demo prediction here before following RLHF: Reward Modeling + KL-Regularized Policy Optimization.
01
Intuition
Build the mental picture first so the rest of the page has something to attach to.
If you train a family of models the same way (same architecture class, data pipeline, optimizer recipe), then "bigger model" and "more data" usually give you predictably better loss.
Scaling laws turn that predictability into a planning tool. Instead of guessing, you can fit a curve from small runs, then forecast how far a larger run will go, and how to spend a fixed compute budget:
- Should we buy more parameters or more tokens?
- If we only get one big run, what is the compute-optimal choice?
- Why do some task behaviors look like they "appear suddenly"?
The key mindset is: scaling laws are not a proof about intelligence. They are an empirical control system for allocating compute.
02
Math
Translate the story into symbols, assumptions, and a derivation you can inspect.
Power-law loss scaling
A common empirical form for test loss is:
where:
- is parameter count,
- is number of training tokens (or examples),
- are exponents you fit from data,
- is the irreducible loss floor for the dataset/model class.
On a log-log plot, and look like straight lines. That's why power laws are useful: they extrapolate smoothly.
Compute-optimal allocation (Chinchilla-style rule of thumb)
Very roughly, training compute scales like:
Substituting into the displayed loss does not, by itself, force a near-linear token/model rule. Differentiating the two reducible terms gives
up to constants from , , , , and the compute model. Equivalently, the fitted power-law toy objective suggests an exponent-dependent frontier:
The Chinchilla-style statement is the empirical next step, not an algebraic consequence of the generic equation alone: Hoffmann et al. found, for their fitted language-model experiments and compute accounting, that compute-optimal training scales model size and training tokens together along the frontier. The practical lesson is still the same: for a fixed compute budget, do not overscale parameters while starving the run of data. The proportionality constant depends on units, data quality, architecture, optimizer, and training recipe.
"Emergent abilities" as sharp transitions
When you measure a capability with a thresholded metric ("accuracy above 50%", "passes a benchmark"), smooth curves in loss can turn into sharp-looking transitions. The underlying performance can still be continuous.
03
Code
Keep the implementation aligned with the notation so the algorithm is legible.
import numpy as np
# Dimensionless toy: n and d are multipliers over a base recipe.
# Equal exponents/constants make a near-linear fitted frontier visible.
L_inf, a, b = 1.5, 1.0, 1.0
alpha = beta = 0.08
def loss(n, d):
return L_inf + a * n**(-alpha) + b * d**(-beta)
C = 1e6 # compute budget in arbitrary units: C = n * d
ns = np.logspace(1, 5, 80)
best = None
for n in ns:
d = C / n
L = loss(n, d)
if best is None or L < best[0]:
best = (L, n, d)
L, n, d = best
print("best loss:", round(float(L), 4))
print("model multiplier:", round(float(n), 2))
print("token multiplier:", round(float(d), 2))
print("token/model ratio:", round(float(d / n), 2))
04
Interactive Demo
Use direct manipulation to connect the explanation to a moving system.
Use the demo to explore how loss changes as you scale and , and why compute-optimal frontiers often prefer more data than you expect.
Live Concept Demo
Explore Scaling Laws & Emergent Abilities
The stage is code-native and interactive. Use it to test the explanation against the mechanism.
Manipulate one control and predict the visible change.
Commit to what Scaling Laws & Emergent Abilities should make visible before reading the result.
After The First Pass
Turn the concept into an inspected object.
Once the invariant is visible in the intuition, math, code, and demo, use these panels to inspect the mechanism visually, check source support, practice the idea, and attach a grounded research question.
Mechanism Storyboard
See the idea move before the page explains it
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.

Start with the picture, metaphor, or geometric mechanism.
Before reading further, choose the kind of change Scaling Laws & Emergent Abilities should make visible.
Visual Inquiry
Make the image answer a mathematical question
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
Which visible object should carry the first intuition?
Pick the cue that should make Scaling Laws & Emergent Abilities easier to reason about before the page gives the answer.
Source Grounding
Canonical references for the mechanism on this page.
Grounds empirical power-law fits between model size, data, compute, and language-model loss.
Open sourceGrounds compute-optimal scaling as a balance between parameter count and training tokens.
Open sourceClaim Review
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
Claims without a substantive review badge still need exact source-support review.
kaplan-2020-scaling-laws, hoffmann-2022-chinchilla
Use equation, code, and demo objects to check whether the source support is operational.
Kaplan supports empirical LM loss power laws over model size, data, and compute. Hoffmann supports compute-optimal training that scales parameters and tokens together. The page's equations, normalized code witness, and Loss Scaling tab instantiate this bounded allocation view.
Sources: Scaling Laws for Neural Language Models, Training Compute-Optimal Large Language ModelsChecks empirical pretraining loss/allocation only: not intelligence, literal one-token-per-parameter scaling, universal exponents, inference-time compute, data-quality effects, emergence, or post-training/RLHF.A bounded review summary is present; still check caveats and exact source scope.Oracle previously fixed the claim to Kaplan/Hoffmann-specific wording. Kaplan supports empirical language-model loss power laws over model size, data, and compute; Hoffmann supports joint parameter/token compute-optimal scaling. Local math/code/demo now witness only that bounded allocation view.
Reviewer: codex+oracle; reviewed 2026-06-27Source support candidates
paper 2020Scaling Laws for Neural Language ModelsGrounds empirical power-law fits between model size, data, compute, and language-model loss.
paper 2022Training Compute-Optimal Large Language ModelsGrounds compute-optimal scaling as a balance between parameter count and training tokens.
Practice Loop
Try the idea before it explains itself
Empirical power laws that predict how loss and capability improve with parameters, data, and compute, and how to choose compute-optimal training runs.
Before touching the demo, predict one visible change that should happen in Scaling Laws & Emergent Abilities.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
A concrete answer is on the canvas.
The answer names why the claim should hold.
It touches the page context or a neighboring idea.
Research Room
Attach the question to an exact object
Pick the concept, equation, source, code witness, claim, misconception, or demo state before asking for help. The handoff stays grounded to that object.Open the draft below to save one note and next action in this browser.
Scaling Laws & Emergent Abilities
What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math?
Local action draftNo local draft saved yetExpand only when ready to capture one local next action
This draft stays locally in this browser for concept:scaling/scaling-laws.
- Source ids to inspect: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla
- Definition, prerequisite, and contrast concept links
- The equation or code witness that makes the concept operational
- One demo state that shows the invariant instead of a slogan
- The learner can state the mechanism in their own words
- The learner can name the prerequisite that would repair confusion
- The learner can predict how the mechanism changes under one perturbation
I am working in Continuous Function's research reading room. Object: concept - Scaling Laws & Emergent Abilities Object key: concept:scaling/scaling-laws Context: Scaling Anchor id: concept/concept-notebook/scaling/scaling-laws Open question: What is the smallest example that makes Scaling Laws & Emergent Abilities click without losing the math? Evidence to inspect: - Source ids to inspect: kaplan-2020-scaling-laws, hoffmann-2022-chinchilla - Definition, prerequisite, and contrast concept links - The equation or code witness that makes the concept operational - One demo state that shows the invariant instead of a slogan What would resolve this: - The learner can state the mechanism in their own words - The learner can name the prerequisite that would repair confusion - The learner can predict how the mechanism changes under one perturbation Answer as a careful research tutor: stay source-grounded, separate verified evidence from assumptions, name the relevant math objects, and end with one next action.
concept/concept-notebook/scaling/scaling-laws
concept:scaling/scaling-laws