You finish a run feeling good, then twenty minutes later your lower back tightens into a dull, achy band across the bottom of your spine — and by the time you've showered and sat down, it's stiff enough that standing back up makes you grunt. If that's the pattern, lower back pain after running is rarely about your spine breaking down. It's about how the rest of your body hands off the work of each stride.
Running is thousands of small, repeated impacts. Every one of them has to be absorbed somewhere. When your hips, glutes, and deep core do their share, your lower back goes along for the ride. When they don't, your back ends up bracing and stabilising on every step, and the ache afterward is the bill for that overtime.
What's actually going on
The lower back isn't built to be a shock absorber on its own. It's meant to stay relatively still and stable while your hips drive movement. The problem starts when the muscles that should drive — mainly your glutes and deep abdominals — are underactive, usually from sitting all day before you lace up.
Sit for eight hours and two things happen. Your hip flexors at the front of the pelvis shorten and tighten. Your glutes at the back switch off and stretch out. Then you go for a run, and your body still has to produce hip extension on every stride — but with the glutes asleep, it borrows that motion from the lower back instead. The spine arches and compresses a little more with each step. Multiply that by a few thousand strides and you get a back that's been working a shift it was never hired for.
This is why the same run can leave one person sore and another fine. It comes down to which muscles are carrying the load, which comes down to your posture and movement pattern. A forward-tipped pelvis loads the lower back very differently than a flattened one.
The ache after a run is usually your back doing your hips' job. Fix the hips and the back goes quiet.
The common culprits behind running back pain
A few patterns show up again and again:
- Tight hip flexors and weak glutes. The classic sitting-then-running combo. Tight in front, asleep behind, so the back overextends to make up the difference.
- Weak deep core. If your trunk can't stay stable, your spine shifts and rotates a little on every stride, and the small muscles along it fatigue and ache.
- Overstriding. Reaching your foot too far out in front sends impact up through a straightened leg into the pelvis and spine instead of letting your hips and knees absorb it.
- Excessive forward or backward lean. Running folded forward at the hips, or leaning back with your hips pushed out, both load the lumbar spine more than a tall, slightly forward-from-the-ankles posture.
- Doing too much, too soon. Ramping up distance faster than your tissues adapt fatigues your stabilisers, and a fatigued stabiliser is a back that takes over.
If your back also flares when you're not running — when you bend over a sink or get out of the car — the running is exposing a pattern that's there all day. That overlap is worth reading about in lower back pain that comes and goes.
How to run without the back pain
Most of the fix happens off the road. The run itself just reveals the weak link.
Wake up the glutes before you go
Spend five minutes activating your backside so it shows up for the run. Glute bridges are the simplest: lie on your back, knees bent, tuck your tailbone slightly, squeeze your glutes, and lift your hips until your body is straight from shoulders to knees. Two sets of ten, slow. Done right, you'll feel it in your backside, not your back — the full how-to is in the glute bridge for back pain guide. Add a set of clamshells or a short walk of side steps with a band around your knees if you have one.
Loosen the front of your hips
Tight hip flexors pull your pelvis forward and force your back to arch as you run. Spend a minute per side in a kneeling hip-flexor stretch: kneel on one knee, tuck your tailbone under, and gently shift your weight forward until you feel a stretch at the front of the hip and thigh of the down leg. Keep the stretch in the hip, not the lower back. More on why this matters in tight hip flexors from sitting.
Fix your form, lightly
Don't overhaul everything at once. Two cues help most people: shorten your stride so your foot lands closer to under your body rather than way out front, and run tall — imagine a string lifting the crown of your head, with a very slight lean forward from the ankles, not folded from the waist.
Build mileage gradually
If you're coming back or ramping up, add distance slowly week to week and keep some easy runs genuinely easy. Fresh legs stabilise; tired legs let the back take over.
What to stop doing
A few habits quietly keep the ache alive:
- Stretching a cold, sore back hard right after a run. Gentle movement is fine; aggressive bending of an already-irritated back is not.
- Sitting straight down for an hour post-run. You've just shortened the hip flexors with impact; parking in a chair locks them shorter. Walk a few minutes first.
- Sucking it up through sharp pain. Dull, fading stiffness is one thing. Sharp or worsening pain is a stop sign.
When to see a doctor
Most post-run back ache is mechanical and settles with the right work. See a clinician promptly if you have numbness, tingling, or weakness spreading down a leg, any loss of bladder or bowel control, pain that started after a fall or hard impact, fever alongside back pain, unexplained weight loss, or pain that's severe or steadily getting worse rather than easing between runs. Those signs point to something running tweaks won't address.
Why the same run hurts one back and not another
Here's the honest part. The advice above helps most runners, but how much it helps you depends on the pattern you're carrying. A back that aches from a forward-tipped pelvis needs a different emphasis than one that aches from a flat back, and a generic glute-and-hip routine can ease one while doing little for the other.
That's the limit of generic running advice — it can't see your alignment. Knowing your own deviations is what turns a list of drills into a routine that actually quiets the ache for good. A posture assessment that measures where your body deviates builds the work around your specific pattern, so the strength you add goes where your stride is leaking. If you want a starting read on your own setup, you can check your posture at home first.
Run tall, wake the glutes, loosen the hips, and build slowly. Then match the work to your body, and the back stops being the part that pays for every mile.
Common questions
Why does my lower back hurt after running but not during?
Often the ache builds from accumulated overwork that you don't notice while adrenaline and movement are masking it. Once you stop and the muscles cool and tighten, the fatigue from your back doing your hips' stabilising shows up as stiffness.
Should I stop running if my lower back hurts?
Not necessarily. If it's a dull ache that fades by the next day, you can usually keep running while you address glute strength, hip mobility, and form. Stop and get it checked if pain is sharp, spreads down a leg, or steadily worsens.
Can weak glutes cause lower back pain when running?
Yes, very commonly. When the glutes are underactive, the lower back takes over the job of extending the hip on each stride, which overloads the spine. Activating and strengthening the glutes is one of the most effective fixes.
Is it better to stretch before or after running for back pain?
Loosen tight hip flexors and do light dynamic movement before you run, and keep any stretching of the back itself gentle afterward. Avoid forcefully stretching a back that's already sore and irritated right after a run.
