A first marathon is a long project. The 18 weeks of training are physically more demanding than most beginners expect, and the mental work of building consistency through a full training block is the part most people underestimate. The good news is that the formula for finishing a first marathon is well established. The training has been refined over 60 years of distance running coaching. The plan below is a practical, conservative approach for someone with a 3 to 6 month running base who wants to finish their first 26.2 in a respectable time without breaking themselves in the process.

A few baseline assumptions: you can currently run 6 miles continuously, you run 3 to 4 times per week, and you have access to a long-run route with reasonable footing and hydration options. If your current base is below this, spend 8 to 12 weeks building it before starting the marathon block.

The 18-week structure overview

Week 1 to 4: Base building. Total weekly mileage starts around 18 to 22 miles. Long runs build from 8 to 12 miles. Three weekly runs plus one optional easy session. The goal is consistency, not intensity.

Week 5 to 9: Volume progression. Weekly mileage builds to 28 to 34 miles. Long runs reach 14 to 16 miles. A fourth weekly run becomes standard. One day per week includes some moderate-pace work.

Week 10 to 13: Peak volume. Weekly mileage reaches 36 to 42 miles. Long runs reach 18 to 20 miles. This is the most demanding phase of the program and where most plan failures happen. Sleep, fueling, and recovery become non-negotiable.

Week 14 to 15: Peak long runs. The 20 and 22 mile long runs sit in these weeks. Weekly mileage stays high. These are the longest sustained efforts of the entire block.

Week 16 to 18: Taper. Volume drops by 30 percent, then 50 percent, then 70 percent in the final week. Legs and aerobic system consolidate the training. Race day is the end of week 18.

Long-run progression by week

The long run is the single most important workout in a marathon plan. The progression should be conservative and consistent. A general rule is that long runs increase by 1 to 2 miles per week, with a step-back week every 3 to 4 weeks.

Sample long-run progression:

Week 1: 8 miles Week 2: 10 miles Week 3: 12 miles Week 4: 9 miles (step-back) Week 5: 13 miles Week 6: 15 miles Week 7: 12 miles (step-back) Week 8: 16 miles Week 9: 14 miles (step-back, optional) Week 10: 17 miles Week 11: 18 miles Week 12: 14 miles (step-back) Week 13: 20 miles Week 14: 22 miles Week 15: 18 miles Week 16: 13 miles (taper begins) Week 17: 10 miles Week 18: 4 miles + race

Pace for long runs is critical. Run them 60 to 90 seconds per mile slower than goal marathon pace. For a 4:30 goal marathon (10:18 per mile), long runs should be at 11:20 to 11:48 per mile. This feels slow. It should feel slow. The aerobic adaptations come from time on feet, not from running long runs at race pace.

Weekly schedule template

A typical training week for the middle of the program looks like:

Monday: Rest or 30 minute easy walk. Recovery from weekend long run.

Tuesday: 4 to 6 mile easy run. Conversational pace.

Wednesday: 5 to 7 mile run with some quality work. This is the “tempo” or “marathon pace” day. The middle third of the run is at goal marathon pace or slightly faster.

Thursday: 4 to 5 mile easy run or cross-training. Cycling, swimming, or elliptical for 45 to 60 minutes.

Friday: Rest or 3 mile recovery jog. Light day before the long run.

Saturday: Long run. The big workout of the week.

Sunday: Rest, 30 to 45 minute easy walk, or 4 to 5 mile recovery jog. Total recovery from the long run.

Five running days, one cross-training day, and one full rest day is the standard layout. Beginners sometimes need to start at four running days and add the fifth in the middle phase.

Pace work for first-timers

For first marathoners aiming to finish, complex pace work (track intervals, fartleks, lactate threshold sessions) is not strictly necessary. The biggest gains come from consistent easy mileage and progressive long runs. That said, one moderate-effort run per week speeds up adaptation and prepares the body for racing.

Three options:

Option one: Marathon-pace miles. During the Wednesday run, after a 1 to 2 mile warm-up, run 2 to 6 miles at goal marathon pace. Cool down for the last mile. This builds familiarity with what race pace feels like.

Option two: Strides. At the end of an easy run, do 6 to 8 strides of 80 to 100 meters at fast (not all-out) pace, with full recovery walks between. This adds neuromuscular work without much fatigue cost.

