Can you run a marathon with no training? Honestly, don't

Can you run a marathon with no training? Some people do finish one. That's not the same as it being a good idea. A marathon with no training usually means walking most of the second half, being sore for days, and taking on risks that a few months of preparation would have shrunk. If you're asking because you've already entered, the honest answer is to defer, drop to a shorter race, or give yourself enough weeks to train.

This post won't help you bluff 26.2 miles. It explains what goes wrong, what the research says about undertrained marathoners, and what the realistic minimum timeline looks like. If you lift and want a plan that fits both, an app like Runna that also programs strength is the long-term answer. For now, let's talk about why "I'll just wing it" is a bad plan.

Can you run a marathon with no training? The honest answer

It depends what "no training" means for you, but the answer gets worse fast as your running background shrinks.

Those timelines line up with how long to train for a marathon from each starting point, and none of them is "zero weeks".

The difference between a 5K and a marathon is not just distance. A fit person can get round a 5K on general fitness. A marathon takes hours, and every one of those hours exposes whatever your training didn't build.

What actually works is a gradual build: a 16-week marathon plan for someone who's already running, or longer if you're not. For everything that goes into that build, from the long run to the taper, start with this breakdown of how to train for a marathon.

What goes wrong when you run a marathon with no training

You hit the wall early and hard

In an analysis of more than 4 million race records, Smyth (2021) describes hitting the wall as a significant slowing of pace late in the race, typically after the 20-mile mark, and usually because of a depletion of the body's energy stores. That study found 28% of male and 17% of female recreational marathoners hit the wall by its pacing-based definition, and those are mostly people who trained.

Training is how you prepare for that: long runs that teach you a pace you can hold, and practice taking carbohydrate on the move. Without it, you're guessing at both. Our guide to hitting the wall covers the pacing and fueling side in detail, and almost all of it assumes you've done the long runs first.

Your injury risk goes up

Your heart and lungs adapt faster than your legs. Muscles, tendons and bones need repeated, gradual exposure to running before they tolerate hours of it.

In a study of 662 marathon finishers, runners who averaged less than 30 km (about 19 miles) a week before the race had about twice the risk of a running-related injury (relative risk 2.02) compared with runners doing 30 to 60 km a week, after adjusting for previous injury and previous marathons (Rasmussen et al., 2013). The authors suggest runners may be advised to run a minimum of 30 km a week before a marathon. That was a retrospective survey with self-reported data, so it's not the final word. But it points one way, and "no training" sits well below 30 km a week.

Your heart takes more strain

A study of 60 non-elite Boston Marathon runners (Neilan et al., 2006) found that finishing a marathon was associated with biochemical and echocardiographic evidence of temporary cardiac dysfunction and injury, and that this risk was increased in those with less training. Compared with runners training more than 45 miles a week, those training 35 miles a week or less showed more right ventricular dysfunction and higher markers of heart muscle injury and stress. The study didn't include untrained runners, but the direction is hard to ignore.

Serious cardiac events are rare. Across 10.9 million marathon and half marathon runners in the US from 2000 to 2010, the cardiac arrest rate during marathons was 1.01 per 100,000 participants, and cardiovascular disease accounted for the majority of cases (Kim et al., 2012). That study didn't look at training levels. It does show why underlying heart conditions matter, and why the next section exists.

You're out there long enough to drink too much

An untrained marathon is a slow marathon, and slow comes with its own hazard. In a study of 488 Boston Marathon finishers, 13% had hyponatremia (low blood sodium), and on multivariate analysis it was associated with weight gain during the race, a racing time over 4 hours, and body-mass-index extremes (Almond et al., 2005). Drinking at every aid station "to be safe" for five or six hours is exactly the wrong instinct.

See a doctor first

If you're seriously considering a marathon on little or no training, see a doctor before you start, especially if you have a heart condition, high blood pressure, diabetes, a family history of heart problems, or any symptoms like chest pain, breathlessness or dizziness when you exercise. That applies to starting a proper training plan too. It's a short appointment compared with a six-hour race.

The realistic minimum timeline

