A 16-week marathon training plan for runners who can already run 10K

A marathon is not a longer 10K. It is a different event with a different governing constraint, and the runners who finish strong are the ones who spend sixteen weeks respecting that. This is a complete 16-week marathon training plan, written out week by week, for someone who can already run 10K and wants to cover 42.2 km in control rather than survival. Every week, every long run, and every pace is below. If you never sign up for anything, you still have a full plan you can follow.

What makes the marathon hard is not aerobic fitness alone, it is durability and fuel. Your legs have to keep producing force after three or four hours of pounding, and your body has to keep finding carbohydrate long after its own stores would have run dry. Sixteen weeks is the right runway to build both without forcing the kind of mileage jump that ends in a stress fracture.

The honest prerequisite: run 10K continuously first

This is not a couch-to-marathon plan, and the distinction is not a formality. Before week 1 you should be able to run 10K continuously, without walking, even if slowly, and you should already be running three to four times a week and have been doing so for at least a couple of months. That is the real entry requirement. The plan below opens at roughly 32 km in the first week, and that opening volume only makes sense if your body is already accustomed to regular running.

If you cannot yet run 10K without stopping, you are not ready for a marathon block yet, and that is completely fine. Spend two to three months building a continuous 10K and a consistent four-runs-a-week habit first. The cleanest on-ramp is our 8-week first 10K plan, which takes you from a continuous 5K to a 10K, after which this marathon plan becomes the logical next step. Trying to skip that base is the single most common reason first-timers get injured, because the marathon punishes accumulated mileage, and accumulated mileage is exactly what an underprepared body cannot absorb. Be honest about where you are. There is no shame in spending another two months building the base, and there is a great deal of pain in skipping it.

You do not need to be fast, and you do not need any racing experience beyond the 10K base. You need a body that already tolerates regular running and the discipline to follow a progression for four months.

How the plan is structured

The plan runs five sessions a week across four phases, each with a clear job:

• Base (weeks 1-4). Build aerobic volume and grease the joints. Almost all easy running, with strides and a short tempo to keep the legs sharp. This is where you raise your weekly mileage to a level the harder phases can build on.
• Build (weeks 5-9). Introduce marathon-pace segments inside the long runs and weekly threshold work. This is where the long run starts becoming specific, teaching your legs to hold goal pace under fatigue.
• Peak (weeks 10-14). The highest mileage and the longest runs, including the single 32 km long run that is the centrepiece of the block. Marathon-pace volume inside the long runs reaches its maximum here.
• Taper (weeks 15-16). Volume drops sharply while a little intensity stays, so you arrive at the start line fresh and sharp rather than tired.

Each week is roughly three easy runs, one quality session (threshold or marathon-pace work), and one long run. Weekly volume climbs by roughly 10% at a time with a deliberate cutback every third or fourth week, because fitness is built during recovery, not during the hard weeks. The peak weekly volume here is around 55 km (about 34 miles), which is a sane, finishable first-marathon peak. Plans that shove you to 80 km out of a 10K base are how people get hurt; this one is built to get you to the start line healthy.

The 16-week marathon plan week by week

Distances are in kilometres. Easy runs fill the days not shown as quality or long. "MP" means marathon goal pace; those segments sit inside the long run after an easy start. Take at least one full rest day every week, and never run your quality session and long run on back-to-back days. If a week feels too ambitious, repeat the previous week rather than forcing the jump. Consistency over sixteen weeks beats two heroic weeks followed by an injury.

Week	Phase	Quality session	Long run	Weekly total
1	Base	Easy + 6 × strides	13 km	~32 km
2	Base	Tempo 5 km	16 km	~35 km
3	Base	Tempo 6 km	18 km	~38 km
4 (cutback)	Base	Easy + strides	14 km	~30 km
5	Build	Threshold 2 × 10 min	21 km	~40 km
6	Build	Threshold 2 × 12 min	24 km (incl. 5 km MP)	~44 km
7	Build	Threshold 3 × 10 min	26 km (incl. 8 km MP)	~47 km
8 (cutback)	Build	Threshold 2 × 8 min	19 km	~37 km
9	Build	Threshold 3 × 10 min	29 km (incl. 10 km MP)	~50 km
10	Peak	Threshold 4 × 8 min	27 km (incl. 12 km MP)	~50 km
11	Peak	Threshold 3 × 12 min	30 km (incl. 13 km MP)	~54 km
12 (cutback)	Peak	Threshold 2 × 10 min	24 km	~44 km
13 (longest)	Peak	Easy + strides	32 km (incl. 16 km MP)	~55 km
14	Peak	Threshold 2 × 10 min	24 km	~42 km
15 (taper)	Taper	Tempo 4 km + strides	16 km	~28 km
16 (race)	Taper	Easy 5 km + strides	Marathon	race week

