Lower back pain from running: causes and solutions

Note: Some links in this article may be affiliate links. If you buy through them, we may earn a small commission at no extra cost to you. We only recommend gear and services we genuinely rate. Learn more.

Photo by Kindel Media on Pexels


Your back was fine until you started running more. Or maybe it’s been niggling for months and you’ve been ignoring it, hoping it’ll sort itself out. Either way, you’re here because running and back pain are colliding, and you want to know what’s actually going on — and what to do about it.

Lower back pain is one of the most common complaints among recreational runners. It doesn’t discriminate between the person training for their first parkrun and the one chasing a sub-4 marathon. But unlike some running injuries, back pain is often caused by factors that have nothing to do with your running itself — your desk job, your hip strength, your form under fatigue. That’s actually good news, because it means most of it is fixable.

This article won’t tell you to “listen to your body” and leave it there. You’ll get the actual causes, what to look for, what to do about it, and when to worry.


Why running can cause lower back pain

Running is a repetitive, high-impact activity. Every stride sends force up through your legs and into your spine. For most runners, the spine handles this fine — but when something in the chain isn’t working properly, the lower back picks up the slack.

The lumbar spine (your lower back) sits between your pelvis and your ribcage. It’s designed to be stable, not mobile. When the muscles that should be doing the stabilising — your glutes, your deep core, your hip flexors — aren’t doing their job, the lower back muscles overwork. Over a 10km run, that’s a lot of compensating.

There’s also a postural factor that most people underestimate: if you spend 8 hours a day sitting at a desk, your hip flexors shorten and your glutes switch off. Then you go for an evening run and expect everything to fire correctly. Often it doesn’t, and your back suffers.


The most common causes: a breakdown

Not all lower back pain during or after running has the same root cause. Here’s how to start identifying yours:

Cause Who it typically affects Key symptom
Weak glutes / hip abductors Desk workers, beginners, returning runners Ache across the lower back, worse on longer runs
Tight hip flexors Anyone sitting for long periods Pain at the front of the hip that refers into the lower back
Poor running form (forward lean, overstriding) All levels, especially when fatigued Pain that worsens in the final third of a run
Core weakness Runners who skip strength work Dull ache after runs, not during
Disc irritation or facet joint issues Older runners, those with history of back problems Sharp or radiating pain, sometimes into the leg
Inadequate footwear / excessive road camber Any runner One-sided back pain
Ramping mileage too fast Anyone following an aggressive plan Gradual onset over several weeks

If your pain radiates down one leg, causes numbness or tingling, or is accompanied by any bladder or bowel changes, stop running and see a doctor. That’s not being overcautious — that’s knowing when a GP or physio needs to be involved.


How your running form contributes

Form matters more than most people admit — not because you need to run like a Kenyan elite, but because small mechanical issues compound over thousands of strides.

Two form patterns that commonly load the lower back:

Overstriding. Landing your foot well ahead of your centre of mass creates a braking force that travels up the kinetic chain. Your lower back absorbs what your legs can’t. Try to land with your foot roughly under your hips. If you’re unsure, a short video of yourself running (even from a phone propped against a bench) is genuinely useful.

Anterior pelvic tilt. This is where your pelvis tips forward, increasing the curve in your lower back. It’s often caused by tight hip flexors and weak glutes. Under fatigue — say, the last 5km of a long run — even runners with decent form can slip into this position. Strengthening the posterior chain (glutes, hamstrings) helps keep you in a more neutral position when tired.

Cadence is also worth considering. Slower cadences tend to correlate with longer, heavier strides. A target of around 170–180 steps per minute is commonly cited, though increasing your cadence by even 5–10% can reduce impact loading noticeably.


Strength work that actually helps

The honest answer is that most runners don’t do enough strength work, and the lower back pays the price. You don’t need a gym membership or an hour a day. Three sessions per week of 15–20 minutes, focused on the right areas, will make a genuine difference within 6–8 weeks.

The movements worth prioritising:

