Free Running Pace Calculator

Calculate running pace, finish time, or distance from any two of the three. Pick a race preset (5K, 10K, half, marathon) or enter a custom distance. Shows race time predictions for other common distances.

Enter your details

Required when calculating pace or distance.

Required when calculating time or distance.

Result
Enter your details on the left, then press Calculate.

More Health & Wellness tools

See all →

What is this calculator for?

You're training for your first half-marathon. Your last long run was 9 miles in 1:17. You want to know your average pace and project your finish time for the 13.1-mile race. The pace calculator handles the math: distance, time, pace are all interrelated, and given any two, the third follows. Use it for race planning, training pace targets, and converting between minutes-per-mile and minutes-per-kilometer.

Running pace is typically expressed as minutes-per-mile (US standard) or minutes-per-kilometer (international standard). 9:00 min/mile = 5:35 min/km. 7:30 min/mile = 4:39 min/km. 6:00 min/mile = 3:43 min/km (elite-level recreational; sub-3-hour marathoners run at 6:50 min/mile average). Common training paces relative to race pace: easy run pace 60-90 seconds/mile slower than 5K pace; tempo run pace 20-30 seconds/mile slower than 10K pace; intervals at or faster than 5K pace.

This calculator handles three conversions (distance/time → pace, distance/pace → time, pace/time → distance), plus race-time projections from training data, plus pace-band creation for specific race targets (e.g., what splits do you need to hit a 1:45 half-marathon).

How to use this calculator

Pick the calculation type: pace from distance/time, time from distance/pace, or distance from time/pace.

Enter the relevant inputs. Distance in miles or kilometers — the calculator handles common race distances (5K, 10K, half marathon 13.1 mi/21.1 km, marathon 26.2 mi/42.2 km). Time in hours:minutes:seconds (e.g., 1:23:45). Pace in min:sec per mile or per kilometer.

For race time projection: enter a recent race result at any distance, the calculator uses the Riegel formula (T2 = T1 × (D2/D1)^1.06) to project performance at other distances. Reasonably accurate for runners with consistent training; less accurate if comparing very different distances (e.g., 5K result projecting to marathon overestimates marathon performance because endurance and pacing are different at long distances).

For pace bands: enter target finish time and race distance. The calculator outputs split times for each mile or kilometer to hit the target.

Understanding your results

The calculator returns the requested unknown (pace, time, or distance) plus useful context: equivalent miles/km, common comparable race paces, age-group context.

Sample calculations. 13.1 miles in 1:55:00 = 8:46/mile pace. Same pace for full marathon = 3:50:30 finish (Riegel-projected, assuming similar training). 5:00 min/mile pace for 5K = 15:32 finish — elite-level. 12:00 min/mile pace for 26.2 miles = 5:14:24 — late-finisher, walk-run pace.

The Riegel formula caveat. Race time projections work well for distances within 2-3× of the reference distance. 5K projecting to 10K: accurate. 10K projecting to half-marathon: reasonably accurate. 5K projecting to marathon: overestimates (typically 5-15 minutes too optimistic) because marathon endurance is qualitatively different from 5K speed. The more honest formula for predicting marathon from shorter races requires substantial training-volume context, which a single race result can't capture.

The training-pace recommendations. After determining race pace from a recent race, derive training paces using percentages: easy run 65-75% race pace effort, long run 60-75% race pace effort, tempo 85-92% race pace effort, intervals 95-105% race pace effort. Heart rate zones often substitute for pace zones; a heart-rate monitor + GPS watch combination tracks both.

A worked example

Marcus, 38, just finished his second 10K race in 51:30 — 8:18/mile pace. He's planning to run his first half-marathon in 12 weeks. He wants to know: what's a realistic time goal, what pace should he aim for, and what training paces should he use.

Riegel projection: 10K result 51:30 → half-marathon 1:53:30 (8:39/mile pace). For a first half-marathon with adequate training, this is the upper bound of likely performance — many first-timers run 5-15% slower than the projection due to pacing inexperience and endurance gaps. Conservative target: 2:00:00 (9:09/mile) for first half-marathon; stretch target 1:55:00 (8:46/mile).

He chooses 1:55:00 as his goal. Pace bands: 8:46/mile means each mile in 8:46. For a half-marathon: cumulative times at each mile: mile 1 8:46, mile 2 17:32, mile 3 26:18, mile 5 43:50, mile 7 1:01:22, mile 10 1:27:40, mile 12 1:45:12, mile 13 1:53:58, finish 1:55:00 with 0.1 mile at slight push.

Training pace targets:

Easy runs (most of the week): 65-75% effort × 8:46 race pace ≈ 10:30-11:30/mile. Conversational pace. He often goes faster than this; his mistake; easy runs should be genuinely easy.

Tempo runs (1/week, 4-7 miles): 85-92% × race pace ≈ 9:15-9:45/mile. Uncomfortable but sustainable for the duration.

Long runs (1/week, 8-14 miles): 70-80% × race pace ≈ 10:00-11:00/mile. Builds endurance without exhausting recovery.

Intervals (1/week, 400-1600m repeats): 95-105% × race pace ≈ 8:00-9:00/mile. Hard effort with rest between intervals.

