Pace Calculator
This free pace calculator converts between running pace, total time, and distance. Choose what you want to solve for, enter the other two values, and the result updates instantly. Nothing you enter is sent anywhere or stored.
How to Use It
- Choose what to solve for: Pace, Time, or Distance.
- Choose Miles or Kilometers.
- Enter the other two values. The result updates instantly, no submit button.
How It Works
Pace, time, and distance are three ways of describing the same run, and any two of them determine the third. Pace is just time divided by distance, so once you know any two, simple division or multiplication gets the third.
Formulas
pace = time ÷ distance
time = pace × distance
distance = time ÷ pace
A worked example: running 6 miles in 48 minutes averages an 8:00 per mile pace (48 minutes divided by 6 miles). Holding that same 8:00 per mile pace for a full 26.2 mile marathon would produce a finish time of 3:29:36 (8 minutes times 26.2 miles). Working backward, someone with 1 hour and 30 minutes to spend at a 7:30 per mile pace could cover 12 miles (90 minutes divided by 7.5 minutes per mile).
Everything runs client-side in your browser. Nothing you enter is sent anywhere or stored.
Frequently Asked Questions
What does "pace" mean, and how is it different from speed?
Pace is time per unit of distance, usually written as minutes and seconds per mile or per kilometer, like 8:00 per mile. Speed is the inverse: distance per unit of time, like miles per hour. Runners generally think in pace because race splits, training plans, and mile markers are all written that way, a pace tells you directly how long each mile will take rather than requiring a conversion first.
How do I turn a finish time goal into a target pace?
Set "Solve for" to Pace, enter the race distance, and enter your goal finish time. The result is the average pace per mile or kilometer you would need to hold for the whole distance to finish in that time.
Why do the minutes and seconds fields cap at 59?
Minutes and seconds are sub-parts of a larger time value, and a value of 60 or more in either one is really a whole extra minute or hour that belongs in the field above it. Keeping each sub-field to 0 through 59 avoids the same duration being enterable two different ways.
Can you give a real-world example?
Planning a marathon around a specific finish time is a common one. Set "Solve for" to Time, enter 26.2 miles as the distance, and enter your target pace to see the finish time that pace would produce, or set "Solve for" to Pace and enter your goal time directly to see the pace you would need to hold.