My first marathon build topped out at 25 miles a week. Twenty-five. And I remember feeling weirdly confident about it. I was running consistently, getting my long runs in, sweating buckets in Bali humidity, telling myself the heat alone was building some kind of superpower.
Race day humbled me fast.
I was cruising until about mile 18. Then it felt like someone flipped a switch. Legs went heavy. Pace evaporated. I wasn’t racing anymore — I was surviving. And that’s when it hit me: I hadn’t respected what 26.2 miles actually demands from you.
That experience changed how I look at mileage forever. As a coach and as a runner, I’ve seen it over and over — the marathon doesn’t punish lack of talent nearly as much as it punishes lack of volume. If you’re wondering how many miles per week you really need, let’s talk about it honestly. Not Instagram mileage. Real-life mileage. The kind that actually carries you past mile 20.
Define the Problem
Misconception #1: “If I can cover 26 miles once in training, I can finish a marathon.”
A lot of first-timers (me included) think one big 26.2 practice run is the golden ticket. Like if you can physically cover it once, you’ve proven you’re ready.
But the marathon isn’t just covering 26.2 miles one time. It’s doing it after months of cumulative fatigue, at a steady effort, without your body falling apart halfway through. One heroic training run can’t replicate that demand.
And honestly, when I tried to “prove” myself with those monster runs, it didn’t make me ready. It just made me exhausted. And kind of fragile. Like my body was asking, “Why are we doing this again?”
Marathon success comes from weeks and weeks of consistent mileage building a deep aerobic base — not one magical long run. The runners who obsess over “hitting the full distance” in training often skip the boring day-to-day miles that actually matter, and then they pay for it on race day.
Misconception #2: “Low mileage = low injury risk.”
It sounds logical. Run less, break less, right?
But in marathon running, undertraining can be just as risky as overtraining. If you haven’t run enough to build resiliency, your muscles, tendons, and ligaments aren’t ready for the sustained pounding of 26 miles. Undertrained runners break down late. Form collapses. Then weird stuff starts hurting that never hurt in training.
I’ve seen it a bunch: runners doing 15–20 miles per week end up with IT band pain, shin splints, or worse by mile 20 because their bodies weren’t conditioned for that duration. And the irony is, a somewhat higher weekly mileage — mostly easy — often makes you more durable and can reduce injury risk because you’re actually building tissue tolerance.
Low mileage might spare you some short-term soreness. But it can leave you vulnerable when fatigue wrecks your form late in the race. I learned that the painful way too — my legs didn’t have enough “base durability” to hold together to the finish.
Real-Life Constraints
Now, I get it. Not everyone can run 50+ miles a week. Work, kids, life, whatever. A lot of marathoners max out at 20–30 miles/week because that’s what time allows. I’ve lived that. I remember thinking, “Okay, I can manage 25 miles a week and that’ll have to do.”
The problem is, 20–30 mpw often sits just below the threshold of what’s actually needed to be marathon-ready.
There was data from a large group of recreational runners showing many runners who finished around the 4-hour mark were logging only ~25 miles per week, even though conventional training wisdom suggests 40+ for that goal (marathonhandbook.com). And that data doesn’t show how those runners felt late in the race. I’d bet a lot of them got pretty dark in the final miles.
This is the trap: life squeezes training, so you show up a little undercooked, then you spend the last hour of the marathon learning a lesson you didn’t want to learn.
Forum Myth
If you hang out on marathon forums long enough, you’ll see somebody say, “You can run a marathon on 20 miles per week — it’ll just be a really long walk.”
And yeah, technically, if you’re fine walking big chunks, you can finish on low mileage. But you read those same threads and you also see the horror stories: people who tried it and hit the wall at mile 18, puking, cramping, limping, or dropping out.
One guy bragged about finishing on ~20 mpw, and somebody replied, “Sure, but how long did it take you to recover?” That’s the real question.
Because finishing alive and finishing strong are not the same thing. Most people don’t want a five-hour suffering march and a week where they can’t walk down stairs without swearing.
SECTION: Science & Physiology Deep Dive
So why does mileage make such a difference?
Because the marathon lives almost entirely in the aerobic world. Marathon pace is roughly around your aerobic threshold, about 80–85% of VO₂ max for many runners. To hold that effort for a few dozen miles, you need a real aerobic engine. And you build that engine with volume. Not one workout. Not one heroic long run. Volume.
High mileage training does a few key things:
First, it increases mitochondrial density. Mitochondria are the “power plants” in muscle cells that make energy using oxygen. More mitochondria means you can produce more energy aerobically before you fade.
Second, consistent running expands your capillary network — more tiny blood vessels in the muscles. That improves blood flow and oxygen delivery. More oxygen delivered = more sustained effort.
Third, lots of easy running improves your ability to use fat as fuel, which helps spare glycogen. That matters because when glycogen runs low late in the race, that’s where the wall shows up and starts punching you in the mouth.
Those changes don’t come from a few spicy workouts. They come from regular, repeated stimulus — day-in, day-out training volume.
As one coach explained, running at low intensities builds your aerobic engine by increasing mitochondria, capillaries, and overall endurance (marathonhandbook.com). And it also conditions your musculoskeletal system to tolerate long durations. You don’t just get fitter, you get tougher.
There’s also this concept in exercise science called the “hierarchy of endurance needs.” At the base is training volume — total miles or hours. It’s the foundation everything else sits on.
Dr. Stephen Seiler summed it up with: “Miles do make champions.” (quantifiedrowing.com) And it’s not just a nice quote. The marathon world keeps proving it.
Look at history:
- In the 1950s, Jim Peters ran on the order of 100 miles per week and set world-best marathon times.
- Today, Eliud Kipchoge reportedly runs around 180–200 km per week (about 110–120 miles) to stay dominant.
No, you do not need triple-digit mileage to finish your marathon. But it’s a loud example of the same truth: even with all the modern knowledge, the main ingredient is still volume.
And it shows up in recreational runner data too.
A 2016 study looking at thousands of marathoners found weekly mileage was one of the strongest predictors of finish time. Men averaging about ~50 mpw ran roughly 25 minutes faster than those averaging ~30 mpw, holding other factors constant, and women showed an even bigger gap — over 30 minutes faster at 50 mpw vs 30 mpw. More miles, faster marathons. That’s basically the story.
A massive analysis of Strava data from 100,000+ marathoners found the faster runners simply ran more. The quickest group (finishing around 2:00–2:30) was logging about 107 km/week, while runners finishing over 4 hours were doing only about ~35 km/week (runningmagazine.ca). That’s roughly 66 miles vs 22 miles per week. Three times the volume. Huge performance gap. And the data made it obvious: as training volume drops, marathon time climbs (runningmagazine.ca).
Even at the elite level, volume separates people. One review noted world-class long-distance runners ran significantly more than national-class or sub-elite runners, and overall training volume explained about 59% of performance variability among elites (run-wise.com). That number is wild when you sit with it. More than half the difference is “how much they run.”
The marathon also sits near the aerobic threshold where lactate starts to creep up. High mileage pushes that threshold pace faster, so you can run quicker while staying aerobic. Lower mileage runners often end up running “hotter” relative to their aerobic base. They creep into higher zones, fatigue builds faster, and the late miles get ugly.
So yeah. The marathon rewards volume.
Intervals and tempos are sharpening tools. Mileage is the rock that makes the edge.
If you skip the base, the blade goes dull fast. If you build the base, you can hold a strong effort through 26.2 miles.
And the science keeps pointing back to the same hard-to-swallow truth: to run a strong marathon, you really do have to run a lot.
SECTION: Actionable Solutions
Alright. So yeah — mileage matters. Cool. But that’s the annoying part, right? Because knowing it and doing it are two different lives. So here’s how I’d actually turn this into a plan that a normal human can follow without exploding.
- Weekly Mileage Targets (Based on Runner Level)
The “right” weekly mileage depends on who you are, what your body can handle, and how much life is currently trying to fight you. But we can still put rough rails on it.
- Beginners:
If this is your first marathon or you’re still pretty new to running, you might start around 15–25 miles per week and slowly build to about 35–40 miles at peak. A lot of beginner plans top out in the high-30s or low-40s. That can be enough to finish. Might not be pretty. Might not be fast. But it can work.
Early on, cycling or swimming on off days is fine. Honestly it can be smart. It helps you build endurance while keeping the running load from jumping too fast. But over time, you want more of your aerobic work coming from actual running, because the marathon is running. Your legs need that specific beating.
- Intermediate Runners:
If you’ve done a marathon or two and you’ve got a decent base, you usually want to live somewhere around 40–50 miles per week during the main part of marathon prep. That’s the range where things start to click for a lot of people. It’s enough volume to build a serious aerobic base without feeling like you’ve joined a monastery.
A lot of intermediate runners end up holding around ~45 mpw for multiple weeks in the middle of a cycle. That level supports long runs in the mid-to-high teens and still leaves room for plenty of easy miles around them.
If you’re chasing a time goal like 4 hours (about 9:00/mile), being in that mid-40s weekly range can make that pace feel a lot less like survival and more like something you can settle into.
- Advanced & Sub-4 Aspirants:
If you’re aiming for something more aggressive (sub-4, sub-3:30, whatever) or you’ve been at this for years, then 50–60+ miles per week can make sense. Some runners chasing Boston or breaking 3 hours might peak at 60–70.
For sub-4 runners specifically, I often like a peak range around 45–55 miles per week in the key weeks (worldmarathonmajors.com). Usually that means running 5 days, sometimes 6.
And just to be clear: it’s not about one week that hits 50 and then you collapse. It’s about being able to sit in the 40s and 50s for a while. A higher average. Multiple weeks. That’s where the base actually builds.
Some advanced plans use doubles (two runs in a day) to reach higher totals, but that’s not a thing you randomly add because you’re excited. That’s more like… you’re already near your ceiling and you’ve got the time and you’ve earned it.
One thing I always have to say out loud: is more always better? No. There are practical upper limits. Above ~60–70 mpw for recreational runners, you can get diminishing returns and injury risk climbs. So I’m not telling everyone to chase some elite number. Most people aren’t even close to that. A lot of runners hang out in the 20s and 30s and have a lot of room to improve by getting into the 40–50 range if life allows.
So shoot for the higher end of what you can manage consistently. Not what you can survive for one heroic week.
- Gradual Build Formula
Okay, so you’ve got a number in mind. Now how do you actually get there without your shins filing a complaint?
Slowly. Boringly. And with some ego control.
A classic guideline is the 10% rule — don’t increase weekly mileage by more than about 10% over the previous week. I usually treat it more like 5–10%, and if someone’s newer or we’re also building the long run at the same time, I lean lower.
Example: if you ran 30 miles last week, adding 2–3 miles the next week (around an 8–10% jump) is reasonable.
And you need cut-back weeks. This is where a lot of people mess up because they feel good and they don’t want to back off. But your body isn’t just adapting on your schedule.
Typically every 3rd or 4th week, drop your mileage about 15–20% to recover and lock in the gains.
Think of it like two steps forward, one step back. It doesn’t feel heroic. It works.
A sample wave might look like:
30 → 33 → 36 → cut back to 28
Then 32 → 35 → 38 → cut back to 30
And so on.
Also: increasing mileage isn’t just adding miles to the long run. It usually means adding a mile here, a mile there, across multiple runs.
Instead of jumping a long run from 10 to 15 in one go (bad idea), you go:
10 → 12 → 14 → cut back to 12 → 16
You creep up. You don’t launch.
And sometimes the safest way to add volume is adding a day. If you’re running 3–4 days a week and trying to cram mileage into those days, you end up with monster runs and you recover poorly. Going from 4 days to 5 days, keeping most runs easy, can spread the load better. Frequency builds durability.
Patience matters. High-mileage marathoners aren’t built in a day. Elite marathoners who run insane volumes like 120 miles per week took years of gradual growth to handle that load (worldmarathonmajors.com). We amateurs have to do the same thing at our scale. Slow build. Hold it. Let the body catch up. Then build again.
And yeah, you’ll have weeks where you feel invincible and you want to jump 15 miles because you had one good week. I’ve had that urge too. But your bones and tendons adapt slower than your enthusiasm. That’s the trap.
Consistency beats quick jumps. Every time.
- Essential Weekly Components
Mileage is the base. But what you do inside that mileage still matters. A marathon week usually has a few pieces that keep showing up, no matter the plan.
- The Long Run
This is the centerpiece. The one run that makes the marathon feel real.
Most plans build the long run to around 16–20 miles, depending on your level. It’s non-negotiable because it gets you close to the physiological and mental grind of the race. It builds endurance, helps your body handle glycogen better, and gives you practice with pacing and fueling.
And it’s also a confidence thing. When you run 18 in training, 26.2 stops being this abstract monster. You’ve been in the neighborhood.
These should usually be easy conversational pace, often about 60–90 seconds per mile slower than marathon pace for many runners. People love to race long runs. I get it. But pushing long runs too fast increases injury risk and doesn’t really give you extra benefit.
If you’re experienced, sure, you can put marathon-pace segments into some long runs. But the bulk should be easy. The goal is time on feet and finishing thinking, “I could maybe do a bit more.”
I still remember my first 18-miler in training where I finished tired but not destroyed and thought, “Alright. I can do this.” That run changed the whole vibe. It went from fear to actual planning.
- Medium-Long Run
A lot of plans sneak in a mid-week run that’s longer than your usual daily run but shorter than the long run — like 8–12 miles easy.
This is a sneaky powerful one because it adds mileage and endurance without the full recovery cost of the weekend long run. In a 50-mile week, something like 10 mid-week + 18 long run does a lot.
It also teaches you to run on a bit of fatigue, since it usually lands after other runs earlier in the week. That’s closer to race reality than always running fresh.
- Quality Workout
Volume is the base, but one or two days a week you still want some faster work so you don’t become a strong-but-slow diesel tractor.
Common ones:
- tempo runs (like 4–10 miles at a “comfortably hard” effort, around half marathon pace or a bit slower)
- intervals (800m or mile repeats around 10K pace, or longer repeats closer to threshold)
These teach your body to handle quicker paces, help with lactate management, and improve running economy. Marathon pace feels easier when you’ve got gears.
Usually you do one big quality session per week. More advanced runners might do two — like one mid-week workout and then marathon-pace work inside the long run.
Example: Wednesday 8 miles with 4 at tempo, then Saturday long run with last 5 at marathon pace.
- Easy Runs & Recovery Runs
These are the miles people disrespect. And then they wonder why they’re always tired.
Most of your miles — like 70–80% — should be truly easy. Zone 2 if you like labels. Conversational pace. You could talk. You could breathe through your nose sometimes.
These runs build the aerobic base and strengthen tissues without wrecking you. They also help you recover from workouts by moving blood through tired legs.
A lot of people struggle with easy pace because it feels “too slow.” But running easy is what lets you handle more volume without breaking. It’s also what the faster runners do — lots of low intensity. That big Strava analysis showed faster marathoners ran most of their miles at low intensity (runningmagazine.ca; marathonhandbook.com).
If you’re drenched and heaving on an easy run, it wasn’t easy. Slow down. No ego.
- Rest or Cross-Training Days
Most plans include at least one rest day, sometimes two. Rest is where the body repairs. If you skip rest because you think you’re tough, the marathon eventually collects the debt.
Cross-training is fine: swim, bike, yoga, strength. Just don’t turn cross-training into another hard workout that wrecks recovery. Keep it low to moderate if it’s on a day that’s supposed to help you recover.
I take at least one full day off running per week. It keeps minor aches from becoming real problems. Recovery is training. Not the absence of it.
A sample intermediate week around 45–50 miles might look like:
- Monday: Rest (or very light cross-training)
- Tuesday: 8 miles easy
- Wednesday: 10 miles with 5 × 1-mile at 10K pace inside the run
- Thursday: 5 miles easy
- Friday: 5 miles easy
- Saturday: 18 miles long run (steady, maybe finish last couple miles a bit faster)
- Sunday: 4 miles super easy recovery jog (or rest depending on how Saturday felt)
That week has the pieces: easy runs, one quality day, one long run, a rest day. Total around 50. Most miles low intensity. That’s the point.
- Taper Strategy
No taper, no peak. That’s the simplest way I can say it.
After weeks of mileage and long runs, you taper so you show up fresh instead of slightly cooked.
Most marathoners start tapering 2–3 weeks out.
A common approach:
- 3 weeks out: last really long run (18–20)
- then drop to about 80% of peak the next week
- then drop to about 50–60% of peak in the final week
Example: peak at 50 miles → then ~40 → then ~25–30 in race week (not counting the marathon itself in that number depending on how you track it).
You don’t stop running. You keep frequency but shrink duration. You keep a little intensity with short workouts so the legs don’t feel dead, but you’re not piling on fatigue.
Taper anxiety is real. Phantom aches. Feeling like you’re losing fitness. Feeling antsy. I’ve had all of it. It’s normal.
And the annoying truth: anything you do in the last 10 days won’t build meaningful fitness. But it absolutely can sabotage your race if you overdo it.
So trust the taper. Err on the side of extra rest.
If you’re going crazy, throw in a few strides or short pickups during an easy run so you remember you still have pop. But don’t go run some hard 15-miler two weeks out “just to be sure.” That’s how people show up tired and then act shocked when mile 22 becomes a crime scene.
I learned this the hard way. Early marathons, I barely tapered because I was paranoid about losing fitness. I did a hard long run two weeks out once, and basically held near-normal mileage right into race week. I toed the line already tired and then faded in the final 10K. No mystery there.
Later, when I finally tapered properly — cutting back hard and resting — I felt almost too good the last few days. Legs wanting to go. Nervous energy. That “am I even training anymore?” feeling. And then race day came and I felt springy.
One of my best times came after a disciplined three-week taper where my longest run in the last 21 days was only 12 miles and I was doing a lot of short, easy runs.
So yeah. I taper hard now. I’d rather be 5% undertrained than 1% overtrained on race day.
And I still remember the first time I hit a 50-mile week and an 18-mile long run in the same cycle. I finished that long run, dropped into a chair with my recovery drink, and thought: “I’m actually going to do this. I’m going to run a marathon and not just survive… but run it well.”
That feeling is different. It’s worlds apart from lining up underprepared and hoping you can fake it. Putting in the miles turns the marathon from an unknowable monster into a big, hard, doable job.
SECTION: Coach’s Notebook – Patterns and Lessons
I’ve coached a lot of marathoners. Brand new folks who still think 8 miles is basically crossing the Sahara. And also Boston-qualifier types who casually say “yeah I’m just doing a 16 after work” like that’s a normal sentence.
And the funny part is… the people who succeed and the people who struggle? They usually don’t differ in “toughness.” Everybody’s tough. Everybody’s busy. Everybody’s trying.
But there are patterns. Same ones over and over. Here’s what I keep seeing.
- Easy Means Easy:
The runners who improve the most actually… let easy be easy. Like actually easy. Their recovery jogs are sometimes embarrassingly slow by normal-people standards — and that’s exactly why they can handle more mileage and still show up for workouts with legs that work.
Easy days relaxed = less burnout, fewer injuries, faster bounce-back for the next key run.
I tell athletes all the time: “If you want to run fast, you’ve got to train slow (most of the time).” It sounds dumb when you first hear it. I get it. But it’s backed by science and it’s backed by the reality of what happens to runners who try to hammer everything.
The ones who ignore this — who run every run like it’s a statement — they plateau. Or they collect aches like souvenirs. Knee. Achilles. Hip. Something always starts whispering, then yelling, then you’re suddenly cross-training in anger.
I had to learn this the hard way too. Once I slowed down my easy runs, I could add another running day per week without falling apart… and my fitness jumped. Like not subtle. It was obvious.
- Long Runs Are Practiced, Not Raced:
The most prepared marathoners treat long runs like rehearsal. Not a competition.
They start gentle. They fuel. They cover the distance smoothly. They don’t turn an 18-miler into a time trial just because the weather feels good and their ego is awake.
Because when someone “crushes” every long run at near race pace… they usually leave their best effort on the training route and show up on race day already tired. Or injured. Or both.
I see this pattern constantly: the runner who keeps long runs comfortable can hit another solid workout a few days later. The runner who goes too hard in the long run? Dead legs for a week. They’re dragging through everything after.
Successful marathoners use the long run to rehearse fueling and pacing discipline. They know the race is where you empty the tank. Not the long run two weeks before.
- Mileage Progression is Steady:
The runners who improve from one marathon to the next usually do this boring thing where they slowly build volume and hold it. They don’t double mileage in a panic because they read a post that said “you need 50 mpw.”
They might add 5 miles per week across a whole training cycle. Or extend the training period by a few weeks. Over a couple years you’ll watch someone go from averaging 30 mpw to 45 mpw and their marathon changes like… yeah. It changes.
The mistake is the rocket jump. I saw a runner try to go from a longest week of 25 miles straight to 40 because he read online that 40–50 is “ideal.” Within 3 weeks he was injured — IT band syndrome. Classic.
We rebuilt him slowly. And a year later he did hit 45 mpw and ran a strong marathon. But it had to be stepwise. Layer by layer. You don’t get to skip that part.
Also: mileage FOMO is real. People feel like they’re behind because someone online is running 60. And they try to force it. Successful runners don’t do that. They respect the process.
- Avoiding the “Just Long Runs” Trap:
This one makes me want to grab people by the shoulders sometimes.
I’ll meet a runner who says, “I do a 16-miler every weekend… but I still bonk at 20 in the race.”
And I’m like, okay… what’s your weekly mileage?
Often it’s 25 miles. Meaning almost two-thirds of their weekly miles are stuffed into that one long run.
That’s a red flag. Big one.
Ideally your long run is no more than about 30–35% of your weekly mileage. If it’s 50%, you’re relying on one run to carry you. And one run can’t carry you through 26.2. It just can’t.
The runners who succeed have weekday mileage. Medium-long runs. Regular easy runs. That steady drip of miles that supports the long run. The long run alone doesn’t make you marathon-fit. It’s the long run plus the other days.
So don’t be the person who runs 3 miles Tuesday, 3 miles Thursday, then a 20 on Sunday and calls it “marathon training.” That’s a recipe for a painful marathon.
Better: 40 miles spread across 5 days with a 16-mile long run than 25 miles with a 20-mile long run and little else. Every time.
- Cross-Training Caution:
Cross-training can help. Cycling, swimming, elliptical — great tools, especially if you’re injury-prone.
But sometimes I see people using it like a full-on replacement for running mileage. Like: run 2 days a week, bike 5 days, then expect to run a great marathon.
They might have the cardio engine, sure. But their legs won’t have the same resilience as if they’d been running.
I’ve coached triathletes moving into marathons — their VO₂ max is legit from biking/swimming, but the first time they try to run 20 miles, their calves and feet get wrecked. Their connective tissue just isn’t conditioned for the pounding and the repetition of running strides.
There’s no exact substitute for running mileage when it comes to conditioning leg muscles, connective tissues, and that neuromuscular rhythm of running. So use cross-training to supplement — add aerobic volume without impact, fine — but be wary of plans that promise great marathon results on very low running mileage with cross-training doing the heavy lifting.
It can work to finish. It rarely works to excel.
One of the most rewarding coaching experiences I’ve had was with a beginner who totally underestimated mileage. She thought three short runs and one weekend long run — like 20–25 miles total — would be enough if she just went slow. Her mantra was basically, “I’ll just jog the whole way, no need for a ton of miles.”
Her first marathon attempt with that approach… it was rough. She hit the wall. She walked. She finished way over her goal time. Completely spent. Like the marathon chewed her up and she wasn’t even surprised, just… disappointed.
For her next try, I convinced her to gradually increase to about 35 miles per week and spread it over 4–5 days. Nothing fancy. We added one more midweek run. We extended a couple runs a little. Kept it easy. She peaked in the mid-30s — still not super high, but higher than before.
And the result? She improved her marathon by 25 minutes and finished smiling. Like actually smiling. She told me she enjoyed it. That blew her mind.
And the crazy thing is we didn’t add some secret workout. No drastic diet changes. No weird hacks. We added about 10 extra miles per week of easy running. That’s it.
Stories like that keep reinforcing what I’ve seen as a coach: nine times out of ten, when someone’s marathon needs improvement, the answer isn’t “more pain.” It’s more easy miles.
SECTION: Community Voices
Marathon runners online… yeah, they’re loud. And honestly, useful. Reddit, r/running, r/AdvancedRunning, Facebook groups — you can learn a lot just by watching the same debates repeat forever.
And the patterns match what coaches and science say, but in a more real way. More blunt. More “I tried this and it hurt.”
Theme #1: “Is 30 miles per week enough?”
This comes up constantly. Usually from someone time-crunched or nervous because they’ve trained low mileage before.
Responses are mixed, but if you read closely, it’s telling.
A few people say, “Yeah I did a marathon on about 30 mpw and I was fine.”
Then you keep reading and it becomes: “…but I walked a lot at the end.”
Or: “…it wasn’t fun.”
Or: they’re 22 and naturally athletic and recovering like Wolverine.
Most experienced voices say some version of: “It might be enough to finish, but you’ll probably do better and feel better at 40–50.”
I remember one thread where someone bragged about going sub-4 on roughly 30 miles a week. They did it. Respect. But a bunch of replies were basically, “Okay… now imagine how much easier that could’ve been with more training.”
The vibe is usually: 30 mpw is bare-minimum. Possible. Not ideal. Especially if you care about the outcome.
Theme #2: “Can I skip long runs?” / “What’s the shortest long run I can get away with?”
This one gets answered almost the same way every time: don’t skip long runs.
Marathoners are weirdly united on this. They’ll fight about shoes for 200 comments, but on long runs? They’ll all say: “The long run is where you physically and mentally prepare. Nothing else replicates it.”
Yeah, some high-volume plans might cap long runs at 16 miles if the weekly volume is huge and there are doubles and stuff. But for most recreational runners, the community advice is: get at least a couple of 18–20 milers in.
And people share the regret stories too: “I only went up to 14 or 15 miles and I deeply regretted it.” That’s almost a rite of passage. The marathon makes you pay when you try to shortcut time-on-feet.
Theme #3: “Higher mileage converted me.”
You see a lot of these and they’re almost… evangelical.
Someone will say: “I used to run ~25 mpw and bonked in two marathons. This cycle I averaged 45 mpw and ran a 20-minute PR feeling strong.”
Then the comments fill with the same thing: “Once I got over 40 miles consistently, the wall stopped showing up at mile 20.” Or “I didn’t realize how much better the last 10K could feel.”
It’s like people don’t shut up about it once they experience it. Which makes sense. Because going from a death march to a controlled race feels like discovering a cheat code — even though it’s not a cheat code. It’s just… doing the work slowly enough.
Theme #4: The hard-way confession posts.
These are half funny, half tragic.
Somebody will write something like: “Confession: I only ran 10 miles before my marathon — and I paid for it.”
They’ll explain how they thought a marathon is just two half marathons, so their 10-mile long run would somehow carry them through.
Spoiler: it doesn’t.
They bonked early, walked the last 8 miles, cried, swore, finished. The replies are supportive but also kinda like: “Yeah… lesson learned, huh?”
And honestly, those stories are useful. Because nobody is special to the marathon. The distance humbles everybody who shows up underprepared.
So when you listen to the community, the pattern is loud and consistent:
The runners who had good experiences almost always talk about adequate weekly volume and proper long runs. The runners who had bad experiences almost always trace it back to not enough miles — especially not enough long runs.
And sometimes hearing it from another regular runner hits harder than any physiology talk. I share these kinds of stories with first-timers I coach because it feels real. It’s not a lecture. It’s a warning from someone who already stepped on the rake.
SECTION: Skeptic’s Corner
At this point, yeah, the skeptical brain kicks in. Like, okay coach… do I really have to run a ton of miles? Are there cases where lower mileage is actually the right call?
And honestly… yeah. There are a few situations where low mileage marathon training isn’t just “allowed,” it might be the smarter move.
- “Just Finish” runners with low-intensity goals:
If your goal is literally to finish and you truly don’t care if the last hour turns into a shuffle-walk festival, you can get by with less mileage. A lot of charity programs basically aim for that. They’ll have walkers or run-walkers peak around 25–30 mpw and they build in a lot of walking right into the plan. Those runners might finish in 5.5–7 hours and that’s totally fine if that’s the agreement they’re making with the day.
In that world, injury avoidance might matter more than performance. Cross-training might be doing a lot of the work. And the marathon isn’t “race day” so much as… an extension of training. Like an adventure where the goal is to finish the thing and get the medal and tell the story after.
So yeah—if you’re okay with a very slow marathon and you’re willing to walk big chunks, you don’t necessarily need 50 mpw. You could conceivably finish on 20–30 mpw if you pace super conservatively, like start walking breaks early instead of pretending you’ll “run until you can’t.”
It’s still not easy. It’ll still hurt. A marathon always finds a way to make you pay something. But it’s doable. Especially for people with constraints, or doing it for charity, or experience, not time.
And even then—I’d still tell them: do as much as you reasonably can. Because even walking 26.2 is a serious effort. It’s not a casual stroll around the neighborhood.
- Injury-prone runners / heavy cross-trainers:
Some runners just… break when they go above a certain mileage. Stress fractures, tendon stuff, recurring knee pain, whatever. And in those cases, lower mileage plus cross-training can be the best compromise.
I coached someone with recurring stress fracture issues; we capped her around ~30 mpw running and she did a lot of pool running and cycling. She finished her marathon using a run-walk approach and avoided injury. That’s a win.
These runners usually need longer build-ups—like 6+ months—because they’re building endurance without relying on tons of running volume. Expectations usually have to shift too. The goal becomes finish healthy, not “set the world on fire.”
Same idea with triathletes who jump into a marathon. Their whole training setup is different because they’re juggling three sports. Though, even there, most triathletes doing Ironman still run a decent amount because they know running fitness is… not optional.
And here’s the honest part: whenever mileage is low, you accept trade-offs. Slower finish time is common. And the race might be more painful because your legs won’t have the same resilience from higher mileage.
I tell people who want to do marathons on minimal training: “You can finish, but it might not be pretty. Decide if that’s okay with you.” That’s not me being dramatic. That’s just the deal.
Now the flip side. When does low mileage fail?
In my opinion—and I’ve watched this happen a lot—low mileage fails most when you have any performance ambition. If you want a PR. If you want to beat a cutoff. If you want to run the whole way without walking. If you want to feel decent in the last 10K instead of bargaining with the universe.
The marathon is relentlessly truthful. If your training didn’t back up your goal, it becomes obvious somewhere after halfway. Usually it’s not subtle. It’s like the lights go out and you’re suddenly doing math in your head like, how many miles is it to the next aid station and can I walk without everyone seeing?
I learned this in my own undertrained attempt where I bonked and had to walk. My ambition was to run the whole way and hit a certain time, and I didn’t have the training to support that. I didn’t “lack grit.” I lacked the base.
Low mileage also fails because it doesn’t prepare your muscles and connective tissue for the strain of running 26 miles. Running is high-impact. It’s repetitive. And your legs have to be conditioned for that in a way that biking and swimming just don’t recreate.
When people haven’t done enough long runs or weekly miles, you see the same breakdown around mile 18–20: shoulders slump, stride gets tiny, feet shuffle, posture collapses. It’s not even “running” anymore. It’s survival mode. And then you get the acute stuff: IT band pain, knee pain, blisters, you name it. Not always—but often.
High mileage accumulated over months delays that breakdown. Your body holds form longer and stays efficient later into the race. That matters for your time, sure, but it also matters for how wrecked you feel afterward.
Another failure mode is glycogen depletion. The wall. The classic. If you haven’t trained enough endurance volume—haven’t taught your body to burn fat better, haven’t built the engine—you’re likely to run out of gas around the 2.5–3 hour mark. That’s textbook undertrained marathon territory.
And no amount of carb-loading the night before fully makes up for that. I hear people say, “I’ll just eat a lot of gels on race day to make up for it.” Look, gels help. They matter. But if your muscles aren’t trained to endure, throwing sugar at them at mile 18 isn’t going to magically keep them firing.
You can’t fully fuel your way out of inadequate training. The body has to be tuned to use that fuel efficiently.
There’s also a mental piece built by higher mileage. When you’ve run 50–60 miles in a week and you’ve done multiple 2–3 hour runs, your mind is calmer on marathon day. You’ve been there. You know tired legs. You know the weird moods that show up after two hours. You’re not shocked by it.
Without that, the first time you experience real fatigue might be during the race itself—and mentally, that can be a slap. People tell me all the time that training volume gave them confidence late in the race. They could say, “I ran 200 miles this month, I got this,” and at mile 22 that kind of thought matters.
Some people love the “quality over quantity” phrase. And I’m not against it. But for the marathon, I’d call it: quality and quantity.
You need the cake (mileage) before you add the icing (workouts). If someone does a bunch of intervals but only runs 20 miles a week total, yeah, they might improve their 5K. But for the marathon it doesn’t hold. You can’t fake endurance with a little speedwork. You just can’t.
People ask all the time: “What’s more important for the marathon—weekly mileage or speed workouts?”
The best answer I’ve seen is basically: mileage builds the capacity, workouts fine-tune it. But if you don’t have the capacity, the fine-tuning doesn’t last. Mileage is the main course. Speedwork is the side dish.
And yeah, I’ve got a humbling personal story here because I earned it.
The only marathon I truly blew up in was the one where I tried to cheat the training. I was coming off an injury and gave myself only 8 weeks to ramp up. I figured my general fitness and some half-marathon experience would carry me.
It didn’t.
I maxed out around 30 miles per week, did maybe one 16-miler, and that was basically it. On race day I felt fine for the first 10–12 miles, then fatigue showed up way earlier than expected. By mile 18, my calves were cramping—something that had never happened to me before. By mile 20, I was taking walking breaks every mile. Like clockwork. Not dramatic. Just… reality.
I finished well over my goal time in survival mode. And I was so disappointed. But I couldn’t even pretend it was bad luck. I owned it. I hadn’t respected the distance in training.
I remember hobbling to a bench after the finish and muttering, “Never again… never running another marathon undertrained.” I kept that promise.
Next time, I overhauled it. More weeks. Built up to the mid-40s in mileage. And the outcome was night and day. I actually enjoyed the next race and hit my goal.
So I’ve lived both sides. And I’m telling you straight: the marathon you run with adequate training is a completely different experience than the marathon you run on a wing and a prayer.
SECTION: Training Data and Examples
Sometimes it helps to see concrete numbers. Let’s sketch out how mileage might increase over a typical marathon build and what sample training weeks look like.
Mileage Buildup (Example)
Suppose you currently run ~20 miles per week comfortably, and you have 16 weeks to train for a marathon.
A realistic build might look like this:
- Month 1: build from 20 → 30 mpw (adding ~2–3 miles each week, with a recovery week in there).
- Month 2: hover around 30–35 mpw, maybe touch 38 on a peak week. Long run builds from 10 → 14 miles.
- Month 3: get into the 40s — say 40, 42, 45 on a peak week. Long run hits 16–18 miles.
- Month 4: a couple more solid weeks in the mid-40s, with a peak long run of 18–20 miles, then begin tapering 3 weeks out.
By the last 2 weeks, you cut back down significantly (maybe 35 miles, then 20 miles not counting the race).
This is just one hypothetical, but it shows a safe build. You gradually climb, you don’t jump to 50 out of nowhere, and you include down weeks.
In reality, some weeks you might repeat the same mileage if you feel tired. The progression isn’t linear for everyone, but the overall trend should be upward, then downward for taper.
Sample Training Weeks
To understand distribution, here are examples of what a weekly schedule might look like at various stages.
Early in Training (Low Mileage Week ~20 miles)
Mon – Rest
Tue – 4 miles easy
Wed – 5 miles easy
Thu – Rest or cross-train
Fri – 3 miles easy
Sat – 8 miles long run (easy pace)
Sun – Rest
Total: 20 miles
This is a starting point for a beginner. Only 4 days of running, lots of rest.
The long run is a big chunk (40%) of the total here, which is okay initially.
Mid-Plan Week (Moderate Mileage ~35 miles)
Mon – Rest
Tue – 5 miles easy + strength training
Wed – 8 miles (with maybe last 2 miles at a steadier pace)
Thu – 5 miles easy
Fri – 4 miles easy
Sat – 12 miles long run (easy/moderate)
Sun – 1 mile super easy jog for recovery (or cross-train 30 min)
Total: ~35 miles
Here we’ve added an extra running day (Sunday shakeout) and extended some weekday runs.
The long run is 12, which is about one-third of weekly volume — a healthier ratio.
There’s a tiny bit of faster running (a pickup on Wednesday) but it’s still mostly easy.
Peak Week (Higher Mileage ~50 miles)
Mon – 5 miles easy
Tue – 8 miles (with 4 x 1-mile at half-marathon pace during the run)
Wed – 6 miles easy
Thu – 5 miles easy
Fri – Rest
Sat – 20 miles long run (first 15 easy, last 5 at goal marathon pace)
Sun – 6 miles recovery run (very slow)
Total: ~50 miles
In this example, the runner is on 6 days of running (taking Friday off before the big long run).
There’s a quality workout on Tuesday, and a marathon-pace finish on Saturday.
Sunday helps loosen the legs. Hitting 50 like this is demanding but very doable if you’ve built up to it.
Notice that 5 days are still relatively easy pace — only Tuesday and part of Saturday carry harder effort.
Pacing and “The Wall” Data
From my own logs, here’s an interesting comparison:
In a marathon where I averaged under 30 mpw in training, I positively split by 15 minutes (second half was 15 minutes slower than the first). I basically crashed and burned.
My pace in the final 10K was a full 2 minutes per mile slower than my early pace. Ouch.
In a later marathon where I averaged around 45 mpw, I ran an almost even split (actually a slight negative split).
My pace only dropped about 10–15 seconds per mile in the final 10K, and that was more due to tactical caution than hitting a wall.
I finished tired, but strong enough to speed up at the end.
What changed between those races?
More mileage. More long runs. Better aerobic base.
I’ve seen similar patterns with athletes I coach: as training mileage goes up across cycles, their fade in the late miles tends to decrease.
Their 20-mile time in the marathon becomes closer to their finish-time indicator (meaning they don’t dramatically slow down after 20).
Simply put: extra miles during training smooth out the fatigue curve on race day.
Instead of a steep cliff at mile 18, it becomes a gentle slope at mile 23.
That’s the difference between surviving and actually racing a marathon.
SECTION: FAQ
Q: Do I really need 50+ miles per week to train for a marathon?
A: Not to simply finish, no.
Many people have completed marathons on less. If your goal is just to cross the finish line by any means (including walk breaks), you can get by with fewer miles.
But if you want to run your best possible marathon (for you) and minimize late-race suffering, a weekly mileage in the ballpark of 50+ is very helpful.
Think of 50 mpw as a benchmark that lots of experienced marathoners gravitate toward because it builds a strong aerobic base.
If 50 isn’t feasible due to life or injury concerns, aim as high as you reasonably can — maybe that’s 40–45 — and you can still do well.
But if you’re dreaming of a significant time goal, be aware that most runners achieving those goals did put in the miles.
There are outliers (some naturally talented runners might run sub-3 on 40 mpw), but those are exceptions.
For most runners chasing something like 4 hours or 3:30, the best results come when they safely push their average mileage upward, with most of it easy.
In short: you don’t have to hit an arbitrary number like 50, but you should strive for as much consistent mileage as you can handle without injury.
Q: How long should my longest run be in training?
A: Conventional wisdom for recreational marathoners is to top out at 18–20 miles for your longest training run.
That prepares you for the distance without the wear and tear of doing 22–24.
Some coaches go by time instead: a longest run of about 3 hours, since beyond that the injury risk can outweigh benefits.
For many runners, 3 hours lands in that 18–20 range anyway.
A few advanced plans include a 22-miler, and elites sometimes go longer, but those are special cases.
For most runners, going beyond 20 doesn’t improve fitness much more, but it does increase recovery demand.
It’s often better to do two quality runs on back-to-back days (like 10 miles + 12 miles) than one 22-miler that wipes you out for a week.
Also, remember: you’ll likely cover 20 miles slower in training than on race day. So the time on feet might already simulate the full marathon time.
My usual recommendation:
- Peak long run: 18–20 miles
- Do it about 3 weeks before the race
- Then taper down
And yes — psychologically, hitting 20 is huge.
It’s “only” 6.2 miles short of the goal, and you trust taper + adrenaline to carry you through the last bit.
Q: Is cross-training enough to replace some of the running?
A: It can replace some, but not all.
Cross-training is a fantastic supplement. It boosts aerobic capacity without pounding your legs.
For injury-prone runners, I often substitute one running day with bike, swim, pool running, or elliptical to reduce impact.
But there are adaptations you only get from running: muscle conditioning, impact tolerance, and the neuromuscular coordination of running stride after stride.
I’ve coached strong cyclists who had huge cardio engines, but their calves and stabilizers still cramped in the marathon because cycling didn’t prepare them for the impact.
My advice:
- Use cross-training to safely increase total aerobic volume
- Still aim to run 3–4 days/week if possible
- Keep the long run as a non-negotiable running day
If you can only run every other day, then yes — cardio on off days helps a lot. You’ll maintain fitness and probably finish fine if you still get key long runs in.
Plans like the FIRST plan (3 runs/week + cross-training) can work, but they’re very focused and often high intensity.
That intensity can be tough to sustain, because all three runs are “important.”
So yes: cross-training counts for cardio, but not 100% for mechanical readiness.
A blend is best.
Q: Can I train for a marathon from scratch in 12 weeks?
A: If “from scratch” means you’re not running at all right now, 12 weeks is very aggressive and generally not recommended.
Most plans are 16+ weeks for a reason — gradual build.
With only 12 weeks, you’d have to ramp quickly, which increases injury risk and reduces adaptation time.
That said, if you have a fitness background and you’re already running 15–20 mpw, 12 weeks might be just enough to get marathon-ready, but it will be tight.
You’ll need:
- ~8–9 weeks to build volume + long run
- 2–3 weeks to taper
There’s very little wiggle room for setbacks.
If you’re truly starting from nothing, I’d recommend a half marathon first or extending the timeline.
If you’re stuck with 12 weeks and you’re already somewhat active, focus on:
- consistency
- careful volume increases
- getting the long run to 16–18 miles by week 9
- tapering properly
And keep expectations realistic — goal may be simply finishing, not racing.
Q: What should I do if I get injured during training?
A: This depends on severity and how far out you are, but rule #1 is:
Don’t run through a real injury.
Pain that changes your gait or worsens as you run is a “stop” signal.
If it’s a minor niggle, sometimes a few days off plus cross-training can fix it early.
For more serious stuff (stress fracture suspicion, severe plantar fasciitis), you may need medical/physio help and a longer break.
Missing 1–2 weeks isn’t the end of the world, especially early or mid-cycle.
You can hold fitness with pool running, cycling, elliptical, etc.
If injury hits 3–4 weeks out, you may need to adjust goals. It’s better to arrive undertrained but healthy than limping.
Sometimes deferring is the smartest move. I know that stings, but one race isn’t worth a long-term injury.
If you do race after missing a lot of training:
- start conservative
- consider a run-walk plan
- listen to the body
- and post-race, actually rehab before chasing the next goal
The marathon will always be there.
Your long-term health matters more.
SECTION: Final Coaching Takeaway
Marathon training isn’t about one heroic workout. It’s about stacking week after week of steady mileage until endurance is basically etched into your bones.
How you feel at mile 26 is the direct result of what you did in the months before.
High mileage (relative to your baseline) is like putting money in the bank. On race day, you withdraw.
Either you’ve got savings… or you’re bankrupt and the wall comes to collect.
If I had to boil marathon success down to one phrase, it’s this:
Respect the distance.
I’ve tried to bargain with the marathon before — do less, hope grit covers the gap.
The marathon doesn’t bargain.
But when you respect it — when you build mileage patiently, with cutback weeks, mostly easy miles, and smart recovery — the marathon rewards you.
It becomes something you can run, not just survive.
Instead of dreading the last 6 miles, you might actually reach mile 20 thinking, okay… now we race.
So how many miles per week should you train?
Ideally: as many as your life and body can handle consistently, mostly easy, generally landing in that 40–60 mpw sweet spot for recreational runners.
Not because it sounds cool.
Because it works.
And because finishing strong feels a whole lot better than crawling in undertrained.
I’ve done it both ways. I’ll take the steady-mileage approach every time.