On an uphill it's hard to breathe, on a downhill you can finally speed up. But it's exactly this comfortable moment that often decides whether you'll be able to run the last third of a trail properly. Every step down requires not only moving your body but also braking it. Your heart may find it relatively easy, while the front of your thigh accumulates load. "Downhills break your legs" is a figure of speech: it's about muscle fatigue and the consequences of unfamiliar work, not an inevitable injury.
Why the quads are the first to complain
When your foot meets the ground on a descent, the knee bends under load. The quadriceps, a large muscle group on the front of the thigh, resists this bending: it produces force even as it lengthens. This kind of work is called eccentric. It helps absorb speed and keep your body under control so the landing doesn't turn into an uncontrolled fall.
- Concentric work. The muscle produces force and shortens. A simple example is the quadriceps when you stand up from a chair.
- Eccentric work. The muscle produces force and lengthens. The same quadriceps controls a slow lowering onto a chair.
- Isometric work. The muscle holds force without a noticeable change in length, for example when holding a static position.
On a long descent there are thousands of such braking actions. Unfamiliar eccentric work can come with microdamage to muscle structures, a temporary drop in strength, and delayed soreness. That's why in the evening your legs still feel ready, and the next day walking down stairs becomes a task of its own. At the same time, the intensity of pain doesn't let you measure the degree of damage precisely, and the absence of pain doesn't prove full recovery.
The calves work too: they help control the ankle and absorb load. But on many descents the most noticeable braking role falls to the quads. Where exactly fatigue shows up depends on the gradient, surface, speed, foot strike, and your familiarity with the terrain. The formula "only your thighs hurt after a descent" is wrong, as is trying to switch to a forefoot strike on purpose to unload them: that may simply shift the load lower down.
A low heart rate doesn't mean an easy workout
An uphill requires a lot of energy to work against gravity. On a moderate descent, gravity itself provides part of the movement, so oxygen demand and heart rate are often lower. But the energy of movement still has to be absorbed by the muscles. Eccentric work allows you to produce a lot of force at relatively low energy cost. Hence the mismatch: your breathing is calm, but the mechanical load is high.
Cardio load and muscle load are not the same thing. A workout can look easy by average heart rate but require several days of leg recovery. Especially if it's your first long descent after flat routes. On a steep or technical trail, heart rate can rise too: a low heart rate here is not a rule, just a possible scenario.
Delayed muscle soreness often becomes noticeable after 12–24 hours and is felt more strongly in the 24–72 hour window. These are guidelines, not a schedule: after a familiar short descent the reaction may be small, after a long unfamiliar one it may last longer. Your breathing returning to normal within a few minutes says nothing about whether your muscles have recovered their ability to brake your body again.
Recovery metrics on your watch are useful as part of the overall picture, but not as a direct sensor of quadriceps condition. A good energy score or a calm morning heart rate does not cancel out heavy legs. Along with watch data, you should consider sleep, how you feel during normal walking, fatigue on stairs, and how freely your usual movement returns.
How descents eat up the last third of the distance
Let's imagine a hypothetical 30 km trail running route with roughly 1500 m of elevation gain and loss each. If most of the descent falls on a few long sections, your legs get a concentrated dose of braking. The same 1500 m spread over short, gentle rollers can feel different. The total metres alone aren't enough: what matters is the continuity of the descent, the steepness, the rocks and roots, your speed, and how you feel at the start of the section.
A simple calculation shows the scale of repetitions. Over 30 minutes of descent at a cadence of 160–180 steps per minute, you get about 4800–5400 ground contacts, roughly half on each leg. This is an illustration, not a target cadence: real rhythm changes with terrain and technique. And each contact is not equal in load, so the number of steps cannot be turned into a measure of damage.
Now let's imagine a pace choice. A runner goes through an early descent 2 minutes faster than they could at a controlled effort. But over the last 10 km, due to tired legs, they lose a hypothetical 30 seconds per kilometre — that's already 5 minutes. The net loss is 3 minutes. These numbers are made up for arithmetic, not taken from a race report and do not predict any specific person's result.
So long descents can cost more in the final result than climbs, even though they are covered faster. Tired quadriceps control landing worse, the stride becomes more cautious, and flat sections no longer let you make up time. This is not the only reason for a collapse in the last third: nutrition, heat, and overall pace also matter. But the habit of judging effort only by breathing easily leaves descent fatigue unnoticed.
How to prepare your legs: dosage, technique, and strength work
Descent resilience is built gradually. Repeated familiar load is often tolerated more easily than the first time, but that's no reason to start with a long, steep slope. It's better to first master a small volume of controlled downhill running on predictable terrain. A descent after a hard climb is already work on tired legs, not a neutral way back to the start.
- Start with short segments. For a runner without pain who is already used to regular runs, an example introductory session could be 4–6 easy descents of 30–60 seconds on a gentle, even slope. This is not a universal prescription: after a break, even that volume may be too much.
- Leave time to assess the reaction. The next morning doesn't always show the full effect. Before adding load, consider how you feel over the next 48–72 hours and the return of your usual ease of movement.
- Change one parameter at a time. First you can increase total descent time, later the length of a continuous section. Speed, steepness, and technical difficulty should not be increased all at once.
- Move closer to race conditions. Once simple descents feel familiar, gradually add similar terrain and longer sections. You don't need to fully replicate the race volume just to check readiness.
In technique, the benchmark is controlled movement, not maximum speed. Your stride should usually be shorter so you don't place your foot far forward and don't brake too sharply with every landing. Your shoulders are relaxed, your arms help with balance, and your gaze is directed forward along the trajectory rather than constantly down at your toes. The distance you can see ahead depends on your speed and the visibility of the trail. There is no universal cadence and no single correct way to land.
On a steep or slippery section, switching to a walk is a normal control tool. Trying to 'let off the brakes' at any cost is no substitute for technique. If your speed no longer allows you to choose where to put your foot, you need to slow down, not compensate with tense shoulders and leaning back.
Eccentric strength work complements downhill running. Examples include controlled lowering in a squat, split squat, or step-down from a low step. Lowering over 2–4 seconds can serve as a guide for control, but the number of seconds itself guarantees nothing. Range, weight, and number of repetitions depend on experience and movement quality. It's wiser to start with a manageable variation, not taking new work to failure. Don't schedule your first such session next to a long descent or right before a race.
Recovery and situations when it's better to postpone downhill running
After an unfamiliar downhill session, it's more useful to let the load show itself than to immediately test your legs with another hard workout. Sleep, adequate nutrition, and easy days create the conditions for recovery. A light walk or another familiar activity is acceptable if it doesn't increase discomfort or change your gait. Aggressive stretching, painful massage, and another downhill run just to "break up the muscles" don't guarantee a faster return of strength.
- Knee pain. This is not a signal to train your patience, and it is not the same as general soreness in your thighs. You should not push through joint pain to finish a downhill session.
- A recent injury. Returning to technical terrain cannot be decided only by your desire to run or by your watch data. The question of what load is acceptable requires an individual assessment by a specialist.
- Accumulated fatigue. Lack of sleep, heavy legs and worsening coordination are reasons to remove intense downhill work from your training plan. On a technical trail, fatigue also affects how safely you choose your steps.
It's better to return to downhill work not based on "two days have passed," but taking into account the recovery of your usual movements and your overall condition. Sharp localized pain, swelling, or a noticeable change in walking is a reason to stop the load and seek a medical assessment, rather than blaming it all on eccentric exercise. It's impossible to distinguish a normal muscle reaction from an injury remotely based on a description alone.
In 1trAIner, the AI coach builds your plan through the planning cascade Season → Month → Week → Day. Data from Garmin and Apple Watch syncs automatically, and the week is recalculated after every workout. First 7 days free.
This material is for informational purposes and does not replace a doctor's consultation.
