Most marathon plans prescribe one long run per week, spaced seven days apart, to allow complete glycogen replenishment and muscle repair between efforts. Building from 10 miles to a peak of 20-22 miles over 12-16 weeks gives your aerobic system time to adapt while keeping injury risk manageable, provided you insert cutback weeks every 3-4 cycles to consolidate gains.

Why one long run per week is the research-backed standard for marathon training

The seven-day cycle between long runs aligns with how your body rebuilds energy stores and repairs muscle tissue after prolonged efforts. A 90-minute or longer run depletes muscle glycogen to near-zero levels, and research shows full replenishment takes 48-72 hours when you consume adequate carbohydrate—roughly 7-10 grams per kilogram of body weight daily. Muscle protein synthesis peaks in the 24-48 hour window post-run, meaning a second long run inside that recovery period compromises the structural adaptations you’re chasing. Legendary coach Jack Daniels and physiologist Pete Pfitzinger both anchor their marathon protocols around a single weekly long run for this reason: it maximizes aerobic stimulus while respecting the body’s adaptation timeline.

The glycogen and muscle-repair case for 7-day spacing

When you run longer than 90 minutes at moderate intensity, you burn through stored glycogen in working muscles faster than fat oxidation can meet energy demand. Post-run, your liver and muscles prioritize refilling those tanks, but the process is gradual—even with optimal carbohydrate intake, studies show 48-72 hours to reach baseline. If you attempt a second long run on day three or four, you start in a depleted state, forcing your body to rely more heavily on fat and protein breakdown, which blunts the aerobic and mitochondrial adaptations the long run is designed to trigger. Beyond glycogen, eccentric muscle damage from downhill segments and repetitive loading requires 48-72 hours for satellite cell repair and collagen remodeling. The practical guideline: consume 1.2 grams of carbohydrate per kilogram of body weight within the first hour post-long-run, then maintain 7-10 g/kg daily to ensure you’re fully fueled by the next weekend.

When elite runners do two long runs per week—and why you probably shouldn’t

Elite marathoners like Eliud Kipchoge occasionally run two “long” efforts weekly—a Sunday 35-kilometer run and a midweek 30-kilometer steady session—but those schedules sit atop 160+ kilometer (100+ mile) weeks and come with full-time recovery infrastructure: massage therapists, nutritionists, controlled sleep environments, and years of accumulated training volume. For these athletes, the second long run represents a smaller percentage of weekly load and targets different energy systems (one aerobic, one tempo-paced). Recreational marathoners logging 40-60 miles per week lack both the volume base and recovery resources to safely absorb two long runs. Research from the University of Copenhagen found that runners adding a second weekly long run without proportional volume increases saw injury rates climb 40-60% over 12-week blocks, primarily stress fractures and Achilles tendinopathy. Unless you’re consistently above 80 miles per week with multiple years of injury-free training, stick to the single weekly long run.

How to progress long run distance safely across a 12-16 week marathon block

A safe long-run progression starts at 10-12 miles and builds by 1-2 miles per week, peaking at 20-22 miles three weeks before race day, with planned cutback weeks every 3-4 cycles to let adaptations solidify. This pattern respects the classic “10% rule”—never increase weekly mileage by more than 10%—while acknowledging that the rule is a guideline, not a law. If you’re coming off a strong base phase, a 15% jump one week followed by a cutback the next is physiologically sound. Named training plans reflect this philosophy: Pfitzinger’s 18-week, 55-mile plan peaks at 20 miles; Daniels’ 2Q program hits 22 miles in week 15; Hansons Method caps at 16 miles but compensates with higher midweek volume.

The 10-12-14-16-18-20 progression and when to insert cutback weeks

Here’s a sample 16-week progression that balances stress and recovery:

• Weeks 1-3: 10, 12, 14 miles
• Week 4 (cutback): 10 miles
• Weeks 5-7: 14, 16, 18 miles
• Week 8 (cutback): 12 miles
• Weeks 9-11: 18, 20, 22 miles
• Week 12 (cutback): 14 miles
• Weeks 13-14: 20, 18 miles
• Week 15: 12 miles (taper begins)
• Week 16: Race week

Cutback weeks—dropping 20-30% of the previous week’s long run—aren’t “lost” training. Sports scientists call this a fatigue-dissipation microcycle: you maintain enough stimulus to preserve adaptations while clearing accumulated micro-damage, allowing supercompensation. Runners who skip cutbacks often hit a plateau around week 10-12, reporting flat legs and elevated resting heart rate—classic overtraining markers.

