Marathon Pace Calculator

The marathon is 42.195 km, or 26.219 miles. That number is fixed. What isn’t fixed is how you spread your effort across it, and that decision shapes your race more than almost anything else. This calculator takes your goal finish time and converts it into a per-kilometer and per-mile pace target, along with split projections for common race checkpoints.

A 3-hour marathon requires a 4:17 min/km (6:53 min/mile) average pace. A 4-hour finish requires 5:41 min/km (9:09 min/mile). The arithmetic is simple. The hard part is holding it.

How Marathon Pace Is Calculated

The core formula is straightforward: divide your total goal time in seconds by the race distance in your preferred unit. That gives you seconds per kilometer or mile, which converts to the familiar minutes:seconds format.

The more complex question is how to distribute that pace across the race. The calculator offers three models: even pacing (identical pace throughout), negative splitting (second half slightly faster than the first), and positive splitting (first half faster, which most recreational runners default to, often unintentionally). Research supports near-constant pace as the strategy used by contemporary world-record holders, who show minimal variation across race segments (Díaz et al., 2018; PMID: 29557279).

Understanding Your Results

Your pace output is a planning target, not a guarantee. It assumes flat terrain, neutral weather, and consistent effort, none of which are given on race day.

What the research does tell us is that pace consistency matters independently of raw speed. GPS data from 285 marathon runners found that pace variability alone predicts finish time with an R² of 0.46, meaning roughly half the variation in marathon performance between runners comes down to how steadily they run, not just how fast (Haney & Mercer, 2011; PMID: 27182360). Slower finishers are distinguished from faster ones as much by inconsistency as by average speed.

For negative-split planning, a 1-3% faster second half is a reasonable target. Running the second half faster than the first supports glycogen sparing, better thermoregulation, and reduced cardiovascular drift (Grivas, 2025; PMID: 40740427). That said, individual fitness, experience, and race conditions all affect whether this is achievable. It is not universally optimal for every runner.

When to Use This Calculator

Race planning. Set a realistic finish goal and work backward to a per-mile or per-km pace. Training at that pace in long runs gives you a concrete reference point, not just a vague sense of effort.

Split strategy. Using the 5 km or 10 km splits as checkpoints lets you make mid-race corrections before small deviations compound into large time losses or, worse, a collapse in the final miles.

Negative-split design. If you want to structure your race with a conservative first half, the calculator shows exactly what that means in absolute time, so you have specific numbers to follow rather than a general intention.

Post-race analysis. Compare your actual splits against the calculator’s projections to identify where you deviated and why. That gap is your most useful data point for the next training block.

Limitations

The calculator assumes even or structured pacing as a baseline. Real races are not flat lines. Course profile, weather, crowd density in early miles, and your own fitness on the day all pull your pace away from the plan. Use the output as a framework, not a script.

The glycogen math matters here. Computational modeling shows that more than two-fifths of marathon runners deplete carbohydrate reserves before the finish line when running at an intensity above their aerobic threshold (Rapoport, 2010; PMID: 20975938). Pace alone does not determine this. Fueling does. A pace plan without a fueling plan is incomplete.

The calculator also cannot account for aerobic decoupling at the marathon distance. Equivalent-pace estimates derived from your 10 K or half-marathon times are useful approximations, but fatigue accumulation at 26 miles makes those predictions less reliable than they are for shorter distances.

Tips for Accuracy

1. Anchor your goal to recent fitness. A finish-time goal based on a race or time trial from the last 6-8 weeks is far more reliable than one based on a result from years ago or pure aspiration.

2. Factor in course elevation. The calculator uses flat-course pace. Add roughly 15-20 seconds per mile for every 100 feet of net elevation gain if your race has significant hills.

3. Build a fueling plan alongside your pace plan. The pace target interacts directly with glycogen availability. Know when you will take in carbohydrates during the race and account for that in your early-mile effort level.

4. Test your target pace in training. Running long runs with portions at goal marathon pace tells you whether the number is achievable or needs adjusting. The body is a better predictor than a spreadsheet.