Glute bridges — 3 sets of 15 reps. Lie on your back, feet flat, push your hips to the ceiling. Hold for 2 seconds at the top. Single-leg progression when this feels easy.

Dead bugs — 3 sets of 10 per side. Builds deep core stability without loading the spine. Slow and controlled — this is not a speed exercise.

Hip flexor stretching — Hold for 60 seconds per side, daily if you’re a desk worker. The kneeling lunge position, with a posterior pelvic tilt, is the most effective version.

Side-lying clam shells — 3 sets of 15 per side, with a resistance band if available. Targets the glute medius, which stabilises the pelvis during running.

Bird dogs — 3 sets of 10 per side. Opposite arm and leg extended from a four-point position, spine neutral throughout.

You can find structured guidance on incorporating strength and recovery into your routine in articles like hip flexor pain when running: causes and treatment.


Should you keep running with lower back pain?

This depends on the type and severity of pain — there’s no universal answer. Here’s a rough framework:

Mild ache that eases as you warm up, and doesn’t worsen during or after the run: You can usually continue running, but it’s a signal to address the underlying cause. Don’t ignore it and just add mileage.

Pain that starts during a run and gets progressively worse: Stop that session. Rest for 2–3 days. If it improves, return gradually. If it doesn’t, see a physio.

Pain that is sharp, one-sided, or radiates into the leg: Do not run through this. This needs professional assessment — it could indicate a disc issue or nerve irritation.

Research from the NHS notes that most non-specific lower back pain improves with movement and exercise rather than rest, but that’s different from continuing the activity that’s causing it. Light walking, swimming, or cycling while you troubleshoot is sensible.

For runners following a structured plan — say, a 16-week marathon training plan for beginners — missing a week to address back pain now is far better than missing six weeks later with something that’s been pushed too far.


Practical changes to make right now

Beyond strength work and form, there are immediate adjustments that can reduce load on your lower back:

Vary your surfaces. If you’re always running on cambered roads (where one side is higher than the other), you’re putting asymmetric load through your spine every run. Switch sides, or find flatter terrain occasionally.

Check your shoes. Worn-out shoes lose their cushioning and support, increasing the impact your spine has to absorb. As a rough guide, most running shoes are done by 500–800km. If yours have more than that on them, they’re a suspect.

Warm up before you run — properly. Dynamic movement before you set off helps activate the glutes and loosen the hip flexors so they’re not doing nothing when your run starts. Five minutes of leg swings, hip circles and glute activation beats walking straight out the door.

Ease up on weekly mileage increases. The 10% rule — don’t increase total weekly mileage by more than 10% week-on-week — exists for a reason. Aggressive increases overload tissues before they’ve adapted. A 2016 study published in the Journal of Orthopaedic & Sports Physical Therapy found that rapid training load increases are strongly associated with running injuries, including those affecting the spine and pelvis.


When to see a physio

If your back pain has been present for more than 2–3 weeks despite rest and basic self-management, it’s time to see a physiotherapist. This isn’t defeat — it’s the efficient move. A physio can identify whether the problem is muscular, joint-related, or something that needs imaging, and give you a specific plan rather than a generic one.

Look for a physio with experience in running injuries specifically. Not all physios are familiar with the biomechanics of running, and the difference matters.


The honest takeaway

  • Most lower back pain in runners comes from weak glutes, tight hip flexors, or poor form under fatigue — not the running itself. Address the cause, not just the symptom.
  • Three 15–20 minute strength sessions per week — glute bridges, dead bugs, bird dogs, clam shells — will produce noticeable improvement in 6–8 weeks if done consistently.
  • Running through mild, improving pain is usually fine. Running through sharp, worsening, or radiating pain is not.
  • Check your shoes, your mileage ramp-up rate, and your running surface. Small changes here reduce cumulative spinal load across hundreds of kilometres.
  • If pain has lasted more than 2–3 weeks, book a physio. A single assessment will tell you more than a month of guessing.

Next read: How to warm up properly before a run