How Many Miles a Week You Need Before a Marathon Training Plan

Full disclosure: Some links in this article are affiliate links. We may earn a small commission at no extra cost to you if you make a purchase through them. Our recommendations are based on what real users report, not on commission size.

What Base Mileage Means and Why It Decides Your First Marathon

Base mileage is the weekly volume you can repeat three or four weeks in a row without nagging pain, crushing fatigue, or skipped runs. That last item carries the most weight. If your Tuesday easy run keeps turning into a rest day because your legs feel like sandbags, you’re over your base — no matter what number sits on your watch.

Treat it as a floor, not a peak. Your base is what you can hit on an unremarkable week: work runs long, the weather turns, you slept six hours instead of eight. Not your best week ever. Your repeatable week.

Where the entry-level number comes from

General coaching practice, not a lab-tested standard, puts the first-marathon entry point at 20 to 30 miles (32 to 48 km) a week, held for at least 8 to 12 weeks before you open a 16- to 20-week plan. Published beginner schedules carry the same assumption from a different angle — Hal Higdon’s Novice plans, for instance, assume you’ve already been running consistently for months and can handle a few miles comfortably before week one. The 20-to-30 range is simply the version of that assumption I’ve seen most coaches write on the whiteboard: enough volume to build on without the plan turning into physical therapy.

The structure logic is easy to see once you map it. An 18-week schedule typically climbs from a 12-mile long run to 20 miles while midweek mileage roughly doubles. Start at 12 total miles and you’re asking tendons, bones, and connective tissue to absorb a jump of 100% or more in four months. Tissue doesn’t adapt that fast. Your lungs will, and that’s the trap — you feel fine aerobically while your shins quietly file a complaint.

What happens if you start under 15 miles a week

Stress stacks too fast, and the blowup almost always lands in weeks 4 through 7. That’s the stretch when long runs cross 14 miles and the midweek runs stop being optional. Those easy Tuesday and Thursday runs are the connective tissue that lets you absorb the long effort. Skip them and Sunday becomes a weekly beatdown instead of a building block.

Signals you’re in that zone:

• Shin, Achilles, or plantar pain that shows up two days after a long run rather than during it
• Heart rate drifting 10 or more beats higher on easy runs at the same pace
• Sleep falling apart midweek, or waking before your alarm with legs that feel heavy and wooden
• Dropping the second midweek run “just this once” three weeks running
• Losing interest in runs you used to look forward to

I’ve watched this play out in training groups year after year, and race date doesn’t change the pattern. The runners who showed up at 25 miles a week sailed through the build. The ones who showed up at 12 spent most of four months fighting the schedule instead of following it — same plan, same coach, very different springs and falls.

If you’re already running more

Runners logging 35 to 45 miles (56 to 72 km) most weeks can start a more aggressive plan, one with tempo work and marathon-pace segments built in from the first month. That’s real headroom. You skip the six weeks most people spend building a chassis and go straight to sharpening the engine.

One caution: don’t confuse a single big week with a base. A 40-mile week followed by three weeks at 15 isn’t a 40-mile base. Look at your last eight weeks and find the number you actually held.

The second gate: your long run

Weekly volume alone doesn’t tell the full story. Add a second checkpoint: an 8 to 10 mile (13 to 16 km) long run completed within the last three weeks, with no walk breaks and no limping the day after. If you can’t clear that, your weekly mileage is probably propped up by a stack of short easy runs that build fitness but not the durability a marathon punishes.

I use both gates together because they catch different problems. High mileage with a weak long run usually means you need more continuous time on your feet, not more total miles. Low mileage with a strong long run means you need frequency — more days of running, shorter and easier.

Which runner are you, and how long should the runway be

Two years of consistent 5K and 10K racing is a completely different starting line than six months of jogging three times a week. Both can get you to a marathon finish, but they need different timelines and different first plans, and you have to be honest with yourself about which one you are.

Here’s how the two timelines fit together. If you’re sitting at 15 to 20 miles a week and just need to firm things up, the shorter 8-week base block covered in the next part of this guide is plenty — you’re confirming a number you mostly already have. If you’re well below 20, or your running has been stop-and-start, plan on 10 to 14 weeks of base building instead, simple easy mileage with one longer run each week. That extra month or two isn’t lost time. It’s the work that lets the 18 weeks after it hold together.

