Running Pace Calculator
Every runner eventually needs to do this math, whether they're planning a race strategy, checking if a training run hit its target zone, or just curious what pace it would take to hit a personal best. Pace is simply the relationship between distance and time, but juggling it in your head mid-run — or converting between minutes-per-mile and minutes-per-kilometer when a race uses a different unit than your training log — gets error-prone fast. This calculator handles all three directions of that relationship: given a distance and a finish time, it finds your pace; given a pace and a distance, it finds your finish time; and given a pace and a time budget, it finds how far you'd go. Whether you're pacing a 5K, plotting splits for a marathon, or just converting a treadmill's pace display into something that matches your GPS watch, this covers the conversion in one place.
How the Running Pace formula works
Pace, time, and distance are related by simple division and multiplication, depending on which value you're solving for:
Pace (min/mile or min/km) = Total time / Distance Finish time = Pace × Distance Distance = Total time / Pace
Step-by-step calculation
- To find pace: divide your total time (converted to minutes) by the distance covered.
- To find finish time: multiply your target pace (minutes per mile or km) by the distance you plan to run.
- To find distance: divide the total time you have available by your target pace.
- Convert between miles and kilometers as needed using the standard 1 mile = 1.60934 km relationship, since pace per mile and pace per kilometer aren't the same number.
Worked example
A runner completes a 10K (6.2 miles) in 52 minutes: Pace = 52 / 6.2 ≈ 8.39 minutes per mile, or about 8 minutes 23 seconds per mile. In kilometers, that's 52 / 10 = 5.2 minutes per km, or 5 minutes 12 seconds per km. Using that same pace, a full marathon (26.2 miles) would project to about 219.7 minutes, or roughly 3 hours 40 minutes.
Why pace strategy matters more than raw speed for race performance
Experienced racers and coaches consistently point to even pacing — or a slight negative split, where the second half of a race is run marginally faster than the first — as the most reliable strategy for a strong finish time, and this calculator is often used specifically to plan that out in advance. Starting too fast is one of the most common mistakes across every distance from the 5K to the marathon: adrenaline and a fresh field of runners around you at the start line make an aggressive early pace feel deceptively easy, but the accumulated fatigue tends to show up hard in the race's second half, often costing far more time than was gained early on. Working out your target pace ahead of time, and then checking splits against it during the race, is a straightforward way to avoid that trap.
Pace also isn't a single number that should apply to every run in a training plan — different training goals call for deliberately different paces. Easy or recovery runs are typically run well slower than race pace, often by a minute or more per mile, to build aerobic base without accumulating excess fatigue. Tempo runs sit closer to race pace or slightly slower, training the body to sustain a hard-but-manageable effort. Interval and speed workouts are run significantly faster than race pace for short bursts, developing top-end speed and running economy. Calculating exact pace targets for each of these workout types — rather than just running by feel — is one of the more common reasons runners reach for a pace calculator throughout a training block, not just on race day.
One practical note worth flagging: pace on a flat, controlled surface (like a track or treadmill) doesn't translate directly to pace on hilly or technical trail terrain, where effort level is a better guide than a fixed time target. Similarly, altitude, heat, and humidity can meaningfully slow achievable pace independent of fitness — so if a calculated 'goal pace' feels unexpectedly hard under those conditions, that's often the environment, not a fitness problem.
Frequently asked questions
How do I convert pace from minutes per mile to minutes per kilometer?
Multiply your minutes-per-mile pace by 0.62137 (or divide by 1.60934) to get minutes per kilometer, since a kilometer is shorter than a mile and therefore takes less time to cover at the same speed.
What's a 'negative split' and why do coaches recommend it?
A negative split means running the second half of a race faster than the first half. It's widely recommended because starting conservatively preserves energy for a strong finish, while starting too aggressively often leads to significant slowdown later in the race that costs more time than the fast start gained.
How accurate is a treadmill's pace display compared to outdoor pace?
Treadmill pace can differ from outdoor GPS-measured pace due to calibration differences between machines, and because treadmill running (with no wind resistance and a moving belt) feels physiologically different from the same pace outdoors — many runners find a small percentage incline (often 1%) helps treadmill effort better match outdoor effort at the same pace.
What pace should I run for an easy recovery run?
A common guideline is roughly 1 to 2 minutes per mile slower than current 5K race pace, though the right number varies by individual fitness and training philosophy — the goal is a genuinely comfortable, conversational effort, not a specific number to hit exactly.