Option three: Tempo run. Run 3 to 5 miles at a comfortably hard pace, roughly 30 seconds per mile faster than goal marathon pace. This builds lactate threshold and is the highest-value quality session for marathoners.

Doing one of these per week, ideally on Wednesday, hits the right balance for most first-timers.

Fueling and the long-run nutrition test

Race day fueling is one of the most common reasons first marathons go badly. The body can store roughly 2,000 calories of glycogen, and a marathon burns 2,500 to 3,500 calories. Without external fuel, most runners hit “the wall” around mile 18 to 22.

Standard fueling protocol: 30 to 60 grams of carbohydrate per hour during the race, starting around mile 6 to 8. Gels, chews, sports drinks, or real food (dates, bananas) all work. The choice matters less than consistency and tolerance.

The key principle: nothing new on race day. Every long run past 12 miles should be a fueling rehearsal. Use the same product, same timing, same volume you plan to use in the race. The gut adapts to fueling under stress with practice, but it needs the practice.

Hydration: drink to thirst is the modern recommendation, not “drink before you are thirsty.” Overhydration causes hyponatremia, which is genuinely dangerous and more common than dehydration in marathon finishers. A reasonable starting point is 4 to 8 ounces every 20 minutes if temperatures are moderate.

The taper

The last 3 weeks before race day are the taper. Mileage drops by 30 percent in week 16, 50 percent in week 17, and 70 percent in week 18 (race week). Intensity does not drop. You should still do short fast strides and a brief tempo segment during taper to keep the legs sharp.

Most runners feel terrible during the first week of taper. Phantom pains appear. Sleep gets worse. Anxiety rises. This is normal. The legs are repairing the cumulative damage from peak weeks and the body has stopped getting its expected daily stress dose. By race week, the freshness returns.

Do not try anything new in the taper. No new shoes (the race-day shoes should have 30 to 60 miles on them already). No new foods. No new workouts. The taper is about consolidation, not gains.

Common first-marathon mistakes

Going out too fast on race day. The most common error. Goal pace feels easy at mile 3 and impossible at mile 22. Start 10 to 15 seconds per mile slower than goal pace for the first 5 miles and let the pace settle.

Skipping the long runs. The 18, 20, and 22 mile long runs are non-negotiable for finishing comfortably. Skipping or shortening these because of schedule pressure shows up at mile 23 on race day.

Adding mileage too quickly. The 10 percent rule (weekly mileage should not jump more than 10 percent week-to-week) prevents most overuse injuries. Marathon plans push this rule. Step-back weeks exist for this reason.

Not training in race-day shoes. The race-day shoes should be the shoes you run your longest runs in. Switching to a new pair in the last 4 weeks is asking for blisters and surprises.

For more on running shoe selection, see our methodology page.

Frequently asked questions

How many miles per week do I need to finish a first marathon?+

Most coaches recommend a peak weekly mileage of 35 to 45 miles for a first marathon if your goal is to finish comfortably. Lower-volume plans of 25 to 35 peak miles per week can work but increase the risk of late-race fatigue, walking breaks, and slower finish times. Higher than 45 per week is rarely necessary for a first attempt.

Do I need to run the full 26.2 miles in training?+

No. The longest training run in most marathon plans is 20 to 22 miles. Running the full 26.2 in training accumulates excessive fatigue without proportional benefit, and most coaches consider it counterproductive. The remaining distance on race day is covered by tapered legs, race-day adrenaline, and a more sustainable pacing strategy.

How long should I have been running before starting a marathon plan?+

A safe baseline is 3 to 6 months of consistent running with a current weekly mileage of at least 15 to 20 miles and a recent long run of 8 to 10 miles. Starting a marathon plan from a lower base substantially increases injury risk, especially during weeks 12 to 16 when long runs reach 18 plus miles.

What pace should I run my long runs at?+

Long runs should be at conversational pace, typically 60 to 90 seconds per mile slower than your goal marathon pace. The point of the long run is time on feet and aerobic adaptation, not race pace simulation. Running long runs too fast is one of the most common training errors that leads to overtraining and injury.

Should I do all my long runs solo or with a group?+

Both have benefits. Group runs make long miles psychologically easier and build accountability. Solo runs teach you to manage pacing, fueling, and the mental work of running tired without external support. A mix of both, with the longest runs sometimes solo to practice race-day independence, works well for most first-timers.

Jordan Blake
Author

Jordan Blake

Sleep Editor

Jordan Blake writes for The Tested Hub.