Write your current number down now — the real one, not the week your watch hit a personal best. The four-week audit that follows will tell you whether it’s genuine or whether you’ve been reading your best week as your average.

Benchmark Test: Where Your Weekly Mileage Actually Stands

One timeline for this entire section: four weeks. The seven-day check at the end of the last section told you whether you’re in the neighborhood of ready. Four weeks of logged running tells you the number you actually build a marathon plan on. Same idea, better resolution. If the quick check and the four-week average disagree, the four-week average wins.

Run the Four-Week Audit

Use whatever you already have, whether that’s Strava, Garmin Connect, a paper log, or a note on your phone. Four consecutive weeks, no gaps. Then do three things with the data.

• Total each week separately. Write four numbers in a column. Four weeks, four totals.
• Average them. Say you logged 26, 19, 31, and 24. That’s 25 miles a week. If the 31 came from a vacation week you can’t repeat in normal life, average the other three instead and use 23. Twenty-three is the number you carry forward.
• Count runs per week alongside miles. Four runs every week is a different runner than six runs one week and two the next.

Runs per week predicts how a plan will land far better than volume alone. Four runs a week for four straight weeks builds a rhythm; legs, sleep, appetite, and laundry schedule are already adapted to it. Six runs one week and two the next looks like the same mileage on paper and behaves nothing like it once you start stacking three straight weeks in the thirties.

Pass the Talk Test on Your Longest Run

Mileage can run ahead of fitness, and the long run is where the gap shows up. Think about your longest run in the past month. If you could speak in full sentences out loud at the pace you held through the middle of that run, your aerobic base matches your numbers. If you couldn’t, shave two or three miles a week off your baseline before you commit.

An illustrative case: a runner logging 30-mile weeks built from two hard efforts and three easy jogs, with the talk test failing on every long run. His sustainable baseline was closer to 22, but the plan he picked assumed 30. About five weeks in, everything felt heavy, easy days stopped feeling easy, and the buildup stalled. The numbers weren’t lying. He was reading them wrong.

Count Cross-Training, But Count It Cheaply

Cycling and pool running build the engine. They don’t toughen tendons and bones for impact, so when you estimate running miles, count cross-training hours at half value at most. We’ll run that math properly a little further on.

Four Flags, and What to Do When You See Them

Scan those four weeks for these before you commit to a starting number:

• Shin, heel, or knee pain that lingered more than two days after a run, especially pain you felt on the first steps of the morning.
• Resting heart rate up 7 beats or more from your normal, measured on waking, on two mornings in a row.
• Sleep that got worse as mileage climbed, like waking at 3 a.m. wired or needing naps you never used to need.
• Two or more runs in four weeks that you cut short or skipped because of fatigue rather than schedule.

Two flags, and you set your baseline at the low end of what you can sustain rather than the high end, then repeat the audit in two weeks.

Bone and tendon pain is the exception. It doesn’t get a monitor-it-and-see answer. Any ache in the shin, heel, foot, or hip that lingers beyond 10 to 14 days, or that changes how you walk or run, goes to a sports-medicine physician or a physical therapist who treats runners. Not a general practitioner who tells you to rest, and not another week of waiting. Stress injuries caught in week two cost you a couple of easy weeks. Caught in week nine, they cost you the race.

Write the Number Down

Starting mileage: ______

Put that number where you’ll see it every week. Top of a paper log, pinned note on your phone, the fridge. Runners who track a baseline catch overreaching about two weeks earlier than runners who eyeball it, because the comparison sits right in front of them. Two weeks early is the difference between dropping one easy run and losing three weeks to a strained Achilles.

Aiming low isn’t sandbagging. Adding two miles in week three of a plan takes one decision. Backing off a grumpy Achilles in week two takes a month.

Post your four-week average in the comments once you have it, and tell me whether your long run passed the talk test.

Mileage Targets by Experience, Weekly Time, and Race Goal

Your starting number comes from three inputs, and you need all three before you grab one off a chart: how long you have been running, how many hours a week you actually have, and what finish time you are chasing. A 26-year-old with two years of running and ten free hours a week is not the same runner as a parent of two who can carve out four. Same 26.2 miles, different starting line.

Find your tier below, then adjust with the hours-based math that follows. Read the last two tiers as context, not as your target. If this is your first marathon, you live in the first two or three.

