Marathon Pace Strategy

How to pick a realistic marathon goal pace from a recent race, why even splits beat fast starts, and how to hold pace without watching your watch all day.

Set goal pace from a recent 10K or half, not a number you like. Even or slight negative splits beat a fast first 10 km. Wear a pace band so you are not racing the watch.

Last updated October 5, 2026

Most marathon blow-ups are not fitness problems — they are pacing problems. You can be in sub-4 shape and finish in 4:20 because the first 10 km felt too easy to slow down. This page is about the boring, repeatable way to avoid that.

Start from a race you have actually run

Goal pace should come from evidence, not from a target you like the sound of. Take a recent race — a 10K or half marathon run in the last few months — and predict the equivalent marathon time with the race time predictor. The Riegel model behind it (T₂ = T₁ × (d₂/d₁)^1.06) is deliberately unkind: it assumes you have trained for the marathon distance. If you have not run further than 25 km in training, be honest and add a few minutes rather than subtracting them.

Two reference points worth memorising: a sub-4 marathon is 5:41/km (9:09/mile), and a sub-3 is 4:16/km (6:52/mile).

Even splits beat fast starts

Every strategy below finishes the same distance. What changes is where the cost lands.

ApproachWhat it looks likeTypical outcome
Even splitsFirst km and last km at the same paceBest finish for the fitness you actually have
Negative splitSecond half slightly fasterFastest possible — but needs a lot of discipline early
Positive splitFirst 10 km 10–15 s/km faster than goalThe classic: survival mode from 30–35 km, minutes lost

The asymmetry is what matters. Banking 60 seconds in the first half rarely returns 60 seconds later; it usually costs two or three times that. The first 10 km should feel almost embarrassingly easy — that feeling is not a sign you are under-cooking it.

Fuel changes pace more than fitness does

From around 90 minutes onward, pace is limited by carbohydrate, not by willpower. Most runners need 60–90 g of carbohydrate per hour — roughly two to three gels, taken early and often rather than in one heroic lump at 30 km. Practise the exact gel and the exact timing on long training runs; race day is the wrong day to try a new flavour.

Hold pace without staring at your watch

Checking your watch every kilometre for three hours is a bad way to spend a marathon. Print a pace band, put it on your wrist, and read the split you need at each marker instead. Silicone reusable bands do the same job without a printer — worth it if you race several times a year.

The small things that cost minutes

Chafing at 30 km does not make you fitter, it makes you slower. Anti-chafe balm before the start and a pair of blister-free socks are the cheapest insurance in the sport. Neither is a performance product — they just remove two ways to lose time you have already paid for in training.

Related Tools

Related guides

How the numbers are calculated

Race time prediction · Pace, speed and distance · Sources

Frequently Asked Questions

Should I really run the first half slowly?

Run the first 10 km at goal pace or a few seconds slower. If you feel strong at halfway, you can pick it up — but do not plan on needing to.

Can I use a recent marathon to predict another one?

Only if the course and conditions were similar. A hot, hilly marathon is not a fair benchmark for a flat, cool one.

Do I need a GPS watch?

No. A printed pace band plus the kilometre markers gives you everything you need to hold even splits.

Want a new tool or fix?

Tell us which calculator, pace chart or fix would help — we build what runners ask for. Replies usually come back in 1–2 days.

Tell us what you need →