A 16-Week Marathon Training Plan for Your First 42.2K
This plan is for a first marathon, not a fast one. The goal is finishing strong and staying injury-free, not chasing a specific time, there will be time for a faster marathon once you know what a first one actually demands of you. It assumes you can currently run a half marathon distance, or close to it, and have a running base of at least 15-20 km a week. That base isn't an arbitrary cutoff, 16 weeks is enough time to safely build from that starting point to marathon-ready volume, but it isn't enough time to build the base itself and then layer 42.2 km worth of long runs on top of it without a meaningfully higher injury risk. If you're newer than that, start with a half marathon first, and come back to this once that's behind you, a completed half marathon is close to the ideal springboard into this plan. Expect the time commitment to run from around 4-5 hours a week in the base phase to 6-8 hours a week at peak volume, then drop sharply through the three-week taper.
How this plan is structured
Four to five runs a week, with the long run as the clear centrepiece. Unlike shorter distances, marathon training success is mostly about accumulated weekly volume and the long run building safely over months, not about workout intensity, this is the opposite emphasis from a 10K plan, where two hard workouts a week do most of the work. Most runs in this plan are easy, deliberately so, the accumulated volume is what builds the aerobic and structural durability a marathon demands, and that volume only sticks if the majority of it is run at a pace your body can absorb without accumulating fatigue faster than it recovers. There's exactly one 32 km long run in this plan, most first-timer plans don't need to go further than that, everything before it exists to build toward that one effort safely, and everything after it exists to let you absorb it.
A few adjustment rules matter more here than in a shorter plan, because a mistake compounds over 16 weeks instead of 8 or 12:
- A single missed week from illness or minor travel disruption in the base or endurance phase (weeks 1-8) is rarely worth restructuring the plan for, resume from wherever the schedule currently is.
- An illness with a fever or chest symptoms is a full-stop signal at any point in this plan, running through it tends to extend the illness and risks a much longer setback than the days you'd lose to resting properly.
- Two or more consecutive missed weeks during the peak volume phase (weeks 9-12) usually means shifting the peak long run back by a week rather than compressing the remaining buildup to hit week 13 on schedule.
- Travel is manageable through week 12, a few easier days around a trip rarely undo months of accumulated volume. Travel that lands in weeks 13-16 is riskier only because there's so little time left to recover the routine, plan travel around this window if you have any control over your calendar.
The plan, phase by phase
| Weeks | Phase | Long run range | Weekly volume | Focus |
|---|---|---|---|---|
| 1-4 | Base building | 12-16 km | 25-35 km | Consistency, easy pace |
| 5-8 | Endurance | 16-22 km | 35-45 km | Long run progression |
| 9-12 | Peak volume | 24-30 km | 45-55 km | Longest runs, race-pace segments |
| 13 | Peak long run | 32 km | ~55 km | One final big effort |
| 14-16 | Taper | 16 km down to 0 | 40 km down to ~15 km | Recovery, race prep |
Choosing a marathon that fits this plan's timeline
Sixteen weeks is a long enough runway that it's worth being deliberate about which marathon you're building toward, rather than picking whatever's next on the calendar. Count backward from race day to set your week 1 start date, and give yourself a few days of buffer, if the math doesn't land on a clean Monday, start slightly early and treat the extra days as additional easy running rather than compressing the base phase to fit. Choosing a race date covers this in more depth if you're picking a race from scratch.
Course profile matters more over 42.2 km than it does at any shorter distance, a hilly marathon doesn't just add difficulty evenly, it adds disproportionate difficulty in the final third when your legs are least equipped to handle it. For a first marathon, a flat or gently rolling certified course is worth prioritising over a scenic but hilly one. Flat vs hilly course training and what makes a race certified both cover why this matters. Cutoff time deserves real attention too, marathon cutoffs vary more widely between events than half marathon cutoffs do, typically somewhere between 6 and 7.5 hours, and a tighter cutoff changes how conservatively you need to pace the first half of the race. Check it before you register, not after. Marathon cutoff times explained covers how organizers typically set these.
What easy pace and marathon-pace effort should actually feel like
The table above talks in terms of long run distance and weekly volume, but almost every run in this plan, including most of the long run, should be run at an effort rather than a fixed pace. Easy pace, which makes up the vast majority of your running in this plan, should feel genuinely conversational, an effort where you could hold a conversation in full sentences without gasping. This is the single hardest instruction in the entire plan for many first-time marathoners to actually follow, easy pace on a marathon plan often feels almost uncomfortably slow compared to what feels natural, and that discomfort is the point, not a sign you're doing it wrong.
Marathon-pace effort, when it shows up inside a long run during the peak volume phase, should feel like a pace you could hold for hours, not one you're straining against. It's meaningfully slower than half marathon or 10K race effort, a useful way to think about it is the fastest pace you could comfortably sustain a genuine conversation at, if only in short bursts. If a marathon-pace segment starts to feel like a tempo effort within a few kilometres, you're running it too fast for what it's meant to simulate.
What a realistic finish time looks like for a first-time marathoner
A first marathon's finish time depends heavily on pacing discipline in a way that shorter races don't punish as harshly, run the first half even slightly too fast and the final 10K can unravel far more dramatically than it would in a half marathon or 10K. Rather than fixating on a specific number before you've run a single week of this plan, use your long run pace from the peak volume phase (weeks 9-12) as a rough guide, and expect your even-paced marathon finish to land somewhat slower than that per-kilometre pace, not faster, the distance and accumulated fatigue see to that. Most first-time marathoners following a structured plan like this one finish somewhere in the 4:30 to 5:30 range, with the biggest determinant of where in that range you land being pacing discipline in the first half rather than raw fitness. Understanding race splits and pacing, how to pace a negative split, and hitting the wall explained are worth reading in the final few weeks before race day, once your fitness is largely set and pacing strategy is what's left to control.
Why the peak long run is 32 km, not 42
You don't need to run the full marathon distance in training to finish it on race day, and trying to do so adds injury risk without a proportional benefit, the marginal fitness gained from running past 32-34 km in training rarely outweighs the extra weeks of recovery and elevated injury risk it demands. A 32 km long run, done 3 weeks before race day, builds enough endurance and mental confidence that the final 10 km on race day is genuinely new ground but not unknown territory. What gets you through those last 10 km is the accumulated fitness of the whole 16 weeks, not any single long run, race-day adrenaline, a taper-freshened body, and the mental rehearsal of having run tired before all combine to carry you further than the raw training numbers might suggest on their own.
Fuelling your long runs matters as much as running them
Any long run past 90 minutes needs fuel during the run, not just before and after, your body's stored carbohydrate runs low well before your legs do, and running out mid-run is a common, avoidable way a good training block turns into a miserable final hour. Practice your race-day nutrition strategy on long runs from week 9 onward, treating those long runs as full dress rehearsals rather than just distance to accumulate, how to fuel a marathon covers what and when in detail. Hydration deserves the same rehearsal, particularly training through Indian heat or humidity, hydration planning for race day and electrolytes for runners cover what a long run past two hours actually requires beyond plain water. Race day is never the right time to try a new gel, drink, or fuelling schedule for the first time, whatever combination gets you through your week 12 or week 13 long run without stomach trouble is what you carry into the race.
Gear that earns its place over 16 weeks
Sixteen weeks is long enough that gear decisions matter differently than they do for a shorter plan, what you wear in week 1 doesn't need to survive to race day unchanged, and testing changes early gives you time to react if something doesn't work. Shoes are the biggest one, most marathon plans benefit from rotating two pairs rather than running every session in one, and it's worth having your race-day pair broken in with at least 60-80 km on it before race day, not brand new. How to choose running shoes for your first race covers the basics. Chafing and blisters, minor annoyances at 10K, become genuine race-ending problems at marathon distance and duration, so anything that causes friction needs solving in training, not discovered at kilometre 30. How to prevent chafing and blister prevention for runners are worth reading well before your first 20+ km long run, not after one goes badly.
Strength and cross-training alongside 16 weeks of running
The two rest days in this plan matter more the longer the plan runs, 16 weeks of accumulating volume without adequate recovery and support work is a considerably longer window for a small imbalance to turn into a real injury than an 8 or 12-week plan gives you. Two short strength sessions a week, 20-30 minutes each, built around hips, glutes, and core, meaningfully reduce that risk, and are worth treating as part of the training plan rather than an optional extra squeezed in if time allows. Strength training for runners has a routine that fits alongside a marathon buildup without adding meaningful fatigue.
Cross-training has a real place here too, particularly in the base and endurance phases, where a low-impact session (cycling, swimming, an elliptical) on a non-running day can add aerobic work without adding to the accumulated impact your legs are absorbing from the growing long run. It's less useful, and can actively work against you, in the two to three weeks immediately before the peak long run and in the taper, when the priority shifts from building fitness to arriving fresh. If a niggle shows up anywhere in the plan, cross-training for injured runners covers how to maintain fitness without training through something that needs rest instead.
Trust the taper
Three weeks is a longer taper than most shorter-distance plans use, and that's deliberate. The marathon's demands on your body accumulate over months, and it takes longer to fully absorb that training and arrive at the start line fresh than a half marathon or 10K plan's shorter taper allows for. Weekly volume drops in stages rather than all at once, roughly 40-60% by the final week, while intensity and running frequency stay closer to normal, the goal is shedding accumulated fatigue without losing the neuromuscular sharpness that comes from still running regularly. Cutting the taper short to fit in one more big week is one of the most common ways first-time marathoners undo months of good training in the final stretch, the fitness from that extra week rarely outlasts the fatigue it adds, and it's the fatigue that's still there on race morning.
16 weeks from today puts you close to race day. Find one that fits.
Browse marathonsThe organizers I've spoken with who track DNF (did not finish) rates consistently see the same pattern: it's rarely the runners who trained the least who don't finish, it's the ones who trained hardest in the final two weeks, trying to bank fitness that doesn't actually bank that way. If you're tempted to add a long run in week 15, that instinct is exactly what this plan's taper exists to override. The other pattern that comes up often in conversations with organizers is race selection, first-time marathoners who choose a hillier or more exposed course because it's more scenic or more prestigious show up disproportionately in the slower finish times and the medical tent conversations, even when their training block looked identical to someone who chose a flatter one. I've also noticed that the runners who message closest to race week asking detailed questions about pacing and fuelling are almost never the ones who struggle on the day, the ones who go quiet in the final month tend to be the ones who skipped the parts of a plan like this that felt boring, easy runs and gear testing, in favour of the parts that felt productive. None of it comes down to raw ability nearly as often as it comes down to whether the boring 80% of the plan got the same respect as the exciting 20%.
Frequently asked questions
What if I miss a week of training due to illness or travel?
One missed week in a 16-week plan is rarely a problem, resume where the schedule currently is rather than trying to make up lost mileage. Two or more consecutive missed weeks in the base or endurance phase may mean shifting your peak long run back by a week rather than compressing the buildup.
Do I need to run a marathon-pace segment in training?
It helps but isn't essential for a first-timer whose main goal is finishing. If you want to include it, add 5-8 km at your target marathon pace inside one long run every two weeks during the peak volume phase, not more often than that.
How many rest days does this plan include?
Two per week throughout, non-negotiable ones. Marathon training injuries usually come from accumulated fatigue, not any single hard run, and rest days are where the adaptation from training actually happens.
Should I taper my diet along with my mileage?
Not your overall eating, but your carbohydrate intake typically increases slightly in the final 2-3 days before race day as your mileage drops. [[Carb loading explained|/blog/carb-loading-explained]] covers how to do this without overdoing it.
What's a realistic finish time for my first marathon?
It depends more on pacing discipline than raw fitness at this distance. Most first-time marathoners following a structured 16-week plan like this one finish somewhere in the 4:30 to 5:30 range, and the biggest factor in where you land is whether the first half was run conservatively rather than how fast training felt in isolation. [[Understanding race splits and pacing|/blog/understanding-race-splits-and-pacing]] is worth reading once your training is largely finished and pacing strategy is what's left to plan.
Do I need to run the full 42.2 km at some point before race day?
No, and doing so is more likely to hurt your race than help it. This plan peaks at 32 km specifically because the fitness and confidence gained from running further rarely outweighs the extra recovery time and injury risk it adds. The accumulated training across all 16 weeks, not any single long run, is what carries you through the final 10 km on race day.
I'm already struggling to fit in the running, is strength training really necessary?
If time is genuinely tight, shorten the strength sessions rather than cutting them, 10-15 minutes of targeted hip and glute work twice a week still meaningfully lowers injury risk over 16 weeks. It's a better trade than skipping strength entirely to protect an easy run, since an overuse injury costs far more training time than a shortened strength session ever would. [[Strength training for runners|/blog/strength-training-for-runners]] has a shorter version of the routine.
My long runs feel fine but I'm exhausted the rest of the week, what does that mean?
It usually means the easy runs around the long run aren't easy enough, or sleep isn't keeping pace with the added training load, both are common in the endurance and peak volume phases. Check your easy pace against a genuine conversational effort first, then look at sleep, marathon training asks more of your recovery than most first-timers expect. [[Sleep and recovery for runners|/blog/sleep-and-recovery-for-runners]] covers what to prioritise when the two are in tension.