Keep every explanation and worked example on the page. Nothing moves or plays by itself, and the larger instruments load only when you ask.
Special relativity · Section 4
A moving clock loses time.Not what a camera sees: what the clock reads.
How much less time does a moving clock record than the clocks it passes, and does a clock that goes out and comes back show the difference when they meet again? Choose a worldline. Compare the traveling clock's own proper time with the platform clocks it moves past, and read both clocks' faces at the reunion event.
Moving clocks
Static worked example
Clock speed (fraction of c)
0.6
Worldline
out and back
Coordinate duration
10 s
Worked example: a clock moving at 0.6c out and back: the platform clocks read 10 s while it reads 8 s.
The moving clock's own time against the platform's coordinate time.
Proper time (τ)
8 s
Coordinate time (t)
10 s
τ / t
0.8
Loss per second: the exact form beside the printed second-order approximation ½β². Neither stands in for the other.
Exact loss per second
0.2
Printed second-order form (½β²)
0.18
When the clocks meet again: the exact lag beside the printed approximation ½tβ², which is labelled as one.
Exact lag at reunion
2 s
Printed approximation (½ t β²)
1.8 s (approximation, not exact)
Each inertial frame reports the same dilation factor for the other clock's rate. Comparing clocks that are apart needs a stated simultaneity convention; only the reunion comparison above holds in every frame.
Dilation factor (γ)
1.25
The light clock (supplemental illustration, offered after the measurement definitions: it illustrates dilation, it does not define it).
Proper tick (2L₀/c)
2 s
Coordinate tick
2.5 s
A clock losing exactly one second per day moves at β ≈ 0.00481124.
A clock that travels away and comes back reads less time than an identical clock that stayed put. At 60 percent of the speed of light, a trip that takes 10 seconds on the clock at home takes only 8 seconds on the traveller.
Section 4 takes a clock at rest at the origin of the moving system k and asks how fast it runs, judged from the resting system K. Its position is x = vt, and the transformation gives its reading as τ = t√(1 − v2/c2), so each second it falls behind by 1 − √(1 − v2/c2) seconds, or ½(v/c)2 to within terms of fourth order. Einstein draws the consequence: a clock carried from A to B and set beside one that stayed there lags by ½t(v/c)2, and so does a clock taken round a closed path back to its start. The instrument computes that reunion for an out-and-back trip or a circle at constant speed. At 0.6c over 10 s of the resting clock, the traveller reads 8 s: the exact loss is 0.2 s per second, 2 s in all, where the printed approximation gives 0.18 s per second, 1.8 s. A light clock with an arm of 1 light-second ticks every 2 s in its own frame and every 2.5 s as judged from K, the same factor 1.25. The comparison is of clock readings at a shared event; it is not what a camera would see.
Take the resting system K and a clock moving along x at speed v = 0.6c, in seconds and light-seconds, so c = 1. The clock's position is x = vt. Section 3's transformation gives the moving system's time as τ = (t − vx/c2)/√(1 − v2/c2). Put x = vt into the top: t − v × vt/c2 = t(1 − v2/c2), and dividing by √(1 − v2/c2) leaves τ = t√(1 − v2/c2). At 0.6c, v2/c2 = 0.36, 1 − 0.36 = 0.64 and √0.64 = 0.8: the moving clock reads 0.8 s for every second of K, and loses 1 − 0.8 = 0.2 s each second. Einstein's approximation uses √(1 − ε) ≈ 1 − ε/2 for small ε, so the loss is about ½ × 0.36 = 0.18 s each second: very good at everyday speeds, 10 percent low at this one. For the trip, out for 5 s and back for 5 s of K's time at 0.6c both ways, the traveller reads 0.8 × 10 = 8 s against the home clock's 10 s, a lag of 2 s; the approximation says 1.8 s. The turn does not change this, because the rate depends only on the speed, so any path at 0.6c for 10 s gives 8 s. A light clock shows the same factor from geometry. In its own frame light crosses an arm of 1 light-second and returns, a tick of 2 s. Seen from K the arm moves at 0.6c while the light crosses, so each leg is the long side of a right triangle: if a leg takes a time T, then (cT)2 = 12 + (0.6cT)2, so 0.64T2 = 1 and T = 1.25 s, a tick of 2.5 s, and 2.5/2 = 1.25 = 1/0.8. At the equator the ground moves at 465 m/s, so (v/c)2/2 = 1.20 × 10−12, about 104 ns a day in special relativity alone. To lose a whole second a day a clock would need ½β2 = 1/86 400, so β = 0.0048, about 1440 km/s.
Modern qualifications
Einstein called the result a peculiar consequence. He proved it for a path made of straight pieces and assumed it for a curve, with a clock whose rate depends only on its speed, an assumption later named the clock hypothesis. His closing example, a balance-wheel clock at the equator running slower than one at a pole, holds in special relativity alone; on the real Earth the difference in gravitational potential cancels it, and clocks at sea level keep the same rate everywhere, which general relativity explains. The light clock is not in the paper: Lewis and Tolman used it in 1909. Hafele and Keating flew atomic clocks round the world in 1971 and found the lags predicted when both effects are included.
Show the code
The site’s own reference code for this law, in TypeScript. It computes the numbers above when the page runs it, and it is what the page uses wherever a FrankenSim result is not available.
dilationLossPerSecond · src/physics/reference/kinematics.ts · this site’s source, as built · sha256:16174608520a91b1901a27754605296b471556b17585818e16bd777a3027c413
This function computes the listed outputs when it runs.
In words
The loss per coordinate second is 1 minus 1 over gamma. The function returns it as exact, computed as beta squared over (1 + the square root of 1 minus beta squared), and beside it printedSecondOrder, which is half of beta squared. The second is what the paper prints on page 904 when it says the moving clock falls behind by half of (v/V) squared per second, neglecting magnitudes of the fourth order and higher.
Implementation
/**
* Clock loss per coordinate second: 1 - 1/gamma = beta^2 / (1 + sqrt(1 - beta^2)).
* printedSecondOrder is (1/2) beta^2.
*/exportfunctiondilationLossPerSecond(beta:number,):KinematicResult<Readonly<{exact:number;printedSecondOrder:number}>>{constbad=refuseBeta(beta);if(bad)returnbad;if(isMode1904())refuseModernSurface("gamma");constroot=Math.sqrt(1-beta*beta);returnok({exact:(beta*beta)/(1+root),printedSecondOrder:0.5*beta*beta,});}
The site’s own reference code for this law, in TypeScript. It computes the numbers above when the page runs it, and it is what the page uses wherever a FrankenSim result is not available.
reciprocalRates · src/experiments/sr05/worldline.ts · this site’s source, as built · sha256:268de30e365ff413ce4b418d22cee21a230f2cdee2730a1f9d744c75ad8b46b0
This function computes the listed outputs when it runs.
In words
There is no asymmetry to find here: the frame at rest reports the moving clock running slow by gamma, and the moving frame reports the resting clock slow by the same gamma. The function returns the single dilationFactor rather than a pair, because a pair would suggest the two numbers could differ.
Implementation
/** Each inertial frame reports the same dilation factor for the other clock's rate -- the
* symmetric statement this bead requires, without constructing a desynchronized separated-
* reading comparison (that needs events.ts's simultaneity apparatus, out of this bead's Scope
* to build). */exportfunctionreciprocalRates(beta:number):KinematicResult<ReciprocalRatesSummary>{constg=gamma(beta);if(g.status!=="value")returng;returnok({dilationFactor:g.value});}
Model: an ideal clock whose rate depends only on its instantaneous speed. Not modeled: gravitational time dilation, real clock mechanisms under acceleration, rotating-frame synchronization, the geoid's actual shape, atomic-clock physics, and clock noise.
The physical argument
Two different questions, kept apart
“What does the clock read at a shared event?” and “What does a camera watching the clock across a growing distance see, including the travel time of the light itself?” are different physical questions. This instrument answers only the first: simultaneous-coordinate readings and reunion comparisons, never the optical appearance of a receding or approaching clock.
Section 4 states the loss per second of coordinate time to magnitudes of fourth and higher order as 21v2/V2. The lab above shows this printed approximation beside the exact, numerically stable form β2/(1+1−β2); the two agree to many digits at everyday speeds and separate visibly as speed grows.
The reunion is the honest comparison
Two separated clocks can only be compared by adopting a simultaneity convention; two clocks brought back together read whatever they read, with no convention involved. This instrument computes the frame-independent reunion comparison for closed worldlines (out-and-back, or a constant-speed circle) rather than a comparison of distant, unsynchronized readings.
An ideal clock, not a mechanism
The model is an ideal clock whose rate depends only on its instantaneous speed; not a model of any particular mechanism, and not a claim about how real atomic clocks behave under acceleration. Two worldlines with the same speed profile but different turning accelerations report exactly the same proper time.
Ideal model, host calculation. Every worldline offered here keeps a constant speed along each piece of its path, so its proper time is each piece’s coordinate time multiplied by 1−v2/c2 and added up, which is exact. A path whose speed changes continuously would need the general integral, which this instrument does not offer.
Before you draw a conclusion
A common wrong turn this instrument speaks to
§ 4 says only that a moving clock runs slow.
§ 4 goes further. Of two clocks synchronized at A and B, one carried from A to B no longer agrees with the other when they stand side by side, and a clock taken round a closed curve comes back behind the one that stayed. The paper then concludes that a clock at the equator runs slow, a conclusion that on the real earth needs gravity as well.