Stretching vs Strength for Runners: What Prevents Injury

Almost every runner alive has been told to stretch. It is the first thing recommended after an injury, the default advice for tight hamstrings, and the thing people feel guilty about skipping. It is also, of all the habits runners maintain in the name of staying healthy, the one with the weakest evidence behind it.

This is not an argument that you should never stretch. It is an argument about what stretching is for, which turns out to be a narrower and more specific job than the ritual implies, and about what should be occupying the time and the belief that currently go into it.

Does stretching prevent running injuries?

No, on the best available evidence. When Lauersen and colleagues pooled 25 randomised controlled trials covering 26,610 people, they found favourable results for every injury-prevention measure they examined except stretching, which showed no protective effect. In the same analysis, strength training reduced injuries to less than a third of the control rate and roughly halved overuse injuries.

A dedicated systematic review of static stretching as part of a warm-up reached the same conclusion independently: all four of the randomised trials it examined found static stretching ineffective at reducing exercise-related injury.

That is a stark comparison, and it is worth stating plainly because so much running advice inverts it.

The two habits sit at opposite ends of the same evidence base. One roughly halves overuse injuries across randomised trials. The other has repeatedly failed to show any effect at all.

Does stretching reduce muscle soreness?

Also no. A Cochrane review of twelve studies found that static stretching before or after exercise did not meaningfully reduce delayed-onset muscle soreness in healthy adults. The average effect was small enough to be irrelevant in practice.

If stretching after a hard session makes you feel better, that is a real experience and there is nothing wrong with it. It just is not doing what you were told it was doing.

Should I stretch before a run?

Not with long static holds, no. The nuance here is genuine and worth getting right rather than flattening into “static stretching is bad.”

A systematic review of the acute effects of stretching found that static stretches held for longer than about 60 seconds per muscle tend to impair subsequent performance, while shorter holds have trivial effects, particularly when followed by dynamic activity. So a two-minute hamstring hold before a track session is a bad idea. Twenty seconds inside a full warm-up that then progresses into drills and strides is fine.

The version with actual support is a progressive warm-up: a few minutes of easy jogging, some dynamic movement through the range you are about to use, then a handful of strides to bring the pace up gradually. It raises tissue temperature, wakes up the nervous system, and rehearses the movement pattern. It is also what most runners intuitively do when nobody has told them to stretch.

What stretching is actually good for

It reliably increases range of motion. That claim is not in dispute, and range of motion occasionally matters to runners in a specific, identifiable way.

The clearest case is the hip flexors. If your passive hip extension is genuinely limited, that limitation shows up at toe-off, where you need the hip to travel behind you. A stretching programme aimed at the hip flexors in people with measured limitation has been shown to change running kinematics. That is a real effect on a real problem. See reduced hip extension in runners for what the sign looks like.

Note the condition attached to it, though. The intervention worked in people who had a measured restriction. Stretching a joint whose range is already adequate does not buy you anything, and most runners who describe themselves as tight do not have a range-of-motion problem at all.

Am I tight, or am I weak?

This is the question that changes what people do, and it is nearly always worth asking before a stretching habit gets built.

The feeling of tightness is a sensation, not a measurement. It is generated by the nervous system, and it frequently shows up in muscles that are working hard, working at long lengths, or protecting something, rather than in muscles that are short. Chronically “tight” hamstrings in runners are a good example: they are often perfectly normal in length and simply working overtime because the glutes are not contributing what they should.

A rough way to tell them apart:

• Actually short: you cannot reach the range passively, with someone else moving the limb or with gravity doing the work. A restriction that is there whether or not you are trying.
• Working hard, feels tight: the passive range is fine, but the muscle feels gripped, gets worse after hard sessions, and comes back within hours of stretching it.

The second one is the common presentation, and the answer to it is not more stretching. It is either more strength in whatever should have been doing the job, or less load for a while.

Chasing that distinction is why the “just stretch it” instinct fails so often. A calf that keeps tightening up on long runs is usually a calf that lacks the strength endurance for the volume, and stretching a fatigued, under-strong muscle relieves the sensation for an afternoon without touching the cause.

What to do instead

Reallocate the time, do not just delete it.

Before a run: five to ten minutes of easy jogging, some leg swings and dynamic movement, a few strides before anything fast. Skip the long holds.

After a run: whatever you enjoy. Some easy stretching if it feels good, because feeling good has value even when it is not doing anything mechanical. This is not a slot with a job to do.

Twice a week, non-negotiable: strength work. Heavy, mostly single-leg, biased toward hips and calves. This is the slot that carries the evidence. The programming detail is in strength training for runners, and the short version is two sessions of 30 to 40 minutes, progressed in load over months rather than repeated at the same weight.

Where you have a genuine, measured restriction: stretch that specific thing, deliberately, and retest whether the range actually changed. Not everything, generically, forever.

And watch your load. The most consistent predictor of running injury is a sudden jump in training. Novice runners who increased weekly distance by more than 30% in a week took on more distance-related injuries than those who stayed under 10%.

Why the myth is so durable

Two reasons, and understanding them makes it easier to let go.

Stretching produces an immediate sensation of relief, which is a powerful teacher. Strength training produces nothing you can feel for about eight weeks. Human beings are not well built for choosing the second one.

And stretching is what you can do when you are injured and frightened. It is free, it feels virtuous, it requires no equipment and no plan, and it fills the space where you would otherwise have to sit with not knowing what is wrong. That is a genuine psychological function, and it is the reason the advice survives its own evidence base.

Keep it honest

Stretching is not harmful, and if you like it, keep it. It just is not injury prevention, it is not recovery, and it should not be the thing you reach for when something starts to niggle.

The thing worth reaching for is the boring one: find out which muscle group is actually under-doing its job, load it properly twice a week for a couple of months, and keep your mileage progression sane. The hard part is the first step, because “which muscle group” is not something you can feel reliably. That is what running gait analysis is for, and it is what RunGait produces from a short phone video: which side is working harder, which capacity is likely behind it, and a strength block aimed at that gap rather than a generic routine. Then you retest and find out if you were right.

If you have pain that persists, worsens, or wakes you up, none of the above replaces a physio. Screening is not diagnosis.