Pace to Speed Converter

What's the difference between Pace and Speed?

Pace and speed are two ways to describe the same motion, useful in different contexts. Pace = time per unit distance, measured in minutes per kilometre or minutes per mile — how runners and cyclists usually think about effort. Speed = distance per unit time, in km/h or mph — the physics-style measure used on treadmills, car speedometers, and gym bikes. They're inversely related: as one increases, the other decreases. The conversion: km/h = 60 ÷ (minutes per km). So 5:00/km pace equates to 60 ÷ 5 = 12 km/h. 6:00/km = 10 km/h. 4:00/km = 15 km/h. 8:00/km = 7.5 km/h. For mile-based: mph = 60 ÷ (minutes per mile). 8:00/mile = 7.5 mph; 6:00/mile = 10 mph. To cross between km and mile units: 1 mile = 1.609 km, so 5:00/km ≈ 8:03/mile and 8:00/mile ≈ 4:58/km. A useful mental rule: 'mile pace ≈ km pace + 1:36' for moderate speeds, though the exact difference scales with pace. The calculator handles both pace and speed in both unit systems and converts between any pair. Knowing which to use depends on context: pace is more meaningful for running, cycling, and rowing where you're tracking effort over distance; speed is more useful for treadmill displays, vehicle speedometers, and physics calculations.

What's the key thing to understand about Common Race Paces?

Memorising a handful of pace-to-distance benchmarks lets you instantly judge any pace or time without a calculator. 5K targets: 25 minutes = 5:00/km = 12 km/h (a popular adult-running target); 30 minutes = 6:00/km = 10 km/h; 20 minutes = 4:00/km = 15 km/h (competitive amateur). 10K targets: 50 minutes = 5:00/km (the 5K pace held over twice the distance, a good intermediate target); 60 minutes = 6:00/km; 40 minutes = 4:00/km (well-trained amateur). Half marathon: 2:00 = 5:41/km (about 10.5 km/h — a common 'just under 2 hours' target); 1:30 = 4:16/km (well-trained); 2:30 = 7:06/km. Marathon: 4:00 = 5:41/km (common amateur target); 3:30 = 4:58/km; 3:00 = 4:15/km (sub-3 is a major milestone); 5:00 = 7:06/km. Sub-2hr marathon (only achieved by Kipchoge in exhibition conditions and approached but not officially broken in races) ≈ 2:51/km — astonishing pace sustained over 42.2 km. Note the pattern: half marathon and marathon paces look similar (5:41/km for 2hr half and 4hr marathon) because they're calibrated to comparable effort levels for trained runners — but you have to be much more aerobically efficient to hold that pace twice as long. This calculator translates any pace into the equivalent times across all common distances and speed units.

What do I need to know about Treadmill Conversion?

Treadmill speeds need translating into running pace, and the units depend on where the treadmill was made. UK treadmills typically display in km/h; US treadmills in mph. 1 mph = 1.609 km/h. The pace conversion: at 6 mph (≈ 9.66 km/h), you're running 6:13/km pace; at 10 km/h, 6:00/km; at 12 km/h, 5:00/km; at 14 km/h, 4:17/km; at 16 km/h, 3:45/km. Useful round-number references: easy recovery jogging is typically 8–10 km/h (6:00–7:30/km); steady runs around 10–12 km/h (5:00–6:00/km); tempo runs 12–14 km/h (4:17–5:00/km); intervals 13–18 km/h (3:20–4:37/km depending on length). Treadmill pace tends to feel easier than the equivalent road pace, for several reasons: no wind resistance (which costs roughly 5–10 seconds per km at typical running speeds), no terrain variation, the belt assists turnover marginally, and the treadmill cushioning is gentler on legs. The standard correction for treadmill-to-road equivalence: set the treadmill incline to 1% to simulate the wind resistance and ground variation of outdoor running. Use higher inclines (2–4%) for hill simulation. Treadmill pacing is also useful for very precise interval work — you set the speed exactly and can't 'cheat' by slowing down without consciously changing the setting. This calculator handles all the conversions so you can train confidently across treadmills and units.