Notice the cutback weeks at 4, 8, and 12. Dropping the volume roughly every third or fourth week is what lets the next block stick instead of grinding you down. Do not skip them because you feel strong; feeling strong in a cutback week is the point. The single 32 km long run lands in week 13, three weeks out from the race, and it is the longest run you will do. From there the volume steps down through week 14 and into the genuine two-week taper of weeks 15 and 16.

This is also the moment to set a realistic goal time, because a marathon plan only works when your marathon-pace segments are run at an honest pace. The Run Coach builds this plan to YOUR paces and adapts it every week to your training, turning your logged runs into a projected finish time that updates as you get fitter, so you can see whether your MP work is actually on track for the number you want.

Pacing: four gears, set from a recent race

"Easy" and "race pace" are useless as feelings. They need numbers, and the cleanest way to get them is from a recent race or hard time trial converted into training paces. Plug a recent 5K or 10K into the free running pace calculator and it returns every pace below in seconds; the method behind it is explained in full in VDOT training paces explained. Four gears carry this plan:

• Easy pace. The backbone. Slow enough to hold a full conversation in complete sentences, typically 60-90 seconds per kilometre slower than goal marathon pace. The majority of your weekly volume is run here, and it will feel almost embarrassingly slow. That is correct.
• Long-run pace. Mostly easy, run at or slightly faster than easy pace. The job of the long run is time on feet and durability, not speed, so resist the urge to push it. The marathon-pace segments are the only fast part.
• Marathon pace (MP). The pace you intend to race at. For a 4:00 marathon that is about 5:41 per km (9:09 per mile); for a 4:30 it is about 6:24 per km (10:18 per mile). Practising it inside long runs teaches your legs and your fuelling to hold it under fatigue, which is the whole game.
• Threshold pace. "Comfortably hard," roughly your 10K-to-half-marathon race pace, run as sustained reps. This lifts the ceiling so marathon pace feels easier underneath it. You should be able to say only a short sentence at this effort.

The most common pacing error is running easy days too fast and long runs too hard, so everything collapses into a grey middle that builds neither endurance nor speed. The fix is the polarised approach: keep the easy running genuinely easy so the hard work is genuinely hard. The full case for that split is in the 80/20 running approach explained, and it matters more in a marathon block than anywhere else, because the volume is high enough that running it too hard will break you long before race day.

The 20-miler debate: how long should the long run be?

You will notice the longest run here is 32 km, which is almost exactly 20 miles, and you will also notice you never run the full marathon distance in training. Both are deliberate. The "20-miler" is the traditional ceiling for a reason: it is long enough to build the durability and the fuelling rehearsal the marathon demands, but short enough that you can recover from it within a week. Running the full 42.2 km in training offers little extra adaptation and a large extra dose of fatigue and injury risk, and it eats into the very recovery that lets you absorb the rest of the block.

There is a real debate here worth understanding. The case for going slightly beyond 32 km is mental: some runners want to have covered more of the distance so the final 10 km of the race is not entirely unknown. The case against, which most coaches favour, is that the marathon's back end is broken by accumulated fatigue and fuel depletion, not by the raw distance, and you train those through total weekly volume and marathon-pace work, not through one heroic ultra-long run. There is also a time-on-feet argument: a 32 km run takes a 3:00 marathoner about two and a half hours but a 5:00 marathoner well over three and a half, which is a very different stress. If you are a slower runner, cap the long run by time, around three to three and a half hours, rather than by distance. Reaching 28-30 km in that window is plenty; grinding to 32 km in four hours buys nothing but a deeper hole to climb out of. The single 32 km run in week 13 is the right ceiling for most first marathoners. Do not chase a bigger number for its own sake.

Fuelling the long run: practise eating on the run

This is the part most first-timers neglect, and it is the part that most often blows up a race. Your body stores only enough glycogen for roughly 90 to 120 minutes of hard running. Beyond that you must take in carbohydrate or you hit the wall, that sudden, total collapse where your legs simply stop responding. The long run is where you rehearse the fuelling that prevents it, so your gut is trained to absorb carbohydrate while running.

The practical numbers: for any run over about 75-90 minutes, take in 30 to 60 grams of carbohydrate per hour, and on your longest runs and race day, work toward the higher end, up to 60 to 90 grams per hour if your stomach tolerates it. That translates to roughly one gel every 30 to 45 minutes, or the equivalent in chews or sports drink, started early rather than once you already feel empty. Drink to thirst, and on hot days include electrolytes. The golden rule is to practise your exact race-day fuelling on your long runs, the same gels, the same timing, the same drink. The marathon is not the day to discover that a particular gel wrecks your stomach. Find that out on a Sunday in week 9, not at kilometre 30 of the race.

