What it is
A recovery run is a short, deliberately very slow run — usually 20 to 40 minutes — taken the day after hard training. It is slower than an easy run, and that is the entire point.
It is the only run in this guide with no fitness target. You are not trying to build anything. You are trying to move blood through tired legs and get through the day without adding fatigue.
Why it works
Gentle movement increases circulation to muscles that spent yesterday getting damaged, and better circulation means waste products clear and repair materials arrive faster than they would if you sat still. Many runners simply feel less stiff after twenty easy minutes than after a full day off.
It's worth being honest about the evidence here: the research on whether recovery runs meaningfully accelerate recovery is mixed, and the effect is modest at best. The stronger argument is practical. A recovery run lets you add a small amount of aerobic volume on a day when a real run is off the table, and it keeps the habit of running daily intact for people who want that. If it makes you feel worse rather than better, it isn't doing its job.
How to pace it
Slower than you think. Then slower again.
- The talk test. You could recite something from memory without noticing you were running.
- Effort. Around 2–3 out of 10.
- Heart rate. Below 65% of maximum.
If you find yourself checking your pace and feeling faintly embarrassed by it, you're doing it correctly. A recovery run that leaves you tired was an easy run, and an easy run the day after a hard session is a small mistake that compounds.
A sample session
25 minutes, flat route, no watch glances. Pick the flattest, dullest loop you have. Leave the pace screen alone — or turn it off entirely — and finish feeling like you haven't run.
Adding a few minutes of walking at either end is a feature, not a compromise.
When to take the rest day instead
If you're too tired for a recovery run to be genuinely easy, take the rest day.
This is worth saying plainly, because recovery runs are often used to avoid admitting you need a day off. A rest day is a legitimate training decision, not a failure of discipline. Sleep, food, and sitting still are the things that actually repair you; the recovery run is at best a mild accelerant.
The signal to watch for: if your effort feels like a 5 out of 10 at recovery pace, your body is telling you the session should have been a rest day.
Where it fits in your week
The day after a hard workout or a long run, and only then. Two recovery runs a week is plenty; more than that usually means the rest of your week is too hard.
Runners on three or four days a week generally don't need recovery runs at all — their rest days already do the job.
Common mistakes
- Letting it drift up to easy-run effort. The most common failure, and it quietly converts a recovery day into another training day.
- Running it on a hilly route. Hills make effort control almost impossible. Save the interesting terrain for a day when the effort is meant to vary.
- Doing one when a rest day was the honest answer. If you're debating it, that's usually your answer.
Track it in Kamee
Track it if you want the mileage logged, but resist watching live pace on this one — it invites exactly the creeping speed you're trying to avoid. Reviewing your splits afterwards is the useful part: if a recovery run's pace matches your easy runs, it wasn't a recovery run.