Beginner: first race, under a year of running

20 to 25 miles a week across 4 runs, longest run 8 miles. Four runs looks like Tuesday, Thursday, Saturday, Sunday, with the long run on the weekend and the other three sitting in the 4 to 6 mile range. From this base, a 4:30 to 5:30 first marathon is realistic. Not a fast time, but you finish upright, and most people want to do it again.

I have watched plenty of first-timers jump straight to a 40-mile plan because it felt serious. Most of them were limping by week six. The plan that gets you to the line beats the plan that looks impressive on Strava.

Intermediate: two to four years running, a few 10Ks or a half behind you

30 to 35 miles a week across 5 runs, longest run 10 miles. The aerobic furniture is already in the room, so you add a fifth easy day and stretch the long run. Sub-4:30 is on the table from here, and if your half marathon is already under 2:00, sub-4:15 is fair.

Higher-volume intermediate chasing a sub-4 (context tier, not a first-marathon starting point)

40 to 45 miles a week across 6 runs, one tempo session, one long run. That works out to roughly 5 to 6 hours of running weekly. A typical structure: Monday easy 5, Tuesday tempo 7 with 3 to 4 miles at threshold, Wednesday easy 6, Thursday easy 6, Friday off, Saturday easy 5, Sunday long 12. The tempo and the long run never sit back to back. That spacing is not optional.

This is where the 30 percent long-run rule actually bites. On a 40 to 45 mile week, a 12-mile long run is the ceiling, not a starting point. Twelve on 40 is exactly 30 percent; twelve on 45 is comfortably under it. If you want more Sunday mileage than that, you have to raise the weekday easy runs first. Sixteen miles on a 42-mile week is 38 percent, and it is a common way to land a stress reaction six weeks out from race day. The same logic applies lower down the ladder. A 20-mile long run on a 35-mile week is a red flag, not a badge.

Chasing a Boston qualifier or a sub-3:30 (context tier)

This changes the answer in a real way, and it is not where a first marathon starts. That build usually begins at 45 to 55 miles a week, and most runners attempting it already have a half marathon around 1:40 or faster behind them. A 1:45 half projects closer to a 3:38 to 3:40 marathon, which is a solid race and not a qualifier. If your half sits in that range, spend a season pulling it down before you spend a season chasing Boston. The fitness needed is not a secret, and it does not arrive in sixteen weeks from a 25-mile base.

Translate the target into hours, because hours are what you actually own

Weekly schedules are real, and mileage numbers stay abstract until you convert them. Here is the rough math at common training paces:

• 3.5 to 4 hours of running is about 20 to 25 miles at a 10:00 to 11:00 per mile pace.
• 5 hours is about 28 to 30 miles at 10:30 pace, or 33 miles if you are running closer to 9:00.
• 5.5 hours is roughly 35 miles at a 9:30 average.
• 6 hours gets you to about 40 miles at a 9:00 average.

Build the base around the hours you truly have, not the hours you wish you had. If four hours is your ceiling, you are a 20 to 25 mile a week runner, and that is a perfectly good place to launch a first marathon from. Chase the volume next cycle.

Count only running toward these numbers. Cycling, swimming, and the elliptical are great for your heart, but they do not build the pounding tolerance that marathon day demands. I have watched runners log 8 hours of cross-training and 15 miles of running, then wonder why mile 20 felt like a wall.

Running in kilometers? Here is the conversion

Canadian runners, keep this handy: 20 miles is 32 km, 30 miles is 48 km, 40 miles is 64 km, and 45 miles is about 72 km. Set your watch to the unit you think in and leave it there. Doing pace math in your head at kilometer 30 of a long run is how good sessions turn into bad ones.

One last check before you commit

Pick your tier, write the weekly number on a sticky note, and pull up your last four weeks of training. If your recent average is more than 20 percent below that target, you are not ready for week one of that plan. Run the eight-week base build first, then start. Sixteen miles a week does not become 25 because you signed up.

If you have already run a marathon, drop your starting mileage and your finish time in the comments. Real numbers from real runners help the next person pick a target that will not break them.

An 8-Week Base-Building Schedule to Run Before Your Marathon Plan Starts

This block scales to whatever you’re running right now. Whether you’re at 15 miles a week or 28, the shape of the eight weeks does not change: add frequency first, then push the long run, back off once, then rebuild higher. Eight weeks later you hand off to your 18-week marathon plan from a stronger place.

