Tapering Before a Race: How Long, How Much, and How to Handle Taper Madness

Ten days before your marathon, you cut your long run short, your legs feel oddly fine, and somehow you're more anxious about your fitness than you were at the peak of training. That's not a contradiction — it's tapering doing exactly what it's supposed to do, while your head tries to convince you otherwise.

What tapering actually does to your body

Tapering means systematically reducing training volume in the days or weeks before a race while keeping some intensity in your legs, so you arrive on race day rested rather than merely tired-but-less-tired. It sounds simple, but the physiology behind it explains why "just take it easy this week" is a different, weaker thing than a structured taper.

During a normal training block, you're carrying a level of accumulated fatigue that masks your true fitness — you're fitter than you feel, because your muscles, connective tissue, and nervous system are still absorbing the cost of recent hard sessions. A taper strips that fatigue away without stripping away the fitness underneath it. Three things happen in the background as volume drops:

Glycogen stores top up. Muscle glycogen is your primary fuel at race pace, and it stays chronically a little depleted during a heavy training block because you're burning through it faster than easy days can fully replace it. Cut volume and glycogen synthesis catches up, so you toe the line with fuller tanks than you've carried in weeks.

Muscle damage repairs. Hard running — long efforts, downhill sections, anything at speed — causes microscopic muscle damage that your body is constantly patching in the background, only to have the next hard session reopen it. Reducing load gives that repair process room to actually finish.

Blood volume and red blood cell mass consolidate. Training expands plasma volume, and this adaptation, along with a modest rise in red blood cell count, needs a period of reduced stress to fully settle in — part of why a well-tapered runner often reports their easy pace suddenly feeling almost uncomfortably light in race week.

None of this is speculative. Sports-science reviews pooling dozens of taper studies across running, swimming, and cycling put the typical performance gain from a well-executed taper at around 2-3% — on a 4-hour marathon, that's 5 to 8 minutes, delivered not by doing anything new but by finally letting fitness you already earned show up on the clock.

How long should you taper, by distance

Taper length scales with the distance you're racing, because it's really scaling with two things: how much accumulated fatigue you're carrying into race week, and how much glycogen and connective-tissue repair you need before the gun goes off. A 5K build-up doesn't dig nearly as deep a fatigue hole as marathon training does, so it doesn't need nearly as long to climb back out.

Race distance	Taper length	Volume cut by race week	What it's protecting
5K	4–7 days	20–30%	Neuromuscular freshness and leg speed more than deep fuel or tissue repair.
10K	6–9 days	30–40%	A mix of leg freshness and modest glycogen top-up.
Half marathon	10–12 days	40–50%	Real glycogen restoration plus recovery from the harder long-run efforts in the build-up.
Marathon	14–21 days	50–65%	Deep glycogen and connective-tissue repair after the highest cumulative load of any distance, plus a final 36–48-hour carb-load.

These are ranges, not a rulebook — a runner coming off a genuinely brutal marathon build with several 30+ km long runs may want the full three weeks, while someone running a lower-mileage plan might taper closer to two. What all four rows share is the shape of the taper, not just its length: a gradual step down, not a single cliff-edge drop the week of the race.

Volume down, intensity stays

The single most common tapering mistake is treating it as a rest week — cutting volume and dropping every session down to an easy shuffle. That throws away half of what makes a taper work.

The evidence on tapering is unusually consistent on this point: it's training volume that should fall, sharply, while training frequency and intensity stay close to what you've been doing. Keep running most of the days you'd normally run, just for less time or distance each session. And keep a reduced dose of race-pace or threshold work in the mix — short intervals, a few strides, a shortened tempo effort — rather than cutting all intensity and coasting on easy miles alone.

There's a reason for this beyond feel. Intensity is what maintains the neuromuscular sharpness, running economy, and enzymatic adaptations you built during training; volume is mostly what's been generating the fatigue you're trying to shed. Drop the fatigue-generating variable hard and keep the fitness-maintaining variable close to normal, and you get both benefits: rested legs and a nervous system that still remembers how to move fast.

