Training & planning

Runner's Knee and Shin Splints: Causes, Care and Getting Back to Running

September 29, 2026 · 8 min read

Two of the most common overuse injuries in distance running — what they are, what usually causes them, general self-care, and when to see a professional instead.

In this guide

Runner's knee and shin splints are two of the most common complaints in distance running, and both share the same basic story: a tissue that's been asked to absorb more load than it's currently able to handle, over and over, without enough recovery in between. Neither is an emergency, but both get worse when ignored and respond well to being caught early. This is general background, not medical advice — for pain that's sharp, sudden, or not improving, see a doctor or physical therapist rather than trying to work it out alone.

What is runner's knee?

"Runner's knee" usually refers to patellofemoral pain syndrome — a dull, aching pain around or just behind the kneecap. It typically shows up gradually rather than from a single moment of injury, and it's commonly worse going down stairs, after sitting for a long time with the knee bent, or on downhill sections of a run, where the kneecap is under more load.

What are shin splints?

"Shin splints" (medial tibial stress syndrome, to use the clinical name) is an ache or soreness along the inner edge of the shin bone, usually in the lower half of the leg. It's extremely common in runners who are new to the sport or who have recently increased how much or how intensely they're running — the bone and surrounding tissue haven't yet adapted to the new load.

What usually causes them

Both injuries tend to trace back to the same handful of patterns, which is why they're often discussed together.

  • A sudden jump in mileage or intensity. Tissue adapts to load gradually; a big increase in a short window is the single most common trigger for both.
  • Worn-out shoes. Cushioning and support break down well before shoes look visibly worn — many runners hold onto a pair long past the point where it's still doing its job.
  • Always running the same surface. Consistently hard, unforgiving surfaces (concrete more than asphalt, asphalt more than trail) add up over time.
  • Weak hips and glutes. Poor control at the hip changes how load travels down the leg, and is a commonly cited contributor to knee pain in particular.
  • Going straight from rest back to a full training load. Returning from time off at the same volume and pace as before is a frequent way both injuries recur.

General self-care

For mild, early symptoms, the usual first steps are the same ones used for most overuse running injuries.

  • Relative rest, not total rest. Cutting mileage and intensity, or swapping some runs for cross-training like cycling or swimming, while staying otherwise active.
  • Ice and basic pain management in the first days if the area is irritated, more for comfort than as a cure.
  • Hip and glute strength work. Simple exercises like clamshells, side-lying leg raises and single-leg bridges are widely recommended for supporting the knee specifically.
  • A genuinely gradual return, adding mileage back in small increments rather than jumping straight to where you left off.

Returning to running safely

The general rule most runners are given is straightforward: pain that stays mild and doesn't worsen during a run, and that settles down within a day afterward, is usually a sign it's safe to keep progressing carefully. Pain that gets sharper as a run goes on, or that lingers or worsens over the following day, is a sign to back off further and reconsider — or to see someone about it rather than pushing through.

SignalWhat it usually suggests
Mild ache, steady or improving, gone by the next dayGenerally reasonable to keep progressing gradually
Pain increasing during the run itselfBack off that session and reassess before the next one
Pain still present the next morning, or worsening over daysTime to cut back further, or get it looked at
Sharp, sudden, or severe pain at any pointStop and get it assessed rather than trying to run through it

Preventing a repeat

  • The 10% rule. A commonly cited guideline is to avoid increasing weekly mileage by more than about 10% from one week to the next — not a strict law, but a reasonable ceiling for how fast to add load.
  • Replace shoes on a schedule, not just when they look worn — many runners find somewhere around 300–500 miles a reasonable point to start watching more closely, though it varies by shoe and runner.
  • Keep some strength training in the weekly routine, even just twice a week, rather than treating it as optional.
  • Mix up running surfaces where practical, rather than running the same hard route every time.

Building back toward a race

Once you're running pain-free again, easing back into structured training — rather than jumping straight into a race-specific plan — gives the tissue time to fully catch up to the load. RaceRove's training plans by distance guide lays out a gradual build for every distance from a 5K up, which is a reasonable starting point once you're cleared to build volume again. From there, browse 5K, 10K, half marathon and marathon races with enough lead time to rebuild properly, or the full list of states if you're open to travelling for one.

Putting it together

  1. Catch it early — a dull ache that's easing off is a much easier problem than one that's been run through for weeks.
  2. Cut back to relative rest rather than total rest, and add hip and glute strength work.
  3. Watch how pain behaves during and after running, not just whether it's present at all.
  4. See a professional if it's sharp, sudden, or not improving — this article is background, not a diagnosis.
  5. Once you're pain-free, rebuild gradually with a real training plan rather than returning to your old mileage all at once.

Browse the race database