It usually starts as a niggle at the front of the knee — around or behind the kneecap. Not sharp, not alarming, just there. You run through it. Over a few weeks it gets more insistent: worse going downhill, worse coming down stairs, worse after you’ve been sitting at a desk or in the car for a while. Eventually it’s there for the whole run, and the run after that.
That pattern is runner’s knee — clinically, patellofemoral pain. It’s the single most common running injury, and one of the most commonly mismanaged, because the instinct (rest it, stretch it, ice it) addresses the symptom and not the reason it started.
What’s actually happening
The kneecap (patella) sits in a groove at the end of the thigh bone (the femoral trochlea). Every time you bend and straighten your knee, the kneecap glides up and down that groove. Running is thousands of repetitions of that glide, under load, with your bodyweight coming down through a bent knee on every stride.
Patellofemoral pain develops when the load through that joint exceeds what the tissue can tolerate — and/or when the kneecap isn’t tracking cleanly through its groove. The cartilage behind the kneecap and the surrounding tissue become irritated and pain-sensitised. It’s not usually a structural injury — there’s rarely anything torn or damaged on a scan. It’s a load and mechanics problem.
That’s why the classic aggravators all make sense: downhill running and stairs both increase the compressive load on the joint (the knee bends under bodyweight with the brake on), and the “movie-goer’s sign” — pain after sitting with the knee bent for a long time — happens because a sustained bent position compresses the joint with no movement to relieve it.
Why it started — and why it’s rarely just the knee
Here’s the part most people miss: the knee is usually where the pain is, not where the problem is. The kneecap’s tracking and the load through the joint are governed by structures above and below it. The common drivers:
- Training load errors — the most common single cause. Ramping up distance, frequency, or intensity faster than the tissue can adapt. New runners, returning runners, and anyone chasing an event deadline are the classic cases.
- Hip weakness — particularly the glutes (especially glute med). Weak hip control lets the thigh rotate inward and the knee drift inward under load, which changes how the kneecap tracks. This is one of the most consistently identified factors in patellofemoral pain.
- Quad and load-capacity deficits— if the quadriceps can’t absorb and control the load through the knee, more of it transmits straight into the joint.
- Foot mechanics — excessive pronation changes the rotational forces travelling up through the lower leg to the knee.
- Sudden surface or footwear changes — switching to hills, harder surfaces, or worn-out shoes mid-training-block.
- Cadence and running mechanics — overstriding (landing with the foot well ahead of the body) increases braking forces through the knee on every step.
If you treat only the knee and ignore the hip, the quad capacity, and the training load that triggered it, the pain comes back the moment you return to your previous mileage. This is the same trap as shin splints — addressing the painful site instead of the reason it became overloaded. More on the same pattern with shin splints →
Why rest alone doesn’t fix it
Rest reduces the load, so the irritated joint settles and the pain eases. This is why two weeks off feels like a cure. But rest does nothing for the hip weakness, the quad capacity gap, or the training error that caused the overload. When you go back to running at the volume that caused the problem, the problem returns — because nothing that made the joint vulnerable has changed.
Worse, prolonged complete rest deconditions the very muscles (quads, glutes) you need to protect the joint, which can leave you more vulnerable on return, not less. The goal isn’t to rest the knee back to health — it’s to reduce load to a tolerable level while building the capacity that lets the joint handle running again.
What treatment actually involves
Patellofemoral pain has some of the best evidence behind its treatment of any running injury — and that evidence consistently points to active, loading-based rehabilitation, not passive modalities. There are three components running together.
Load management — not total rest
Running usually doesn’t need to stop entirely. It needs to drop to a level that doesn’t reproduce significant pain — both during the run and the next day. A practical benchmark: pain during the run stays at or below 3 out of 10, settles quickly afterwards, and you’re not worse the following morning. Flat ground, shorter distances, and avoiding hills and stairs temporarily all reduce the joint load while you rebuild.
Hip and quad strengthening — the actual fix
This is the part that resolves it long-term. The strongest evidence in patellofemoral pain supports a combination of hip-focused and knee-focused strengthening. Hip strengthening (glutes, particularly the abductors and external rotators) improves the control of the thigh and how the knee tracks under load. Quad strengthening rebuilds the capacity to absorb load before it reaches the joint.
Hip-targeted work often produces faster early pain relief than knee work alone — but the combination is what produces durable results. This isn’t a few generic exercises off a printout; it’s a progressive loading programme tailored to where your specific deficits are.
Hands-on treatment and running retraining
Manual therapy and soft tissue work to the quad, ITB region, and surrounding structures can reduce pain and improve tolerance in the short term — opening a window to load the joint and do the strengthening work effectively. For some runners, addressing running mechanics directly — increasing cadence slightly to reduce overstriding, for example — meaningfully reduces the load through the knee on every stride. More on how hands-on work and exercise fit together →
What about scans, braces, and orthotics?
Scans— usually unnecessary. Patellofemoral pain is a clinical diagnosis, and an MRI rarely changes management because there’s typically no structural lesion to find. Imaging is reserved for atypical presentations, a clear traumatic mechanism, or failure to respond to proper rehabilitation.
Patellar taping and braces— can provide useful short-term pain relief that makes loading exercises more tolerable. They’re a bridge, not a destination. Relying on a brace without addressing the underlying capacity gap just manages the symptom.
Foot orthotics— can help a subset of people with significant pronation-related mechanics, but they’re not a blanket solution. They work best as one part of a programme, not as a substitute for strengthening.
How long does it take
Caught early, in someone who modifies their load and starts targeted strengthening promptly — often six to eight weeks to get back to comfortable running. A chronic presentation that’s been pushed through for months, with significant hip and quad deconditioning, takes longer — three months or more is realistic, because you’re rebuilding capacity that took a while to erode.
The runners who recover fastest are the ones who stop trying to push through, modify their training early, and commit to the strengthening rather than just resting and hoping. The ones who take longest are the ones who rest until it feels better, return to full mileage, and restart the cycle — sometimes several times before getting it properly assessed.
Returning to running follows the same graded principle as any return to sport: rebuild progressively rather than jumping back to where you left off. More on returning to sport without re-injury →
The bottom line
Runner’s knee is rarely a damaged knee. It’s an overloaded, poorly-supported one — usually a combination of training load that outpaced your capacity and hip or quad strength that wasn’t controlling the joint well enough. Rest settles the symptom; building capacity fixes the cause. For most runners, the path back to running pain-free is modifying load, strengthening the hips and quads properly, and returning gradually — not waiting it out and hoping it’s gone.