ISAA Blog

Long Run, Taper and Recovery for a Half or Full Marathon

How long should your long run be, how long to taper, and how many recovery days after a half marathon or marathon? Daniels and the research, with numbers.

September 28, 20268 min read

You've circled the date. A half marathon in April, a marathon in the fall, it doesn't matter: you have a bib and a countdown. And you're asking the same three questions as everyone else. How long should my longest long run be? When do I start tapering? And after the race, how long before I can do intervals again?

Short answers: cap the long run at 25 to 30% of your weekly volume or about 2.5 hours, whichever comes first; taper for about 2 weeks; and take one easy day per 3 km raced. These three moments decide your race more surely than any VO2max workout. A long run that's too long tires you out without building you up. A botched taper puts you on the start line with heavy legs. A rushed comeback costs you the next season. Here's what the references say, numbers included, and what is simply common practice.

What is the long run for?

The long run is the workout that teaches you to keep going. Jack Daniels, in Daniels' Running Formula, puts it at the heart of every half marathon and marathon build: it strengthens your base endurance and gets you used to being on your feet for a long time. It trains your head too. Running 1:45 on a Sunday morning is rehearsing how the second half of the race feels.

You run it at an easy pace. Not race pace, not "a bit faster because I feel good". Daniels files it under his easy paces, and that's what lets you absorb it every week without sacrificing your quality sessions. If you struggle to slow down, we cover it in detail in our article on zone 2 and slow running.

How long should your long run be?

This is the most common question, and Daniels answers it with a two part rule. In Daniels' Running Formula, the long run should not exceed 25% of your weekly volume (up to 30% if you run less than about 64 km a week) or about 150 minutes, that is 2.5 hours, whichever comes first.

Why a cap? Because beyond it, the benefit no longer makes up for the fatigue. The cost climbs (legs wrecked for several days, the following workouts sabotaged) while the endurance gain barely climbs at all. Two and a half hours is the practical limit Daniels proposes; it isn't a threshold measured in a lab, it's a coach's benchmark.

The percentage trap at low mileage

Take a runner doing 20 km a week who's training for a marathon. 30% of 20 km is a 6 km long run. To prepare for 42 km, that's absurd: you can't come out of that ready.

The percentage was designed for runners who train a lot. For them, a quarter of their volume is already a real long run. At low volume, popular training plans, including Hal Higdon's, do the opposite: they keep a long run that grows week after week, and it's the time cap that limits it. It then makes up far more than 30% of the week. That's a coach's adaptation, not the letter of Daniels' book, but it's the only way to prepare for the distance.

Real example: 35 km a week, marathon goal

You run 35 km a week and your easy pace is around 6:15/km. A quarter of your volume is barely 9 km. At your pace, 2.5 hours is about 24 km. That second benchmark guides your build: your long run climbs gradually toward 2.5 hours, and your weekly volume rises with it, so everything doesn't hinge on Sunday.

How to build up your long run

Gradually. No study sets the right rate of increase: it's a coaching convention, shared by Daniels and Hal Higdon in their plans. You lengthen it in small steps, then step back down.

The cutback week every 3 to 4 weeks is a convention too. You shorten the long run and the weekly volume, let your body absorb the work, then start again one notch higher. It's the same logic as in our article on running plateaus: training creates the stress, recovery creates the progress.

Race pace blocks late in the build

In the final weeks, the long run takes on a new role. Daniels' marathon plans slip in segments at marathon pace, often toward the end of the run. The idea: learn to hold race pace when your legs are already tired. Again, this is a coaching practice, not a protocol validated by a controlled trial.

Real example: you run 35 km a week and you're training for a half marathon. Four weeks out, your 14 km long run can finish with 3 km at half marathon pace, everything else easy. If you don't know that pace yet, your VDOT gives it to you from a recent race.

What is a taper and how long should it last?

The taper is the period when you cut your training load before the race to arrive fresh. It isn't complete rest. It's a measured reduction.

The strongest reference is a meta-analysis by Laurent Bosquet and colleagues, published in 2007 in Medicine & Science in Sports & Exercise (Bosquet et al., 2007). It pools 27 studies of competitive athletes. Its conclusion:

  1. A taper of about 2 weeks has the best effect on performance.
  2. Training volume should drop by 41 to 60%, progressively.
  3. Intensity stays the same: you keep your fast paces.
  4. Session frequency stays the same too: you run as often, just shorter.

An earlier review by Iñigo Mujika and Sabino Padilla (Mujika and Padilla, 2003) sums up the goal in one sentence: reduce accumulated fatigue without compromising adaptations. They report a typical performance gain of about 3% after a well run taper.

