Running Pace Calculator

Pace is the inverse of speed: how many minutes and seconds it takes you to cover one fixed unit of distance. Pace per mile is the standard in the US, UK road racing, and most American training plans, so an 8:00/mi pace means each mile takes 8 minutes flat. Pace per kilometer is the global track-and-field and European road-race standard, so a 5:00/km pace means each kilometer takes 5 minutes. The conversion is 1 mile = 1.609344 km, so 8:00/mi is roughly 4:58/km and 5:00/km is roughly 8:03/mi. Most GPS watches let you switch the display unit without changing the underlying measurement, which is why the calculator returns both numbers for every input combination.

They are descriptive labels distilled from common recreational-running training plans (Jack Daniels Running Formula, Pete Pfitzinger Advanced Marathoning, Hal Higdon's plans, McMillan Running Calculator), not a single official taxonomy. The bands here use per-mile thresholds: easy 10:00+ (aerobic base, the bulk of weekly mileage in an 80/20 polarized plan), moderate 8:00 to 10:00 (steady recreational running, marathon pace for most adults under 4:00), tempo 7:00 to 8:00 (lactate-threshold work, half-marathon pace for trained recreational runners), race 6:00 to 7:00 (5K to 10K race pace for serious amateurs), and elite under 6:00 (sub-elite to elite competition pace, requires sustained training around 60+ miles per week). The right label depends on age, fitness, and the race distance, so treat them as orientation rather than a fitness verdict.

Not very. Holding the same per-mile pace from a 5K all the way to 26.2 miles overstates real marathon performance by 25 to 45 percent for most runners, because endurance, fueling, and pacing discipline all degrade the longer the race goes. The Riegel formula (T2 = T1 * (D2/D1)^1.06), Daniels VDOT tables, and the McMillan calculator all apply a fatigue exponent to scale time non-linearly with distance: a 22:00 5K (about 7:05/mi) maps to roughly a 3:34 marathon (about 8:10/mi), not a flat 7:05/mi pace. Use the splits table in this calculator to translate a chosen pace into segment-by-segment finish times, then compare against your actual training long-run pace rather than your fastest 5K when planning a marathon.

GPS pace is real-time and noisy. Watches sample position every 1 to 5 seconds, compute pace over a tiny rolling window (often 5 to 30 seconds), and add filtering to smooth the readout. Tall buildings, tree cover, sharp turns, tunnels, and treadmill use all introduce errors of 3 to 8 percent on the displayed instant pace. The calculator computes pace as the simple ratio of total time to total distance, which is what your watch will eventually show as the average pace for the run after you stop the timer. If your watch reads 7:45/mi during a 5K but the calculator says 8:02/mi from your finish line time and the measured course distance, the calculator number is the one to trust. Tighten the gap by lap-pace fields, by re-measuring the course on a known track, or by enabling all-satellite mode (GPS plus GLONASS plus Galileo) on the watch.

Yes, and that is its primary use. Pick the target finish time for your race, switch the calculator to "Time from pace and distance" mode, and enter the target pace plus the race distance. The splits table then shows the cumulative time at each standard milestone inside the race (1 mile, 5K, 10K, half marathon for a marathon goal, for example) and the segment time between milestones. Print or save those numbers and check them against your watch at each split during the race. The classic mistake is going out 15 to 20 seconds per mile faster than goal pace in the first 5K because the legs feel fresh, then dying in the second half. A printed split sheet you actually look at every mile is the simplest, most underused pacing tool in road racing.