Pace Converter Explained: How min/km and min/mile Relate

Why pace travels in two units

Running pace is the inverse of speed: time per distance instead of distance per time. The same effort can be quoted as 5:00 per kilometre, 8:03 per mile, 12.0 km/h, or 7.46 mph — and a runner who does not notice the unit changing from one number to the next is the runner who blows up at mile six of a half marathon because the watch said 7:30 but the coach said 7:30 in the other unit. The pace converter on this site takes one pace in one unit and returns the same pace in every other useful unit at once, including projected finish times for the four standard road distances.

Two units dominate the world of road running. Min/km is the working unit of European running, World Athletics course measurement, parkrun result emails, and most GPS-watch defaults sold outside the United States. Min/mile is the working unit of US road racing, UK marathon plans, and the coaching literature that grew out of the American running boom — Daniels, Pfitzinger, Hanson — all of which quote training paces in min/mile. A runner who trains off any of those plans and races in Europe needs to convert between the two units fluently, and a runner who trains off the kilometre and races in the US needs to do the same in reverse.

The conversion itself is one multiplication. The confusion is everything around it: which way to multiply, why a smaller pace number is a faster runner, and why the per-mile number is always larger than the per-km number for the same effort. The next few sections unpick that, with worked numbers throughout.

The exact conversion factor

The international mile is defined as exactly 1609.344 metres. That definition was set in 1959 in the international yard and pound agreement signed by the United States, the United Kingdom, Canada, Australia, New Zealand, and South Africa, and it replaced a tangle of slightly-different national miles that had drifted apart by a few parts per million. NIST Handbook 44 and ISO 31-1 both record the same value. For running, the practical consequence is that

1 mile = 1.609344 km   (exact)
1 km   = 0.6213711922… mile

and that the same exact factor — 1.609344 — converts every length, speed, or pace number between the two unit systems with no rounding error introduced. The US survey mile, used in some legacy land-surveying contexts, is about 3.2 parts per million longer than the international mile, but no running event in the world is measured against it. Track and road events are certified against the SI metre by World Athletics or the relevant national federation, and a kilometre marker on a certified course is a true 1000 metres, not an approximation.

Two things follow from the mile being the longer unit. First, a min/mile number for a given pace is always larger than the min/km number for the same pace, because the runner is covering more ground per minute of clock time. Second, multiplication and division go opposite ways depending on direction: min/km becomes min/mile by multiplying by 1.609344 (more time to cover more distance), while min/mile becomes min/km by dividing by the same factor.

Pace vs speed: the inverse trap

Pace and speed are reciprocals. If pace is in seconds per kilometre, then speed in km/h is 3600 divided by pace, because there are 3600 seconds in an hour. The same identity in the other unit system: speed in mph is 3600 divided by pace in seconds per mile. Both identities are exact.

speed_kmh = 3600 / pace_sec_per_km
speed_mph = 3600 / pace_sec_per_mile

The reciprocal relationship is the source of the most common pace-conversion mistake: doubling a runner's pace does not double their finish time, it halves their speed and therefore doubles the finish time. And halving a pace number — say, going from 6:00/km to 3:00/km — does not change the runner's speed by half, it doubles the speed, which is what would happen if a casual jogger sprinted past a world-record holder on the same lap. Pace is the right unit when you are running and looking at a watch; speed is the right unit when you are setting a treadmill or comparing to a cycling effort. Both are useful, and the speed converter on this site handles the related km/h, mph, m/s, knots and ft/s conversions when the unit you need is not pace at all.

A worked example at 5:00/km

Take a clean case: a 5:00 per kilometre pace. This is a popular benchmark — it is a common marathon-pace target for sub-elite club runners, it is what a strong recreational runner runs at parkrun, and it falls in nearly every coached plan as a marker for a steady long-run pace. Plugging 5 minutes 0 seconds into the pace converter with the unit set to min/km returns the full picture in every useful form at once.

Pace:        5:00 per km
= 5 × 1.609344
= 8.04672 min/mile
≈ 8:03 per mile

Speed:       3600 / 300 = 12.00 km/h
12.00 / 1.609344 = 7.456 mph

Finish times (even splits):
5K      = 5  × 300 s = 1500 s = 25:00
10K     = 10 × 300 s = 3000 s = 50:00
Half    = 21.0975 × 300 s = 6329.25 s ≈ 1:45:29
Marathon= 42.195  × 300 s = 12658.5 s ≈ 3:30:59

Three numbers in that block are worth committing to memory. The first is the mile-to-km factor itself: 1.609344, exactly. The second is that pace in seconds per kilometre, divided into 3600, gives km/h directly — a 6:00/km is 600 s/km, so 3600 ÷ 600 = 6 km/h, and a 4:00/km is 240 s/km, so 3600 ÷ 240 = 15 km/h. The third is the half- and full-marathon distances — 21.0975 km and 42.195 km — which are the exact World Athletics standard distances and are why a marathon time is always a half-marathon time slightly more than doubled, never exactly doubled. Even-splits arithmetic falls out of those three facts.