Real example: tapering from 50 km a week

Your biggest week peaks at 50 km. Over the last two weeks, you drop to around 28 km, then around 20 km counting the race itself, which puts you in Bosquet's range. You keep one short session at marathon pace or threshold, with fewer reps. And you still run your four or five times a week.

Why you gain nothing in the last 10 days

Because fitness builds slowly and fatigue leaves fast. A hard workout produces its fatigue right away; its benefit takes days, even weeks, to settle in. Ten days out from the race, a big session mostly leaves you tired, without time to make you stronger. That's what Mujika and Padilla's logic reflects: the taper keeps your adaptations and wipes out the fatigue.

"You gain nothing in the last ten days" is a coach's rule of thumb, not a measured number. But it follows directly from that observation. And the risk is lopsided: you'll gain almost nothing by making up a missed workout, but you can end up on the start line with heavy legs. When in doubt, do less.

What to do in race week

Race week is not the time to experiment. No new shoes, no new gel, no new breakfast. Everything you'll use on race day should have been tested on a long run. That's runner's common sense, not a study, but it's also why your last long runs serve as a dress rehearsal.

Sleep matters, without panicking over a bad night before the race: pre race nerves are completely normal. Focus on the nights in the days before.

Carb loading: who, how much, when?

The joint position statement of the American College of Sports Medicine, the Academy of Nutrition and Dietetics and Dietitians of Canada (Thomas, Erdman and Burke, 2016) recommends, for efforts longer than 90 minutes, eating 10 to 12 g of carbohydrate per kilo of body weight per day for the 36 to 48 hours before the event.

The 90 minute threshold matters. For a marathon, carb loading is relevant for everyone. For a half marathon, it is if you run longer than an hour and a half; below that, a normal carb rich diet is enough.

Real example: you weigh 70 kg and you run your marathon in 3:50. At 10 g/kg, that's 700 g of carbs a day for two days. That's far more than you'd think: several big plates of pasta or rice, bread, fruit, sugary drinks. Cut back on fiber and fat so it all fits in your stomach, and test the approach before a long run rather than discovering it the night before.

How long to recover after a half marathon or marathon?

Daniels offers a simple rule of thumb: one easy day for every 3 km raced before going back to a quality session. That gives:

  1. About 7 days easy after a half marathon (21.1 km).
  2. About 14 days easy after a marathon (42.2 km).

During that time, no intensity. No intervals, no threshold, no race pace. You can run, walk, ride a bike gently. Complete rest for the first few days is perfectly fine.

What happens in your muscles

This rule isn't a proven number, but it's in line with what we observe. In 1985, Warhol and colleagues took calf muscle samples from 40 marathon runners at different times after the race (Warhol et al., 1985). They saw fiber damage in the 1 to 3 days after, then a gradual repair of mitochondria and myofibrils that stretched over 3 to 4 weeks.

A more recent study of 11 students who finished a marathon (Tojima et al., 2016) tracked creatine kinase, a marker of muscle damage, along with leg muscle stiffness. Creatine kinase peaked the day after the race, and so did soreness. Stiffness in several muscles had still not returned to its pre race level 5 days later.

In other words: your legs can feel more or less normal after a few days while the repair isn't finished. That's exactly why you wait before bringing intensity back.

Real example: you ran your half marathon on a Sunday. Run easy on the days you feel like it until the following Sunday, with no watch and no pace target. Your first quality session comes back the week after. After a marathon, allow two full weeks before your first real interval workout.

Summary

  1. Long run: at an easy pace, capped at 25 to 30% of weekly volume or about 2.5 hours, whichever comes first (Daniels). At low volume, the percentage would make the run too short: the time cap is what limits it.
  2. Progression: in small steps, with a cutback week every 3 to 4 weeks (coaching convention), and race pace blocks at the end of the long run in the final weeks.
  3. Taper: about 2 weeks, volume cut by 41 to 60%, intensity and frequency kept (Bosquet et al., 2007).
  4. Race week: nothing new, and 10 to 12 g/kg of carbs per day for 36 to 48 hours if the effort lasts over 90 minutes (Thomas, Erdman and Burke, 2016).
  5. Recovery: one easy day per 3 km raced, no intensity during that time (Daniels). Your muscles take days, sometimes weeks, to repair.

Your race takes months to prepare. It can be ruined by ten days of overzealousness. Trust the work you've already done.

AI running coach

Ready to run with a coach who gets you?

ISAA analyzes your data and coaches you at your own pace, without judgment.

Free · No commitment