Pace Calculator
Calculate your running or walking pace per mile or kilometer. Perfect for training, race planning, and tracking fitness progress.
Reviewed by the Calcura editorial team · Last reviewed
- Question
- How do I calculate running or walking pace?
- Answer
- pace = time / distance. Run 5 miles in 45 minutes: pace = 45 / 5 = 9:00/mile. For km, pace = 45 / 8.05 ≈ 5:35/km. Going the other way, speed = distance / time. A 9:00/mile pace = 60 / 9 = 6.67 mph. To project a finish time, multiply your target pace by the race distance — a 9:00/mile pace runs a marathon (26.2 miles) in 3:55:48.
▸Show formula & caveatsHide formula & caveats
- Formula
pace = time / distance; speed = distance / time- Caveats
- Flat-course pace; real performance depends on elevation, heat, and fatigue.
- Treadmill pace reads differently from road pace; treadmills often auto-adjust at 1% incline.
- GPS watches have ±2–3% distance error in dense cities or under tree cover.
What This Calculator Does
This calculator converts a distance and elapsed time into pace (minutes per mile and minutes per kilometer) and speed (mph, km/h). It's the basic arithmetic behind every GPS watch and treadmill display — useful for planning race splits, projecting finish times, comparing training runs across unit systems, and figuring out what average pace you need to hold to hit a goal. It does not predict performance or account for elevation, weather, or fatigue — those require more sophisticated models (Daniels' VDOT, Jack Daniels' running calculator, or lab VO₂max testing).
When To Use This Calculator
Planning race-day splits
Goal: 1:45 half marathon (13.1 miles). Target pace is 1:45 ÷ 13.1 ≈ 8:01/mi. Running your first mile at 7:30 probably means you'll blow up around mile 9; this calculator lets you verify target pace before you toe the line.
Projecting a finish time from training pace
If you've comfortably held 9:15/mi on long runs, plugging 26.2 miles × 9:15 pace returns a ~4:02 marathon. Worth comparing against published finish-time predictors (Riegel formula) before committing to a time goal.
Converting treadmill speed to outdoor pace
6.5 mph on a treadmill: 60 / 6.5 ≈ 9:14 min/mile. Useful when a workout calls for '8:30 tempo miles' and you need to know what number to dial in.
Comparing races across metric and imperial
A 22-minute 5K is a 7:05/mile pace and a 4:24/km pace. Makes it easy to compare your performance against a friend who races European events in km.
How It Works
The calculator sums your input time into total seconds, divides by the distance to get pace (seconds per unit), and formats the result as MM:SS. Speed is distance divided by time in hours. Unit conversions use the exact factor 1 mile = 1.609344 km. Pace and speed are inverses: at 8:00 min/mile, speed is 60/8 = 7.5 mph. Nothing in the calculator adjusts for elevation gain, surface, or environmental conditions — it's strictly time-over-distance arithmetic.
Formula
Pace = Total seconds / Distance (formatted as MM:SS per unit)
Speed = Distance / (Total seconds / 3600)Real-World Example
Scenario
Priya just finished a 10K (6.214 miles) in 52:34 and wants to know her pace per mile and per kilometer, plus an idea of what pace she'd need for a sub-50:00 next time.
Calculation
Total time: 52:34 = 3,154 seconds Pace per mile: 3,154 / 6.214 ≈ 507.5 sec ≈ 8:28/mi Pace per km: 3,154 / 10 ≈ 315.4 sec ≈ 5:15/km Speed: 10 km ÷ (3154/3600 hr) ≈ 11.41 km/h (7.09 mph) Sub-50:00 target: 3,000 / 10 = 300 sec/km ≈ 5:00/km (8:03/mi)
Result
Priya ran at 8:28/mi. To break 50 minutes she needs to hold 5:00/km (8:03/mi) — about 25 seconds per mile faster. A feasible 3–6 month target with focused interval and tempo training; a 2-week jump would be aggressive.
Common Mistakes to Avoid
Mistake: Treating pace as a predictor across all distances
Solution: A 22:00 5K does not imply a 1:35:00 half marathon. Endurance falls off as distance increases; use the Riegel formula (T2 = T1 × (D2/D1)^1.06) or a published race-time calculator for distance projections.
Mistake: Comparing treadmill pace directly to outdoor pace
Solution: Treadmill belts reduce wind resistance and provide a smoother surface, making treadmill pace effectively easier at the same speed. Most coaches add 1–2% incline to approximate outdoor effort at the same pace.
Mistake: Not accounting for elevation
Solution: A hilly course adds ~10–30 seconds per mile per 100 feet of elevation gain, depending on grade. A flat-course pace goal won't translate to a mountain race — build elevation adjustments into your pacing strategy.
Mistake: Using GPS pace as ground truth on short intervals
Solution: Consumer GPS watches have ~5–10 meter error; on a 400m interval that's 2–3% noise, and lap-by-lap pace jumps are mostly GPS artifacts rather than real pace changes. Use a track or measured course for precision interval work.
Pace Calculator vs. Related Tools
Calorie Calculator
Once you know pace and duration, combine with body weight to estimate calories burned — useful for training nutrition planning.
BMI Calculator
Body composition context for interpreting training paces. Useful when comparing paces across athletes of very different sizes.
One-Rep Max Calculator
For runners doing strength work — prescribing lifting loads by percentage of max, complementing aerobic pace-based training.
When This Isn't the Right Tool
Race-time prediction across distances
Use instead: Use the Riegel equation or published tools like Jack Daniels' VDOT tables or McMillan's running calculator, which account for the nonlinear relationship between distance and pace.
Heart-rate-based or effort-based training
Use instead: For Zone 2 / Maffetone / polarized training, pace is a lagging indicator of effort. Use a heart-rate monitor or rating of perceived exertion (RPE) and let pace fall where it falls.
Elevation-adjusted pace
Use instead: Strava's GAP (Grade Adjusted Pace) and similar algorithms normalize effort for terrain. For hilly training or mountain races, use those rather than raw pace.
Swimming or cycling pace
Use instead: Swim pace is typically per 100m; cycling uses speed (km/h or mph) or power (watts) rather than pace. Different tools and conventions apply.
How to Verify This Calculation
Cross-check on a Garmin, Strava, or Apple Health activity. A 5K in 25:00 should always return 8:03/mi and 5:00/km, regardless of which tool computes it. Differences >2 seconds usually come from rounding conventions (some tools truncate seconds, others round).
Sources
- USATF — Certified Course Measurement Standards — USA Track & Field's course certification database — the canonical source for accurate race-distance measurements.
- Jack Daniels — Daniels' Running Formula — Standard reference for pace-based training zones, VDOT scores, and race-time equivalents.
- Pete Riegel — Time Predicting Formula — The Riegel formula (T2 = T1 × (D2/D1)^1.06) is the standard for projecting race times across distances.
Reviewed by the Calcura editorial team · Last reviewed