Weeks 1 and 2: Frequency Before Distance

The first change I’d make isn’t mileage. It’s how often you run. Running three days a week? Add a fourth, short and easy, 3 to 4 miles. That extra day builds more durability in your tendons and bones than two extra miles bolted onto Saturday ever will.

Everything else holds. Long run stays at 6 to 8 miles. If you’ve been running 8 miles every Saturday for a month, it stays at 8. Boring. Correct.

Weeks 3 and 4: All the New Miles Go Long

Add 2 miles to your weekly total and put every one of them into the long run. Cap the long-run increase at 1 mile per week, no exceptions. I’ve watched plenty of runners jump 3 miles on a single long run in week 3, feel fantastic, and spend week 6 on the couch with a shin that hurts to touch. That one-mile cap is the best injury-prevention habit in this entire block.

Week 5: Cut Back on Purpose

Drop weekly volume 20 to 25 percent and shorten the long run to 6 or 7 miles. There’s nothing to prove this week. The work from weeks 3 and 4 gets converted into fitness while you’re running less, and skipping the cutback usually leaves weeks 6 and 7 feeling flat and heavy.

Weeks 6 and 7: Rebuild With More Room

Resume adding 2 to 3 miles a week. You can spread some of that across midweek runs now instead of dumping it all into Saturday. The long run reaches 10 miles by the end of week 6 and 12 miles (19 km) by the end of week 7.

Here’s the test: by week 7, a 10-miler should feel like a normal Saturday rather than an event you plan your whole week around. If it still wrecks you, repeat week 6 instead of pushing to 12.

Week 8: Consolidate, Then Hand Off

Run roughly 80 percent of your peak volume, keep the long run at 10 miles, and start your 18-week marathon plan. If your peak week was 30 miles, week 8 lands near 24 with a 10-mile long run. You enter the plan with a double-digit long run already banked, which makes the first month of marathon training feel manageable instead of terrifying.

The 80/20 Split Runs Through Every Week

At least 80 percent of your weekly miles at a chatty, easy pace. One tempo run or hill session covers the rest. If you can’t speak in full sentences on an easy run, you’re going too fast, and that is the most common reason base-building blocks fall apart.

A Sample 25-Mile Week

Here is what that looks like with the quality session built in:

• Monday: rest
• Tuesday: 5 miles easy, then the strength circuit
• Wednesday: 5 miles total, 1.5 warmup, 2 at tempo, 1.5 cooldown
• Thursday: 4 miles easy
• Friday: rest
• Saturday: 7 miles long, easy pace
• Sunday: 4 miles easy

Twenty easy miles plus one 5-mile quality session. That’s 80/20 almost exactly. The long run is 7 of 25 miles, a touch under 30 percent of the week, and that’s where I want it in the first half of this block. It will drift toward 40 percent in weeks 6 and 7 as the long run grows to 12 miles, which is normal during base building and comes back down once the marathon plan adds midweek volume.

Adjust the midweek numbers up or down to match your starting point. The ratio matters more than the exact totals.

Twice-Weekly Strength, 20 to 30 Minutes

Split squats, step-ups, calf raises, single-leg bridges, dead bugs. Two sets of 10 to 12 reps each, three sets if you have time. Do it after an easy run or on a non-running day, never before a quality session. Tired legs under a tempo run is how a good workout turns into a bad one.

I do mine Tuesday after the easy run with a step and a pair of dumbbells in the garage. Twenty-two minutes, and it’s the reason my calves stopped complaining in the 14-to-20-mile range.

One Piece of Gear Worth Sorting Out First

Grab a second pair of running shoes before week 1 so you can rotate them. Alternating two pairs spreads the wear and lets the foam in each midsole decompress between runs. I’ve had good luck checking current prices on Amazon for last-season versions of shoes I already trust. As an Amazon Associate I earn from qualifying purchases.

If you run this eight-week block, tell me in the comments how the week 5 cutback felt. That’s the week where people either trust the process or start fighting it.

Cardio, Strength, Recovery, and Gear While You Build Miles

You built the base. The job changes now. You are not chasing a new mileage record every week. You are holding what you have, staying healthy, and letting the marathon plan do its work. That takes two short strength sessions, one cross-training day, real sleep, and shoes with foam still in them.

