Running Pace Calculator
Calculate running pace from total time and distance, converted to seconds per kilometer or per mile depending on unit selection. Use it to track training run efficiency, plan race goal paces, and compare performance across different distances.
Last updated: May 2026
Compare with similar
About this calculator
The formula converts time (in hours, minutes, seconds) and distance to a pace value in seconds per unit. Total time in seconds = hours × 3600 + minutes × 60 + seconds; pace = total seconds ÷ distance (with mile-to-km conversion 0.621371 applied if unit is miles). The result is seconds per kilometer (or per mile), rounded to 2 decimal places. To express as min:sec format, divide by 60 (minutes) and take remainder (seconds). A pace of 270 sec/km = 4 min 30 sec/km or 4:30 pace per kilometer. Pace is the reciprocal of speed — slower pace means slower running. Conversion: speed (km/h) = 3600 / pace (sec/km). So 4:30/km pace = 3600/270 = 13.33 km/h. Mile-to-km conversion: pace_per_mile = pace_per_km × 1.609344; speed_mph = speed_kmh × 0.621371. Common benchmarks: elite marathon pace ~4:30/mile or 2:48/km; sub-3-hour marathon pace 6:52/mile = 4:16/km; sub-4-hour marathon pace 9:09/mile = 5:41/km; couch-to-5K finishing pace 12-14 minutes per mile; "easy run" pace 1-2 minutes/mile slower than 5K pace; threshold (tempo) pace 20-30 sec/mile slower than 5K pace. Edge cases: zero distance produces division by zero. For training, run easy paces 80%+ of weekly mileage (faster running has higher injury risk and lower aerobic-base benefit per mile). For race goal paces, use predictive equivalency tables (McMillan, VDOT/Jack Daniels) to map a known race time to expected paces for other distances.
How to use
Example 1 — Training 5K. Distance 5 km, time 0:25:30. Total seconds = 1530. Pace = 1530/5 = 306 sec/km = 5:06/km. Convert to min/mile: 306 × 1.609344 = 492.4 sec/mile = 8:12/mile. Enter 5 for Distance, 0 for Hours, 25 for Minutes, 30 for Seconds, kilometers for Unit. ✓ A 5:06/km pace for a 5K is moderately fit recreational performance — competitive amateur 5K times are 4:00-4:30/km. Use slower paces (5:40-6:30/km) for easy training runs; reserve race pace for specific workouts. Example 2 — Marathon prediction. You hold 5:00/km pace for 5K. Extrapolating: 10K pace ~5:15/km, half-marathon ~5:30/km, marathon ~5:50/km (approximate scaling: each doubling of distance adds 5-7% to pace). For a marathon goal, train at 5:50/km pace for long-run progressions; this produces ~4:06 marathon finish time. ✓ The pace converter is most useful as part of an integrated training plan rather than for single-run analysis. Use Garmin's race-time predictor or McMillan Running Calculator for more sophisticated cross-distance pace projections.
Frequently asked questions
How do I convert between pace per mile and pace per kilometer?
Pace per km = pace per mile ÷ 1.609344. So 8:00/mile = 4:58/km; 7:00/mile = 4:21/km; 10:00/mile = 6:13/km. Conversely, pace per mile = pace per km × 1.609344. So 5:00/km = 8:03/mile; 6:00/km = 9:39/mile; 4:00/km = 6:26/mile. Speed conversions: km/h = mph × 1.609344; mph = km/h × 0.621371. Most modern GPS watches show both simultaneously, so manual conversion is rarely needed during runs. For long-distance running planning, learn pace equivalencies for your common training paces (5K/10K/HM/M goals) in whichever unit your training partners and races use. Coastal US races mostly use miles; European, Canadian, and international races use kilometers; the math works the same either way.
What pace should I run for my goal race?
Use pace equivalency calculators (Jack Daniels VDOT, McMillan Running, Greg McMillan). Rough scaling: if you can run a 5K at X pace, expect 10K at X + 5-10 sec/km, half-marathon at X + 20-30 sec/km, full marathon at X + 35-50 sec/km (with proper marathon training). Examples: 5:00/km 5K → 5:08/km 10K → 5:25/km HM → 5:40/km marathon. Marathon pace is hardest to predict because it requires extensive endurance training and pacing discipline; many runners hit a "wall" around 30-35 km in marathons where pace inevitably slows. Negative splitting (second half faster than first) is the standard race strategy. For most amateur runners, race-day execution is more important than training pace — start 5-10 seconds slower than goal for the first 5K, gradually settle into goal pace, push the final miles only if energy allows.
Why does my pace feel harder than usual?
Many factors affect perceived effort beyond pace: weather (heat, humidity, wind, cold all increase effort at same pace); terrain (hills make any pace harder); fatigue from previous training (cumulative fatigue without adequate recovery); sleep deprivation; nutrition status (low glycogen, dehydration, low electrolytes); illness or impending illness (often felt before symptoms); altitude (1500+ meters significantly increases effort at sea-level pace); time of day (most people perform best mid-late afternoon). For consistent training feedback, use heart rate or rate of perceived exertion (RPE) instead of pace alone. Heart rate at the same external pace varies with: training fatigue (higher HR same effort), heat (higher HR), dehydration (higher HR), illness (often higher HR even before symptoms). Treat unusually high HR or RPE at familiar paces as a signal to reduce intensity or take a recovery day, not push through.
What are the most common mistakes people make with pace tracking?
The biggest is running every workout at "race pace" or near it — most training should be easy (60-90 sec/mile slower than 5K 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 third is using GPS-watch pace as the only metric; rate of perceived exertion (RPE) and heart rate are more reliable indicators of effort. 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 different training phases, age groups, or experience levels. The sixth is obsessing over pace optimization while ignoring strength training, mobility, and recovery — which produce larger gains than pace tweaking after a certain point. Finally, many runners try to "push through" pace targets when their body is signaling fatigue, leading to injury or burnout.
When should I not use pace as a training metric?
Skip pace as the primary metric for easy / recovery runs — use heart rate or 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. For new runners 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.