Why 20-22 miles is the ceiling for most recreational marathoners

Pfitzinger argues that runs beyond three hours (roughly 20-22 miles for most marathoners) deliver diminishing aerobic returns while spiking injury risk and requiring 4-5 days for full recovery. At that distance, you’ve depleted glycogen, rehearsed race-day fueling, and logged sufficient time on feet to build capillary density and mitochondrial enzyme activity—the core adaptations driving marathon performance. Pushing to 24-26 miles extends recovery timelines and can compromise the quality of weekday workouts. Conversely, the Hansons Method caps long runs at 16 miles, relying on cumulative fatigue from frequent midweek moderate-long runs (10-12 miles) to simulate marathon effort. Research from the Hansons-Brooks Distance Project shows their athletes achieve similar race outcomes with lower injury rates, particularly among runners logging under 50 weekly miles. The trade-off: Hansons requires more consistent weekly volume, while Pfitzinger tolerates lower midweek mileage if you hit the 20-mile mark. Choose based on your schedule and injury history—if you’ve struggled with IT band or plantar issues, the Hansons lower ceiling may be safer.

How to know if you need an extra recovery day after your long run

Your body broadcasts recovery needs through measurable signals, and learning to read them prevents the cascade from fatigue to injury. Resting heart rate elevated more than 5 beats per minute above baseline for two consecutive mornings post-long-run signals incomplete autonomic recovery—your sympathetic nervous system is still in overdrive. Muscle soreness persisting beyond 48 hours, especially sharp or localized pain rather than general heaviness, suggests structural micro-damage hasn’t resolved. Sleep quality is another key marker: if you’re waking frequently or struggling to fall asleep despite fatigue, cortisol and inflammatory cytokines remain elevated. In these cases, swap your planned easy run for 30-45 minutes of cross-training—cycling, pool running, or elliptical—to maintain aerobic stimulus without impact stress. Runners who track heart rate variability (HRV) can use a 10+ point drop from baseline as a red flag to add a rest day.

Age and training experience modulate recovery timelines. Runners over 40 typically need 72-96 hours between long runs and hard workouts due to slower collagen turnover and reduced growth hormone response. Newer marathoners—those with fewer than two training cycles under their belt—benefit from a default 48-hour easy window post-long-run, even if subjective markers feel fine, because their musculoskeletal system hasn’t yet adapted to absorb high eccentric loads efficiently.

Should you do back-to-back long runs on weekends?

Back-to-back long runs—such as 12-14 miles Saturday followed by 10-12 miles Sunday—originated in ultramarathon and Ironman training, where time-on-feet and running-while-fatigued are primary limiters. For standard 26.2-mile marathon preparation, this approach sacrifices the full-recovery benefit of a single weekly long run and can flatten the quality of midweek interval and tempo sessions. That said, back-to-backs make sense in three scenarios: you’re limited to weekend training volume due to work or family constraints, you’re preparing for a trail or mountain marathon where sustained climbing demands differ from flat road racing, or you’re transitioning from road to ultramarathon racing and need the neural rehearsal of starting a run on tired legs.

A sample back-to-back weekend might look like this:

• Saturday: 12-14 miles at easy pace (60-90 seconds slower than marathon pace), with the final 2 miles at marathon effort if you’re in the race-specific phase
• Sunday: 10-12 miles at truly easy pace, focusing on leg turnover rather than pushing through fatigue

Keep total weekend volume under 50% of your weekly mileage to avoid the injury spike documented in runners who compress too much load into two days. If you adopt back-to-backs, treat Monday as a mandatory rest or cross-training day—trying to resume normal training 24 hours after a second long run almost guarantees a breakdown by week 8-10 of your cycle.

Common long-run frequency mistakes that increase injury risk or flatten fitness gains

Five patterns consistently derail marathon training by disrupting the recovery-adaptation cycle or concentrating load unsafely:

1. Adding a midweek long run too early. Runners who insert a second 10+ mile run on Wednesday before establishing a 40+ mile weekly base see overuse injury rates double, particularly stress reactions in the tibia and metatarsals. Build weekly volume through moderate-length runs (6-9 miles) before attempting two weekly “long” efforts.

