Pacing is the single biggest factor separating a marathon that goes to plan from one that falls apart in the last six miles. Fitness gets you to the start line capable of running a certain time — pacing decides whether you actually run it, or whether you're walking through water stations at mile 22 wondering where it all went wrong.
This guide covers the two pacing strategies that actually work for road marathons — even splits and negative splits — why they work, why the third option ('positive splitting', starting fast and slowing down) is how almost every bad marathon happens, and how to translate a target finish time into an actual mile-by-mile plan you can run to.
Even splits vs. negative splits: what they actually mean
An even split marathon means running close to the same pace from mile 1 to mile 26.2 — if your target pace is 9:00/mile, you're running 9:00/mile at mile 3, at mile 15, and at mile 24, allowing for small natural variation from hills, water stations, and crowds.
A negative split marathon means running the second half faster than the first — for example, going through halfway a minute or two slower than goal pace, then closing the gap and finishing strong. Elite marathoners frequently run negative splits deliberately, since it lets them bank energy early and race the second half when the field has spread out.
A positive split — running the first half faster than the second — is not a strategy. It's what happens by accident to almost every runner who goes out too fast on race-day adrenaline. The problem is that the fade is rarely gentle: a few minutes of "free speed" in the opening miles routinely costs ten or twenty minutes in the closing ones, once glycogen stores run low and form breaks down.
Why going out fast costs more than it earns
Running 20 seconds/mile faster than goal pace for the first 10 miles banks you roughly 3 minutes. But arriving at mile 20 with depleted glycogen and breakdown-level fatigue routinely costs 5-15 minutes in the last 10K as pace collapses toward a walk. The trade is almost always a loss.
Why starting fast is the most common way marathons go wrong
Three things make an aggressive first half feel deceptively easy, which is exactly what makes it dangerous:
- Adrenaline and a fresh crowd mask effort — the first few miles of any marathon feel far easier than they actually are, because you're rested, excited, and running downhill on nervous energy.
- Glycogen depletion is a cliff, not a slope — your muscles have roughly 90-120 minutes of stored glycogen at marathon effort. Run the first half too hard and you arrive at that cliff edge early, with 8-10 miles still to run on empty.
- Form breaks down under fatigue, which makes every subsequent mile more expensive — once you're overstriding and heel-striking from fatigue, the same pace costs more energy than it did fresh, compounding the slowdown.
This is why experienced marathoners treat the first 5K as the one section of the race where you deliberately hold back, even though it's the easiest part to run fast.
How to build your own marathon pacing plan
Start from a target finish time that's grounded in real evidence, not hope. If you've run a recent 10K or half marathon, use a race-time predictor to see what that performance actually translates to over 26.2 miles — training paces and recent race results are a far more reliable guide than picking a round number.
Once you have a target time, convert it into a per-mile and per-km pace, then map it onto checkpoint splits (5K, 10K, half marathon, 30K) so you have concrete numbers to check yourself against on the day rather than a vague sense of effort.
A sensible even-split plan looks like this in practice:
| Section | Pacing guidance |
|---|---|
| Miles 1-3 | Deliberately conservative — 10-15 sec/mile slower than goal pace. This is the one section where feeling like you're holding back is correct. |
| Miles 4-13 | Settle into goal pace once the field has spread out and legs feel warmed up. |
| Miles 14-20 | Hold goal pace. This is where discipline matters most — the temptation to push is strongest here, and the cost of doing so is highest. |
| Miles 20-23 | The genuine test. Fatigue is real by now — focus on form and effort, and accept a slight, controlled slowdown rather than fighting it into a bigger one later. |
| Miles 23-26.2 | If you've paced well, this is where you have something left to give — a negative-split finish, even a small one, is the sign of a well-run race. |
Should you run with an official pacer?
Most major marathons offer official pacers running with flags or balloons for target times (3:00, 3:30, 4:00, and so on). Running with a pacer removes the decision-making burden — you just stay with the group — but it's only useful if the group's actual pacing strategy matches yours. Some pacers run even splits; others deliberately go out conservatively and negative split. If a race publishes its pacer strategy in advance, check it against your own plan rather than assuming.
A GPS watch with a pace alert, or simply checking your split at each mile marker against your own printed pace band, works just as well and doesn't depend on being physically able to stay with a group in a crowded race.
Adjusting your plan on the day
Weather, course profile, and how you actually feel all matter more than the number you wrote down weeks earlier. A hot, humid race day can justify slowing your target pace by 15-30 seconds/mile from the outset — fighting the heat to hit an unrealistic split is a faster way to blow up than adjusting early. Hilly courses are better paced by effort than by pace, since a flat-pace target on rolling terrain forces you to overwork the uphills to keep the number steady.
The single most reliable rule across all of this: if you're unsure whether you're going out too fast, you probably are. The adrenaline of race morning consistently makes an unsustainable pace feel sustainable for the first few miles — every experienced marathoner has a story about learning this the hard way.