Transparent method
The formula
Worked example
Example inputs
How to interpret the result
A single pace reading says little in isolation, since pace naturally varies with terrain, weather and effort level on any given day, but a pace trend measured across comparable routes and conditions over weeks reveals genuine fitness change in a way that no single run's number can show on its own.
Before you rely on it
What to check
Compare pace trends across genuinely comparable routes and conditions, not a single run against a different route or a very different weather day.
The common error
Where people go wrong with running pace calculator
Judging fitness progress from one run's pace compared against a different run on a different route or in different weather. Only a trend across comparable conditions actually reveals whether fitness is genuinely improving.
Sensitivity evidence
How distance changes the pace (minutes per mile)
| Distance | Pace (minutes per mile) | Speed (mph) |
|---|---|---|
| 2.5 | 11.2 | 5.4 |
| 2.8 | 10 | 6 |
| 3.1worked example | 9 | 6.6 |
| 3.4 | 8.2 | 7.3 |
| 3.7 | 7.6 | 7.9 |
Every input, tested
Which input moves the pace (minutes per mile) most
| Input | Tested from | To | Pace (minutes per mile) at each end | Swing |
|---|---|---|---|---|
| Time | 25 | 31 | 8.1 to 10 | 1.9 (21%) |
| Distance | 2.8 | 3.4 | 10 to 8.2 | 1.8 (20%) |
Two variables at once
Pace (minutes per mile) by distance and time
| Distance \ Time | 22 | 28 | 34 |
|---|---|---|---|
| 2.5 | 8.8 | 11.2 | 13.6 |
| 2.8 | 7.9 | 10 | 12.1 |
| 3.1 | 7.1 | 9 | 11 |
| 3.4 | 6.5 | 8.2 | 10 |
| 3.7 | 5.9 | 7.6 | 9.2 |
Step by step
The worked example, input by input
| Input | Value used | What it means |
|---|---|---|
| Distance | 3.1 | Distance covered, in miles. |
| Time | 28 | Total time, in minutes. |
| Pace (minutes per mile) | 9 | |
| Speed (mph) | 6.6 | |
Inputs, definitions and assumptions
Distance
Distance covered, in miles.
Time
Total time, in minutes.
Where the inputs come from
Enter the distance in miles and the time in minutes, which you can take from a GPS watch, a race result or a treadmill. For a run with pauses, use moving time. Pace is minutes per mile, and speed is miles per hour. If you have kilometers, convert with the unit conversion pages. Use a flat course for a benchmark, since hills and wind change pace.
When the result stops applying
Pace varies with terrain, weather, fatigue and race distance, and you cannot simply extrapolate a 5K pace to a marathon, since the pace slows as distance grows. GPS devices can misreport distance by a small percentage. The tool computes an average and hides fluctuations within the run.
What to compare it with
See heart rate targets on the target heart rate and max heart rate pages, fitness on the VO2 max calculator and energy use on the calories burned page. The steps to miles calculator converts step counts. The time duration calculator helps with race clocks.
People also ask
Frequently asked questions
How do I convert pace to speed?
Divide 60 by the pace in minutes per mile. A 9-minute mile is about 6.7 miles per hour.
Can I predict my marathon time from my 5K?
Roughly, but not by simply scaling the pace, because endurance matters more at longer distances. Race predictors adjust for it, and training determines the result.
What is a good running pace?
It depends on age, fitness and goal. Many recreational runners run between 9 and 12 minutes per mile, and pace improves with consistent training.