Pace Converter: Min/km, Min/mile, MPH and km/h

A pace converter changes running pace between min/km, min/mile, km/h and mph. One international mile is exactly 1.609344 km; NIST's SI conversion tables list that factor as exact. So multiply seconds per kilometre by 1.609344 to get seconds per mile, and divide seconds per mile by 1.609344 for the reverse conversion. Worked through, a 5:00 min/km pace comes out at 8:03 min/mile, 12.00 km/h or 7.46 mph. That conversion preserves the same speed—it does not decide whether the pace suits your fitness, course or race-day conditions.

Pace conversion chart

Pace is the elapsed time needed to cover one unit of distance. Min/km means minutes per kilometre, while min/mile means minutes per mile. Speed reverses the relationship: it measures distance covered per hour.

The displayed mile paces are rounded to the nearest second. Keep the unrounded value when calculating a finish time. At exactly 5:00 min/km, for example, the equivalent pace is 8:02.803 min/mile—not precisely 8:03. The same pace produces 25:00 for 5K and 50:00 for 10K. Over the official road distances of 21.0975 km for the half marathon and 42.195 km for the marathon, as World Athletics defines them, it works out to 1:45:29 and 3:30:59 (3:30:58.5 before rounding to the nearest second).

For comparison, the Depicus conversion chart lists speed and pace columns side by side and gives the speed factor as 1 km/h = 0.621371192 mph, which is simply 1 ÷ 1.609344. Calculator.net combines pace, time and distance calculations, while RaceID provides a focused min/km and min/mile conversion.

How to convert running pace accurately

My working rule is simple: convert in seconds and round once at the end. Rounding the displayed pace before calculating a race time turns a formatting choice into a finish-time error.

Convert min/km to min/mile

Use this formula:

`seconds per mile = seconds per kilometre × 1.609344`

For 4:37 min/km:

1. Convert the pace to seconds: `4 × 60 + 37 = 277`.
2. Multiply by 1.609344: `277 × 1.609344 = 445.788` seconds.
3. Convert back to minutes and seconds: 445.788 seconds is 7:25.788.
4. Round for display: 7:26 min/mile.

For the reverse calculation:

`seconds per kilometre = seconds per mile ÷ 1.609344`

Worked example: a 7:30 min/mile pace is 450 seconds per mile. Dividing 450 by 1.609344 gives 279.617 seconds, or 4:40 min/km when rounded.

Convert pace to km/h or mph

Speed is the reciprocal of pace. Convert the pace to decimal minutes, then use:

• `km/h = 60 ÷ minutes per kilometre`
• `mph = 60 ÷ minutes per mile`

Worked examples: at 5:00 min/km, the calculation is `60 ÷ 5 = 12 km/h`. At 8:00 min/mile, it is `60 ÷ 8 = 7.5 mph`.

The same relationships run in reverse and between the two speed units:

• `minutes per kilometre = 60 ÷ km/h`
• `mph = km/h ÷ 1.609344`

Calculated this way, 10 km/h is 6:00 min/km and 6.21 mph. Do not apply the 1.609344 distance factor directly to a minutes-and-seconds display; convert the time to total seconds first.

Convert pace into finish time

Once pace and distance use matching units:

`finish time = pace × distance`

At 6:00 min/km, a 10K takes 60 minutes. At 8:00 min/mile, 10 miles take 80 minutes. For a detailed marathon calculation, the marathon pace calculator per mile explains how the full 26.2188-mile distance affects the clock.

A converter can also solve for missing pace: divide total time by distance. For example, 50 minutes ÷ 10 km = 5 minutes, so a 50-minute 10K averages 5:00 min/km. The operation says what average pace the result represents; it does not show how individual kilometres were distributed.

Rounding can move the finish clock

Rounding is harmless when you only need a readable watch target. It becomes visible when a rounded per-unit pace is multiplied across an entire race.

Three rounding errors worked through

These are arithmetic differences, not race predictions. A one-second error repeated over every kilometre changes a marathon calculation by 42.195 seconds; one second per mile changes it by about 26.219 seconds.

The practical fix is to store pace as unrounded seconds, calculate cumulative checkpoints from that value, and round only what the runner sees. Avoid building a pace band by repeatedly adding a rounded lap split; the marathon pace band calculator guide shows the proportional checkpoint method that keeps the last row on the target time. For the per-kilometre split arithmetic itself, see the running pace calculator per km guide.

Conversion is not adjustment or prediction

A unit conversion preserves speed. A race-equivalency calculation estimates what one performance might imply at another distance. A course-adjusted plan changes individual splits around elevation, wind or altitude while targeting a broader race strategy.

Those operations should remain separate. Converting 5:00 min/km into 8:03 min/mile does not account for a climb, and converting a recent 10K result does not by itself establish a marathon target. A frequent mistake is to blur that line and present a mathematically correct conversion as if it were an individual pacing decision. TrainingFlow's race-day strategies belong to the adjustment side: they build course-adjusted splits on the real elevation profile and your fitness, while the unit conversion underneath remains plain arithmetic.

Turn the converted pace into a race-day plan

A pre-race preparation workflow

Complete the unit conversion before adding course or race-week inputs:

1. Record the target average pace in total seconds per kilometre or mile.
2. Confirm whether the course signs, watch alerts and training plan use kilometres or miles.
3. Generate cumulative checkpoints from the unrounded pace.
4. During race week, check the course profile and current forecast separately; use a dedicated heat and humidity pace adjustment if those conditions require another planning pass.
5. Print a fallback row rather than recalculating mid-race. By calculation, adding 5 seconds per kilometre adds 3:31 across a marathon (5 × 42.195 = 210.975 seconds); adding 10 seconds per kilometre adds 7:02.

Those fallback figures are time conversions, not recommendations about which pace a runner should choose. Their value is operational: the alternative clock times are available before the start.

Check the output before using it

Use two independent routes to catch input errors. Convert the pace, reverse the result, and confirm that it returns to the original value within the expected rounding difference. Then calculate one familiar distance by hand: 5:00 min/km × 5 km should produce 25:00, while 8:00 min/mile × 5 miles should produce 40:00.

Also inspect the unit labels. Entering 5:00 as min/mile instead of min/km changes the implied speed from 12.00 km/h to 19.31 km/h. The arithmetic may still look clean, so the implausible output is often the first sign that the wrong unit was selected.

FAQ

How do I convert min/km to min/mile?

Turn the min/km pace into seconds, multiply by 1.609344, then convert the result back into minutes and seconds. For example, 300 seconds per kilometre becomes 482.803 seconds per mile, displayed as 8:03 min/mile.

Can a pace converter calculate finish time?

Yes, when pace and distance use matching units: multiply pace by distance. Keep the pace unrounded until the final step if you need cumulative race checkpoints rather than a quick estimate.

What is the difference between a pace converter and a race-equivalency calculator?

A pace converter expresses the same speed in another unit. A race-equivalency calculator applies a performance model to estimate a result at another distance, so its output depends on assumptions beyond the unit conversion.