Pace Conversion: min/km vs min/mile vs km/h — and Why GPS Lies

Pace conversion is the most basic arithmetic in running — divide minutes by kilometres, multiply by 1.60934 to get miles. It should be trivial. And yet runners get confused by it constantly, GPS watches display numbers that don't match calculator outputs, and race plans built in one unit system end up wrong in another.

This guide explains the exact conversion mathematics, why GPS pace readings are systematically different from what a calculator gives you, and how to build a race plan that survives contact with your watch mid-race.

Key takeaways

The conversion factor between kilometres and miles is exactly 1.60934 km per mile (international definition since 1959)
To convert min/km to min/mile: multiply by 1.60934. To convert min/mile to min/km: divide by 1.60934
GPS watches calculate pace from position samples taken every 1–3 seconds, smoothed over a rolling window — the displayed pace is never truly instantaneous
GPS pace on a curved course (bends, switchbacks) is always slightly slower than actual pace due to the difference between GPS-measured path distance and true distance
Treadmill speed in km/h converts to min/km via: pace = 60 ÷ speed

The conversion factor

The international definition of the mile was fixed at exactly 1,609.344 metres in 1959 by agreement between the United States and Commonwealth countries. This gives the exact conversion:

1 mile = 1.60934 kilometres (rounded from 1.609344 to 5 decimal places)

All pace conversions derive from this single number.

min/km to min/mile

Multiply the min/km value (in decimal minutes) by 1.60934:

5:00 min/km = 5.000 minutes per km × 1.60934 = 8.047 minutes per mile = 8:02.8 min/mile (rounds to 8:03)

4:30 min/km = 4.500 × 1.60934 = 7.242 = 7:14.5 min/mile

3:00 min/km = 3.000 × 1.60934 = 4.828 = 4:49.7 min/mile

The "multiply by 1.6" mental shortcut is often close enough: 5:00 × 1.6 = 8:00 (actual: 8:03). For rough in-race estimates, this works. For building an accurate race plan, use the full factor.

min/mile to min/km

Divide by 1.60934:

9:00 min/mile = 9.000 ÷ 1.60934 = 5.592 = 5:35.5 min/km

8:00 min/mile = 8.000 ÷ 1.60934 = 4.971 = 4:58.3 min/km

Pace to speed (km/h)

Speed in km/h is the distance covered per hour if you maintained that pace. Since pace is already expressed as time per km:

km/h = 60 ÷ (min/km expressed in decimal minutes)

At 5:00 min/km: 60 ÷ 5.000 = 12.0 km/h At 4:30 min/km: 60 ÷ 4.500 = 13.3 km/h At 6:00 min/km: 60 ÷ 6.000 = 10.0 km/h

And the reverse: min/km = 60 ÷ km/h

At 10.5 km/h: 60 ÷ 10.5 = 5:43 min/km

The calculator

The pace calculator converts between all three formats instantly and includes finish time predictions for standard distances:

Interactive calculator

Open full page →

Pace (min:ss per km)

min/km

5:00

min/mile

8:03

km/h

Finish time predictor

Enter a recent race result to predict other distances.

Race time (H:MM:SS or MM:SS)

Distance (km)

All calculations are performed locally in your browser. No data is sent to any server.

Pace reference table

For quick reference, paces from 3:30 to 8:00 min/km:

min/km	min/mile	km/h	5K	10K	Half	Marathon
3:30	5:38	17.1	17:30	35:00	1:13:51	2:27:43
4:00	6:26	15.0	20:00	40:00	1:24:23	2:48:46
4:30	7:14	13.3	22:30	45:00	1:34:55	3:09:50
5:00	8:03	12.0	25:00	50:00	1:45:29	3:30:57
5:30	8:51	10.9	27:30	55:00	1:56:02	3:52:05
6:00	9:39	10.0	30:00	1:00:00	2:06:35	4:13:11
6:30	10:28	9.2	32:30	1:05:00	2:17:08	4:34:17
7:00	11:16	8.6	35:00	1:10:00	2:27:41	4:55:23
7:30	12:04	8.0	37:30	1:15:00	2:38:14	5:16:29
8:00	12:52	7.5	40:00	1:20:00	2:48:47	5:37:35

Finish times are exact at constant pace — multiply pace × distance.

Why GPS pace doesn't match calculator pace

This is where runners get genuinely confused. You set your race plan at 5:00/km. You look at your watch mid-run. It says 5:04. Then 4:57. Then 5:10. The average might be right, but the instantaneous reading is never stable. Why?

Position sampling and smoothing

GPS watches don't track a continuously moving point — they sample your position every 1–3 seconds (depending on the device and GPS mode) and calculate velocity as the displacement between samples divided by time elapsed. The resulting velocity estimate is noisy for several reasons:

Satellite geometry error: Your position is triangulated from satellite signals, with horizontal accuracy typically ±3–10 metres in open conditions. At 5:00/km pace, a 5-metre position error in a 1-second sample translates to ±18 sec/km of noise. Watches smooth this over a rolling window (typically 5–30 seconds depending on device and setting) to reduce jitter.

Signal multipath: In urban environments, satellite signals bounce off buildings before reaching the receiver. The watch may receive both direct and reflected signals, contaminating the position estimate.

GPS drift on curves: GPS distance measurement treats your path as a series of straight-line segments between position samples. On a curved course, the true path length exceeds the sum of the straight segments. On tight bends (like the turns in a 400m track), GPS systematically under-records distance — meaning it also under-records your pace, showing you slower than you actually are.

