Conversion calculator

Pace Converter

Pace is one over speed, and that single fact explains why treadmill buttons feel uneven, why two paces sometimes cannot be averaged, and why the numbers never behave the way distance and time do.

Calculator

Try:

5:00 per km

5:00 /km · 8:03 /mi

12.00 km/h · 7.46 mph. Pace and speed are reciprocals, which is why they behave so differently as numbers.

What that pace finishes in

Race times at 5:00 per kilometre, held exactly
DistanceKilometresFinish time
1 km15:00
1 mile1.6093448:03
5 km525:00
10 km1050:00
Half marathon21.09751:45:29
Marathon42.1953:30:59
50 km504:10:00

A marathon is exactly twice a half — 42.195 against 21.0975 km — so these figures double exactly. Real marathon times do not, and the gap between a doubled half and an actual marathon is entirely about pace degrading over the distance. That is a physiological question rather than an arithmetic one, and this page does not attempt to predict it.

The pace a target needs

Pace required5:41 /km9:09 /mi · 10.55 km/h
Against your current pace0:41 slower per kmfinish 29:02 earlier

A four-hour marathon and a two-hour half need the same 5:41 per kilometre, because the distance and the time halve together. The two are not equally hard, which is the point at which arithmetic stops being useful.

Two paces do not always average

True average pace4:48.0 /kmtotal time ÷ total distance
Averaging the two paces5:00.0 /kmwrong by 0:12.0 per km

Switch between the two options above and watch the second row. Over equal distances the simple mean is exactly right. Over equal times it is not, because more ground is covered at the faster pace — half an hour at 4:00 and half an hour at 6:00 averages 4:48, not 5:00. Nothing in the units tells you which case you are in, which is why the mistake survives.

Why the treadmill buttons feel uneven

What one more km/h is worth, at different speeds
SpeedPaceNext km/h saves
8 km/h7:30 /km50.0 s/km
10 km/h6:00 /km32.7 s/km
11 km/h5:27 /km27.3 s/km
12 km/h5:00 /km23.1 s/km
14 km/h4:17 /km17.1 s/km
15 km/h4:00 /km15.0 s/km
16 km/h3:45 /km13.2 s/km
18 km/h3:20 /km10.5 s/km

Pace is one over speed, so equal steps in speed are not equal steps in pace. Going from 10 to 11 km/h takes 32.7 seconds off every kilometre; going from 15 to 16 takes only 15.0. The same button on the same machine buys less than half as much at the faster end — which is part of why pace improvements get harder, quite apart from anything happening to the runner.

What this converter covers

Pace in either unit, treadmill speed, every standard race time, and the pace a target needs — with the averaging trap shown rather than described.

  • min/km, min/mile, km/h and mph, on the exact mile
  • Finish times for 5K, 10K, half, marathon and 50K
  • The pace a target time requires, and the gap from your current one
  • True average pace against the naive mean, over distance or over time
  • What one more km/h is worth at different speeds
Pace and speed The averaging trap Race times Exact mile

Free, no signup — exact by definition, not an estimate.

Updated 8 September 2026

At a glance

Formula shown
pace (s/km) = 3600 ÷ speed (km/h) · average pace = total time ÷ total distance
Scenario support
5:00/km is 8:02.8/mi · 30 min at 4:00 and 30 at 6:00 averages 4:48, not 5:00
Educational estimate
Planning support from the values you enter — not professional advice.

Pace is one over speed

Speed says how far in a given time. Pace says how long for a given distance. They carry the same information and behave completely differently as numbers, because one is the reciprocal of the other.

What one more km/h is worth
SpeedPaceNext km/h saves
8 km/h7:30 /km50.0 s/km
10 km/h6:00 /km32.7 s/km
12 km/h5:00 /km23.1 s/km
15 km/h4:00 /km15.0 s/km
18 km/h3:20 /km10.5 s/km

The same button on the same treadmill is worth 50 seconds a kilometre at 8 km/h and 10.5 at 18. Nothing about the runner has changed; the arithmetic has.

That is a real part of why pace improvements get harder as they get faster, quite separately from anything physiological. Taking thirty seconds a kilometre off a 6:00 pace is one step on the dial. Taking thirty off a 4:00 pace is two and a half, and the effort behind each of those steps is not equal either.

