Race Prep

Marathon training plan for beginners: 16 weeks that adapt

Nikolai Madlener Nikolai Madlener Oct 30, 2026 11 min read
Marathon training plan for beginners: 16 weeks that adapt

The topic at a glance

  • ✓ Most marathon plans run 16 to 20 weeks; beginners starting from very little running should allow closer to six months.
  • ✓ Marathon Handbook's 16-week plan peaks at about 68 km (42 miles) a week, with a longest run of 32 km (20 miles).
  • ✓ Raising weekly distance by more than 30% over two weeks came with a higher rate of distance-related injuries in a study of 874 novice runners, though the difference was not statistically significant and the authors call the finding exploratory.
  • ✓ The long run and easy runs carry a first build, a weekly quality session matters once you chase a time, and missed sessions are never stacked onto the next week.
  • ✓ A meta-analysis found the best results with a taper of about two weeks in which volume drops by 41 to 60% while intensity and frequency stay.

How long should a first marathon build be?

Ask five plans how long a first marathon build should take and you get one answer with soft edges: most plans run between 16 and 20 weeks. Runner’s World puts the typical plan at 16 to 20 weeks and advises true beginners to add one to two months of base training on top of it, Runstreet works with 12 to 16 weeks depending on your level, and HIGH5’s guidance spans 16-week plans for experienced runners up to six-month schedules for beginners. The ranges agree more than they differ: you need months of gradual loading for your heart, muscles, tendons and ligaments to adapt to 42.2 km (26.2 miles), and rushing that process is where injuries come from.

SourceTypical build lengthWho it fits
Runner’s World16 to 20 weeksMost runners; true beginners add one to two months of base work
Runstreet12 to 16 weeks12 weeks for runners who can already run 10 km (6 miles); 16 weeks for first-timers
HIGH516 weeks to 6 months16-week plans for experienced runners; beginners closer to 6 months
Marathon Handbook16 weeksRunners who can run 8 km (5 miles) without stopping and run 3 to 4 times a week for 30+ minutes

A 16-week plan assumes a starting point, and it is worth checking yourself against it before you commit. The Marathon Handbook’s 16-week plan expects you to run 8 km (5 miles) without stopping and to already run three or four times a week for 30-plus minutes without injury. ACTIVE’s coach Pete Rea asks first-timers for a minimum of six weeks running 29 to 39 km (18 to 24 miles) per week before the final 12-week specificity block even begins. Runstreet’s shorter 12-week option asks that you can already run 10 km (6 miles) before you start. If that is not where you are yet, build your base first and let the 16-week clock start once the foundation is there.

Choose the longer build when your base is thin or your calendar is heavy. Longer, more flexible cycles leave room for work travel, personal conflicts and illness. The Marathon Handbook makes the same point in planning terms: sixteen weeks gives most runners enough time to absorb one or two lost weeks and still taper properly.

One practical rule ties the choice together: let race day set the calendar, and count backwards from there. Your race date fixes the taper, the peak long run and the peak weeks, and the calendar you can honestly protect decides whether 16 weeks is realistic or optimistic. If the maths only works when nothing goes wrong, start earlier.

The four phases of a 16-week plan

Almost every structured marathon plan, whatever its length, moves through the same four phases: base, build, peak and taper. The Marathon Handbook lays the 16-week version out cleanly, and it is a useful skeleton even if your own plan shifts the week boundaries slightly. At its peak, that plan reaches about 68 km (42 miles) a week, with a longest run of 32 km (20 miles).

PhaseWeeksWhat the weeks look like
Base1 to 6Easy-dominant volume, the long run grows from roughly 6 to 8 km (4 to 5 miles) toward 14 to 18 km (9 to 11 miles), weekly threshold work appears
Build7 to 12Marathon-specific work: marathon-pace progression, threshold intervals, the long run climbs to 28 to 32 km (17 to 20 miles)
Peak13 to 14Highest specificity and load, the biggest long runs land here, two to three weeks out from race day
Taper15 to 16Volume drops while intensity and frequency hold, race day sits at the end of week 16

Runstreet describes the same logic from the session side: base runs at a relaxed, conversational effort form the foundation, and one long run per week grows gradually, with benchmark workouts along the way. The long run is the spine of the build; everything else arranges itself around it.

The injury math behind gradual progression