Race day: Marcus runs the first 10 miles at 8:42 average — slightly faster than target. He hits the wall at mile 11, slows to 9:30/mile for last 2.1. Final time: 1:56:48. Just outside his stretch goal but well within the realistic range. He learns the pacing lesson — starting at goal pace, not faster, would have produced a finish closer to 1:55. His next race (12 months later) he runs 1:51:15. Steady improvement; the pace-band discipline kicks in.

Related resources

For broader fitness and weight goals, see Calorie Calculator, TDEE Calculator, and Water Intake Calculator (hydration heavily affects running performance). For body composition context, the BMI Calculator and Body Fat Calculator. For sleep quality affecting recovery, the Sleep Calculator. The USA Track & Field publishes race-time standards and qualifying times; McMillan Running publishes detailed training pace calculators favored by coaches.

Related calculators

unit convertertdee calculatorcalorie calculator

Frequently asked questions

What is a good running pace for beginners?

For a new runner finishing a 5K, an 11:00–13:00 per mile pace (40–45 minute 5K) is solid. Trained recreational runners average 8:00–10:00 per mile (25–31 minute 5K). Sub-7:00 per mile is competitive amateur territory; sub-5:00 is elite. The right pace for you is one you can hold while breathing comfortably — being able to speak in short sentences is a good check.

How do I run negative splits?

Negative splits means running the second half of a race faster than the first. Start 5–10 seconds per mile slower than your target average pace; settle into goal pace by mile 2–3; accelerate the final third. This conserves glycogen, manages heat buildup, and is how nearly all marathon world records are set. Most amateur runners do the opposite (positive splits) and crash in the final miles.

What's the difference between pace and speed?

Pace is time per distance (e.g. 8:00 per mile). Speed is distance per time (e.g. 7.5 mph). Same idea, inverse units. Pace is standard among runners because it makes mental math easier on the run — '8:00 pace × 26.2 miles = 3:30:00' is straightforward. Most GPS watches show pace by default and speed only when selected.

How accurate is the Riegel formula for race-time prediction?

Within 5-10% for distances within 2-3× of the reference. 5K to 10K: very accurate. 10K to half-marathon: usually accurate to 2-3 minutes. Half-marathon to marathon: accurate to 10-15 minutes for trained runners; can be off by 30+ minutes for runners with inadequate endurance base. 5K to marathon: notoriously over-optimistic (often 30+ minutes too fast). The formula's assumption of consistent fitness-to-distance scaling breaks down for the marathon specifically because the energy systems differ — 5K is anaerobic/aerobic mix; marathon is purely aerobic. For marathon prediction, the McMillan calculator (which uses more nuanced scaling) is generally more accurate than Riegel.

What's a 'good' marathon time?

Highly age and experience dependent. Boston Marathon qualifying times (which are competitive but accessible): age 30-34 men 2:55, women 3:25. Age 50-54 men 3:25, women 3:55. Age 65-69 men 4:00, women 4:30. Sub-3-hour marathon: top 5% of recreational male runners; very small percentage of female runners. Sub-4-hour: top 25-30% of all marathon finishers. Sub-5-hour: top 65%. Median marathon finish time in the US: around 4:30 men, 4:55 women. First-time marathoners typically finish in the 4:30-5:30 range with 16-20 weeks of focused training; substantially faster requires multi-year training base.

How do I convert minutes-per-mile to minutes-per-kilometer?

Multiply min/mile by 0.6214 to get min/km. Or divide min/mile by 1.609 to get min/km. Example: 8:00/mile × 0.6214 = 4:58/km. 6:00/mile × 0.6214 = 3:44/km. Reverse: min/km × 1.609 = min/mile. 5:00/km × 1.609 = 8:03/mile. Most modern GPS watches let you toggle between units. International race results typically use km; US races typically mile. Converting effort levels is the same in either system — just the numbers change.

What's a 'tempo run' pace?

A pace that's 'comfortably hard' — sustainable for 20-60 minutes but not for a full race. Typically 20-30 seconds/mile slower than your 10K race pace, or your half-marathon race pace for trained runners. Heart rate around 85-90% of max. The lactate threshold pace — the fastest pace you can sustain without lactate accumulating faster than your body clears it. Tempo runs are the bread-and-butter aerobic-fitness workout for distance runners; one tempo session per week (typically 4-8 miles at tempo pace, after warm-up) provides outsized fitness improvement. The goal isn't to suffer for the workout's sake; it's to spend time at a specific physiological intensity that builds threshold fitness.

Should I run my training paces by feel or by GPS?

Both. GPS watches are excellent for objective pace data on flat, open terrain. They become less reliable in dense urban canyons (skyscraper interference), in heavily wooded trails, or in extreme weather. 'Feel' (rate of perceived exertion, RPE) is what's available in any conditions and matches actual physiological intensity better than GPS pace in hilly terrain (heart rate climbs on uphills even if pace is identical to flat ground). Many coaches recommend training to specific heart rate zones rather than pace zones — heart rate adjusts naturally for terrain, weather, fatigue, etc. The hybrid approach: use GPS pace for benchmarking objective improvements over time; use feel and heart rate for daily intensity calibration.

Sources