Runner's knee (the proper name is patellofemoral pain syndrome) is the most common knee complaint in runners and one of the most common injuries in the sport overall. About 1 in 4 runners gets it at some point. It rarely shows up on a scan. Nothing tears, nothing breaks, but the area around or behind the kneecap aches, especially when you go down stairs or run on hills.

This is the beginner's guide to spotting it, fixing it, and stopping it returning. We'll cover what's actually happening, the four-week recovery protocol, and the hip and quad work that makes the difference long term.

What's Actually Happening

Your kneecap (the patella) is supposed to glide cleanly up and down a groove in your thigh bone every time you bend and straighten your knee. When the muscles around it (quads, hips, glutes) aren't pulling evenly, the kneecap drifts slightly out of its track and the underside grinds against the cartilage instead of gliding smoothly.

That grinding is what hurts. It's not a structural injury, it's a tracking problem. Which is why strength work, not rest alone, is what actually fixes it.

How to Tell If It's Runner's Knee

The classic signs:

• Dull ache around or behind the kneecap. Not a sharp pain in one spot, more like the whole front of the joint feels off.
• Worse going down stairs than up. Downhill running flares it. Up is usually fine.
• Sore after sitting still. The "movie theatre sign", knee feels stiff after sitting for a while, eases as you walk.
• No swelling, no clicking, no instability. If your knee swells, locks, or feels like it gives way, that's not runner's knee. See a physio.

Why It Happens

Runner's knee is almost always caused by one of three things, often in combination.

1. Weak Hips and Glutes

This is the big one. If your glute medius (the side of your hip) can't keep your knee tracking straight, it caves in slightly with every step. Multiply that by 5,000 steps per run and you have a tracking problem.

2. Tight Quads or IT Band

Tight muscles pull on the kneecap from one side, making the tracking issue worse. Hip flexors, quads and the IT band on the outside of the thigh are the usual suspects.

3. Sudden Mileage or Hill Increase

Same trigger as shin splints: doing too much too quickly. Hills are particularly punishing on the kneecap because the quad has to work harder going up and the impact is bigger coming down.

The 4-Week Recovery Protocol

Most cases resolve in 2 to 6 weeks with the right approach. The trick is doing strength work alongside the running cutback, not instead of it.

• Week 1: Replace running with cycling or swimming. No hills, no stairs where avoidable. Start daily glute and quad strengthening (3 sets of 12 each: glute bridges, clamshells, terminal knee extensions).
• Week 2: One easy 20 minute run on flat, soft surface. Pain should stay below 3 out of 10 during the run. If it does, continue strength work daily.
• Weeks 3-4: Build back to 50 to 60 per cent of previous mileage, all flat. Add Bulgarian split squats, single-leg glute bridges, and step-downs (slow, controlled, off a small step).
• Week 5 onwards: Reintroduce hills slowly. Keep the strength work in permanently. Two sessions per week is enough.

If pain is sharp, in one specific spot, or if your knee is swelling or giving way, stop and see a physio. Patellar tendinopathy and meniscus issues mimic runner's knee but need different treatment.

The Strength Work That Stops It Coming Back

The Bottom Line

Runner's knee is rarely a knee problem. It's almost always a hip and glute problem that shows up at the knee. Cut the running back, do the strength work, fix the cadence, and most cases clear up within a month.

The mistake is resting it for two weeks, feeling fine, going back to the same training that caused it, and getting it again four weeks later. The injury isn't the issue. The weak link in the chain is. Find it and fix it once.