Running Pace Calculator
Calculate your running pace per mile (or per kilometer) given total time and distance covered. Use it to track training-run efficiency, set race goal paces, and compare your current performance against benchmark times for 5K, 10K, half-marathon, or marathon distances.
Last updated: May 2026
Compare with similar
About this calculator
The formula converts total elapsed time and distance into a pace expressed as minutes and seconds per mile (or per kilometer depending on unit selection). The internal math: total seconds = hours × 3600 + minutes × 60 + seconds; if input is kilometers, convert to miles by multiplying by 0.621371; then pace_per_mile_seconds = total seconds ÷ distance in miles; final pace = floor(pace_seconds / 60) minutes + (pace_seconds % 60) seconds, formatted as "mm:ss". Pace is the reciprocal of speed — slower pace means slower running. Common pace benchmarks for fit runners (per mile): elite marathon pace ~4:30–5:00; sub-3-hour marathon pace 6:52; sub-4-hour marathon pace 9:09; couch-to-5K finishing pace 12:00–14:00. Edge cases: zero distance produces division by zero; very short distances (under 1 mile) produce paces that can be wildly fast or slow depending on negative or positive splits. For comparing performances across runs, use pace rather than total time because distances differ. Race-specific paces scale with distance: a runner who can hold 7:00/mile for a 5K typically holds 7:20/mile for 10K, 7:45/mile for half-marathon, and 8:15/mile for full marathon — the longer the distance, the slower the sustainable pace. Heart-rate-zone training is another useful framework: zones 1-2 (recovery, easy) are typically 60–90 seconds/mile slower than your race pace; zones 4-5 (threshold, VO2 max) are 0–30 seconds faster.
How to use
Example 1 — 5K run. You completed a 3.1-mile training run in 0 hours, 23 minutes, 45 seconds. Enter 3.1 for Distance, 0 for Hours, 23 for Minutes, 45 for Seconds, and miles for Unit. Total seconds = 0 + 1380 + 45 = 1,425 seconds. Pace per mile = 1,425 / 3.1 = 459.7 seconds = 7 minutes 39.7 seconds, displayed as 7:40 per mile. ✓ A 7:40 mile pace for 5K is solid recreational-runner performance — extrapolating to longer distances, you'd expect roughly 8:00–8:10 pace for 10K, 8:30 for half-marathon, 9:00–9:15 for full marathon (with appropriate training). Example 2 — Long training run. 8 miles in 1 hour, 12 minutes, 30 seconds. Enter 8, 1, 12, 30, and miles. Total seconds = 3600 + 720 + 30 = 4,350. Pace per mile = 4,350 / 8 = 543.75 seconds = 9:03.75, displayed as 9:04 per mile. ✓ A 9:04 pace on an 8-mile training run is consistent with someone targeting a 4:00 marathon (which requires 9:09 race pace) — long runs are typically run 30–60 seconds slower than race pace to build endurance without taxing recovery, so this pace is appropriate for marathon training in the 4:00–4:15 finish-time range.
Frequently asked questions
How do I convert pace per mile to pace per kilometer?
Pace per kilometer = pace per mile ÷ 1.609344. So 8:00/mile = 4:58/km; 7:00/mile = 4:21/km; 10:00/mile = 6:13/km. Going the other direction, pace per mile = pace per km × 1.609344. The conversion preserves the time/distance relationship; whether you think in miles or kilometers is mostly geographic preference (US runs in miles, most of the rest of the world in kilometers) and convention (5K and 10K races worldwide use km; marathon distance is always quoted as 26.2 miles or 42.195 km). Common pace equivalents: 5:00/km = 8:03/mile; 6:00/km = 9:39/mile; 4:00/km = 6:26/mile; 4:30/km = 7:14/mile. Most modern GPS watches show both simultaneously, so you don't need mental conversion during runs.
What pace should I run for my goal race?
Use pace equivalency tables (McMillan Running Calculator, VDOT calculator from Jack Daniels, Greg Maffetone's 180 formula) or your race-distance training. Rough scaling: if you can run a 5K at X pace, expect 10K at X + 20-30 sec/mile, half-marathon at X + 45-60 sec/mile, full marathon at X + 75-90 sec/mile (with proper marathon training). Examples: 7:00/mile 5K → 7:25/mile 10K → 7:55/mile half → 8:30/mile marathon. Important: marathon pace is harder to predict than shorter races because it depends heavily on endurance training, fueling strategy, and pacing discipline. Negative splitting (second half faster than first) is the standard race strategy — start 5-10 seconds slower than goal pace for the first 5K, gradually settle into goal pace, then push slightly in the final miles if energy allows. For most runners, going out too fast in the first 5K is the single biggest cause of marathon disappointment.
Why does my pace feel slower at the end of a long run?
Several physiological reasons. Glycogen depletion: muscles store carbohydrate as glycogen, and after 90+ minutes of moderate running, glycogen stores deplete, forcing the body to shift toward less efficient fat oxidation, which feels harder for the same actual pace. Dehydration: even 2-3% body-weight fluid loss measurably impacts pace and perceived effort. Heat accumulation: core temperature rises during sustained running, especially in warmer conditions, forcing the cardiovascular system to do double duty cooling and moving. Form deterioration: as muscles tire, biomechanics change — stride shortens, cadence may decrease, posture worsens, all of which increase effort per stride. Mental fatigue: maintaining focused pacing over 1-3+ hours is genuinely hard, and concentration lapses lead to pace drift. For training, run "easy" pace (Zone 2 heart rate) for most miles and reserve race pace for specific workouts; this builds endurance without burning out. For race day, fueling (gels, sports drink) every 30-45 minutes helps maintain glycogen and electrolyte balance.
What are the most common mistakes people make using pace?
The biggest is running every workout at "race pace" or near it — most training should be easy (60-90 sec/mile slower than race pace) to build aerobic capacity without overtraining. Top distance runners spend 80%+ of training miles at easy pace. The second is comparing pace across different conditions without normalizing for hills, heat, wind, surface (track vs. trail), and altitude; the same pace effort produces different watch times in different conditions. The third is using GPS watch pace as the only metric; rate of perceived exertion (RPE) and heart rate are more reliable indicators of effort, especially in changing weather. The fourth is starting races too fast; the dopamine of feeling "easy" in the first 5K consistently leads to suffering in the final 10K. The fifth is comparing your pace to others on Strava without considering they may be in a different training phase, age group, or experience level. Finally, many runners obsess over pace optimization while ignoring strength training, mobility, and recovery — which produce larger gains than pace tweaking after a certain point.
When should I not use pace as a training metric?
Skip pace as the primary metric for easy / recovery runs — use heart rate or perceived exertion (RPE 4-6 out of 10) instead, since easy effort produces different paces on different days based on fatigue, weather, and terrain. It is the wrong tool for hill workouts or trail running where pace varies dramatically with grade and surface; use effort, time on trail, or vertical gain instead. Do not rely on it during interval training (track repeats, tempo intervals); for those, focus on hitting target time per interval, not maintaining consistent pace across the whole workout. For very short distances (under 1 mile), pace is meaningful but should be paired with full-distance race times rather than extrapolated long. In hot or humid conditions, pace will be slower than baseline at the same effort; don't try to "hit pace" if it feels disproportionately hard — back off and trust effort. And for any new runner starting a training program, focus on consistency (showing up for runs) rather than pace targets for the first 6-12 months; speed comes from accumulated mileage, not from pushing pace early.