The reason coaches keep the build gradual is not caution for its own sake. In a one-year prospective cohort study, 874 healthy novice runners were given GPS watches and followed; those who increased their weekly running distance by more than 30% over a two-week period showed a higher rate of distance-related injuries such as patellofemoral pain, iliotibial band syndrome and medial tibial stress syndrome than runners who kept progression under 10%, with a hazard ratio of 1.59 (95% CI: 0.96 to 2.66). The confidence interval crosses 1, and the authors describe the study as exploratory, calling for randomised trials to confirm the finding.

Read practically, that means two things for your 16 weeks: progression stays gradual, and easier weeks sit between build blocks so your tendons and ligaments keep up with your cardiovascular fitness. Treat the volume ranges here as coaching guidance to frame your own plan, and talk to your own healthcare provider if you have an injury history.

Which sessions matter most each week

Before a week goes wrong, it helps to know which sessions are load-bearing and which ones can bend. A marathon week typically has three kinds of running plus rest and strength work, and they are not equally replaceable.

  1. The long run: one per week, the session that builds the endurance and the race-day confidence a marathon demands. Runstreet suggests placing it on a Saturday or Sunday, on a day when you are not working or doing anything else demanding, and says the schedule can move to fit your life.
  2. Easy runs: most of the week’s volume. These are relaxed-pace runs where you can hold a conversation and the effort feels like a 4 or 5 out of 10 on the Rating of Perceived Exertion scale. They build your aerobic engine and add volume without adding much recovery cost.
  3. One quality session: tempo runs or intervals, mainly for runners chasing a time goal such as a sub-4-hour marathon, where speed work is what moves race pace. Performance Bullet’s sub-4 plan schedules a tempo or interval session every week and keeps the long runs easy, with the long runs doubling as a chance to practise race-day fuelling.

If you are training for your first finish rather than a time, the quality session is the one to defer. Runstreet’s Marnie Kunz is direct about this: novice runners usually do not need speed training, because the focus should be on building endurance and completing the distance. HIGH5’s guidance points the same way for beginners, prioritising a conversational pace and a gradual build.

The overall shape of the week follows what exercise scientists call polarised or 80/20 training: roughly 80 percent of your running at easy, conversational effort and a small share at threshold or above. The Marathon Handbook cites the Seiler 80/20 distribution as outperforming threshold-only and pyramidal distributions in trained distance runners. When a busy week forces a cut, protect the long run, keep the easy runs easy, and let the quality session be the first thing to move.

What to do when a week falls apart

Sixteen weeks is long enough that something will go wrong: a cold in week 9, a work trip over a planned long run, three short nights in a row. A build that survives is one with rules ready before the week goes sideways.

  • Illness: let your symptoms decide rather than the calendar, and build again only once you are symptom-free; our guide to being sick during marathon training covers the return step by step.
  • Travel or a busy stretch: move the long run to another day rather than dropping it, as long as it lands on a day without other demands. If it cannot move, shorten it. A 90-minute version of a planned two-hour run keeps the rhythm without the recovery cost.
  • Poor sleep: when a short night lands before a hard session, make the day lighter, for example an easy run instead of intervals, and pull your evening routine earlier.
  • A missed session: skip it and move on; the next week continues from where you are.

Runner’s World makes the same case from the other side: a writer who skipped a planned long run during a marathon build found it benefited the training, and run coach Angie Spencer’s view is that running has to be a flexible sport. Pushing through fatigue only to tick a box is what raises the risk of overtraining and injury.

A niggle gets its own rule: a rest day and a reassessment rather than pushing through. Constant soreness, nagging aches and lingering fatigue are worth treating as overtraining risk, a signal that the plan needs adjusting rather than that you need more willpower. For a deeper look at how a plan can read recovery signals and adjust the week, see our guide to recovery-based workout planning.

Using sleep and recovery data in the plan

If you wear a Garmin, an Oura or another wearable, you already collect the numbers that make these calls easier: heart rate variability (HRV), resting heart rate and sleep duration. The useful question is how today’s readings sit relative to your own baseline. A dip in HRV alongside a raised resting heart rate after a hard interval session tells a consistent story; one red number after a late night tells a much weaker one.

  • Look at HRV, resting heart rate and sleep duration together, against your own normal, rather than reacting to a single score.
  • When the data and your legs agree, train as planned. When they disagree, let how you feel break the tie and keep the harder session for another day.

The data has limits, and it is worth naming them. Wearables inform the easy-versus-hard call; they do not replace how your legs feel during the warm-up, and they do not replace what your own healthcare provider advises about an injury or illness. Research supports the general idea: a systematic review with meta-analysis found that HRV-guided endurance training had a significant medium positive impact on submaximal physiological parameters compared with predefined training00108-0/fulltext), but the reading still needs a human decision on top.

