Running Pace Calculator
Running Pace Calculator
The Running Pace Calculator converts any distance and finish time into a training pace, expressed either as minutes per kilometer (min/km) or minutes per mile (min/mile), and into a speed in km/h or mph. Pace is the single most useful number a runner can track: it turns vague goals like "run faster" into a concrete target you can train toward, week after week.
Whether you are preparing for your first 5K, chasing a sub-4-hour marathon, or simply trying to hold a steady effort on easy days, knowing your pace removes guesswork. A runner who knows they average 5:30 min/km can plan interval workouts, tempo runs, and long slow distance (LSD) sessions around that number. Without a pace reference, runners drift: easy days become too hard, and hard days become too easy, blunting fitness gains.
This calculator handles both metric and imperial inputs. Enter a distance in kilometers or miles and the time it took, and it returns your average pace, your average speed, and the original total time. You can flip the pace unit at any time without re-entering data, which is especially handy when following a training plan written in miles but you prefer to think in kilometers.
Beyond one-off conversions, the tool is the foundation of every structured running plan. Coaches express workouts as paces — "6 × 800 m at 4:15 min/km with 2-minute jog recovery" — and the only way to hold those targets is to know your current pace cold. Recreational runners benefit just as much: a steady easy-day pace protects aerobic base building, while a controlled tempo pace drives the lactate threshold upward. The calculator bridges the gap between a stopwatch reading and a training stimulus.
Using the calculator takes three steps: enter the distance and its unit, enter the total time split into hours, minutes, and seconds, and choose whether you want pace shown per kilometer or per mile. The calculation is instant.
Example 1 — a 5K parkrun. You ran 5 km in 25 minutes exactly. Enter distance 5, unit km, 0 hours, 25 minutes, 0 seconds. The calculator returns a pace of 5:00 min/km and a speed of 12.00 km/h. That is a common benchmark: sub-25 for 5K is a goal for many recreational runners. Compare this against your previous parkrun to see whether your aerobic engine is improving week over week.
Example 2 — a 10-mile long run. You covered 10 miles in 1 hour 35 minutes. Enter distance 10, unit miles, 1 hour, 35 minutes, 0 seconds. Pace comes out to 9:30 min/mile (5:54 min/km equivalent). The mile-based pace is what most U.S. training plans quote, so this view is directly usable. If your plan instead prescribes a 9:00 min/mile long-run pace, you can immediately see that you ran 30 seconds per mile slower than prescribed and adjust next week.
Example 3 — a half marathon from a recent race. Suppose you finished a half marathon (21.0975 km) in 1:58:30. Enter distance 21.0975, unit km, 1 hour, 58 minutes, 30 seconds. The calculator returns a pace of 5:37 min/km and a speed of 10.69 km/h. That single number now becomes the anchor for your next training block — your easy days should sit near 6:50–7:10 min/km and your tempo days near 5:50–6:00 min/km.
Example 4 — an edge case. A distance of 0 or a time of 0 returns no result, because pace is undefined when you have not actually moved. Very short distances (a 100 m sprint) produce very fast paces (under 0:20 min/km) that are mathematically correct but not representative of sustainable running; treat sprint paces separately from endurance pace. Similarly, an extremely long time over a short distance (a walk broken into many stops) yields a slow pace that reflects elapsed clock, not moving effort — use moving time, not total elapsed time, for honest training data.
Unit note. Kilometers and miles use a fixed conversion: 1 mile = 1.609344 km. The calculator applies this exactly, so a 6:00 min/mile effort equals 3:44 min/km (since 6:00 ÷ 1.609344 ≈ 3:44). The reverse is just as useful: a 4:00 min/km threshold effort equals 6:26 min/mile, a number many imperial-plan runners memorize for track workouts.
Pace is distance divided into time. If total time is measured in seconds and distance in a single unit, the average pace per that unit is:
The calculator works in seconds internally to avoid rounding errors, then formats the result as minutes:seconds. Speed is the inverse relationship, scaled to an hour:
Manual check. For a 10 km run finished in 50:00, total seconds = 3000. Pace per km = 3000 ÷ 10 = 300 seconds = 5:00 min/km. Speed = (10 ÷ 3000) × 3600 = 12.0 km/h. Both match the calculator. To convert a min/km pace to min/mile, multiply by 1.609344: 5:00 min/km × 1.609344 = 8:03 min/mile.
The table below shows common race distances and the pace required to hit round finish times. Use it to set realistic targets.
| Distance | Finish 20:00/mi | Finish 9:00/mi | Finish 8:00/mi | Finish 7:00/mi |
|---|---|---|---|---|
| 5 km | 32:11 | 27:58 | 24:51 | 21:43 |
| 10 km | 1:04:22 | 55:56 | 49:43 | 43:27 |
| Half marathon | 2:23:30 | 2:04:48 | 1:50:58 | 1:37:09 |
| Marathon | 4:47:00 | 4:09:36 | 3:41:56 | 3:14:18 |
Distances in miles shown for pace reference; 5 km ≈ 3.11 mi, 10 km ≈ 6.21 mi, half ≈ 13.1 mi, marathon ≈ 26.2 mi.
A second view, in min/km, for metric training plans:
| Target pace (min/km) | 5 km | 10 km | Half marathon | Marathon |
|---|---|---|---|---|
| 4:00 | 20:00 | 40:00 | 1:24:48 | 2:49:36 |
| 5:00 | 25:00 | 50:00 | 1:51:00 | 3:42:00 |
| 6:00 | 30:00 | 1:00:00 | 2:13:12 | 4:25:12 |
| 7:00 | 35:00 | 1:10:00 | 2:35:24 | 5:10:24 |
These tables assume even splitting (same pace throughout). Real races are rarely perfectly even, but even-split pacing is the most efficient way to run a personal best. They also assume a flat, sea-level course in mild weather; heat above 20°C, steep grades, or altitude each add several seconds per kilometer that the reference numbers do not capture.
A third view, useful for interval design, maps repeat distance to the total time at a target pace:
| Repeat distance | Pace 4:00/km | Pace 5:00/km | Pace 6:00/km |
|---|---|---|---|
| 400 m | 1:36 | 2:00 | 2:24 |
| 800 m | 3:12 | 4:00 | 4:48 |
| 1000 m | 4:00 | 5:00 | 6:00 |
| 1600 m (1 mile) | 6:24 | 8:00 | 9:36 |
Coaches use this to call out splits mid-workout: "hold 2:00 per 800" is far easier to track live than "hold 4:00 min/km." Converting your prescribed pace to a repeat time once, before the session, removes guesswork on the track.
- Train by pace zones, not feel alone. Easy runs should sit 1:00–1:30 min/km slower than your threshold pace. The calculator helps you verify you are actually recovering.
- Use tempo pace for fitness. A common rule: tempo pace is about the pace you could hold for 60 minutes — roughly 25–30 seconds per km slower than 5K race pace.
- Account for hills. Pace on a steep climb is not comparable to flat pace. Use heart rate or perceived effort on terrain days and reserve the calculator for flat or treadmill efforts.
- Convert plans cleanly. If your plan is in miles and your watch is in km, compute the equivalent once with this calculator and write both numbers on your plan.
- Warm up before time trials. A cold 5K produces a slower pace than a properly warmed-up one; always jog 10–15 minutes first.
- Don't over-index on one run. Pace varies with heat, fatigue, and shoes. Track it as a rolling average, not a single session.
- Reverse-engineer workouts. Enter a target repeat distance and a known goal pace to get the exact split time to hit, then set your watch lap alerts to that number.
- Use speed for cross-training context. The km/h or mph figure lets you compare a run with a bike, rowing, or swimming effort, which is useful when balancing weekly cardio volume across modalities. If you track pool sessions, the Pool Lap Calculator converts total distance and time into a per-lap pace you can line up against your running pace.
Pace is an average. It hides positive splits (slowing in the second half), negative splits (speeding up), and the effort distribution across hills and flats. For interval work, calculate each repeat separately rather than averaging the whole session. The calculator also assumes a constant conversion factor between miles and kilometers and does not model wind, altitude, or surface — all of which shift real-world pace by several seconds per kilometer.
What is a good running pace for a beginner?
Most new runners settle around 6:30–8:00 min/km (10:30–13:00 min/mile) on easy runs. Race pace for a first 5K is often 7:00–8:00 min/km. Consistency matters more than speed early on.
How do I convert min/km to min/mile?
Multiply your min/km pace by 1.609344. For example, 5:00 min/km equals 8:03 min/mile. This calculator does the conversion automatically when you switch the pace unit.
Why is my watch pace different from this calculator?
GPS watches estimate pace per second from satellite noise and can swing by 10–20 seconds per km. A calculator using your known total time and measured course distance is more accurate for post-run analysis.
What pace should my long run be?
Typically 60–90 seconds per km slower than marathon goal pace, or about 1:00–1:30 min/km slower than threshold pace. The aim is aerobic development without accumulating fatigue.
Is a faster pace always better?
No. Running every session fast raises injury risk and blunts adaptation. Most weekly volume should be at easy pace; only 20% at moderate-to-hard pace.
How accurate is the mile/km conversion?
The factor 1.609344 km per mile is exact by definition. Inaccuracy comes only from rounding your entered time or distance.
Can I use this for walking?
Yes. Walking paces (10:00–15:00 min/km) compute identically; just enter your walk distance and time.
Does elevation change my pace?
Yes. Expect to slow roughly 5–10 seconds per km per 1% of grade. The calculator shows flat-equivalent pace; adjust mentally for hills.
What is threshold pace?
The hardest pace you could sustain for about 60 minutes — roughly 10K race pace plus 15–20 seconds per km. It is the key driver of endurance fitness.
How do I predict race time from training pace?
Use the reference tables above, or enter a recent training pace and a target distance to estimate finish time. Then validate with a shorter tune-up race.
Last updated: July 19, 2026
UnByte — Independent Software Engineering
Every calculator references authoritative sources — Editorial policy