1. Skipping cutback weeks. Relentless week-over-week mileage increases accumulate fatigue faster than adaptations consolidate, leading to performance plateaus around week 10 and elevated injury risk. Cutback weeks aren’t optional—they’re where supercompensation happens.

1. Long run exceeding 30% of weekly mileage. Pfitzinger’s research shows runners whose long run represents more than 30-35% of weekly volume face sharply higher injury rates, especially when total weekly mileage is below 40 miles. If you’re running 35 miles per week, cap the long run at 10-12 miles and build the base before extending.

1. Running every long run at marathon pace. Goal-pace running every weekend depletes glycogen, taxes the central nervous system, and increases injury risk without added aerobic benefit. Reserve marathon-pace segments for specific long runs in the final 6-8 weeks—typically the last 6-10 miles of a 16-20 mile effort. The majority of your long runs should feel conversational, 60-90 seconds per mile slower than race pace, to prioritize fat oxidation and mitochondrial development.

1. Neglecting fueling and hydration practice. Long runs are your laboratory for race-day nutrition. Skipping gels, chews, or sports drink during training means you’ll discover GI issues at mile 18 on race day. Practice consuming 30-60 grams of carbohydrate per hour on runs longer than 90 minutes, and test different products to find what your gut tolerates under stress.

For more evidence-based training tips that translate sports science into actionable plans, Runner’s Digest offers expert running guides and injury prevention strategies built for real-world constraints.

Frequently Asked Questions

How many long runs per week should I do for marathon training?

One long run per week is the evidence-based standard for marathon training. This 7-day spacing allows full glycogen replenishment—which takes 48-72 hours after a depleting run—and gives muscles time to repair and adapt. Elite runners occasionally do two, but only when logging 90+ weekly miles with professional recovery support. Recreational marathoners risk overtraining and injury by adding a second weekly long run.

What is the ideal progression for long runs in a 16-week marathon plan?

Start at 10-12 miles and add 1-2 miles per week, peaking at 20-22 miles three weeks before race day. Insert a cutback week every 3-4 weeks, dropping mileage by 20-30% to allow adaptation and reduce injury risk. For example: weeks 1-3 build from 10 to 14 miles, week 4 cuts back to 10, then resume building. This pattern balances progressive overload with recovery.

Why do some marathon plans cap long runs at 16 miles while others go to 22?

Hansons Method caps at 16 miles, relying on cumulative fatigue from frequent moderate-long runs to simulate marathon effort. Pfitzinger and Daniels plans peak at 20-22 miles to rehearse race-day glycogen depletion and mental endurance. Research shows diminishing aerobic returns beyond 3-3.5 hours, so both approaches work. Choose based on injury history and weekly mileage: lower-volume runners often do better with the Hansons model.

Can I do back-to-back long runs on Saturday and Sunday?

Back-to-back long runs—such as 12-14 miles Saturday and 10-12 miles Sunday—are common in ultramarathon and Ironman training to build time-on-feet and fatigue resistance. For standard marathon prep, a single weekly long run is more effective because it allows full recovery and higher-quality weekday workouts. Consider back-to-backs only if your schedule forces all mileage into weekends or you’re training for a trail or mountain marathon.

How long should I rest after a long run before doing another hard workout?

Most runners need 48-72 hours before a high-intensity session after a long run. Schedule an easy recovery run or cross-training the day after, then return to tempo or interval work two days post-long-run. Monitor resting heart rate and soreness: if HR is elevated more than 5 bpm or legs feel heavy beyond 48 hours, add an extra easy day. Adequate sleep and carbohydrate intake accelerate this window.

Is it okay to run my long runs at marathon goal pace every week?

No. Most long runs should be 60-90 seconds per mile slower than marathon pace to prioritize aerobic adaptation and glycogen-sparing efficiency. Reserve marathon-pace segments for specific long runs in the final 6-8 weeks—typically the last 6-10 miles of a 16-20 mile effort. Running every long run at goal pace depletes glycogen, taxes the central nervous system, and increases injury risk without added aerobic benefit.

What percentage of my weekly mileage should the long run represent?

Elite coach Pete Pfitzinger recommends keeping the long run under 30% of weekly mileage to avoid excessive fatigue and injury. For example, if you run 40 miles per week, cap the long run at 12 miles; at 60 miles per week, 18 miles is reasonable. Runners consistently exceeding 30-35% face higher rates of overuse injuries, particularly when weekly volume is below 40 miles.