I have watched runners hit 25 miles a week, feel great, and bolt on a fifth easy run because more has to be better. Three weeks later their calves were angry and their easy pace was 30 seconds slower. Two strength sessions and one bike ride do more for your first marathon than another 5 easy miles.

Two Short Strength Sessions, Not Two Long Ones

Twenty to thirty minutes, twice a week. That is the whole prescription. Put them after easy runs on Tuesday and Thursday, or on separate days if your legs feel beat up. Keep the load moderate and stop two reps short of failure. You are teaching tendons and hips to absorb repeated impact, not training for a powerlifting meet.

A simple circuit covers it:

• Split squats or step-ups: 3 sets of 8 per leg
• Single-leg Romanian deadlifts: 3 sets of 8 per leg
• Calf raises: 3 sets of 12 to 15
• Side planks: 3 sets of 30 to 45 seconds per side
• Dead bugs: 3 sets of 10 per side

That hits the hips, calves, and core, which are the three spots that break down first when mileage climbs. Add a light band warm-up before runs if your glutes feel asleep. Strength work lowers overuse injury risk more than another 5 miles of easy running, and it takes less time than you think.

One Cross-Training Session a Week

Bike, elliptical, or pool. Forty-five to 60 minutes at a conversational effort. You get aerobic load with zero impact, and sore calves get a day off from pounding. I like Wednesday on the bike because it breaks up back-to-back run days and lets me judge effort by feel instead of watching pace on my watch.

Calves still tight from Tuesday? Cross-train instead of running. Feeling great? Still keep it easy. The goal is blood flow, not a second hard workout. You can push the last 10 minutes a little if you want, but stay under the point where your legs burn.

Sleep Is Training

Seven to nine hours. Adaptation happens overnight, and growth hormone, glycogen refill, and nervous system recovery all depend on it. Sleep debt shows up first as pace drift on runs that used to feel easy. If your Tuesday easy run suddenly feels like a tempo, check your sleep before you blame your fitness.

I track one thing: how the first mile feels. If two easy runs in a row are harder than they should be, I go to bed 30 minutes earlier for three nights. That usually fixes it. No app required.

A Sample Week at a 25-Mile Base

Here is a week that protects the base while you build toward the plan:

• Monday: Rest or 20 minutes of mobility
• Tuesday: Easy run 4 to 5 miles plus a 20-minute strength circuit
• Wednesday: Bike, elliptical, or pool 45 to 60 minutes
• Thursday: Easy run 4 to 5 miles plus a 20-minute strength circuit
• Friday: Rest
• Saturday: Easy run 4 to 6 miles
• Sunday: Long run 8 to 10 miles

That lands around 20 to 26 miles depending on your easy pace and how long the long run goes. When week one of the marathon plan arrives, the cross-training day stays, one strength session stays, and Sunday belongs to the long run. You keep the structure without adding junk miles.

Retire Shoes on Mileage, Not Vibes

Retire running shoes at 300 to 500 miles (480 to 800 km). A base-building block plus an 18-week plan often means two pairs per marathon cycle. The range is wide because foam, body weight, surface, and gait all change the number. Weigh over 180 pounds or run mostly on pavement? Lean toward 300 to 350 miles. Lighter and mixing in trails? 400 to 500 is reasonable.

Do not wait for a visible hole or a collapsed heel. By the time the outsole looks dead, the midsole has been flat for 50 miles, and your legs pay the bill. Rotate two pairs so midsoles rebound between runs. It is cheap insurance for the last 10K of the race, when dead foam turns into aching quads. I ran my first marathon in a pair with 520 miles on them and felt every step after 20. Now I rotate two pairs and write the purchase date on the inside tongue with a Sharpie.

Once a pair crosses the mileage mark, check current prices on Amazon and compare them against your local running store before you commit. Sometimes the local shop has last year’s model for less. Sometimes Amazon is cheaper and gets it to your door in two days. Either way, you already know your number, so you can buy without guessing.

Put Your Number in the Comments

Post your starting weekly mileage and target race in the comments. Reading what other first-timers are building from makes the next eight weeks a lot less lonely. I read every comment and I will answer questions about fitting strength or cross-training into a busy week. You do not need a perfect base. You need a base you can protect. Do the strength work, buy the second pair before the first pair dies, and show up at week one ready to build.