Pace calculator: time to pace per kilometre and mile
This form works without JavaScript: submit it and the server renders the result.
5K — Pace table
5 km · 3.1069 mi
| Finish time | Pace per kilometre | Pace per mile |
|---|---|---|
| 12:0025.0 km/h · 15.5 mph | 2:24 | 3:52 |
| 13:0023.1 km/h · 14.3 mph | 2:36 | 4:11 |
| 14:0021.4 km/h · 13.3 mph | 2:48 | 4:30 |
| 15:0020.0 km/h · 12.4 mph | 3:00 | 4:50 |
| 16:0018.8 km/h · 11.7 mph | 3:12 | 5:09 |
| 17:0017.6 km/h · 11.0 mph | 3:24 | 5:28 |
| 18:0016.7 km/h · 10.4 mph | 3:36 | 5:48 |
| 19:0015.8 km/h · 9.8 mph | 3:48 | 6:07 |
| 20:0015.0 km/h · 9.3 mph | 4:00 | 6:26 |
| 21:0014.3 km/h · 8.9 mph | 4:12 | 6:46 |
| 22:0013.6 km/h · 8.5 mph | 4:24 | 7:05 |
| 23:0013.0 km/h · 8.1 mph | 4:36 | 7:24 |
| 24:0012.5 km/h · 7.8 mph | 4:48 | 7:43 |
| 25:0012.0 km/h · 7.5 mph | 5:00 | 8:03 |
| 26:0011.5 km/h · 7.2 mph | 5:12 | 8:22 |
| 27:0011.1 km/h · 6.9 mph | 5:24 | 8:41 |
| 28:0010.7 km/h · 6.7 mph | 5:36 | 9:01 |
| 29:0010.3 km/h · 6.4 mph | 5:48 | 9:20 |
| 30:0010.0 km/h · 6.2 mph | 6:00 | 9:39 |
| 31:009.7 km/h · 6.0 mph | 6:12 | 9:59 |
| 32:009.4 km/h · 5.8 mph | 6:24 | 10:18 |
| 33:009.1 km/h · 5.6 mph | 6:36 | 10:37 |
| 34:008.8 km/h · 5.5 mph | 6:48 | 10:57 |
| 35:008.6 km/h · 5.3 mph | 7:00 | 11:16 |
| 36:008.3 km/h · 5.2 mph | 7:12 | 11:35 |
| 37:008.1 km/h · 5.0 mph | 7:24 | 11:55 |
| 38:007.9 km/h · 4.9 mph | 7:36 | 12:14 |
| 39:007.7 km/h · 4.8 mph | 7:48 | 12:33 |
| 40:007.5 km/h · 4.7 mph | 8:00 | 12:52 |
The calculator above converts a finish time into a pace, and shows you which target time that pace would reach. It takes the same two inputs in either direction — time and distance in, pace out — and it works with or without JavaScript: submit the form and the server renders the answer into the address.
Accepted time formats
| You type | It means |
|---|---|
3:30:00 |
3 hours 30 minutes |
3:30 |
3 minutes 30 seconds |
210 |
210 minutes |
21.5 |
21 minutes 30 seconds |
A single number is always minutes, not hours or seconds. That is the one convention worth remembering, because 210 meaning "210 minutes" is unambiguous but 3:30 meaning "three and a half hours" would not be.
Worked examples
A 3:30:00 marathon. 12600 seconds over 42.195 km is 298.6 s/km, which the table displays as 4:59 per kilometre and 8:01 per mile. That is the pace most marathon training plans mean by "goal pace", and it is also the pace that makes a negative split possible: running the first half at 4:59 leaves exactly the same average for the second.
A 20:00 5K. 1200 ÷ 5.000 = 240 s/km, exactly 4:00. Per mile it is 386.24 s, displayed as 6:26. Nothing is rounded before the division, which is why this one comes out exact.
A 1:45:00 half marathon. 6300 ÷ 21.0975 = 298.6 s/km — deliberately the same pace as the 3:30 marathon above, because 1:45:00 and 3:30:00 are the same pace at twice the distance.
What the target time tells you
Under the result you will see the tightest target time that finish reaches, for example "Inside sub-3:00 with 0:00 to spare". The boundary is inclusive: a 3:00:00 marathon is inside sub-3:00, a 3:00:01 is not. The full list of target times per distance is on each pace chart.
If the result is slower than every target shown, the note says so instead of silently showing the slowest one. That matters more than it sounds: a chart's top row is an editorial boundary, not a claim about what is achievable.
Why both units, always
Pace is the same number in two costumes, and readers arrive with one of them in mind. A toggle would either change the address (two addresses for one answer, which search engines read as duplicate pages) or depend on JavaScript. Showing both costs one column and removes a decision.
Related
- 5K pace chart, half marathon pace chart, marathon pace chart — every finish time for one distance.
- VDOT calculator — turn a result into training paces.
- Race time predictor — turn a result into equivalent times at other distances.
- Methodology — the rounding rules, in one place.
Why the two unit columns are computed separately
Both columns come from the same two inputs — your time and the metric distance — and each is rounded once when it is displayed. The site deliberately does not compute kilometres per mile and then convert: converting an already-rounded pace is how a value ends up one second away from the same calculation done directly. If you convert one column into the other by hand, expect to disagree with the other column in the last second now and then, because you rounded twice and this page rounded once.
Why is my pace 4:59 on one site and 5:00 here?
Because one of us rounded earlier. 4:59.5 rounds to 5:00; 4:59.4 rounds to 4:59. This site keeps milliseconds and rounds once, at the end. For a full explanation see methodology.
Should I run even pace or a negative split?
The calculator only tells you the average pace either strategy has to produce. Even pacing is the simplest way to hit a target because every mile is the same problem; a negative split means deliberately running slower than average early and faster than average late. Both are arithmetic; which suits you is a training question. This site does not build you a plan — it gives you the pace a target requires, and the training ranges derived from a published source, and leaves the plan to you.