Photo by Matic Zupan on Pexels
You finished a hard session at 7pm, you’re wired by 10pm, and you’re staring at the ceiling wondering why a day of physical effort didn’t knock you out. Or the opposite: you’re sleeping fine on paper — seven hours, in bed by 11 — but you wake up heavy-legged and unrested, like the sleep didn’t actually do anything. Both of these are common, and both are tied directly to how you’re running, when you’re running, and what’s going on in the rest of your life.
Running and sleep have a two-way relationship that most training advice skips over. Good sleep makes your training work better — recovery happens overnight, not during the run itself. But training also changes your sleep, sometimes for the better, sometimes not. A hard interval session at 6pm can leave your nervous system too activated to switch off at 10pm. A long run that leaves you exhausted can mean you fall asleep fast but wake up at 3am anyway. None of this means you’re doing something wrong. It means sleep is a variable in your training, the same way pace and mileage are — and it’s worth managing deliberately rather than hoping it sorts itself out.
This isn’t a “get 8 hours or your training is wasted” lecture. Most runners reading this have jobs, kids, early alarms, and sleep that’s good some nights and rubbish others. The goal here is to understand what’s actually happening physiologically, and find the two or three adjustments that make the biggest difference for your real week — not a perfect one.
What actually happens to your body overnight
Most of the physical adaptation from running doesn’t happen during the run. It happens afterwards, largely during sleep. Deep sleep (the slow-wave stage, usually concentrated in the first half of the night) is when growth hormone release peaks, which drives muscle repair and tissue remodelling. This is the stage that matters most for recovering from a hard tempo run or a long run that left your quads trashed.
REM sleep, which increases later in the night, is more about nervous system recovery and memory consolidation — useful for motor skill learning (your running form adapting) and processing the mental fatigue of a tough training block.
Here’s the practical implication: if you’re consistently cutting sleep short at the end of the night — say, getting to bed late but still waking for an early alarm — you’re disproportionately losing REM sleep, since it’s weighted toward the back half of your sleep cycle. If you’re falling asleep late and waking up through the night, you may be losing deep sleep instead. Different problems, different fixes.
Why hard training sometimes makes sleep worse, not better
The assumption that exercise always helps sleep is only half true. The NHS notes that regular exercise can improve sleep quality, and for most people, most of the time, that’s accurate. But intensity and timing matter.
High-intensity sessions — intervals, hill reps, a hard parkrun effort — raise core body temperature and spike cortisol and adrenaline. Your body needs time to bring those back down before sleep becomes easy. If you train hard within 2–3 hours of bedtime, you may find it takes longer to fall asleep, even though you’re physically tired. This is especially common with evening track sessions or a 6pm 10k time trial.
Easy runs and recovery runs don’t carry the same cost. A conversational-pace run at any time of day rarely disrupts sleep onset, which is one more reason the distinction between an easy run and a genuine recovery run matters more than most runners think — worth reading if you’re not sure you’re actually running your easy days easy.
The sleep-recovery-injury link you can’t train around
Sleep deprivation doesn’t just make you tired. It changes how your body handles training load. Research in sports medicine consistently links reduced sleep duration to higher injury risk and slower tissue repair — the mechanism is straightforward: less deep sleep means less growth hormone release, which means muscle and tendon repair falls behind the damage you’re doing in training.
This matters most when you’re building volume — marathon block, half marathon base phase, or any period where weekly mileage is climbing. If you’re running a 16-week marathon plan on five or six hours of sleep most nights, you’re not getting the same training adaptation as someone on the same plan sleeping seven to eight hours. This isn’t about perfection — it’s about recognising that a heavy training week paired with a bad sleep week is a combination that often produces the ache, tweak, or niggle that derails a block. If you’re already building a base, it’s worth reading about base building for runners properly, because sleep and base-phase volume rise and fall together — you can’t out-train a sleep deficit by just adding more easy miles.
What a bad night actually costs you (and what it doesn’t)
One bad night before a race or a key session is rarely catastrophic. Race-week insomnia — lying awake the night before a half marathon, worrying about the start time — is extremely common, and most runners still perform close to their expected pace the next day. Adrenaline and taper carry you further than people expect.
What actually erodes performance is chronic short sleep: multiple nights under six hours, stacked over weeks. That’s when you see real drops in reaction time, pacing judgement, and perceived effort — a run that should feel like zone 2 starts feeling like threshold.
| Sleep pattern | Short-term race impact | Training impact over weeks |
|---|---|---|
| One bad night before a race | Minimal — adrenaline compensates | None |
| 5–6 hours, 2–3 nights/week | Slightly higher RPE on hard sessions | Slower recovery, more niggles |
| Consistently under 6 hours | Noticeably harder easy runs | Elevated injury risk, plateaued fitness |
| 7–9 hours, most nights | — | Full adaptation from training |
If you’re trying to understand why some sessions feel harder than they should despite easy pacing, checking your recent sleep pattern is a more useful first step than assuming you’re just fatigued or undertrained — it might help to compare how you’re pacing against your actual heart rate training zones to separate “tired legs” from “bad night.”
Practical fixes that work with a real schedule
You don’t need a sleep sanctuary or a digital detox to improve this. A few specific, low-effort changes make a measurable difference:
- Move hard sessions earlier where you can. If you can shift intervals or tempo runs to lunchtime or early evening (finishing by 6–6:30pm) rather than 8pm, you give cortisol and core temperature time to settle before bed.
- Cold shower or 10 minutes of stretching post-run lowers core temperature faster than sitting still, which helps if you can only train in the evening.
- Keep a consistent wake time, even on rest days. Wake time anchors your circadian rhythm more than bedtime does — this is the single highest-leverage change for runners with inconsistent sleep.
- Avoid caffeine after 2pm if you’re training in the evening. Caffeine’s half-life is roughly 5–6 hours, so a 4pm coffee before a 6pm run is still active in your system at 10pm.
- Eat enough post-run. Under-fuelling after a long run or hard session raises cortisol and can fragment sleep later that night — this is one more reason getting protein and carbs in within a couple of hours matters, alongside hitting your overall recovery nutrition.
When poor sleep is a sign to back off, not push through
There’s a difference between “tired from training” and “sleep debt that’s compounding.” Watch for: resting heart rate creeping up 5–10 bpm from your normal baseline, irritability that’s out of character, or easy runs that consistently feel harder than they should at the same pace. Any of these, sustained over a week or more, is a signal to cut volume or intensity — not grind through it on willpower.
This is particularly relevant if you’ve had a string of rough nights and a race or key long run is coming up. Dropping a planned interval session for a genuine easy run, or moving a long run to the weekend when you’ve actually slept, isn’t weakness — it’s the same training logic as resting after a bad run, just applied preventively instead of reactively.
The Honest Takeaway
- If you train hard in the evening, finish by 6–6:30pm where possible — your nervous system needs 2–3 hours to calm down before sleep.
- Protect your wake time, not just your bedtime. A consistent wake time does more for sleep quality than an earlier bedtime alone.
- One bad night before a race won’t ruin it. Multiple bad nights stacked across a heavy training week will — that’s when niggles and plateaus show up.
- Resting heart rate creeping up and easy runs feeling harder than usual are early warning signs of sleep debt — treat them as a reason to back off, not push through.
- You don’t need 8 perfect hours every night. You need most nights to be reasonable, and the ability to recognise when a bad stretch means it’s time to adjust the week’s training, not ignore it.