Marathon Pacing Strategy — A Practical Guide

The 5K is forgiving — you can go out fast and survive. The marathon is not. Every second you spend faster than your steady-state pace in the first half costs you two to four seconds in the second half. The reason is glycogen: above ~85 % of VO₂max, you burn carbohydrate fast enough to deplete your liver and muscle stores before the finish. Once those stores empty, your pace doesn't just slow — it collapses.

The implication is simple: a marathon is a fuel-budget problem disguised as a pace problem. Hold your pace tightly enough that you finish your glycogen at the same time you finish the race.

VDOT is Jack Daniels' metric for current running fitness. It combines VO₂max with running economy into a single number that predicts performance across distances. A VDOT of 50 corresponds to roughly a 19:57 5K, a 41:21 10K, a 1:31:35 half, and a 3:10:49 marathon — at sea level, on a flat course, in mild conditions.

Compute yours with our VDOT calculator. Use your most recent honest race effort — not last spring's PR. VDOT is a snapshot of present fitness; if you haven't raced in three months, it's probably stale.

• Even splits — flat course, target time you've already demonstrated at half-marathon pace × 2 + 5 minutes.
• Slight positive split — first half 30–90 s faster than the second. This is what most world records actually look like.
• Negative splits — start 30–60 s slower than goal, finish 30–60 s faster. Best for first marathons and races with a downhill finish.
• Effort-based — pace by RPE or heart-rate zones, accept whatever finish time the course allows. Best in heat or for trail/hilly courses.

The classic "bonk" at 32 km happens when muscle glycogen runs out. It is preventable in three ways:

1. Pace honestly. Going out too fast burns glycogen on log-scale — a 5 % overshoot in pace costs ~25 % more carbohydrate per kilometer.
2. Fuel from kilometer 8. 60–90 g of carbohydrate per hour during the race spares muscle glycogen. ISSN 2018 guidelines: 60 g/h for 2.5–3 hour finishers, up to 90 g/h for marathon-fit racers using glucose-fructose blends.
3. Train your gut. The 90 g/h ceiling is only reachable if you've practiced taking carbohydrate during long runs. Race day is not the day to find out.

Every 1 % of grade costs about 4 % of pace going up and gives back about 2.5 % going down — gravity-based pace adjustment is asymmetric because braking on downhills caps how much you can gain. A net-flat course with rolling hills is slower than a perfectly flat course; a net-downhill course is faster than a flat one, but only if you protect your quads in the early downhill kilometers.

Practical rule: budget the elevation as "time tax" before the race, and pace uphill segments by effort, not pace.

Marathon performance peaks around 5–12 °C dry-bulb. Each degree above 12 °C costs roughly 0.2–0.4 % of pace, with humidity multiplying the effect above 60 % RH. Use our heat-pacing calculator for a quick estimate. Heat-acclimatization (10–14 days in similar conditions) cuts the penalty by about 40 %.

• Carb-load 1.5–2.5 g of carbs / kg bodyweight per day for 2–3 days pre-race.
• Test your gels on your last long run, not on race day.
• Eat your pre-race breakfast 3 hours before the gun.
• Front-load fluid in the first half — it's harder to catch up later.
• Memorize your kilometer splits, not just your finish time goal.

The principles above are universal. The actual splits aren't — they depend on your VDOT, the race's elevation profile, and the typical climate baseline. Plug your numbers into TrainingFlow's pacing engine and we'll output per-km splits, a nutrition timeline, and a race-week checklist calibrated to your race.