Running your first full marathon is one of the most common entries on a bucket list — and a good first marathon training plan is what turns that dream into 42.195 kilometres you actually run. The truth almost no one tells you is that the finish line is reached through structure, not sheer willpower: a weekly rhythm, a fixed race date, a long-run ladder, a saved fund, and a captured moment. This guide walks you through all seven, calmly, one piece at a time.
Which training plan should a beginner follow?
Most first-timers should follow Hal Higdon's Novice 1 plan. It is the canonical beginner blueprint: 18 weeks, four runs per week, no complicated speed work. It asks only that you keep showing up. Its long runs build gradually and its rest days are non-negotiable, which is exactly what a body new to marathon distance needs.
The reason this plan works isn't secret intensity — it's steadiness. Three short weekday runs, one long run on Saturday, two rest days, and gentle cross-training on Sunday. Everything is arranged so that consistency, not heroics, carries you to the start line.
How many weeks do I need to train?
Plan for eighteen weeks. That's the length of Novice 1, and it's roughly four months of preparation that lets your mileage climb safely — never more than about 10% per week — with a recovery week built in every third week. Eighteen weeks is enough to earn the distance without rushing your body toward injury.
Those eighteen weeks aren't padding. They're what let a 9.7 km long run grow into a 32.2 km peak without breaking you. If you're staring at the calendar wondering whether it's too long, remember: the weeks are doing the work you can't fake.
What does a typical training week look like?
A typical week has a simple shape: rest Monday, a short run Tuesday, a "sorta-long" run Wednesday, another short run Thursday, rest Friday, your long run Saturday, and easy cross-training Sunday. Weekday runs start at about 4.8 km and build toward 8 km; Wednesday grows from 4.8 km up to 16.1 km over the plan.
This is your first tracked piece: the habit of running four times a week. The Tuesday/Wednesday/Thursday runs plus that Saturday long run form a rhythm you repeat for eighteen weeks. Treat it as a streak you're protecting rather than a table you're obeying. When a run feels optional, the streak answers for you — and that's the point. Willpower is unreliable; a rhythm you've kept for six straight weeks quietly becomes who you are. Marking each of the four runs done, week after week, is how consistency stops being a decision and starts being a default.
How far does the long run go — and how do I know I'm ready?
The Saturday long run rises from 9.7 km in week one to a 32.2 km peak in week 15, then tapers before the 42.195 km race. You know you're ready not by the calendar but by the level you're standing on: once you've completed a 25.7 km and then a 32.2 km run, the marathon distance stops feeling theoretical.
This is your skill ladder, and it's the heart of the plan. Think of the long run as four levels of earned capability. Base takes you from 9.7 to 16.1 km. Half-Marathon carries you to 19.3 km and the raced half in week 8. Peak stacks 24.1, 25.7, 29.0 and 32.2 km. Race Day is the 42.195 km itself. Each long run is a milestone you tick off. A beginner doesn't need to know "week 13 equals 29 km" — they need to feel "I'm in the peak block now, and I've already run 25.7 km." That's what finally gives the question am I ready? a visible, honest answer. Run these at a conversational pace; there is genuinely no such thing as too slow, and walking through aid stations is completely legitimate.
How does having a fixed race day keep you on track?
A fixed race date turns eighteen abstract weeks into a countdown with checkpoints. The date doesn't move, so your training organises itself around it: the week-8 half-marathon test, the 29 km run in week 13, the 32.2 km peak in week 15, the start of your taper, and finally race morning. Each milestone tells you exactly where you stand.
This is your deadline, and it's oddly freeing. When the date is fixed and the milestones are counting down, you stop negotiating with yourself. You're not asking whether to run — you're asking how many weeks remain until the half-marathon test, or how close the peak long run is. The countdown carries the motivation so you don't have to manufacture it each morning. Choose your race and lock the date in first — everything else in this 18-week plan hangs off it.
How many kilometres will you run in total — and what are stepback weeks and tapering?
Across the full eighteen weeks you'll cover roughly 700 km (about 435 miles), including the week-8 half-marathon test. That means you run 700 km before you ever reach the start line. Every third week is a stepback week with reduced mileage for recovery, and the final three weeks taper your volume down so you arrive fresh.
This is your cumulative metric, and watching it grow is quietly powerful. Stepback weeks aren't setbacks — they let your body absorb the work. The taper feels counterintuitive because you run less right when the race looms, but that rest is what lets your legs unload their training on race day. Seeing the total tick past 300, then 500, then 700 km reframes the whole journey: by race morning you've already done the hard part many times over. The marathon is just the celebration lap of a distance you've quietly banked for months.
What does a marathon actually cost, and how do you fund it?
Budget $300 to $600 all in. Good shoes run $100–140 and should be replaced every 480–800 km, so you may need two pairs across the plan. Add race entry, kit, and fuel, and the real total lands in that range. Saving toward it steadily means race week arrives paid-for and stress-free.
This is your fund, and it deserves a section because money quietly derails good intentions. Set aside a little each week toward entry, shoes and gear so the cost never becomes a wall between you and the start line. Test your fuel — 30 to 60 g of carbs per hour — on two or three long runs so the gear you buy is gear you trust. A funded plan is one less reason to postpone the dream.
Should you race a half marathon during training, and how do you handle race week?
Yes — week 8 has no long run, and racing a half marathon (21.1 km) in its place is the ideal way to test your pace, fuel and nerves in a real event. Then, in the final week, work through a simple checklist: bib pickup, gear laid out, carb-load schedule, and fuel you've already tested. The golden rule is nothing new on race day.
This is your race-week checklist, the low-drama finale to eighteen weeks of work. Carb-loading begins about five days out, around 8 g of carbs per kilogram of body weight per day. Lay everything out the night before. Pin the bib. Confirm the fuel is fuel you've rehearsed on long runs. The checklist exists so that on race morning your only job is to run — every decision already made, calmly, in advance.
Why does the finish-line photo matter?
The finish-line photo is the single captured moment that proves everything held together — the habit, the ladder, the date, the fund and the checklist all converging as you cross the line, typically somewhere between 4:30 and 5:30 for a first-timer. It's not vanity; it's the closing of a loop you opened eighteen weeks earlier.
This is your captured experience, and it's worth planning for deliberately. Note where the official photographers stand. Tell a friend which corner to wait at. That one image becomes the anchor of the whole story — proof that a bucket-list dream, broken into seven honest commitments, actually got done. Long after the soreness fades, the photo remains the moment you can point to and say: I did that.
When you're ready to stop reading about it and start living inside the plan, set up your first marathon as a bucket-list goal in DreamPaths — the weekly rhythm, the long-run ladder, the race date, the mileage, the fund, the race-week checklist, and the finish-line photo, all in one calm place. The grid tells you what to run; these seven commitments are what keep you running it.