It also explains the units. Runners talk in pace because a pace difference maps directly onto a finish-time difference — five seconds a kilometre is three and a half minutes over a marathon, whatever the pace. A speed difference does not behave that tidily.

Two paces do not always average

This is the one that catches everyone, and the annoying part is that it works half the time — which is exactly why the habit survives.

Running at 4:00/km and 6:00/km, two ways
Split byCoveredTrue averageNaive mean
Equal distance — 1 km each2 km in 10:005:00 /km5:00 — correct
Equal time — 30 min each12.5 km in 60:004:48 /km5:00 — wrong

Over equal distances the simple mean is exactly right: each pace applies to the same amount of ground, so the times add and the distances add and it comes out as the average.

Over equal times it is not, because more ground is covered at the faster pace. Half an hour at 4:00 is 7.5 km; half an hour at 6:00 is 5. The faster pace therefore counts for more of the total, and the true average — 4:48 — sits nearer the faster figure.

The rule that always works is total time divided by total distance. It reduces to the simple mean when the distances are equal and handles everything else correctly. Nothing in the units warns you which case you are in, which is why the safe habit is to compute it that way every time rather than to remember when the shortcut is allowed.

Where this bites in practice is any run measured by time rather than by distance — a fartlek session, a treadmill workout in intervals of minutes, a warm-up and cool-down bracketing a hard middle. Averaging the paces on those overstates them every time.

Minutes and seconds are not decimals

Converting a pace between kilometres and miles is a multiplication by 1.609344, and the trap is that a pace is written in minutes and seconds rather than as a number.

5:00 per kilometre times 1.609344 is 8.0467 minutes per mile. That is 8:02.8 — eight minutes and about three seconds — and not “8.05”, which is neither a time nor a pace. The 0.0467 of a minute is 2.8 seconds, and multiplying the minutes without re-expressing the remainder is the commonest slip in doing this by hand.

Common paces, both ways
Per kilometrePer mileSpeed
4:006:26.215.00 km/h
4:307:14.513.33 km/h
5:008:02.812.00 km/h
5:308:51.110.91 km/h
6:009:39.410.00 km/h
7:0011:15.98.57 km/h

A related detail worth knowing, because it produces impossible-looking output in a lot of tools: a pace of 3:59.6 rounds to 4:00, not “3:60”. The seconds field has to carry into the minutes when it rounds to sixty, and forgetting that is why pace calculators occasionally print times that cannot exist.

Twice the distance, more than twice the time

A marathon is 42.195 km and a half marathon 21.0975 — exactly twice, with no rounding. So at a fixed pace, the marathon time is exactly double the half time, and the calculator above says so.

Real marathon times are not double real half times, and the difference has nothing to do with the arithmetic. Pace degrades over distance, and by how much depends on training, fuelling, the course, the weather and the day.

Paces at some familiar targets
TargetPace neededSpeed
Marathon in 4:00:005:41 /km10.55 km/h
Half in 2:00:005:41 /km10.55 km/h
10 km in 50:005:00 /km12.00 km/h
5 km in 20:004:00 /km15.00 km/h

The first two rows need the identical pace, because the distance and the time halve together. They are not equally hard, and no amount of unit conversion says anything about that.

Which is why this page computes finish times and required paces, and does not predict a race time from a shorter one. Prediction models exist, they disagree with each other, and their disagreement is about physiology rather than about arithmetic — so a converter offering one would be presenting a contested estimate in the same voice as an exact conversion.

What the arithmetic will not tell you

Everything above is exact given its inputs. Four things sit outside it and are worth naming, because a clean number invites more confidence than it deserves.

Nobody holds one pace. A finish time computed from a pace is what would happen if that pace were held for the whole distance, which is not how a race goes even for people running a deliberate even split. It is a target, not a forecast.

Devices disagree with the ground. A GPS watch drifts under trees and among buildings, and typically over-reads distance — so its pace looks faster than a certified course would give. A treadmill has its own calibration, and belt speed under load is not always the number on the display.

Courses are measured generously on purpose. A certified course is measured along the shortest legal route and includes a small allowance so it can never be short. Running the racing line is nearly impossible in a crowd, so almost everyone covers slightly more than the nominal distance — which shows up as a pace a few seconds slower than the finish time implies.

