Running With Back Pain: What the Evidence Actually Says
Lower back pain and running have an uneasy reputation as a pair. The assumption — that running is hard on the spine, that it's beating up your discs, that you should probably take it easy or switch to something lower-impact — is one of the more persistent ideas in sport and rehab. The evidence tells a different story.1
Back pain is common. It affects roughly 80 percent of people at some point in their lives, most of the time without a clear structural cause.1 Runners are not exempt — but they're also not uniquely vulnerable. The spine is designed to absorb and transmit load. Running, done progressively, is a form of mechanical input that healthy spinal tissue responds to. The question, as with most running-related pain, is rarely whether you should be running at all. It's whether the load introduced was more than the tissue could handle at that moment in time.
Why the Back Hurts During Running
The most common culprit in running-related low back pain isn't damage to spinal structures — it's how load is being managed and distributed across the body. The lumbar spine doesn't work in isolation. It sits at the junction of the thoracic spine above, the pelvis and hips below, and is directly influenced by how well the rest of the kinetic chain is doing its job.
When hip extension is limited — because of tight hip flexors, reduced glute activation, or altered movement habits — the lumbar spine often compensates by extending further than it needs to. Over the course of thousands of running strides, that repeated compensation pattern accumulates, and the structures bearing extra load eventually register the complaint.
Research has consistently linked hip muscle weakness and imbalance to low back pain in athletes — particularly when hip abductor and extensor strength is reduced relative to the demands being placed on the runner.4 This is one of the clearest examples of regional interdependence in sport: the pain is in the back, but the driver is often a few joints away.
The Load Management Question
When low back pain shows up in a runner, one of the first questions worth asking is what changed recently. A new training block. A jump in weekly mileage. A shift from the treadmill back to outdoor pavement as spring arrives in Winnipeg. A return to running after a winter of lower activity.
Gabbett (2016) described the injury risk mechanism in sport as a mismatch between acute and chronic workload — where the body is asked to absorb a spike in stress before it has built the tissue capacity to do so.3 There are no bad exercises, and there's nothing inherently dangerous about running. The risk emerges when the rate of load increase outpaces the rate of tissue adaptation. The back, the hips, the hamstrings — all of it needs time to catch up when volume or intensity ramps up.
This framing matters practically: it shifts the focus from "should I stop running" to "how do I adjust the load so the tissue can adapt."
What the Research Says Helps
The most consistent finding in the low back pain literature is that movement and progressive loading outperform rest and avoidance for the large majority of presentations.2 This doesn't mean pushing through sharp or worsening pain — it means that controlled, graded movement keeps tissue healthy, maintains strength, and prevents the kind of deconditioning that can turn a manageable episode into a recurring one.
For runners specifically, the evidence points toward a few high-value areas:
Hip strength and motor control — particularly glute max and hip abductor work — to reduce the compensatory demand on the lumbar spine during stance phase
Lumbopelvic stability exercises — targeting the deep stabilizers that support spinal segment control under load, including the multifidus, which has been shown to demonstrate measurable atrophy on the symptomatic side in people with low back pain5
Running mechanics awareness — cadence, forward lean, and hip extension range all influence how much compressive and shear force the lumbar spine absorbs per stride
Gradual return-to-load progressions — rather than binary rest-or-run decisions, managing volume, pace, and terrain incrementally while symptoms are present
When to Get It Assessed
Most running-related low back pain fits a pattern: it's diffuse, it's worse with volume, it improves with rest and some targeted exercise, and it has a clear training-load explanation. That pattern is generally manageable and responds well to the kind of loading and mechanics work described above.
Pain that radiates down one or both legs, pain that wakes you from sleep, or back pain accompanied by changes in bladder or bowel function warrants a more thorough clinical evaluation sooner rather than later. Those presentations suggest nerve involvement or a different underlying process — and the approach to management changes accordingly.
For everything in between, the goal is understanding what's driving the pain, addressing any contributors in the kinetic chain, and building a return-to-running plan that the tissue can actually handle.
At Boreal Spine & Sport, assessments for running-related back pain include evaluation of hip mobility and strength, lumbopelvic movement patterns, and running history — because the back rarely tells the whole story on its own.
References
Hartvigsen J, Hancock MJ, Kongsted A, et al. What low back pain is and why we need to pay attention. Lancet. 2018;391(10137):2356–2367.
Foster NE, Anema JR, Cherkin D, et al. Prevention and treatment of low back pain: evidence, challenges, and promising directions. Lancet. 2018;391(10137):2368–2383.
Gabbett TJ. The training—injury prevention paradox: should athletes be training smarter and harder? Br J Sports Med. 2016;50(5):273–280.
Nadler SF, Malanga GA, Bartoli LA, Feinberg JH, Prybicien M, Deprince M. Hip muscle imbalance and low back pain in athletes: influence of core strengthening. Med Sci Sports Exerc. 2002;34(1):9–16.
Hides JA, Richardson CA, Jull GA. Multifidus muscle recovery is not automatic after resolution of acute, first-episode low back pain. Spine. 1996;21(23):2763–2769.