Worked example. A runner averaging 65 km a week in marathon build-up, including a Tuesday interval session and a Saturday long run, might taper like this: week 3 out, volume drops to roughly 45 km with the interval session shortened but still present; week 2 out, volume drops to about 35 km, long run cut to 12-14 km with a handful of goal-pace kilometres inside it; race week, volume drops to 20-25 km across four short, easy runs with one very short set of strides two days out, then nothing but a short shakeout the day before. Frequency barely changes across the three weeks — the runner is still out most days — but total distance falls by well over half, and intensity, in small, controlled doses, never fully disappears.

Taper madness: phantom pains and doubt

Almost every runner who tapers seriously hits a stretch of taper madness — a cluster of physical and mental symptoms that show up right when training volume drops, and that have nothing to do with losing fitness even though they feel exactly like that.

Phantom aches. A twinge in a knee, a tightness in a calf, a niggle that was never there during 100 km training weeks suddenly demanding attention during a 30 km taper week. Reduced training changes the sensory noise your body is used to filtering out; smaller aches that were always present but drowned out by bigger training stress become newly noticeable, not newly created. Unless a pain is sharp, localized, and worsens with easy running specifically, it's far more likely to be taper-week noise than a new injury.

Restlessness and irritability. Regular hard exercise is a mood regulator for most runners, and cutting volume removes a chunk of that regulation right when race-day nerves are climbing. Trouble sleeping, a shorter fuse, and a vague sense of unease in the days before a goal race are reported often enough that they're considered a normal, expected part of tapering rather than a warning sign.

The nagging conviction that fitness is draining away. This is the taper-madness symptom that causes the most damage, because it's the one that tempts runners into a "confidence-boosting" hard workout that undoes the taper's benefit. Fitness built over 8-16 weeks of training doesn't meaningfully erode in 10-14 days of reduced volume — the physiology reviewed above shows the opposite is happening, even when it doesn't feel that way. Trust the plan you followed to get here, not the anxious voice showing up in week 15.

The most reliable fix for all three isn't more information, it's a plan you commit to in advance and follow regardless of how any single day feels — decide your taper schedule while you're calm and rational, then execute it on autopilot when the doubt inevitably arrives.

Race-week checklist

With volume down and doubt up, race week is a good time to shift your attention from training toward the logistics and habits that actually move the needle on race day:

• Lock in sleep, starting two nights out. The night immediately before a race is often disrupted by nerves regardless of what you do — the sleep that actually matters most is two and three nights before, so prioritize it deliberately rather than assuming one good night at the end will cover you.
• Carb-load with intent for anything half-marathon distance or longer. In the final 36-48 hours, shift a noticeably larger share of your calories to carbohydrates and ease off fiber and unfamiliar foods, aiming to walk into the race with glycogen stores topped off rather than merely "not empty."
• Rehearse race-morning logistics once, on paper. Wake time, breakfast timing, transport to the start, gear-check or bag-drop deadlines, and warm-up timing — write it out the way you'd plan a flight, so decision fatigue doesn't creep in on the morning itself.
• Lay out gear the night before, tested, not new. Everything you'll wear and use should have been worn on at least one training run already, including socks and any nutrition you plan to carry — race morning is the wrong day to discover a seam that rubs.
• Keep a short, familiar warm-up. A light jog and a few strides is usually enough; race week is not the moment to add new mobility work or a warm-up routine you haven't used before a hard effort.
• Plan your pacing before the gun, not during mile one. Decide your target splits ahead of time so the adrenaline of the start line doesn't talk you into going out faster than the taper earned you.

That last point is where your taper and your race-day execution actually connect: all the rested legs and topped-up glycogen in the world get spent in the first 5K if you go out too hard on adrenaline. Working out realistic goal splits with the splits calculator before race week, based on a time the race time predictor suggests you're actually fit for, turns your taper's payoff into a pacing plan you can trust when the starting gun goes off — rather than a vague sense that you should "feel good" and hoping that translates into the right number on your watch.