The taper: trust the fitness you already built

The final two weeks reduce volume sharply while keeping a little intensity, and they are not optional rest you have earned, they are part of the training. The taper is when the accumulated fatigue of sixteen weeks finally clears and your body absorbs the work, arriving at the start line fresher and stronger than at any point in the block. Cut your weekly volume to roughly 60% in week 15 and around 40% in race week, but keep some short, sharp efforts, a few strides, a brief tempo, so the legs stay snappy rather than going flat.

You will feel restless, slightly out of shape, and convinced you are losing fitness. Every marathoner feels this. It is an illusion; fitness is not lost in two weeks, but freshness is gained, and a well-tapered runner beats an over-trained one every time. Do not cram. The work is done. Resist the urge to "test" your fitness with one last hard session, sleep well, eat normally, and let the rest do its job. In the final two or three days, eat a little more carbohydrate than usual to top off your glycogen stores.

Race-day pacing: even, or a slight negative split

You have done four months of work. Race day is about not wasting it, and the way you waste it is by going out too fast. Adrenaline, a crowd, and fresh tapered legs conspire to make your goal pace feel absurdly easy in the first few kilometres, at a pace you cannot possibly hold for 42. Almost every first-timer makes this error, banks a few "free" minutes early, and pays them back with brutal interest in the final 10 km.

The goal is an even pace, or a slight negative split, meaning your second half is run as fast as or marginally faster than your first. Practically, hold yourself to goal marathon pace, or even 5 to 10 seconds per kilometre slower, for the first 10 to 15 km. It should feel almost too easy. Settle into goal pace through the middle, keep fuelling on schedule, and only if you genuinely feel strong past 30 km do you allow yourself to push. The marathon does not begin until kilometre 32; everything before that is positioning. The runner who paces evenly spends the last 10 km passing people, while the one who went out hard becomes one of the people being passed. The full case for this approach, and how to rehearse it, is in the negative split pacing guide. Trust the plan over how good your legs feel in the opening miles.

Turn the plan into a target time

This plan gets you to the start line ready to finish your first marathon in control. If you want to know what time you are actually on track for, and whether your marathon-pace long runs are moving the number, the Run Coach builds this plan to YOUR paces and adapts it every week to your training. It turns your logged runs into a projected finish time that updates as you get fitter, and its AI coach reviews your sessions and tells you what to adjust each week, so your goal stops being a guess and becomes something you can watch get closer.

Frequently asked questions

Can a beginner run a marathon in 16 weeks?

Yes, provided you can already run 10K continuously and have been running three to four times a week for at least a couple of months before you start. Sixteen weeks is enough to safely raise your mileage, build your long run to 32 km, and rehearse race-day fuelling. If you cannot yet run 10K without walking, build that base first, ideally over two to three months, then begin this plan. Starting a marathon block from a weaker base than this is the fastest route to injury.

How many days a week do I need to run?

Five sessions is the target in this plan: three easy runs, one quality session, and one long run. You can finish a first marathon on four days by dropping one easy run, but protect the long run and the marathon-pace work, they do the most specific work. Fewer than four runs a week makes the required weekly volume hard to reach safely, because each remaining run has to carry too much load.

Do I need to run 20 miles in training?

One 32 km (roughly 20 mile) long run is the ceiling most first marathoners need, and this plan schedules it three weeks out. You do not run the full marathon distance in training, the extra fatigue and injury risk outweigh any benefit. If you are a slower runner, cap the long run by time, around three to three and a half hours, rather than forcing 32 km, since time on feet, not raw distance, is what matters.

What should I eat during the marathon?

Take in 30 to 60 grams of carbohydrate per hour, working toward 60 to 90 grams per hour on race day if your stomach tolerates it, which is roughly one gel every 30 to 45 minutes or the equivalent in chews or sports drink. Start early, before you feel empty, and drink to thirst with electrolytes on hot days. Crucially, practise your exact race-day fuelling on your long runs so nothing is a surprise on the day.

How should I pace my first marathon?

Aim for an even pace or a slight negative split. Hold goal marathon pace, or slightly slower, for the first 10 to 15 km even though it feels too easy, settle into goal pace through the middle while fuelling on schedule, and only push after 30 km if you feel strong. Going out too fast and fading is the single most common and most costly first-marathon mistake. Discipline in the first half is what lets you run the second half well.

To turn this plan into a projected finish time and watch your training move the number, open the Run Coach. To set your four training paces precisely from a recent race, use the running pace calculator and read VDOT training paces explained, and to understand why most of your running should stay genuinely easy, read the 80/20 running approach. If 10K is still a stretch today, start with the 8-week first 10K plan and come back to this one.