How this instrument works
Marathon pace is the average minutes-per-mile figure a runner needs to hold, without variation, to cross the marathon's certified 26.2-mile (42.195 km) distance in a chosen finish time. It's the same division every pace calculation uses — total time divided by total distance — but framed around the one distance where even small pacing mistakes compound over 26.2 miles instead of 3 or 6, so runners plan around it explicitly months ahead of race day.
A 4:22:00 marathon (262 minutes) works out to an even 10:00 per mile; trim that to 3:29:36 (209.6 minutes) and the required pace drops to 8:00 per mile — both figures assume dead-even pacing with no positive or negative split, which real marathons rarely deliver but which remains the standard planning baseline. Training plans typically build goal pace backward from a target finish time, then check it against recent race times using a race-time predictor to see whether the goal is realistic.
Because a small pace error multiplies by 26.2 miles, marathon runners obsess over this number more than shorter-distance runners do: starting even 15 seconds per mile too fast can bank over 3 minutes of accumulated fatigue by halfway, often costing far more than 3 minutes back in the final miles as glycogen runs low. Race-day pacing strategy — even splits, a conservative first 10K, a planned negative split — is built entirely around holding close to this single per-mile number.
- Enter your Finish time (minutes) — the total marathon time you're targeting or the total time from a completed race.
- Enter Distance (miles) — 26.2 for the standard marathon distance, or a shorter distance if checking a training-run pace.
- Read Pace (min per mile) — the steady per-mile pace that finish time over that distance implies.
- Compare the result against recent race performances using this site's race-time predictor before committing to it as a goal.
Worked example — 30 minutes over 5 miles
Enter 30 for Finish time (minutes) and 5 for Distance (miles) — a clean 6:00-per-mile baseline check, not yet a marathon distance. Pace = 30 ÷ 5 = 6.00 minutes per mile, confirming the division before it's scaled up to a full 26.2-mile race.
The identical division scales to race distance: a 4:22:00 marathon (262 minutes over 26.2 miles) works out to an even 10:00 per mile, and a 3:29:36 marathon (209.6 minutes over 26.2 miles) works out to 8:00 per mile — both exact by the same division, no rounding involved.
Questions
What marathon pace do I need to break 4 hours?
A sub-4:00:00 marathon (under 240 minutes) over 26.2 miles requires an average pace of about 9:10 per mile (240 ÷ 26.2 ≈ 9.16 min, or 9:09.6) — enter 240 and 26.2 to see the exact figure, then build in a small safety margin, since most runners can't hold dead-even pace and prefer to bank a few seconds early rather than fight for them in the final miles.
Is marathon pace the same as 5K or 10K race pace?
No — the exponential slowdown built into endurance racing means marathon pace is meaningfully slower than a runner's shorter-distance race pace, not just an extrapolation of it. This site's race-predictor applies Riegel's formula to estimate a realistic marathon time from a recent 5K or 10K result, which is a better starting point for a goal than assuming marathon pace equals 5K pace with no adjustment.
Should I run even pace or a negative split for a marathon?
Even pacing is the standard planning baseline this calculator assumes, but many experienced marathoners deliberately run a slight negative split — a touch slower than goal pace for the first half, a touch faster for the second — because starting conservatively banks glycogen and reduces the risk of the severe late-race slowdown known as 'hitting the wall.' Either way, the single per-mile number from this calculator is the average to aim for across the full distance.
How accurate is a marathon-pace goal based on a shorter race time?
It's a reasonable starting estimate but not a guarantee — factors this simple division can't see, like heat, hills, fuelling, and how well marathon-specific long runs went in training, all move the achievable pace on race day. Treat the pace from a goal finish time as the target to train for, and cross-check it against a recent race result with the race-predictor calculator before locking it in.
Why does marathon pace matter more than pace for a 5K?
Because pacing errors compound over 26.2 miles in a way they don't over 3.1. Starting even 15 seconds per mile faster than goal pace can bank roughly 3.3 minutes of accumulated effort by the halfway point — a deficit that frequently costs far more than 3.3 minutes back in the last 10K once glycogen runs low, which is why marathon runners plan and rehearse this single number more carefully than shorter-distance racers typically need to.