Marathon Pace Calculator
A marathon pace calculator does one of two things: it converts a goal time to a per-mile pace, or it predicts a realistic marathon time from a shorter race result. Most people use the first version. The more useful version is the second.
Here’s why that distinction matters: if you type in “3:30 marathon” and get back “8:01 per mile,” that number is only meaningful if your current fitness can actually sustain 8:01 for 26.2 miles. A lot of runners discover on race day — usually around mile 20 — that it cannot.
A VDOT-based marathon pace calculator works from the other direction. You enter what you’ve actually run — a recent 5K, 10K, or half marathon — and the formula tells you what marathon pace your current fitness supports. That’s the number worth training for.
How to calculate marathon pace from a recent race result
The cleanest input for a marathon pace calculation is a recent half marathon. Enter that time into the Race Time Predictor and it returns a predicted marathon finish time using the VDOT formula. Divide 26.2 miles by that time and you have your marathon pace.
A 1:55 half marathon, for example, predicts a marathon finish around 3:58-4:02, depending on fatigue modeling. That maps to roughly 9:07-9:12 per mile. If you’ve been training at 8:30 because that’s what a 4:00 goal implies, you’re carrying 37 seconds per mile of accumulated stress across every long run and every marathon-pace workout. That’s the kind of error that shows up at mile 22.
The math behind this comes from Dr. Jack Daniels’ VDOT system, which derives a proxy for VO2 max from race performance and uses it to project equivalent performances at other distances. A 1:55 half marathon yields a VDOT of roughly 44. The VDOT 44 marathon pace is approximately 9:10 per mile. A 1:45 half (VDOT ~51) projects to a marathon pace around 7:58 per mile.
You can work these numbers yourself with the VDOT Calculator: enter any recent race result and it returns not just your predicted marathon time but your full set of training paces — Easy, Threshold, Interval, and Repetition — all calibrated to current fitness.
What your marathon pace is actually telling you
Marathon pace in the VDOT system isn’t arbitrary. It sits at roughly 75-84% of VO2 max effort — higher than easy aerobic running, lower than threshold. That’s the intensity your body can sustain for the 3-6 hours a recreational runner typically spends on the course.
At this intensity, your body is burning a mix of fat and glycogen. Go 15 seconds per mile faster and the glycogen burn rate rises sharply. That’s why the first-half banking-time strategy fails so reliably: glycogen depletion accelerates exponentially above marathon pace, and once it’s gone, the body can’t replace it mid-race at anything approaching the same rate.
The marathon pacing strategy guide covers this physiology in depth, including the case for negative splits and why even perfectly even pacing beats optimistic early pacing every time.
Converting goal time to marathon pace per mile
If you want to target a specific finish time — a BQ, a sub-4, a sub-5 — here’s the clean arithmetic:
Marathon pace (minutes/mile) = goal time in minutes ÷ 26.2
| Goal time | Per mile | Per km |
|---|---|---|
| 3:00 | 6:53 | 4:16 |
| 3:30 | 8:01 | 4:59 |
| 3:45 | 8:35 | 5:20 |
| 4:00 | 9:09 | 5:41 |
| 4:30 | 10:18 | 6:24 |
| 5:00 | 11:27 | 7:06 |
| 5:30 | 12:35 | 7:49 |
The critical check: take your target marathon pace and work backward through the Race Time Predictor to see what half marathon or 10K time it implies. If the implied 10K is 45 seconds faster than you’ve ever raced, your goal pace isn’t grounded in current fitness — it’s a wish.
Half marathon pace calculator: the math for 13.1
The same principles apply for half marathon pace calculation, just with a 13.1-mile divisor.
Half marathon pace (minutes/mile) = goal time in minutes ÷ 13.1
| Goal time | Per mile | Per km |
|---|---|---|
| 1:30 | 6:52 | 4:16 |
| 1:45 | 8:00 | 4:58 |
| 1:55 | 8:47 | 5:27 |
| 2:00 | 9:09 | 5:41 |
| 2:15 | 10:18 | 6:24 |
| 2:30 | 11:27 | 7:06 |
Half marathon pace tends to run about 15-20 seconds per mile faster than marathon pace for recreational runners. If you’re targeting a 2:00 half marathon (9:09/mile), your equivalent marathon pace — if you had the aerobic base to sustain it — is around 9:28-9:40/mile. The difference reflects the additional glycogen conservation required over the extra 13 miles.
The VDOT cross-check: a 2:00 half marathon corresponds to a VDOT of approximately 43. VDOT 43 marathon pace is about 9:15/mile. If your marathon goal is faster than that, you need either more fitness or a better half marathon result in your recent log.
How to build your mile-by-mile split plan
A single marathon pace number is a starting point, not a race plan. Course elevation, weather, and your own fatigue curve all mean the pace will vary mile to mile even if your effort stays constant.
Two approaches work:
Even splits. Every mile at the same pace, adjusted for hills using effort rather than GPS pace. Climb at consistent effort (which means slightly slower GPS pace), let the descent recover it. This requires course knowledge and a willingness to let uphills look slow on the watch.
Negative splits. First half at 5-10 seconds per mile slower than goal pace, second half at goal pace or slightly faster. Research on recreational marathon performance consistently shows negative-split finishers slow down less in the final 10K than even-split or positive-split runners. The metabolic explanation: slower early miles preserve glycogen, which translates to genuine capacity in the closing miles.
The Race Split Planner generates a mile-by-mile or kilometer-by-kilometer breakdown for any goal time and distance — even splits or negative splits — formatted to print and carry to the start line. If you’ve done the work of finding a realistic goal pace, this turns that number into an actionable race document.
Why training at the wrong marathon pace is expensive
Most recreational runners either train marathon-pace workouts at goal pace (too fast) or skip them entirely and run all their quality work at tempo or interval intensity.
Marathon-pace workouts serve a specific physiological purpose: teaching the body to sustain fat-dominant energy metabolism at race intensity, and building the neuromuscular efficiency to hold form at that effort for hours. They belong in the training plan at 10-20% of weekly volume, alongside easy runs and higher-intensity threshold work.
The training pace calculator guide explains exactly how marathon pace fits into the full VDOT training system — where it falls relative to Easy, Threshold, and Interval paces, and how to use it in workouts without drifting into the physiological gray zone.
Updating your pace calculation as fitness changes
A marathon pace calculation is only valid for current fitness. A PR from two seasons ago doesn’t tell you what pace to train at this week.
The practical cadence: run a tuneup race — 5K, 10K, or half marathon — every six to eight weeks during a training block. Enter the result into the Race Time Predictor and recalculate your marathon pace. If your predicted marathon time improved by 3 minutes, your training paces should reflect that. Running at paces built from stale fitness leaves adaptation on the table in both directions — too easy fails to stimulate progress; too hard accumulates injury risk.
If you can’t race frequently, a well-paced 10K time trial on a flat course gives a reliable VDOT estimate. The VDOT Calculator handles this the same way it handles race results.
From pace math to race day execution
The gap between knowing your marathon pace and actually running it on race day is where most training plans live or die. Three things close that gap:
Specificity in long runs. Include at least two to three long runs during your buildup where the final 6-8 miles are run at marathon pace. Don’t run the entire long run at MP — that’s too much stress. Run the back half.
Printed splits. Write your mile splits on the back of your hand or print a split band to carry. In the second half of a marathon, decision-making under fatigue is unreliable. Preset checkpoints remove the calculation from the race.
Patience in the first six miles. The most common cause of positive-split marathons — and the bonk at mile 22 — is a first 10K that’s 30-60 seconds per mile too fast. The course feels easy. The legs feel good. The crowd is pulling you forward. The correct response is restraint, not acceleration. Every second you spend above marathon pace in the first six miles costs you more than one second in the final six.
If you want all of this — VDOT calculator, race predictor, pace calculator, and split planner — in one place offline, Pacesmith is a one-time $1.99 iOS app with no subscription, no account, and no internet required. Calculate your marathon pace, generate your splits, and carry it all to the start line.