Ask Tempo

How long does a taper need to be?

Tempo · 5 min read · AI-assisted

A taper is a planned cut in training volume before a race that clears fatigue while keeping fitness. Most tapers run between 3 and 21 days: about 3 to 7 for a 5k or 10k, 7 to 10 for a half marathon, 14 to 21 for a marathon. The training block behind the taper decides where it lands.

What does a taper actually clear?

A taper clears fatigue, not fitness. Aerobic fitness (VO2Max, capillary density, the enzymes that let muscle burn fat and carbohydrate efficiently) builds and decays slowly, over many weeks. Fatigue from the hardest weeks clears far faster: muscle glycogen refills within about 1 to 3 days once volume drops and carbohydrate intake is adequate, and muscle damage from repeated hard efforts settles over roughly one to two weeks.

The gap between slow-moving fitness and fast-clearing fatigue is the whole logic of a taper. Cut enough volume to let the fast-clearing fatigue go, without cutting so much, for so long, that the slow-building fitness starts to erode too.

Why does a marathon taper take longer than a 10k taper?

A marathon taper takes longer because the marathon block behind the taper built more fatigue to clear. Race distance sets the size of the block, and the block sets the fatigue. A 5k or 10k build carries less accumulated load, so a taper of about 3 to 7 days is enough to feel fresh without losing sharpness. A half marathon block runs longer and harder, and most tapers there stretch to 7 to 10 days.

Marathon blocks carry the deepest fatigue of the three, built from months of long runs and threshold work. Tapers of 14 to 21 days are common there because shedding damage at that scale takes about that long. Ultra-distance blocks push the number further out again, with the same mechanism: bigger block, longer taper, same trade.

The trade inside the taper: volume down, sharpness kept

Cutting volume and cutting intensity are different moves, and treating volume and intensity as one move is where tapers go wrong in both directions. Total distance or time on feet drops by somewhere between 20 and 60 percent over the taper window, front-loaded early and steepest in the final days. Intensity and frequency matter less to cut: keeping some faster efforts, even short ones, in the days before a race helps hold the neuromuscular sharpness and pace feel that a pure rest week lets slip.

An undercut taper leaves residual fatigue, and race day shows the leftover fatigue as legs that won't respond. An overcut taper brings the opposite problem: flat, sluggish legs from a system gone quiet, sometimes called staleness. Neither error is about picking the wrong length in the abstract. Both are about the volume-to-recovery ratio inside whatever length gets picked.

One block, two taper lengths

Picture a marathon block whose last big long run lands three weeks before race day. The first taper week keeps most of the running but trims the long run, the second week cuts deeper, and race week keeps short race-pace efforts with little volume around them. The three-week shape sits at the long end of the range and fits a block that ran on schedule.

The second version changes one input: the final two weeks of the peak were cut short by a cold, so far less fatigue went in at the end. A full 21-day taper on that block spends a week clearing fatigue that was never built, which is how staleness starts. A length nearer the 14-day end of the range matches that block better. The race distance stayed the same; the fatigue behind it changed, and the length followed.

Where the ranges stop working

The day ranges assume one goal race at the end of a normal block. A tune-up race in the middle of a build gets a mini-taper of a few days, not the full range, because the block is meant to keep going afterward. A runner coming off low weekly volume has less fatigue to clear, so the short end of the range fits more of the time. Two races close together turn the second taper into recovery from the first, which is its own problem.

Age, training history, how much the peak block really asked, and how well sleep and food held up through the peak block shift the real taper length away from the generic range. A day count copied from a plan sees none of those inputs.

How do you know the taper length is right?

The signals during the taper tell you, not the calendar. The day count is a starting guess, and personal signals confirm or override it. A resting heart rate trending down, easy pace feeling easier at the same heart rate, and sleep normalizing after a hard block mark fatigue actually clearing, not just days passing.

Your own training file is where to check. Compare resting heart rate across the last two weeks of the peak with the first week of the taper, and look at heart rate on easy runs at a pace you know well. Falling numbers on both say the fatigue is going. Numbers that stay high a week into the taper say the block asked for more than the calendar allowed, or something outside training is adding load.

A marathon block that ended on a rough final long run needs a different taper than the same mileage cruised on schedule, and a fixed plan can't see the difference. The days-on-a-calendar number is a reasonable start; whether it was right for a given runner is a question their own data answers better than a generic rule can.