The honest answer depends entirely on where you are starting. A runner who is already comfortable with 30 km weeks needs a different timeline than someone who has not run since high school. The good news is that the ranges are well established, and you can probably figure out which one applies to you in 30 seconds.
Here is the breakdown by starting point.
If you have never really run before: 9 to 12 months
The training plan you actually need is not a marathon plan. It is a base-building plan that turns into a marathon plan. Start with three to five months of building up to where you can run continuously for 45 to 60 minutes, three to four times a week. Once you can do that without falling apart, the marathon-specific 16-to-20-week block can begin.
Compressing this is the single most common way runners get injured before the start line. The musculoskeletal adaptations that let you absorb three to five hours of running take real time. Tendons especially. Patience is the cheat code.
If you can already run 30 minutes continuously: 16 to 22 weeks
This is the sweet spot for most first-time marathoners. The standard programs (Hal Higdon's Novice plans, Pete Pfitzinger's beginner builds, Jack Daniels' marathon plans) all live in this range. Eighteen to twenty weeks gives you room for a four-phase build: base, aerobic strength, marathon-specific, and taper, each with enough time to deliver its adaptation.
Sixteen weeks is the minimum that still gives the marathon-specific phase enough room to do its job. Anything shorter compresses the long-run progression into a window too tight to absorb safely.
If you ran a marathon before (within the last 2 years): 12 to 16 weeks
Your aerobic base is still there, even if it has gone quiet. A returning marathoner can compress the build because the base phase is shorter. Twelve weeks is feasible if you can already log 30 to 40 km per week comfortably. Sixteen is the more comfortable number that gives the long runs room to grow without rushing.
The risk with returning runners is overconfidence. The body has muscle memory for the running pattern, but the tendons and bones often need to be re-acclimated to the load. Treat the first three weeks as a re-introduction phase, not a starting point.
If you are training for a time goal (not just to finish): 16 to 24 weeks
Chasing a Boston qualifier, sub-3, or a meaningful PR needs the longer end of the range. Time-goal training adds three things to a standard plan: more total volume, more quality work at threshold and marathon pace, and a more structured taper. All of those are time-consuming to build correctly.
Coaches who specialize in time-goal marathons (Pfitzinger and the Hanson brothers, for example) routinely build 18 to 24-week cycles for amateurs aiming at specific finish times.
What "training" actually looks like, week by week
A typical week in a beginner marathon plan has four or five runs and one day of cross-training, with two days fully off. The pattern is usually:
- 2 to 3 easy runs per week (the foundation of the plan, run at conversational pace)
- 1 quality run per week (a tempo, intervals, or progression run, more in the back half of the build)
- 1 long run per week (the centerpiece, grows gradually to a peak of 30 to 35 km about 3 weeks before race day)
- 1 cross-training day (bike, swim, strength, anything low-impact)
- 2 rest days (genuine rest, not "active recovery" that is actually exercise in disguise)
Beginner peak weekly mileage usually lands between 40 and 55 km (25 to 35 miles). You do not need 100 km weeks to finish your first marathon. You need consistent 40 to 50 km weeks for 12 or more weeks.
The three-week rule
Whatever timeline you pick, build it in three-week blocks. Progress for two weeks, then take an easier cutback week with about 70 to 80 percent of the previous week's volume. This rhythm gives the body time to absorb training rather than just accumulating fatigue. Without it, the load curve climbs straight up, and at some point past week 8, the climb becomes a cliff.
What can compress the timeline, what cannot
Things that legitimately compress a marathon build:
- Recent aerobic base. If you are coming off serious training in a different sport (cycling, swimming, cross-country skiing), the cardiovascular adaptations transfer. Your running-specific tendons still need time, but the engine is there.
- Recent marathon or ultra experience. The neuromuscular pattern is there. You can build back faster.
- Young age and good genetics. Boring but true. Adaptation timelines are faster in your twenties than in your fifties.
Things that do not compress it, no matter what you read on the internet:
- "I am in great shape from CrossFit." Strength does not transfer well to marathon-specific aerobic endurance.
- "I ran a half marathon last month." A half is a different physiological event. The marathon adds two hours of running on tired legs, which is the actual challenge.
- "I will just run a lot in the next 8 weeks." The fastest path to a stress fracture.
What to do once you know your timeline
Pick a race date, count back, pick the right plan length for where you are starting. Smart Runner's first-marathon plan auto-sets the build length based on your race date and current weekly distance from Apple Health. If you have already done a marathon and want a tighter build, the 16-week plan uses Pfitzinger's mesocycle structure.
The structure is the easy part. The hard part is the next four to six months of showing up.