Four units, one speed
Pace in minutes per kilometre, speed in km/h, pace per mile and speed in mph all describe the same speed in different units. Enter any one of them and the converter updates the other three live, with no button. That makes it easy to turn a US training plan given in mph straight into the pace in min/km you are used to.
How the converter works
Converting pace to km/h uses 60 divided by the pace in minutes: a pace of 5:00 min/km gives 60 / 5 = 12 km/h. For miles the internationally defined value is 1 mile = 1.609344 km, so pace per kilometre is multiplied by that factor to get pace per mile. km/h and mph use the same factor (km/h divided by 1.609344 gives mph).
Example: 5:41 min/km times 1.609344 gives a pace of 9:09 min/mile, with a speed of about 10.6 km/h or 6.6 mph.
What the marathon and half marathon time in the table means
For every pace the table shows the time you would get holding that exact pace for the full marathon distance (42.195 km). It is a pure calculation, not a prediction: running faster early or slowing down later changes the actual result. To project a finish time from an existing best, the race time predictor is the better tool.
Where the converter stops being useful
The converter assumes a constant, flat speed. On trails with elevation gain, or on a treadmill with an incline, the actual effort at the same pace changes a lot. For those cases use the km-effort calculator for trail races and the treadmill pace calculator.
Frequently asked questions
How many km/h is 5:00 min/km?
5:00 min/km equals 60 divided by 5, which is 12 km/h.
How do I convert min/km to min/mile?
Multiply the pace per kilometre by 1.609344. 5:41 min/km becomes 5:41 times 1.609344, about 9:09 min/mile.
How many mph is 10 km/h?
10 km/h divided by 1.609344 is about 6.2 mph.
What marathon time does a 4:15 min/km pace give?
Holding 4:15 min/km for the full 42.195 km gives 2:59:20, see the table above for the exact figure.
Why doesn’t my GPS watch match the table exactly?
Watches round numbers and drift slightly due to GPS inaccuracy. The table calculates with exact values without rounding mid-calculation.