When Should You Start Marathon Training?

By Stride Editorial TeamFact checked Aug 17, 2026

Count back from your race day: most first-time marathoners should start structured training 18 to 20 weeks out, runners with a base and a race or two behind them do well on 16 weeks, and experienced marathoners can sharpen in 12. If you're starting from little or no regular running, add 8 to 12 weeks of base building before the plan even begins. The most common marathon mistake isn't a bad workout, it's starting the clock too late and trying to cram fitness that only accumulates slowly.

The timeline by experience level

Brand new to running (or returning after years off): 6+ months total. Before a marathon plan makes sense, you want to be running 3 to 4 days a week comfortably, with a long run around 6 to 8 miles. Getting there from zero takes 2 to 3 months of base building. Then start an 18-to-20-week first-finish plan. Rushing this stage is where injuries come from; mileage your legs haven't earned yet is the classic overuse setup.

First marathon with a running base: 18 to 20 weeks. If you already run regularly and have maybe raced a 5K or 10K, an 18-to-20-week build gives you room for gradual long-run progression, step-back weeks, and a proper taper, with slack for a cold or a busy work stretch. Compare the complete 18-week four-day plan with the 20-week marathon training plan.

Second or third marathon, or strong half marathoner: 16 weeks. This is the sweet spot for most trained runners and the most common plan length for good reason. Our 16-week marathon training plan page walks through what those weeks actually contain.

Experienced marathoner with consistent year-round mileage: 12 to 14 weeks. When the aerobic base never went away, the buildup is really a sharpening block: race-pace work, peak long runs, taper. The complete 12-week marathon training plan starts at 25 miles with a 12-mile long run, so it only makes sense if that opening week is already close to your current training. Twelve weeks from the couch is not a shortcut.

Open the schedule that matches your runway

These are complete fixed four-day schedules, not phase summaries:

The number of weeks is only one constraint. Before you choose, compare the first week's mileage and long run with what you have completed recently. If the opening week would be a sharp jump, take the longer runway.

Why longer is usually safer than shorter

Marathon fitness is mostly aerobic volume, and aerobic volume compounds slowly. The standard guidance of increasing weekly mileage gradually exists because tendons and joints adapt slower than your cardiovascular system; feeling fit in week 4 doesn't mean your legs are ready for week 10. A longer runway also buys insurance. Over 16+ weeks, almost everyone gets sick once, travels once, and has one bad week. Plans with step-back weeks absorb that; an 10-week cram does not.

The flip side: starting too early has costs too. Peak marathon fitness holds for a handful of weeks, not months. A 30-week "plan" usually means either burning out in the middle or plateauing before the taper. If your race is very far out, stay in base building and start the structured block at the right distance from race day.

Work backward from a real race

Timing gets concrete when the date is real. A few examples from races Stride builds plans for:

  • Fall races like the Marine Corps Marathon (late October) and NYC (early November) put an 18-week build's start in late June or early July, meaning most of the buildup happens in summer heat. Train by effort and trust that cool race-day air gives the pace back.
  • Winter races like Houston (January) and Honolulu (December) start their builds in the fall, and your biggest weeks land near the holidays. Pick a plan that fits your real schedule, not an idealized one.
  • Spring races like Boston (April) and LA (March) mean winter buildups: treadmills, layers, and darkness during peak weeks. Plan for it rather than being surprised by it.

This is the exact problem Stride was built around. Choose your race, then share your current mileage, recent longest run, marathon experience, goal, and available run days. Those answers decide which plans rank first. After you choose one, Stride dates every workout through race day and sets training paces from your recent PRs. You can adjust, swap, or rewrite workouts when training changes.

What if the race is closer than the ideal runway?

Be honest about your base. A trained runner can finish well off 12 weeks. A newer runner 10 weeks out faces a choice: run it conservatively as a finish-only goal (with a plan that respects where you are), or pick a later race and arrive strong. There's no shame in the second option; races happen every month. See how apps handle compressed timelines in our first marathon app guide.

FAQ

How many weeks do I need to train for a marathon? 16 weeks is the standard for runners with a base. First-timers should plan 18 to 20; experienced marathoners can do 12 to 14. Starting from no running at all, budget 6 or more months including base building.

Can I train for a marathon in 12 weeks? Yes, if you already run consistently and have marathon or strong half marathon experience. From a thin base, 12 weeks forces mileage jumps your legs haven't earned, which is how overuse injuries happen.

How many miles a week should I be running before starting a plan? A comfortable 15 to 20 miles per week across 3 to 4 runs is a solid launch point for a first-marathon plan. Below that, spend a few more weeks base building first.

Is it bad to start training too early? Mostly it's inefficient. Peak fitness doesn't keep for months, and very long structured builds invite staleness or injury. Better: base build until you're the right number of weeks out, then start the block.

When should I start training for a fall marathon? For an October or November race, an 18-week plan starts in June or July. Stride does this arithmetic for you: pick your race, get matched, and every week from today to race day is mapped.

Build My Plan →