Wearable data and your calendar are most useful when they feed the plan directly, instead of leaving you to interpret three apps every morning. For the mechanics of turning HRV into training decisions, our HRV-based training adjustments guide goes deeper, and our sleep optimization overview covers how sleep data turns into decisions.

Race week and the taper

The last weeks of a 16-week plan look different on purpose. Most marathon builds taper over the final two to three weeks after the last long run, and the outline above uses two, and Mayo Clinic Health System describes the taper as the period of reduced training before a race that lets your body recover while staying race-ready. The goal is arriving at the start line with fresh muscles, full glycogen stores and less psychological stress from training.

  • Volume drops, sharply: a meta-analysis of 27 studies in Medicine & Science in Sports & Exercise found performance gains when training volume is progressively decreased by 41 to 60% over about two weeks.
  • Intensity and frequency stay the same: keep the same number of sessions and the same paces, and shorten each session instead.
  • Race day and the taper stay in place, even when earlier weeks fell apart. The taper is where the build banks the work you did.

The short version is enough here: trust the cut, keep the rhythm, and let the fresh legs be the plan.

Your first marathon with miora

Everything above describes a build that works when the weeks cooperate. A fixed PDF plan cannot see the short night before your long run, the HRV dip two days after intervals, or the business trip that lands on week 10. It just prints the sessions and leaves the judgement to you, on the mornings when you have the least capacity for it.

Many first-timers download a free plan before week one: a Hal Higdon novice schedule, a Runna plan, a sheet from the running club. That plan can stay. Send it as a PDF or screenshots to miora, and from then on miora reminds you of each session in iMessage or WhatsApp, counts the runs your watch sends to Apple Health and shifts days when the week falls apart. No plan yet? Give miora your race date and the days you can run, and it builds the 16 weeks backwards from race day with lighter weeks and a taper, then checks every Sunday what you ran and adjusts the weeks ahead.

Example chat, written for this article to show how it works:

  • You: signed up for my first marathon, it’s on 26 april. I can run 4 days a week
  • miora: amazing. your 16 weeks are built backwards from race day and week 1 is in the app. tuesday: 30 minutes easy, conversational
  • You (week 10): two short nights in a row, legs feel heavy
  • miora: then today’s run becomes 40 minutes easy. sunday’s long run stays, we’ll check in on saturday

If your first marathon is on the calendar, open the iPhone app or getmiora.com, start with miora Essential, connect your watch and calendar, and send miora the race date or the plan you downloaded. miora Concierge adds a team of longevity clinicians on top, by application, if you want people involved from week one.

Frequently asked questions

How many weeks do I need to train for a first marathon?

Most plans run 16 to 20 weeks, the range Runner's World gives for a typical plan; Runstreet's plans run 12 to 16 weeks by level, and HIGH5 spans 16-week plans for experienced runners up to six months for beginners. Starting from very little running, allow closer to six months so the volume can build gradually.

How much should a beginner run per week in marathon training?

Marathon Handbook's 16-week plan expects that you can run 8 km (5 miles) without stopping, three or four times a week, and peaks at about 68 km (42 miles), with a longest run of 32 km (20 miles). The right number depends on your running history; gradual progression matters more than any single figure.

What happens if I miss a week of marathon training?

You do not make it up: pick the plan up where it is now, and after illness build again only once you are symptom-free.

Should beginners do speedwork in marathon training?

Not necessarily. Runstreet's Marnie Kunz notes that novice runners usually do not need speed training; the focus is building endurance. Speedwork becomes relevant when you chase a time goal, such as a sub-4-hour marathon, where plans add a weekly tempo or interval session.

How long should my long run be, and how fast?

Many beginner plans build the long run toward a peak of around 32 km (20 miles), once per week, ideally on a day off work. Run it at an easy, conversational pace, so the session builds endurance without leaving you flat for the rest of the week.

What is the marathon taper and how much do I cut?

The taper is the final stretch of two to three weeks after your last long run. A meta-analysis of 27 studies found the best results with a taper of about two weeks in which training volume drops progressively by 41 to 60% while intensity and frequency stay the same: shorter runs, the same number of sessions and the same paces.

How is an adaptive marathon plan different from a fixed plan?

A fixed plan is a calendar written months ahead; an adaptive plan changes with your week as it unfolds. When sleep, HRV or resting heart rate show you have not recovered, the day gets lighter, and lost sessions are dropped instead of stacked onto the next week.

Sources

Stop managing your health. Let miora run it.

Explore more articles

All articles