Pace Calculator

Pace, speed, and the two-of-three rule

Distance, time, and pace are locked together: pace = time ÷ distance. Given any two, the third follows — 10 km in 50 minutes is 5:00 per km, which is also 8:03 per mile and 12 km/h. Runners think in pace rather than speed because splits on a watch and markers on a course arrive per kilometre or mile.

Only one of the three is ever unknown, which is why the form asks for two values and leaves the third blank. Rearranging the same identity gives the other two solutions: time = distance × pace, and distance = time ÷ pace. There is no fourth relationship and no hidden model behind the answer — the engine performs the division, converts the units, and reports the result as clock time, because a pace carried to extra decimal places would imply a precision that a stopwatch and a course measurement do not have.

Solving for each of the three

Which variable is unknown depends on what you already have, and each case is a different rearrangement of the same identity. Every result below is computed at build time from the stated inputs by the same engine the calculator runs in your browser.

Pace, from distance and time. This is the after-the-run case: you know the route and you have the stopwatch. Five miles in 40:00 works out to 8:00 per mile — the same run expressed metrically as 4:58 per kilometre over 8.05 km, at 12.07 km/h. Entering the distance in miles and reading the answer in both units is the reason two paces are shown rather than one.

Time, from distance and pace. This is the before-the-race case: you have a target pace and want the finish time it implies. A distance of 21.0975 km (13.11 miles) held at 5:30 per kilometre comes to 1:56:02 — which is the same as 8:51 per mile, or 10.91 km/h, if either of those is the figure your watch reports.

Distance, from time and pace. This is the planning case: you have a fixed window and a pace you can hold. Forty-five minutes at 6:00 per kilometre covers 7.5 km (4.66 miles), at 9:39 per mile. Leave the distance field empty and the calculator solves for it instead.

Pace and speed are one fact, inverted

Speed answers "how much ground per unit of time"; pace answers "how much time per unit of ground". Each is the reciprocal of the other, scaled by whatever unit conversion applies, so neither carries information the other lacks. A treadmill belt set to 9 km/h covers that many kilometres in an hour, which the engine reports as 6:40 per kilometre and 10:44 per mile — so to convert any belt speed, enter the distance it would cover with a time of 60:00 and read the pace off the result.

The reciprocal relationship has one consequence worth knowing. Because pace is one divided by speed, equal steps in speed are not equal steps in pace: adding a fixed increment of speed removes progressively less time from each kilometre the faster the belt is already moving. That is arithmetic rather than physiology, but it explains why the same speed increase shaves less and less off a split as a treadmill session escalates.

Using it for race planning

Work backwards from a goal: enter the race distance and target time to get the pace you must average, then test that pace over shorter training runs. A plan that deliberately varies the split — a slower first half and a faster second, say — changes nothing about the arithmetic: whatever the halves are, they still have to average out to the number this calculator gives you.

The same arithmetic produces a split sheet. Multiply the target pace by each intermediate distance and you have the clock time you expect to see at every marker; enter that distance with the pace, leave time blank, and the multiplication is done for you. Comparing an actual split against the sheet mid-race tells you the size of the error so far — not what to do about it, which depends on the course, the conditions, and how the day is going.

An average hides everything that happened inside it

A single pace figure is total time divided by total distance, so it is an average by construction. Two runs with an identical average pace can be entirely different sessions: one held steady from the first kilometre to the last, the other opened far too fast, faded badly, and arrived at the same summary number. The calculator cannot tell them apart, because the only inputs it has are the totals.

This is what splits are for. Solving the same relationship separately over each kilometre or mile gives a series of paces instead of one, and the spread across that series is exactly the part an average discards. To check whether a training pace was consistent, compare the splits against each other rather than against the summary line — and read the summary as the arithmetic mean it is, not as a description of how the run actually unfolded.

Pace measures the ground, not the effort

Pace is a fact about distance and time. The calculation has no input for hills, heat, altitude, wind, surface, or how rested the runner was, so none of them appear anywhere in the result. That is the standing limitation of pace arithmetic: it describes the ground covered and the time taken, and nothing else about the run.

Pace is one of several ways to describe a run. The heart-rate zones guide explains how the common zone model is built and where it is known to be unreliable, and the Target Heart Rate Calculator computes the bands themselves. Neither replaces pace; they answer a different question about the same run.

Frequently asked questions

Not medical advice: this calculator provides general educational estimates from published population formulas. It cannot account for your individual health context and must not be used to diagnose or treat any condition — consult a qualified healthcare professional before major changes to exercise intensity. Values are processed locally in your browser and never transmitted. See the methodology page.