Running guide
Running Pace Versus Speed
Understand pace and speed, convert mile and kilometer units, and see how a chosen finish time becomes cumulative race checkpoints.
Ready to work on this now? open race pace planner.
Pace describes time per distance
Running pace answers: how long does one unit of distance take? A pace might be written as 8:00 per mile or 5:00 per kilometer. A smaller time per unit represents a faster pace because each mile or kilometer takes less time.
Pace is convenient for planning race checkpoints. If the pace is even, cumulative time can be calculated at each mile or kilometer and reconciled to the chosen finish time.
Speed describes distance per time
Speed turns the relationship around: how much distance is covered in an hour or another unit of time? A runner moving at 12 kilometers per hour covers one kilometer in five minutes, so that speed corresponds to a 5:00-per-kilometer pace.
The two measures describe the same movement from different directions. Pace is time divided by distance. Speed is distance divided by time. Keep the units attached to the number so the result is not ambiguous.
Miles and kilometers use different unit lengths
A per-mile pace and a per-kilometer pace cannot be compared as if the units were the same. NIST lists one international mile as exactly 1.609344 kilometers. A mile therefore takes longer to cover than a kilometer at the same speed.
Convert using the complete value before rounding the displayed pace. Repeatedly adding rounded split times can create a final checkpoint that no longer matches the selected finish time.
Worked example
A 50-minute 10K goal
Ten kilometers completed in 50 minutes produces an even pace of 5:00 per kilometer. The equivalent pace is about 8:02.8 per mile. A display may round that to 8:03 per mile, but the underlying calculation should continue to use the complete race time and authoritative distance.
At even kilometer checkpoints, the cumulative plan is straightforward:
- 2 km: 10:00
- 5 km: 25:00
- 8 km: 40:00
- 10 km: 50:00
If the same race is shown in miles, the final row is a partial mile because 10 kilometers is approximately 6.214 miles. The final partial segment must reconcile to 50:00 rather than pretending the race ends at a whole mile.
Finish time, pace, and splits are connected
When distance and finish time are known, required average pace is total time divided by distance. When distance and pace are known, projected finish time is pace multiplied by distance. Cumulative splits apply that relationship from the start to successive checkpoints.
A reliable split table calculates checkpoints from the complete plan and fixes the last row to the selected total. This avoids a small rounding difference at every row becoming a larger discrepancy at the finish.
Read displayed rounding as a presentation choice
A calculator may show pace to the nearest second even though the underlying division produces a fraction of a second. That display is useful for reading, but multiplying the rounded number back across the race can differ slightly from the chosen finish time. The authoritative values are the selected race distance and the complete total time.
Cumulative checkpoints should therefore be calculated from the complete plan, not by repeatedly adding the displayed rounded pace. The last checkpoint can then reconcile exactly even when earlier rows are shown in whole seconds.
Keep race distance separate from checkpoint units
A 5K or 10K can still be displayed with mile checkpoints, and a half marathon or marathon can be displayed with kilometer checkpoints. Changing the checkpoint unit does not change the race distance or finish goal; it changes where intermediate rows appear.
This distinction matters near the finish. When the race distance is not a whole number of the selected checkpoint units, the final row represents only the remaining fraction. Omitting that partial row would stop the table before the actual finish.
What the math does not decide
A pace calculation does not determine whether a goal is appropriate for a particular runner. It does not assess training, health, terrain, elevation, surface, weather, aid stations, crowding, or day-of-race conditions. It also does not require a runner to hold exactly even pace.
Use the Race Pace & Split Planner after choosing a goal or expected pace through an appropriate process. Treat the result as timing and unit-conversion information, not coaching, medical advice, or a performance prediction.