How to Train for a Marathon by Pace

Marathon training fails in two predictable ways: running every run too hard, or having no idea what pace to run on race day. Pace-based training fixes both. Every run gets a purpose and a number, and by race day your goal pace feels familiar instead of frightening. Here is how to build a pace-based plan from scratch.

Step 1: Find your paces from a recent race

Everything starts with one honest data point: a recent race result, ideally a 5K, 10K, or half marathon run all-out within the last couple of months. From that single result, you can derive your whole pace range. The standard approach is a race-time predictor (the classic formulas date back to exercise physiologist Jack Daniels): plug in your race time and distance, and it estimates equivalent performances at other distances plus training paces.

For a concrete example, take a runner who recently ran a half marathon in 2:00:00. That is 9:09 per mile. The equivalent marathon is roughly 4:10–4:15, not 4:00 flat, because endurance fades over the longer distance — a reality the predictors account for. From that same result, the training paces fall out: easy runs around 10:10–10:40 per mile, tempo runs near 8:50–9:00 per mile, and intervals around 8:00–8:15 per mile. Notice how wide the range is: the slowest training pace is more than two minutes per mile slower than the fastest. That spread is the point. Different runs stress different systems, and they only work if you actually run them at different speeds.

If you have no recent race, run a hard 5K time trial on a flat course after a good warm-up. It hurts for twenty-five minutes, but it buys you four months of accurate training. Do not guess your paces from your best-ever race three years ago, and do not set them from your goal — set them from your current fitness, then update them after your next race.

Step 2: Structure the week around four run types

A typical marathon week has four kinds of runs, and each has a pace job. Easy runs are the bulk — roughly 70–80% of weekly mileage — at a conversational effort, 60–90 seconds per mile slower than marathon goal pace. Their job is aerobic development and recovery, and they only work if they are genuinely easy. The long run, once a week, builds endurance: start it at easy pace and, in the second half of the plan, finish the last few miles at goal marathon pace. The tempo run, once a week, is a sustained effort around your 10-mile to half-marathon pace — comfortably hard, the fastest pace you could hold for about an hour. The interval session, once a week or every other week, is short repeats at 5K pace or faster with recovery jogs between, building speed and running economy.

A sample week for a 40-mile runner might look like this: Tuesday intervals (6 × 800 meters at 5K pace), Wednesday easy 6 miles, Thursday tempo 5 miles, Saturday easy 8 miles, Sunday long run 16 miles, with rest or cross-training on Monday and Friday. The exact days matter less than the pattern: hard days separated by easy days, one long run, and at least one full rest day. The most common beginner error is stacking hard days together because the schedule looks tidier that way — it is also how injuries happen.

Step 3: Marathon-pace workouts are the dress rehearsal

Among all workouts, marathon-pace sessions deserve special attention because they are the only ones that teach your body what race day actually feels like. The classic versions progress through a plan: early on, 4 miles at goal pace inside a longer easy run; mid-plan, 8–10 miles continuous at goal pace; late in the plan, 12–14 miles at goal pace, sometimes with the last two miles slightly faster. These sessions answer the only question that matters: can I hold this pace when I am tired?

Run them on terrain similar to your race — if the marathon is hilly, train on hills — and practice everything else at the same time: the shoes, the fueling, the water stops, the pre-race meal. A marathon-pace workout that ends with you raiding the kitchen for food you never practiced is a lesson, not a failure, as long as it happens in training and not on race day. If you cannot hold goal pace for the workout, that is information, not defeat: adjust the goal rather than forcing workouts that break you.

Step 4: Taper by pace, not by panic

The taper — the final two to three weeks — is where runners most often sabotage themselves. Volume drops by roughly 20–40% per week, but intensity stays: keep a short tempo session and a few strides so your legs stay sharp. The purpose is to shed accumulated fatigue while holding fitness, and the research is consistent that a proper taper improves race performance by a few percent — the difference between 4:05 and 3:58 for many runners.

During the taper, trust the paces you have trained. The sudden urge to "test" your fitness with a hard effort the week before the race is the taper's trap; fitness does not meaningfully improve in the final ten days, but fatigue and injury risk absolutely can. Your last long run should land about three weeks out, around 20–22 miles, and the final week should feel almost suspiciously easy.

Step 5: Pace race day itself

Race day pacing is simple to describe and hard to execute: run even splits, or a slight negative split where the second half is marginally faster. For a 4-hour marathon goal, that means reaching halfway around 2:00–2:01, not 1:55. The first miles always feel too easy — adrenaline, crowds, fresh legs — and that feeling is a liar. Runners who bank time early almost always pay it back with interest after mile 20, when glycogen runs low and the race truly begins.

Use the course's mile markers rather than your watch alone, since GPS watches read long on courses with turns and crowds. Check your split at each marker against your goal-pace band: within 5–10 seconds per mile is perfect, and a drift of 15 seconds or more deserves a correction. If you are ahead of pace at halfway, the disciplined move is to hold steady, not to accelerate — the marathon rewards patience more than courage for the first 20 miles, and then it rewards whatever you have left.

Five pacing mistakes to avoid

Most marathon disappointment traces back to a handful of pacing errors, and all of them are avoidable. First, starting too fast: the opening miles feel effortless, so runners bank time they will repay with interest after mile 20. Second, racing your training partners instead of your plan — someone else's goal pace is not yours, no matter how good they look at mile 8. Third, skipping fueling practice: your stomach needs training just like your legs, and gels you have never tried have no place on race day. Fourth, turning the taper into a fitness test with a hard effort the week before the race; fitness is banked by then, and all a hard session can do is add fatigue. Fifth, refusing to adjust: if heat, hills, or illness put goal pace out of reach by halfway, the smart move is to reset to a finish-first pace rather than blowing up chasing a number. A marathon finished strong at a slower pace beats a marathon walked from mile 22 every single time.

Frequently asked questions