Can You Train for a Marathon in 12 Weeks? It Depends on These 3 Things

Yes, if you already run. Three things decide it: your base today, how fast your long run can grow, and whether you want to finish or hit a time.

You registered late. The race is 12 weeks out. Now you’re wondering if that’s enough. For some runners it is. For others it’s a fast track to a sore knee and a DNS.

Thing 1: Who Can Train for a Marathon in 12 Weeks

Think of your running base as a bank balance. Twelve weeks can’t make a big deposit. It can only invest what you already have.

Here’s a rough guide. It’s a coaching heuristic built from the research below. It is not a published cutoff.

In short: if you can run a half marathon distance comfortably, you’re in. If a 10 km run still feels big, you’re not.

The weekly volume matters because it tracks with results. A meta-analysis of 85 studies and 137 groups of runners found that faster marathon times go with higher weekly distance, more runs per week and a longer longest run (PubMed). Translation: the runners who already run a lot run faster. You can’t fake that in 12 weeks.

Injury odds matter too. In a 12-week study of first-time marathoners, 9.5% had a major injury and 49.2% a minor one. A major injury meant they couldn’t start or finish (HSS, Toresdahl). Even so, 99% of those who started finished (Healio report on the same study).

A separate study of Rotterdam marathon runners found 28.1% were injured in the 4 weeks before the race (van Middelkoop 2008).

Half of first-timers get something. Most still cross the line. That’s the trade.

Thing 2: How Fast Your Long Run Can Grow

Your fitness can grow faster than your tendons. That’s the catch with a short runway.

Picture a rubber band. Stretch it a little each week and it holds. Yank it hard once and it snaps. Your legs work the same way.

The old advice is the 10% rule: add no more than 10% to your weekly distance. The evidence is mixed. Among 874 novices, jumps over 30% a week had a hazard ratio of 1.59 for injury (Nielsen 2014). But the confidence range was 0.96 to 2.66, so it crossed “no effect.” Treat it as a warning trend, not proof.

Newer data points elsewhere. The Garmin-RUNSAFE study followed more than 5,000 runners across 87 countries for 18 months. It found that one run far above your longest run of the past 30 days drove injury risk. Weekly mileage jumps alone did not (LIH summary). The paper’s exact thresholds aren’t quoted here, so check the study before you build rules on them.

In short: don’t leap past your recent longest run. Climb in steps.

A 12-week plan is limited by how fast the long run can safely grow. Total miles are the easier part. As a working rule, we keep each new long run about 10 to 15% above the longest run of the last month. That’s our heuristic, not a study number.

The rushed line looks fitter. It’s just riskier, because it asks your legs for 29 km in week 4.

Thing 3: Finish Goal or Time Goal

A finish goal needs about 10 weeks of steady work. A time goal needs a base that already exists.

Why 10 and not 12? Because the taper takes 2 weeks. A meta-analysis found that cutting volume 41 to 60% for about 2 weeks, while keeping intensity, improved performance by about 3% on average (Bosquet 2007). Translation: those two easy weeks are worth more than two extra hard ones.

So a 12-week plan has about 10 build weeks. Skipping the taper to squeeze in more training is a bad trade.

Here’s a composite example, not a real athlete. Take Dana, 41, who ran a 2:05 half marathon in the spring. In July she registered for a marathon 12 weeks away. She ran 28 km a week over 3 days, and her longest run in the past month was 14 km. She wanted to finish and break 4:30.

Her plan stepped the long run up from 14 km to 29 km over 10 weeks, with a lighter week every fourth week. In week 6 she caught a cold and lost 5 days. She resumed at about 70% of her volume and kept the long-run steps small. She finished in 4:26.

She didn’t have a big base. She had a decent one and used it well.

Dana’s story is the best case. A runner at 12 km a week doesn’t get it.

Plan the build in three parts:

• Weeks 1 to 4: hold 3 run days, add easy volume and build the long run from 14 to 17 km, then ease off in week 4.
• Weeks 5 to 10: add one steady tempo run, keep stepping the long run up to 29 km.
• Weeks 11 to 12: taper. Cut volume about 40 to 50% two weeks out, then more in race week.

One more number. In the first-timer study, runners who skipped the 18-mile (29 km) long run had more minor injuries on race day. Runners training 4 or more days a week also had higher injury rates (Healio). For a first block on a short runway, 3 run days is the safer default.

What to Do When You Miss a Week

A short runway has no slack. One lost week is 10% of your block.

Don’t cram the missed miles. That creates the exact spike the research warns about. Skip the week, resume at about 70% volume, and keep your next planned long run if it’s still a safe step from your last one. We break down the numbers in what to do after you miss a week of marathon training.

Also watch for trouble. Heavy legs, a resting heart rate that stays up and flat moods are all warnings. Our guide to warning signs your marathon plan is too hard lists seven.

When a week goes wrong, the plan has to bend. AthleteOS builds your training plan back from your race date and your real base. After a missed week, the AI coach re-plans the remaining weeks, keeps the taper, and explains each change in plain language. You can start your 14-day trial here.

Plans that can’t flex break first.

When 12 Weeks Isn’t Enough

Pick a later race if you run under 16 km a week, have a recent injury, or haven’t run in two months. A 16 to 20 week block gives you room to build a base without chasing the long run. Our self-coached 16-week marathon block shows how to do it with free tools.

Already racing halves? Read how long to wait between a half and a full marathon before you register.

Twelve weeks works for a runner with a base. For anyone else it’s a gamble.