Here's the good news: the real answer isn't "never". It's "not in three weeks". The timeline depends on where you start:

A large analysis of recreational runners puts the floor plainly: completing a marathon usually requires at least 12 to 16 weeks of consistent training (Feely et al., 2022). And that's for people who already run.

Training marathon 12 weeks out is possible if you're already doing around 20 miles a week with a recent half marathon behind you. From the couch, 12 weeks is too short for a comfortable finish, and zero weeks is a lot shorter than 12.

A real build also changes things race day can't fake: legs that tolerate impact, a gut that's practiced taking carbs, and a pace you actually know you can hold. Even the confusing parts, like the scale changes behind marathon training weight gain, are your body adapting to the work. You can't skip to the adapted version.

If your race is too soon

• ›Defer. Many races allow deferral to the next year, though policies vary, so check yours.
• ›Drop to the half or 10K. Many marathons have shorter races on the same day.
• ›Volunteer or spectate, then enter next year's race with a real plan.

If you lift, your squat won't carry you

Gym people are the most likely to try this, because they're fit and strong and assume that transfers. Some of it does: your heart and lungs will cope better than a sedentary person's. Your running legs won't, and neither will your feet, shins or Achilles.

Lifting is genuinely useful for marathoners, as part of a running build, not instead of one. A guide to marathon strength workout planning covers how to keep one or two sessions a week while the running builds, with heavy legs kept away from the long run.

If you're doing it anyway

We'd rather you didn't. If you've already seen a doctor, can't defer, and are going to start, limit the damage:

1. ›Check the cut-off time before race day, and plan a finish that fits inside it.
2. ›Run-walk from the first mile, not from the moment you're exhausted. Something like a few minutes running, a minute walking, held all day.
3. ›Start slower than feels sensible. Then slower again.
4. ›Take carbohydrate regularly. The ACSM, Academy of Nutrition and Dietetics and Dietitians of Canada position stand gives 30 to 60 g per hour for exercise lasting 1 to 2.5 hours, and up to 90 g per hour beyond about 2.5 to 3 hours (Thomas, Erdman and Burke, 2016). Use what you've tried before, if anything.
5. ›Drink, but don't drink at every station by default. Drinking more than you sweat is the main driver of hyponatremia, according to the same position stand (Thomas, Erdman and Burke, 2016).
6. ›Stop and get help from race medical staff for chest pain, dizziness, confusion, or anything that feels wrong rather than tired. A DNF is a story. An ambulance is a worse one.

Then expect a slow recovery. Walk, rest, and don't lift heavy legs until the stairs stop being a problem.

How exrsz handles this

exrsz builds a periodized marathon plan backward from your race date, using your goal, schedule, level and equipment, with running and lifting balanced in one plan. If the timeline is too short for your starting point, that shows up in the plan. It adapts each week to how you actually trained and reshuffles missed sessions so the build still lands on race day.

FAQ

Can you run a marathon with no training?

Some people finish one, usually with a lot of walking, but it isn't recommended. Lower training volume is linked to higher injury risk (Rasmussen et al., 2013) and more cardiac strain during the race (Neilan et al., 2006).

Can I walk a marathon with no training?

Walking reduces the impact, but it's still many hours on your feet, and long finishing times come with their own risks, such as overdrinking (Almond et al., 2005). Check the race cut-off, see a doctor first, and build up your walking before race day.

What is the minimum training for a marathon?

For people who already run, completing a marathon usually requires at least 12 to 16 weeks of consistent training (Feely et al., 2022). From no running at all, plan on roughly 9 to 12 months.

Can a fit person run a marathon without running training?

Cardio fitness helps, but your legs need gradual running volume to handle the impact. Runners averaging under 30 km a week before a marathon had about twice the injury risk of those running 30 to 60 km a week in one study (Rasmussen et al., 2013).

What happens to your body if you run a marathon untrained?

Expect heavy fatigue, a high chance of hitting the wall, and severe soreness for days afterwards. Research on non-elite runners found markers of temporary cardiac dysfunction and injury after a marathon were greater in those with less training (Neilan et al., 2006).