Marathon Pace From Half Marathon Time
A representative recent half marathon is useful context for a marathon goal. The conversion still assumes how your pace changes over twice the distance. Explore the scenarios below, then review preparation and conditions before choosing a target.
Half → marathon calculator
Model background: power-law time vs distance scaling, commonly associated with the Riegel model.
The mode changes fixed exponent choices. It does not assess your fitness, long-run preparation or probability of finishing at that pace.
Use the half as evidence, with context
If the half is still ahead of you, build its own 21.1 km pacing plan first. The opening pace and checkpoint decisions deserve attention before using the eventual result as a marathon input.
A half marathon is closer to the duration and distance of a marathon than a 5K or 10K, so a representative recent result is useful context. It still leaves a large additional demand untested.
My Run Melbourne comparison shows a stronger 2026 finish, including final full kilometres of 4:53 and 4:51. That was encouraging evidence about the half marathon. My subsequent Sydney result showed why it was not proof of a sub-four marathon.
What the three modes actually calculate
This tool uses T₂ = T₁ × 2k. The three modes choose the following exponents; the centre value is another selected scenario, not a statistical expectation.
On a small screen, swipe the table to see all columns.
| Mode | Lower-time example | Centre example | Higher-time example |
|---|---|---|---|
| Aggressive | 1.05 | 1.055 | 1.06 |
| Balanced | 1.06 | 1.065 | 1.075 |
| Conservative | 1.065 | 1.075 | 1.085 |
The quick table below uses single exponents 1.055, 1.065 and 1.08 for its three columns. These settings are illustrative. The calculator does not infer an exponent from your training or produce a personal confidence interval.
Why the prediction can miss
The model can be wrong even when you execute the race well. Its endurance assumption may not fit you; the input may be old or unrepresentative; and marathon preparation, conditions, health and race decisions can differ.
A GPS activity with a recorded-distance problem is especially unsuitable for a precise race-time conversion. In my 2025 record, the note about distance loss is a reason to use the lap pattern descriptively rather than reconstruct a missing half-marathon result.
Quick rule-of-thumb table
This table shows three selected exponent scenarios. The calculation does not change in response to your training history.
| Half marathon time | Marathon (aggressive) | Marathon (balanced) | Marathon (conservative) |
|---|
Once you choose a target, build exact checkpoints using the Marathon Pace Calculator and study pacing discipline with Marathon splits explained.
What to do after you get your prediction
- Choose the most honest range, not the most flattering one.
- Turn that target into exact pace and checkpoints with the Marathon Pace Calculator.
- Adjust for heat, wind, and hills with the Race-Day Pace Adjuster.
- Build your next 4 weeks around that target using the Monthly Training Plan.
- Print a race-day reference using the marathon or half-marathon pace-band generator.
FAQ
Is the half always the best input?
No. Its longer duration is useful, but a representative recent race matters more than automatically preferring an old or compromised result.
Can I just double my half time?
Doubling preserves average pace over twice the distance. The power-law model allows slowing, but its chosen exponent may not match you.
Does a strong half-marathon finish prove marathon readiness?
No. It describes capacity late in that half marathon. The full distance adds demands that remain untested.
Which mode should I choose?
Use the modes to explore assumptions, then review your training and conditions. Their names are not assessed runner categories.
References
- Riegel PS. “Athletic Records and Human Endurance.” PDF.
- Review of performance models: Predictive Performance Models in Long-Distance Runners.
- Large dataset prediction example: PLOS ONE performance prediction.
Compare the estimate with your long runs, fueling practice and expected race conditions.
A recorded example from my Sydney build
My 1:50:57 half marathon converted to about 3:51:19 at exponent 1.06. I did not achieve my sub-four goal at Sydney. That experience shows why the conversion needs to be checked against marathon preparation.
Turn the estimate into checkpoints
Once you have chosen a realistic finish goal, compare its actual checkpoints: the 3:25 marathon guide explains the rounding trap, while the five-hour marathon guide accounts for run/walk intervals and stops. For all targets, use the marathon pace chart and calculator.
The Running Lab prediction and pacing collection connects these model assumptions with recorded Run Melbourne laps and my subsequent Sydney experience. It is evidence to review alongside the scenario, not a validation of a model for every runner.
Planning the half marathon you will use as evidence?
Calculate its checkpoints with the half-marathon chart and plan the opening with the half-marathon strategy guide. Keep the recorded race result separate from a planned split schedule when returning to the marathon scenarios above.