5. Treat the first 10 miles as data collection. Even if your pace plan calls for even splits, the first third of the race is where most runners make their biggest mistake, going out too fast. A pace that feels easy at mile 3 is probably correct. A pace that feels sustainable is probably too fast.

Frequently Asked Questions

Why do so many marathon runners slow down in the second half?

Positive pacing, starting faster than you can sustain, is the dominant pattern in recreational racing. A systematic review of 39 studies found it appeared in approximately 77% of marathon competitions (Sha et al., 2024; PMID: 39281580). The consequence is predictable: 28% of male and 17% of female recreational runners experience significant late-race pacing collapse (Smyth, 2021; PMID: 34010308). Most runners know this in theory and do it anyway because the early miles feel easy and the discipline required to hold back is genuinely difficult to execute.

What causes hitting the wall, and does pace affect it?

The wall is primarily a glycogen depletion event. When carbohydrate stores run out, the body shifts toward fat metabolism, which cannot sustain marathon-level intensity, and pace drops sharply. Modeling work shows that more than two-fifths of marathon runners deplete glycogen before finishing when racing above their aerobic threshold (Rapoport, 2010; PMID: 20975938). The wall is typically experienced around miles 18-22, but the precise point varies based on running intensity and pre-race fueling. Running at a more conservative pace delays depletion; combining that with mid-race carbohydrate intake delays it further.

Is negative splitting actually better for most runners?

Research suggests negative splits may improve performance for many runners; however, optimal strategy depends on individual fitness, experience, and race conditions. Contemporary world-record holders run near-constant pace with minimal variation, not dramatic negative splits (Díaz et al., 2018; PMID: 29557279). For recreational runners, a modest negative split of 1-3% in the second half offers physiological benefits including glycogen sparing and better thermoregulation (Grivas, 2025; PMID: 40740427), but it requires an early-mile discipline that many find difficult to maintain.

How accurate is a pace calculator for predicting my race result?

The arithmetic is exact. The assumption is not. This calculator assumes you will hold your target pace evenly across 26.2 miles, which no runner does perfectly. Studies show a strong association between consistent pacing and faster finish times, though individual factors including training level and course profile affect what is achievable (Haney & Mercer, 2011; PMID: 27182360). Treat the output as a planning target grounded in real data, then adjust on race day based on how you actually feel.

Can I use my half-marathon time to predict my marathon pace?

Equivalent-pace models can give a reasonable starting estimate, but marathon performance often diverges from what shorter-race predictions suggest. Fatigue accumulation across 26 miles introduces aerobic decoupling that does not appear in a half-marathon. Equivalent paces across distances are estimates based on aerobic models; individual performance at the marathon distance may differ from half-marathon or 10 K equivalent predictions due to fatigue accumulation. If your half-marathon-derived pace feels too fast in training long runs, it probably is.

References

1. Sha, J., et al. (2024). Pacing strategies in marathons: A systematic review. Heliyon, 10(17), e36760. PMID: 39281580.

2. Smyth, B. (2021). How recreational marathon runners hit the wall: A large-scale data analysis of late-race pacing collapse in the marathon. PLoS One, 16(5), e0251513. PMID: 34010308.

3. Rapoport, B.I. (2010). Metabolic factors limiting performance in marathon runners. PLoS Computational Biology, 6(10), e1000960. PMID: 20975938.

4. Díaz, J.J., Fernández-Ozcorta, E.J., & Santos-Concejero, J. (2018). The influence of pacing strategy on marathon world records. European Journal of Sport Science, 18(6), 781-786. PMID: 29557279.

5. Haney, T.A. Jr. & Mercer, J.A. (2011). A description of variability of pacing in marathon distance running. International Journal of Exercise Science, 4(2), 133-140. PMID: 27182360.

6. Grivas, G.V. (2025). [Negative-split pacing review]. Frontiers in Physiology, 16:1639816. PMID: 40740427.

7. World Athletics. Official marathon distance standard: 42.195 km / 26.219 miles.

8. American College of Sports Medicine. Guidelines for Exercise Testing and Prescription. Pacing based on aerobic capacity and individual athlete parameters.