The practical implication

Your GPS watch's instantaneous pace display is always an estimate with noise. On a straight flat road in good GPS conditions, the noise is ±5–10 sec/km from the smoothed display. On a winding trail or urban course, it can be ±20–30 sec/km.

For in-race pacing, use average pace (for the current km or mile) rather than instantaneous pace. Most watches allow you to display lapped pace rather than rolling pace — this is more stable and more useful.

GPS vs. measured course distances

One more source of discrepancy: GPS-measured race distance is not always equal to certified course distance. A GPS watch typically records a marathon as 42.3–42.5 km rather than exactly 42.195 km, due to weaving around other runners, taking the non-tangent racing line on curves, and GPS drift. If you run 42.4 km at 5:00/km, your watch shows 3:32:00 — but the official time is based on the certified 42.195 km distance, meaning your per-km average pace was slightly faster.

Certified course tangents

Certified marathon courses are measured along the shortest legal path (tangent line through each turn). A runner who drifts wide through corners adds distance. GPS records where you actually went, not the certified shortest path. The official finish time is what matters — plan your race around the certified distance.

Treadmill speed to outdoor pace

Treadmill speed displays in km/h (or mph), not min/km — the opposite of how most runners track outdoor training. Converting:

min/km = 60 ÷ km/h

At 10.0 km/h: 60 ÷ 10 = 6:00 min/km At 12.0 km/h: 60 ÷ 12 = 5:00 min/km At 14.4 km/h: 60 ÷ 14.4 = 4:10 min/km

Note on treadmill vs outdoor equivalence: Running on a flat treadmill requires slightly less energy than outdoor running at equivalent pace because you encounter no air resistance. A 1% incline on the treadmill approximately compensates for this and produces equivalent energy cost to flat outdoor running at the same speed. This is a rough calibration — the exact correction depends on runner size, speed, and the treadmill's calibration accuracy.

Common conversion mistakes

Mistake 1: confusing seconds and decimal minutes 5:30 min/km is 5.5 decimal minutes (five minutes, thirty seconds), not 5.3 (five minutes, thirty hundredths of a minute). When doing calculations, always convert MM:SS to decimal minutes first: MM + (SS/60).

Mistake 2: treating miles and kilometres interchangeably in race plans A runner training in kilometres who signs up for a race using miles (some US events) and forgets to convert their per-km pace to per-mile pace will start at the wrong effort. Double-check the race's measurement unit before building a split plan.

Mistake 3: GPS pace for an 800m or 1km interval For very short intervals on a curved track, GPS error dominates. Use a calibrated track and time the intervals with a stopwatch — distance is measured by the track, not GPS.

Frequently asked questions

What is a good running pace for a beginner?▾

A comfortable beginner starting pace is typically 7:00–9:00 min/km (11:15–14:30 min/mile). The benchmark is conversational effort — you should be able to speak full sentences without gasping. Your GPS watch may show pace fluctuating significantly; look at average km pace rather than instantaneous. Beginners often go out too fast in the first kilometre; aim to feel comfortable for the first 5 minutes even if that feels artificially slow.

Why does my watch pace lag behind my effort?▾

GPS pace smoothing is the main cause — the display averages over a rolling window (often 5–15 seconds). When you accelerate, your pace doesn't immediately register. When you slow, it takes a few seconds to drop. For very short efforts (200m sprints), this lag means the displayed pace at the end of the effort may still be updating as you finish. Chest-based GPS or foot pod sensors respond faster than wrist GPS for interval work.

My marathon watch time says 3:28 but my official chip time is 3:31. Why?▾

Your watch started when you crossed the start line (or when you pressed start, if before the gun) and stopped when you finished. The official chip time is gun-to-chip-finish in mass starts, or chip-to-chip for wave starts. Additionally, your GPS-measured distance was probably 42.3–42.4 km rather than 42.195, meaning you ran slightly further at slightly faster than calculated pace. The official time from the chip is your actual race performance.

How do I calculate what pace I need for a target finish time?▾

Divide target time in seconds by distance in metres, then convert back to min/km. For a 4-hour marathon: 14,400 seconds ÷ 42,195 metres = 0.3412 sec/m × 1,000 = 341.2 sec/km = 5:41 min/km. Or use the calculator above: enter 4:00:00 and 42.195 km to see required pace.

Is GPS pace accurate enough to pace a race by?▾

For marathons and half marathons where you're maintaining roughly constant pace, GPS average pace is useful and usually within ±5 sec/km of true pace. For 5K racing where every second matters, GPS is too noisy — experienced 5K runners pace by effort and landmark splits, not GPS. For intervals on a track, use a stopwatch and the measured track distance.

References

[1]
Terenzoni, M., Sainas, G., and Crisafulli, A. (2021). GPS watch accuracy in measuring distance and pace in road races. Journal of Human Kinetics. 76. pp. 155–165.
[2]
Haugen, T. and Buchheit, M. (2016). Accuracy of GPS devices for assessing mechanical properties of sprint acceleration. International Journal of Sports Physiology and Performance. 11(8). pp. 999–1006.
[3]
Jones, A.M. and Doust, J.H. (1996). Oxygen cost and energy expenditure of running on a treadmill vs outdoor running. Journal of Sports Sciences. 14(4). pp. 321–327.