Does Sleep Affect Running Performance? What the Numbers Show
Asier G. Morato
·
·
7
min read
Cover image generated with AI — © Chubby Studio S.L.
KEY TAKEAWAY
Sleep changes running performance by roughly 3% in controlled studies: one sleepless night cut 30-minute treadmill distance by about 3%, and three nights of extra sleep made endurance athletes about 3% faster. Athletes rated the effort the same either way, so short sleep slows you down without feeling any harder.
Yes, and by more than most people expect. In controlled studies, one night without sleep cut the distance runners covered in 30 minutes by about 3%, and three nights of extra sleep made endurance athletes about 3% faster in a time trial. The catch is that you rarely feel it: in both studies the athletes rated the effort the same while their output changed.
This post is about sleep across a training block, not the single rough night before one session (that has its own answer in what one bad night does to a workout). It is one piece of the bigger question of how to actually get faster at running, and the cheapest one.
How much does sleep affect running performance?
Roughly 3% in either direction in the best controlled studies we have, which on a 50-minute 10K is about a minute and a half. The studies are small, so treat it as a sense of scale, but running and cycling experiments agree.
The cleanest running study comes from Bangor University (Oliver and colleagues, 2009). Eleven men ran a 30-minute warm-up at a moderate effort, then a self-paced 30-minute treadmill test to see how far they could get. They did it twice: once after a normal night of a little over eight hours, and once after 30 hours awake. After the sleepless night they covered 6,037 metres on average, against 6,224 metres after normal sleep. In other words, a single night without sleep cost about 3% of the distance.
Thirty hours awake is extreme. The more realistic case is a run of short nights, which a second study tested. At Deakin University, Roberts and colleagues (2019) had nine trained cyclists and triathletes ride a 60-minute time trial on four consecutive days under three conditions: their normal sleep, 30% less time in bed, and 30% more. Normal sleep came out at roughly 6.5 to 7 hours a night, restriction at just under 5. After three short nights, the time trial took 60.4 minutes instead of 58.8.
Why do you run slower without feeling it?
Because short sleep seems to change how much speed a given effort buys you, not how hard you think you are trying. In both studies, ratings of perceived exertion did not differ between conditions. The athletes simply settled into a slower pace that felt exactly as hard as their normal one.
In the Bangor study, average heart rate during the distance test was 174 beats per minute after normal sleep and 170 after the sleepless night, and the runners did not feel like they were trying any less. The authors' explanation is that perception of effort shifted: the same sense of this-is-hard arrived at a lower speed.
That fits the wider research rather than contradicting it. When the workload is fixed, studies across sports find that sleep loss makes the same pace or the same weight feel heavier. Fix the pace and it feels harder; let people choose the pace and they quietly slow down until it feels normal again. Either way, the feel of a run stops being a reliable gauge on short sleep.
So on a short week, a tempo run or race effort run by feel will come out slower and you may blame your fitness. Run strictly to pace and you will be working harder than the plan intended.
Does more sleep make you faster?
In the one controlled study that tested it on endurance athletes, yes. Three nights with roughly one to two hours more sleep than usual improved a 60-minute time trial by about 3%. The evidence is thin, nine athletes on bikes, but it points the same way as every study of sleep loss.
In the Deakin experiment, the extended nights came out at a little over eight hours of actual sleep, against six and a half to seven normally, and three nights of extra sleep made them about 3% faster: 56.8 minutes against 58.7. The authors concluded that endurance athletes should aim for more than eight hours a night.
Read that with care: nine people is a tiny sample, and they were cyclists and triathletes rather than runners. The useful reading is not that everyone needs nine hours. It is that many people who train sleep less than they think, and closing that gap costs nothing but an earlier night.
See which weeks your sleep cost you
FitWoody reads your Apple Watch data, scores your sleep against your own patterns and analyses every run against your personal cardiac load, so you can see your slow weeks next to your short nights. Comes with a 7-day free trial.
Download the app
★★★★★
4.5 · 732 ratings on the App Store
How much sleep do recreational runners actually get?
Less than seven hours, on average, in the largest wearable study of runners so far. A year of Garmin data from 224 recreational runners, published in 2026, found an average of 6.6 hours a night, below the seven-hour minimum that sleep guidelines recommend for adults.
The study (Xu and colleagues, Frontiers in Physiology) matched more than 30,000 days of training and sleep from June 2024 to June 2025. The relationship ran both ways. After heavy training days, runners got slightly less deep and REM sleep and their overnight HRV dipped. After nights under six hours, their next runs were slower on average: 6.15 minutes per kilometre against 6.00 after nights over seven hours.
The honest caveat is that the effects were small and the study is observational, so it cannot say short sleep caused the slower runs. The short-sleep days also included longer runs, which are naturally slower. What it does show is the baseline: most runners who track everything are still short on sleep.
Does poor sleep raise your risk of running injuries?
Probably, but in adult runners the best evidence is about sleep quality rather than hours. A 2025 prospective study that followed 339 runners for six months found lower reported sleep quality was linked to a 36% higher risk of a running injury, while sleep quantity on its own showed no significant link.
Goldberg and colleagues had 339 experienced runners (average age 43) report their sleep, fatigue, soreness and stress every week in an app, while their own watches logged training load. Lower sleep quality, not shorter sleep, was the factor linked to injury, and soreness and fatigue tended to climb in the two weeks before one. The authors describe poor sleep as a possible early warning sign and ask for caution: this is an association, not proof that sleeping better prevents injuries.
Sleep is not the main driver of running injuries, though. Load is, and in particular sudden jumps in the length of a single run, which is why most running injuries are a load problem rather than bad luck. Poor sleep is best read as one more reason to hold back in a week when your load is already climbing.
What should a runner change first?
Protect the timing before chasing the hours. A wake time you hold every day, a bedtime moved 20 to 30 minutes earlier, and extra sleep in the weeks of your heaviest training will usually do more than any single long lie-in at the weekend.
Add sleep before the hard weeks, not after them. The Deakin athletes improved after only three nights of extension, which suggests the benefit shows up quickly, so the week of your longest run or your key race-pace session is the one to be strict about bedtime. Trying to repay a month of short nights in one weekend works less well than you would hope, for reasons we go through in how sleep debt builds and how long it takes to repay.
When sleep goes short anyway (a newborn, a deadline, travel), keep the easy runs, soften the hard session, and do not read one slow tempo run as lost fitness. You did not get slower in a week. You got tired, and tired is temporary.
What can your Apple Watch tell you about sleep and your running?
It can show you the pattern, which is the part you cannot feel. Your watch estimates how long and how regularly you sleep, plus your overnight HRV and resting heart rate. Put next to your runs, that lets you see whether your slow weeks line up with your short ones.
FitWoody is built for that comparison. It scores each night against your own sleep goal and your usual patterns, reads HRV, resting heart rate, temperature, blood oxygen and respiratory rate against your own baselines, and analyses every run against your personal cardiac load. So the same route at the same pace can be read for what it actually cost you after a good week and after a short one. A wrist estimate of sleep is not a lab measurement, so trust trends across weeks more than a single night's graph.
Sleep will not replace easy miles, hard sessions or patience. But it changes how fast you can run on the day, and you will not feel it doing so. If you are chasing a faster time, the cheapest improvement available this week is probably an earlier night. Showing up, in any form, counts, and that includes showing up to bed.
Frequently asked questions
How many hours of sleep do runners need?
Most adults need at least seven hours a night, and the one controlled study on endurance athletes found time-trial performance was best when they slept a little over eight. Individual need varies, so a useful target is the amount that leaves you alert on rest days without an alarm.
Can one bad night of sleep ruin a race?
Rarely. In a lab study, a fully sleepless night cut 30-minute treadmill distance by about 3%, and that was after 30 hours awake, far worse than a restless night before a race. The weeks of sleep leading into the race matter more than the last night.
Does hard running training hurt your sleep?
It can, slightly. In a year-long study of 224 recreational runners, heavy training days were followed by a little less deep and REM sleep and lower overnight HRV. The effects were small, so spreading hard days across the week is a sensible first step before cutting any running.