How slow should a recovery run be?

Updated August 26, 2026 · By the Runked team

Recovery run vs. easy run: what coaches actually mean

"Recovery run" and "easy run" get used interchangeably in casual conversation, but the coaches and sites that define them precisely don't always draw the line in the same place, or draw it at all. The table below lines up four named sources side by side: what each calls the run's purpose, and the pace or effort cue each attaches to it.

Sources: RunnersConnect, "Recovery Runs vs Easy Runs"; vdoto2.com, "What's Your Easy Pace?"; Run161, "Recovery Run: The Forgotten Running Intensity", summarizing Pfitzinger and Douglas's Advanced Marathoning.

Why the definitions don't agree

RunnersConnect treats recovery and easy runs as two different physiological targets. A recovery run's job, in that framing, is to flush fatigue and accelerate muscle repair after a hard workout or long run, capped under 65% max heart rate so the effort stays below anything that could itself count as training. An easy run sits one notch higher, at 65 to 75% max heart rate, and is meant to build aerobic base on its own terms. RunnersConnect's ordinary easy-day pace offset, separate from its recovery-run numbers, is 60–90 seconds per mile (37–56 seconds per km) slower than race pace, the same figure used in Runked's average running pace guide.

Jack Daniels' system, described on vdoto2.com, skips that split entirely. Easy (E) pace, at 59 to 74% of VO2max, is defined broadly enough to cover warm-ups, cool-downs, recovery runs and long runs under one intensity band, on the reasoning that the physiological benefit comes from time spent running at that effort rather than from a separately tuned number for each label.

Pete Pfitzinger and Scott Douglas, in Advanced Marathoning, land closer to RunnersConnect on structure: coaching site Run161 reports their recovery-run guideline as roughly 2 minutes per mile (1:15/km) slower than half marathon pace on flat ground, a distinct, slower category from an ordinary easy day. None of these three sources contradicts the others on what a slow run should feel like; they disagree on whether "recovery" needs its own separate pace category at all, or whether it's simply the far end of one broader easy range.

How to apply it

Whichever formula you use, the effort check matters more than the exact figure: full sentences on the talk test, and if a 1-to-10 scale is more natural, about 2 out of 10 for a true recovery run or 3 to 4 for an ordinary easy day. A recovery run fits the day after a hard session, an interval workout, a tempo run, or a long run, when the goal is arriving at the next hard session recovered rather than adding more training stress on top.

Compare a recovery run to your own easy-day pace, not to anyone else's; in Runked the rank starts everyone at Bronze and only moves on your own runs, the same way a recovery pace only means something measured against your own baseline. See how the running rank works.

Common mistakes with recovery runs

• Running it at easy-day effort. RunnersConnect's framing is that a recovery run creeping past roughly 65% max heart rate starts working like a second training day, undercutting the reason it was scheduled after a hard session.
• Chasing the watch instead of the talk test. Heat, terrain and how tired you already are all shift what a given pace costs on a given day; treat the formulas above as a loose starting point and adjust when the effort feels wrong.
• Treating a slow jog as a substitute for real rest. Pfitzinger and Douglas's approach, per Run161, is built around staying well short of anything that could deplete you for the next hard session. On a day that calls for a full rest day instead, a slow jog doesn't do the same job.

What research does and doesn't show about recovery runs

Whether a recovery run speeds recovery, beyond what doing nothing would, is less settled than the pace tables above suggest. The clearest supporting evidence is Nicholas Gill, Christian Beaven and Christian Cook's 2006 study in the British Journal of Sports Medicine: 23 elite rugby players were split across four post-match recovery strategies, contrast water therapy, a compression garment, light active exercise, and passive rest. Those assigned to light active exercise recovered creatine kinase, a blood marker of muscle damage, faster over the following 84 hours than those assigned to passive rest, and the contrast water therapy and compression garment groups also beat passive rest, a difference the study reports as statistically significant. That study measured one bout of light exercise immediately after a match in rugby players. It did not test a jog the day after a hard run in distance runners, which is what this page means by a recovery run, so it supports light movement over full rest as a general principle more than it proves any specific recovery-run pace, distance or day-after timing.

Coaching site Run161, summarizing the wider literature on the same question, is direct about the gap: "Exercise science has yet to determine a physiological benefit with regards to immediate recovery." Both things can be true at once. Light movement most likely beats full rest after a hard effort, and the specific pace numbers coaches attach to that idea are their own judgment, built on top of that general finding. The research itself did not measure those numbers directly.

What to do next

The pace tables above narrow the range; RPE and the talk test settle the rest on any given day. RPE, the effort scale several of the numbers above are pegged to, is worth understanding on its own before trying to hit an exact heart-rate percentage. If recovery runs keep feeling harder than they should regardless of pace, that overlaps with the signs of overtraining worth ruling out before assuming the formula is wrong. And if the real question is how much total running a week should include before recovery days even become relevant, weekly mileage by level is the place to start.

Frequently asked questions