Running Pace Calculator

Background.

This pace calculator converts between the three numbers that define every run — distance, time, and pace — so you can answer the questions every runner actually asks: what pace do I need to hold to break 50 minutes for 10K, how long will a 5:30/km marathon take me, and how far did I actually go in this morning's 42-minute run. Enter any two values and the calculator solves for the third using the identity time = distance × pace, then reports the same result in minutes per kilometre, minutes per mile, kilometres per hour, and miles per hour so you do not have to think in two unit systems at once.

Pace and speed are inverse expressions of the same physical quantity. Speed measures how much distance you cover per unit of time (km/h, mph); pace measures how much time you spend per unit of distance (min/km, min/mi). Runners overwhelmingly think in pace because race goals are distance-anchored — you do not aim for an average of 12.1 km/h in a marathon, you aim for a 5:00/km pace that will bring you home in 3:30:58. Pace also scales linearly with split times: holding 5:00/km means every kilometre marker should tick over five minutes apart, which is far easier to monitor on a GPS watch or a chip-timed road race than a constantly oscillating speed readout. The relationship is strictly reciprocal — speed (km/h) × pace (min/km) is always exactly 60 — so a coach saying 'pick it up to 4:30/km' is the same as a treadmill saying '13.3 km/h'.

Race-day pacing strategy is largely the art of running the right pace for long enough. The Riegel 1981 endurance prediction (T2 = T1 × (D2/D1)^1.06) and the Tanda 2011 marathon model both confirm that goal pace must be calibrated to the distance — a runner who can hold 4:00/km for a 10K will not hold 4:00/km for a marathon, because the fatigue exponent is greater than 1. Most coaches recommend running the first 5–10 km of a marathon 5–10 seconds per kilometre slower than goal pace (negative-split strategy), letting glycogen depletion and core-temperature rise be offset by a slight acceleration in the back half rather than the brutal positive split that hits runners who go out at goal pace from kilometre one.

Pace also defines the structure of training. Jack Daniels' VDOT system in Daniels' Running Formula assigns five training paces — easy (E), marathon (M), threshold (T), interval (I), and repetition (R) — each derived from your current race-equivalent VDOT and calibrated against lactate threshold and VO2 max. Yasso 800s, a marathon prediction workout, claim that the average time you can hold for 10 × 800 m in minutes-and-seconds equals your marathon finish in hours-and-minutes (a 3:10 marathoner runs 800s in 3:10 each).

Marathon-equivalent paces are particularly useful for setting expectations. A 5:00/km runner covers 5 km in 25:00, 10 km in 50:00, half marathon in 1:45:29, and marathon in 3:30:58 — if your half marathon is faster than that conversion, your marathon target is probably too aggressive; if it is slower, you may be undertraining your long runs. This calculator does that conversion in one click for any pace, any distance, and any unit system, so you can build a complete race plan — goal time, average pace, split markers, and treadmill speed equivalent — without leaving the page.

What is running pace calculator?

Running pace is the time required to cover one unit of distance — minutes per kilometre or minutes per mile — and it is the universal language of distance running. It is the mathematical inverse of speed: speed = distance ÷ time, pace = time ÷ distance. Because pace is anchored to distance rather than time, it scales naturally with race markers (every kilometre or mile post becomes a checkpoint) and with training prescriptions (a 'threshold pace' is a single number that a runner can verify on every kilometre split). The calculator solves the three-variable identity totalTime = distance × pace for whichever variable you leave blank: give it any two and it returns the third, plus full unit conversions and the equivalent steady-state speed.

How to use this calculator.

1. 01Pick what you want to calculate from the 'What do you want to calculate?' menu — pace (you know distance and time), time (you know distance and pace), or distance (you know time and pace).
2. 02Enter your distance, choosing km or mi from the distance unit selector. Common shortcuts: 5K = 5 km / 3.1069 mi, 10K = 10 km / 6.2137 mi, half marathon = 21.0975 km / 13.1094 mi, marathon = 42.195 km / 26.2188 mi.
3. 03Enter your total time in seconds. Convert from clock format: 50:00 = 3000 s, 1:45:00 = 6300 s, 3:30:00 marathon = 12 600 s. Most GPS watches let you export this directly.
4. 04Enter your pace in seconds per unit and pick the pace unit (min/km is the global standard, min/mi the US and Commonwealth road convention). 5:00/km = 300 s, 8:00/mi = 480 s.
5. 05Read all seven outputs at once: pace in both min/km and min/mi, speed in km/h and mph, total seconds, and distance in km and mi. The primary output (pace in min/km) is highlighted for goal-setting; the rest are conversion aids.

The formula.

The calculator implements the single identity totalTime = distance × pace, rearranged three ways. Solve for pace: pace (min/km) = (timeSeconds ÷ 60) ÷ distanceKm. Solve for time: totalSeconds = distanceKm × paceMinPerKm × 60. Solve for distance: distanceKm = (timeSeconds ÷ 60) ÷ paceMinPerKm. Speed and pace are reciprocals scaled by 60 — speed (km/h) = 60 ÷ pace (min/km) — so once any of pace, time, or distance is fixed, speed in km/h and mph follow algebraically. All internal arithmetic uses Decimal.js arbitrary-precision arithmetic to avoid the floating-point drift that bites simple JavaScript pace calculators (the classic bug where 5:00 × 42.195 lands on 3:30:58.5 instead of 3:30:58.4). Unit conversions use the NIST SP 811 exact factor 1 mi = 1.609344 km, so pace in min/mi is paceMinPerKm × 1.609344 and distance in mi is distanceKm ÷ 1.609344. Race distances are sourced from World Athletics and USATF: marathon = 42.195 km, half marathon = 21.0975 km, 10 000 m = 10 km exact.

A worked example.

Frequently asked questions.

References& sources.

1. [1]Daniels JT. Daniels' Running Formula. 3rd ed. Champaign, IL: Human Kinetics; 2014. VDOT tables and the five training-pace prescriptions (E, M, T, I, R) used throughout coaching practice.
2. [2]Riegel PS. Athletic Records and Human Endurance. American Scientist. 1981;69(3):285–290. Original derivation of the endurance equation T2 = T1 × (D2/D1)^1.06.
3. [3]Tanda G. Prediction of marathon performance time on the basis of training indices. Journal of Human Sport and Exercise. 2011;6(3):511–520. Marathon time as a function of weekly training distance and training pace; consistently outperforms Riegel for marathon prediction.
4. [4]World Athletics. Marathon — World Records and Definitions. Marathon distance defined as 42.195 km (set 1908 London Olympics, ratified 1921 by IAAF).
5. [5]USA Track & Field. Competition Rules. Official event distances for road and track events including 5 km, 10 km, half marathon (21.0975 km), and marathon (42.195 km).
6. [6]National Institute of Standards and Technology. Special Publication 811: Guide for the Use of the International System of Units (SI). 2008 ed. International mile defined as exactly 1.609344 km.
7. [7]Jones AM, Doust JH. A 1% treadmill grade most accurately reflects the energetic cost of outdoor running. Journal of Sports Sciences. 1996;14(4):321–327. Empirical basis for the 1% treadmill incline correction.
8. [8]Boston Athletic Association. Qualifying Standards for the Boston Marathon. Age-group and gender-specific qualifying times updated annually.