What's the key thing to understand about Progressive Overload and Recovery?

For sustained fitness improvements, progressive overload (gradually increasing training load over time) combined with adequate recovery is essential. The principle: the body adapts to a training stimulus, then requires a new stimulus to continue improving. Without progressive overload, fitness plateaus. Without adequate recovery, overtraining prevents adaptation and increases injury risk. Signs of overtraining: persistent fatigue, declining performance despite consistent training, increased resting heart rate, disturbed sleep, and mood changes such as irritability or loss of motivation. If these signs persist for more than a week or two, reduce training volume and intensity, prioritise sleep and nutrition, and consider a full rest week before resuming progressive overload.

How Do You Convert Pace Between Metric and Imperial Distances?

Pace is usually expressed as minutes per mile or minutes per kilometre, and converting between the two requires more than simply converting the distance unit, because pace is a rate, not a fixed quantity. Since one mile equals 1.60934 kilometres, a pace in minutes per mile converts to minutes per kilometre by dividing by 1.60934 (a faster-looking number, since a kilometre is a shorter distance than a mile), while converting minutes per kilometre to minutes per mile means multiplying by 1.60934. A common point of confusion is assuming the conversion works the same direction as a simple distance conversion — it's the inverse relationship that catches people out, since a runner running the same actual speed will have a pace per mile that looks like a bigger number than their pace per kilometre, purely because a mile is the longer unit. This matters practically for anyone training with a US-based plan using miles and racing on a course measured in kilometres, or vice versa — misreading a 4:30/km pace as 4:30/mile pace (or the reverse) represents a very different actual running speed, roughly a 38% difference, which would produce a dramatically wrong pacing strategy if used on race day without converting correctly first.

Why Do Your Watch and Treadmill Pace Sometimes Disagree?

GPS watches and treadmill displays calculate pace through entirely different methods, and small systematic differences between them are normal rather than a sign either device is faulty. A GPS watch estimates distance by tracking satellite-based position changes over time, which works well outdoors with a clear sky view but is subject to small errors from satellite signal quality, tree cover, tall buildings, or the watch's sampling rate smoothing out tight turns and elevation changes — GPS distance is typically accurate to within 2-3% outdoors under good conditions, but can read short or long on winding paths or in dense urban areas. A treadmill, by contrast, calculates speed and distance from the belt's actual mechanical rotation speed, which is generally very precise and consistent, but depends on the treadmill being properly calibrated — belts that haven't been serviced or calibrated recently can read a percent or two off true speed in either direction. Because the two measurement methods are independent, a runner who trains on a treadmill and races using GPS, or switches between the two, may notice their "pace" at a given perceived effort looks slightly different between contexts. Neither is necessarily wrong; for comparing a training session to a race performance, it's more useful to cross-check both against heart rate or perceived effort than to assume one device's number is the definitive truth.

Worked Example: Converting a Half Marathon Pace to Speed

A runner holding a pace of 5:30 per kilometre covers 1km every 5.5 minutes, which converts to a speed of 60 ÷ 5.5 ≈ 10.9km/h. Over a half marathon (21.1km), that pace predicts a finish time of 21.1 × 5.5 ≈ 116 minutes, or 1 hour 56 minutes. Converting to miles, 5:30/km is roughly equivalent to 8:51 per mile, or a speed of about 6.8mph — useful when comparing a GPS watch reading in metric pace against a treadmill display set to imperial speed, a common source of confusion covered elsewhere on this page.

What should I know about Rounding Errors Over Long Distances?

Small rounding differences in pace-to-speed conversion become more noticeable the longer the distance involved — a pace rounded to the nearest second per kilometre can shift a predicted marathon finish time by a minute or more once multiplied out over 42.2km, even though the per-kilometre difference looks trivial. This is why race-pacing plans for longer events, such as marathons, are usually built from precise decimal pace figures rather than rounded watch or treadmill displays, with the rounding only applied back to a readable split time at the end of the calculation.