Useful pace benchmarks across both units

The pace pairs below come up constantly in training plans, race forecasts, and runner conversations. Worth knowing approximately, even if the calculator is one tap away.

• 3:00 /km ≈ 4:50 /mile ≈ 20.0 km/h ≈ 12.4 mph — world-class marathon pace; Eliud Kipchoge ran his unofficial sub-2 at about 2:50/km.
• 4:00 /km ≈ 6:26 /mile ≈ 15.0 km/h ≈ 9.3 mph — sub-elite club runner; this pace finishes a marathon in 2:48:46.
• 4:30 /km ≈ 7:15 /mile ≈ 13.3 km/h ≈ 8.3 mph — strong amateur marathon pace; 3:09:53 marathon.
• 5:00 /km ≈ 8:03 /mile ≈ 12.0 km/h ≈ 7.46 mph — classic sub-3:30 marathon target.
• 5:41 /km ≈ 9:09 /mile ≈ 10.55 km/h ≈ 6.55 mph — sub-4 marathon pace, the most common amateur marathon goal in the English-speaking world.
• 6:00 /km ≈ 9:39 /mile ≈ 10.0 km/h ≈ 6.2 mph — comfortable long-run pace for many recreational runners; 4:13:00 marathon.
• 7:00 /km ≈ 11:16 /mile ≈ 8.57 km/h ≈ 5.33 mph — easy jogging pace; sub-5 marathon at 4:55:30.

Each row in that table is the same effort restated four times. The point of the pace converter is to make the restating mechanical, not to memorise every pair.

Common mistakes runners make crossing units

A handful of errors recur often enough that it is worth naming them.

Multiplying the wrong way

The most common mistake is dividing min/km by 1.609344 to get min/mile, which gives the right magnitude for an ultrarunner but is wrong by a factor of more than two and a half for a road runner. The mile is longer than the kilometre, so the per-mile pace is the larger number; min/km × 1.609344 = min/mile is the direction that produces a larger number, and it is the correct one. A runner who thinks 5:00/km is 3:06/mile has just promised themselves a 1:21 half marathon they are not going to run.

Confusing pace with speed

Asking how fast 5:00/km is in mph and getting back an answer of 8:03 is a sign the unit has slipped. 5:00/km in mph is 7.46 mph — a single number with no colon, because mph is a speed and the colon notation belongs to pace. The reciprocal between the two is exact, but the units are not interchangeable. If the answer has a colon in it, it is a pace; if it does not, it is a speed. The pace converter always returns both, side by side, to make the difference obvious.

Trusting a treadmill in the wrong unit

Treadmills sold in the US display speed in mph by default; treadmills sold in Europe display km/h. A runner travelling between regions and reading 6.0 off the console without checking the unit may think they are running 6 km/h (a slow jog) when they are running 6 mph (a more committed 6:13/km pace) — or the other way around. Most modern treadmills include a unit toggle in the settings menu; finding it once is worth more than five mental conversions per session.

Trusting a race forecast on the wrong distance

Holding 5:00/km for a 5K is straightforward. Holding 5:00/km for a marathon is not, and the pace converter is silent on the question of whether the pace is sustainable for the distance — it only reports the finish time if it is. For the harder forecast — given a recent race, what should my marathon time be — use the marathon time predictor instead, which applies the Riegel exponent to a recent result to estimate how the effort scales with distance.

How to use the converter in training

Three uses come up often enough to be worth flagging.

Translating a coached plan into the unit on the watch. Most published plans — Daniels, Pfitzinger, Higdon, Hanson — quote tempo, threshold, interval, and long-run paces in min/mile. A runner on a GPS watch that defaults to min/km can either change the watch unit or convert every prescribed pace once at the start of the block and write them down. Either works; the second is more portable across watches and apps and is what the pace converter is built for.

Pacing an international race. A UK runner racing a US marathon needs to know that the miles markers will appear before the kilometre markers, and that the coached pace they have trained off is probably already in min/mile. A US runner racing London or Berlin needs the reverse: kilometre markers, mostly no mile markers on the course at all, and a watch that either needs reconfiguring to per-km lap splits or a pre-loaded second screen with the per-km target. The converter does the pace pair; the screen choices do the rest.

Setting a target time and working backwards. Working back from a goal finish time to the required even-split pace is the inverse problem. For that, use the marathon pace calculator — enter the goal time, get the per-km and per-mile target back in both units. Then drop the per-km pace into the pace converter to see the full grid of splits for shorter race rehearsals at the same effort.

When the math is not enough

Pace conversion is exact arithmetic. The harder questions are about whether to hold a given pace at all, and the converter cannot answer those. Heat, altitude, elevation gain, wind, time of day, and the runner's recent training all push the sustainable pace away from the cold-floor target. A 5:00/km that is comfortable in Berlin in October may not be sustainable in Dubai in January at the same effort. A converter that reports the same finish time for both is being technically correct and practically useless. Treat the output as the answer to one specific question — “what does this pace look like in the other unit and what would it produce on a flat, calm, sea-level course held constant” — and bring everything else to the question separately.