Terrain and conditions are not in the units. Hills, heat, humidity and wind all move the pace a given effort produces, sometimes substantially, and none of them appears anywhere in a conversion. A pace is a measurement of what happened, not of how hard it was.

Related calculators

Other speed, distance and time tools:

Speedmph, km/h, m/s, ft/s and knots on exact factors, with the nautical mile behind the knot explained rather than assumed.
LengthMillimetres to miles on the exact 1959 factors, with the mil kept clearly apart from the millimetre — they differ 25-fold.
Time PercentageWork out what percentage one span of time is of another, or the percentage increase or decrease between an old and a new duration.
Time ZoneConvert a date and time between EST, IST, GMT, UTC, CET, PST, or any IANA time zone, with live daylight-saving handling and a multi-zone world clock view.
Fuel Economympg, L/100 km and km/L — US and UK mpg kept apart, and the reciprocal explained, since a better car has a LOWER L/100 km.
EnergyJoules, kilojoules, calories, food Calories, kWh, BTU and therms — with the two calories listed apart, since one is a thousand of the other.

More in Conversion, or browse all calculators.

Sources and methodology

The race distances are the World Athletics standards, and the marathon’s awkward 42.195 km is a historical accident rather than a design: it comes from the 1908 London course and was fixed as the standard in 1921, which is why it is a round number in neither system. The mile has been exactly 1609.344 m since 1959, so every pace conversion here is exact.

Conversion note

This converts pace and computes times at a pace held exactly — which is not what running is like. Nobody holds one pace for a marathon, and this page deliberately does not predict a race time from a shorter one: those models exist, they disagree with each other, and they depend on training history, the course, the weather and how the day goes in ways no formula carries. A finish time here is what would happen if the pace were held, not a forecast. Course measurement, GPS drift and treadmill calibration all introduce real differences between a device's pace and the ground truth — a watch reading 5:00 and a certified course rarely agree exactly. Nothing here is training or medical advice; pacing decisions, and whether a target is appropriate at all, belong with a coach and, where health is a factor, a clinician.

How we calculate · Found an error? email us

Authorship & verification

Written and maintained by , a business operator who builds spreadsheet-based calculators.

What's changed (10 updates)

Published 8 September 2026

  1. Published the Pace Converter: minutes per kilometre, minutes per mile, kilometres and miles per hour, with finish times for every standard race distance and the pace a target time requires.
  2. Establishes that pace is the reciprocal of speed and shows the consequence rather than the formula: the same one km/h step saves 50 seconds a kilometre at 8 km/h and only 10.5 at 18, which is part of why pace improvements get harder quite apart from anything physiological.
  3. Sets out the averaging trap and, unusually, the case where the naive method is RIGHT: over equal distances the simple mean of two paces is exact, while over equal times it is not, because more ground is covered at the faster pace.
  4. Gives the concrete figure -- half an hour at 4:00 and half an hour at 6:00 averages 4:48 per kilometre, not 5:00 -- and the rule that always works, total time divided by total distance.
  5. Names where that bites: any run measured by time rather than distance, which is most treadmill and interval work.
  6. Notes that minutes and seconds are not decimals, so 5:00 per kilometre is 8:02.8 per mile rather than 8.05, and that a pace of 3:59.6 must round to 4:00 rather than the impossible 3:60 -- a formatting carry the engine handles and the suite asserts directly.
  7. Records that a marathon is exactly twice a half marathon in distance, 42.195 against 21.0975 kilometres, so a four-hour marathon and a two-hour half need the identical 5:41 per kilometre while being nothing like equally hard.
  8. Declines to predict a race time from a shorter one, and says why: prediction models exist, they disagree with each other, and their disagreement is about physiology rather than arithmetic, so offering one would present a contested estimate in the same voice as an exact conversion.
  9. States the four things outside the arithmetic -- nobody holds one pace, GPS watches typically over-read distance, certified courses are measured along the shortest legal route so almost everyone runs slightly further, and terrain and weather move the pace a given effort produces.
  10. Verified by 55 automated cases, asserting that pace times speed is 3600 at every speed, that each additional km/h saves strictly less than the one before, that the naive mean is correct for equal distances and wrong for equal times, and that a segment supplying both a distance and a time is refused.

Add this calculator to your site

Responsive embed — and private: nothing your visitors type leaves their browser.