A dull ache around or behind the kneecap. Worse going downstairs, worse after sitting for a long time, worse during or after running — especially downhill. This is patellofemoral pain syndrome, commonly called runner’s knee, and it’s the single most common diagnosis among recreational runners.

Despite the name, running doesn’t cause it. The problem is almost always one of three things — or a combination of all three.

Training Load

The most common trigger: too much, too fast. A sudden increase in running volume or intensity overloads the patellofemoral joint before the surrounding structures can adapt. The cartilage behind the kneecap receives more compressive force than it can absorb, and inflammation follows.

This is why runner’s knee often appears 3-4 weeks into a new training plan — right around the time that initial enthusiasm leads to mileage jumps that exceed safe progression rates.

The fix is the same as any training load injury: reduce volume to a level that doesn’t produce pain, then rebuild gradually using appropriate volume caps. The knee needs less total load, not no load — complete rest often leads to deconditioning that makes the problem worse when running resumes.

Strength Deficits

The knee is caught between the hip and the ankle. If the hip muscles (particularly the gluteus medius) are weak, the thigh rotates inward during running, changing the tracking of the kneecap through its groove. If the quadriceps are weak or imbalanced, the kneecap doesn’t track smoothly.

Research consistently identifies hip and quadricep weakness as risk factors for patellofemoral pain.[1] The knee isn’t the problem — it’s the victim of dysfunction above and below it.

The strengthening prescription:

  • Hip abductors: Side-lying leg raises, clamshells, banded walks
  • Glute bridges: Standard and single-leg
  • Quadriceps: Wall sits, step-ups, partial squats (pain-free range)
  • Single-leg exercises: Single-leg deadlifts, single-leg squats — these address the functional weakness that bilateral exercises mask

2-3 sessions per week, 3 sets of 10-15 reps. Results typically appear in 4-8 weeks. This isn’t a quick fix — it’s a structural correction that takes time.

Running Form

Form corrections are the most overemphasized and least evidence-based intervention for runner’s knee. There’s limited evidence that deliberately changing your stride reduces patellofemoral pain — and significant risk that conscious form changes create new movement patterns that stress other structures.

Two form-related factors do have evidence:

Stride length. Overstriding (landing with your foot well ahead of your center of mass) increases braking forces and quadricep loading. A shorter stride at the same pace reduces patellofemoral stress. This doesn’t mean forcing a specific cadence — it means not reaching with your feet.

Downhill technique. Downhill running dramatically increases patellofemoral compressive forces. Shorter strides and a slightly higher cadence on descents reduces the load. If hills aggravate your knee, avoid steep downhill runs until the pain resolves.

What Pacewright Does

The algorithm’s safety systems are designed to prevent the training load spikes that trigger runner’s knee:

  • Volume caps prevent sudden mileage increases
  • The spike guardrail prevents abnormally long individual runs
  • ACWR monitoring catches when recent training is outpacing baseline
  • Return-to-training ramps prevent comeback spikes

These systems don’t know about your knee specifically — they prevent the broad class of training errors that cause overuse injuries, of which runner’s knee is the most common.

Healthcare provider note: If anything in this article conflicts with guidance from your healthcare provider, follow your provider’s advice — they know your situation, we don’t.