How Many Rest Days Do Runners Need? What the Research Says
Asier G. Morato
·
·
7
min read
Cover image generated with AI — © Chubby Studio S.L.
KEY TAKEAWAY
Most runners need one or two rest days a week: two while building up or running hard often, one at five or six mostly easy runs. Where the rest falls matters more than the count, and in trials where runners rested when their morning data dipped, they improved as much or more while doing fewer hard sessions.
Most runners need one or two rest days a week: two while you are building up or running hard often, one once you run five or six days and most of those runs are easy. The number matters less than where the rest falls. A rest day does its job when it comes right after the work it is meant to absorb.
That second part is what most advice skips. The "one or two days" figure is a coaching convention, not the result of a trial that compared rest-day counts, and the studies that come closest point somewhere more useful: runners who rested when their body asked for it, rather than on a fixed calendar, improved at least as much while doing fewer hard sessions.
How many rest days a week do runners need?
For most recreational runners, one or two full days off a week. The right number depends on how much hard running sits around those days and how long you have been running at your current volume. The harder and newer the volume, the closer to two.
In practice it plays out like this. If you run three or four times a week, you already have three or four days without running, so the real question is whether those days are restful. At five runs a week, one or two full rest days fit naturally. At six, one full day off is common, but it only works if most of the other days are truly easy. In your first months of running, three runs on non-consecutive days is the safer pattern, which we explain in how to start running when you are out of shape.
Where does the "one or two rest days" rule come from?
From coaching practice, not from a study that tested it. We could not find a trial that assigned runners to different numbers of rest days and compared their race times, and the articles that repeat the rule quote coaches rather than data. That does not make it wrong. It makes it a sensible default rather than a law.
What the research does settle is the principle underneath it. The joint consensus statement on overtraining from the European College of Sport Science and the American College of Sports Medicine says successful training must involve overload, but must avoid excessive overload combined with inadequate recovery. A short dip in performance after hard training is normal and, once you recover, turns into improvement. Skip the recovery and the same dip can drag on with nothing to show for it.
Why do runners get faster on rest days?
Because the run is only the signal. The changes that make you faster are built in the recovery that follows a session, not during it, and they need the next hard effort to wait until they have happened.
The consensus statement calls the productive version of this functional overreaching: you train hard enough to dip, then recover and come back better. The key word is recover. A hard session followed by another hard session is not twice the training; it often leaves the first one unabsorbed. That is why rest days belong next to the work they are meant to absorb, not wherever the calendar happens to have a gap.
See what your rest days are doing
FitWoody reads your Apple Watch data, scores every run by its cardiac load and compares your HRV and resting heart rate with your own baseline, so you can see your hard days and your recovery side by side. Comes with a 7-day free trial.
Download the app
★★★★★
4.5 · 732 ratings on the App Store
Is an easy run as good as a rest day?
Often, yes, but not always. An easy run at a conversational effort adds very little fatigue for a runner used to the volume. A full rest day is the better choice when your legs are sore, when the volume is new to you, or when the signs of accumulated fatigue are already showing.
The trap is the easy run that is not easy. When recovery days drift to a comfortably hard effort, you collect the fatigue of training without the benefit of rest, which is the pattern behind most of the advice in 80/20 running. If you cannot hold a conversation, it is not a recovery day, whatever the plan calls it.
Should rest days be fixed or decided by your data?
Fixed rest days are a good default, and flexible ones are at least as good. In the studies that let a morning measurement decide when to train hard and when to back off, runners improved as much as, or more than, those on a fixed plan, usually while doing fewer hard sessions.
The first trial, by Kiviniemi and colleagues in 2007, split 26 moderately fit men into a fixed plan and a plan guided by morning heart rate variability for four weeks. The fixed group ran six days a week, four of them hard. The guided group ran hard only when their morning HRV held steady, and switched to an easy session or rest when it dropped. Both got faster, but the guided group's maximal running speed rose more: from 15.5 to 16.4 km/h, against 15.1 to 15.7 km/h on the fixed plan.
It was a small, short study, and later work tempered it. In 2017, Schumann and colleagues followed 24 recreational runners for 12 weeks: one group chose each day's session from their accumulated training load, the other followed a standard four to six sessions a week. Both improved by similar amounts. A 2021 meta-analysis by Düking and colleagues pooled 8 studies and 198 participants and found the same shape. Most data-guided groups did fewer moderate and hard sessions than the fixed groups and performed no worse. The performance advantage was small and not statistically significant, but there were fewer non-responders.
The honest takeaway is not that a number on your wrist should run your week. It is that resting when your body is clearly behind costs you nothing, and often spares you the hard session that would have done more harm than good.
Where should rest days go in a running week?
After the sessions that cost the most: the day after your long run or your hardest workout, or the day before one if you need to arrive fresh. Two hard days in a row with no easy day between them is the arrangement most likely to leave you flat for both.
For five runs a week, one workable shape is rest on Monday, a quality session on Tuesday, an easy run on Wednesday, a second quality session or another easy run on Thursday, rest on Friday, a long run on Saturday and an easy run on Sunday.
Keep one more variable in view: sleep. A rest day after a short night recovers less than one after a full night, and the effects of short sleep on running are measurable even when you cannot feel them.
How can you tell you need more rest than you are taking?
When several signals point the same way for several days: a resting heart rate a few beats above your usual, HRV below your own rolling average, sleep getting worse while training gets harder, and a familiar easy pace that suddenly costs more heartbeats. One of these on one morning means little. Three of them together for a week is your body asking for more rest than your plan is giving it.
Read those signals against your own baseline, because a single number means little on its own: a resting heart rate of 55 is high for one runner and low for another, which is why resting heart rate trends tell you more than any one morning. If the signals stay off for more than a week or two, it is worth understanding the difference between overreaching and ordinary tiredness. Pain is a different matter: anything that hurts in one spot or changes the way you run belongs with a physiotherapist or doctor, not with a rest-day count.
This is where FitWoody fits today. It reads your Apple Watch data and compares your HRV, resting heart rate, body temperature, blood oxygen and respiratory rate with your own baseline each day, so you can see whether you are above, below or in range. Each run is scored by the cardiac load it cost you, and your training load is tracked over weeks. An Apple Watch is required, and it informs you rather than diagnosing anything.
Where to start this week
Look at your last two weeks and mark each day as hard, easy or rest. If hard days sit back to back, or your easy days were not easy, fix that before you change how many rest days you take. Then put one full rest day after your hardest session and keep it, even when you feel good.
Feeling good on a rest day is not a reason to skip it; it usually means the rest is working. Showing up, in any form, counts, and some weeks the most useful way to show up is to stay off your feet.
Frequently asked questions
Is it OK to run every day?
Some experienced runners do, but it only works when most of those runs are genuinely easy and short enough to recover from. For most recreational runners, at least one full day off a week is the safer default, and newer runners do better with runs on non-consecutive days.
Should I take a rest day after a long run?
Usually, yes, or a short easy run at most. The long run is often the biggest single load of the week, so the day after it is the natural place for rest. Avoid scheduling a hard workout the next day.
Do rest days make you lose fitness?
No. One or two days off a week do not cost you measurable fitness; losses from stopping training show up over weeks, not single days. The rest day is when your body adapts to the runs before it.