Injury Prevention 3 min read 21 August 2026 Updated 21 August 2026

IT band syndrome: why it happens to runners, and what actually helps

Iliotibial band syndrome has a very specific personality. It shows up as a sharp pain on the outside of the knee, it often arrives at almost exactly the same point in a run, and it has a cruel habit of feeling completely fine when you walk out the door. You start, you're fine, and then somewhere around the same distance it flares and forces you to stop. Runners describe it as maddening more than agonising, and that's a fair summary.

niek

Close detail of a runner's lower leg and knee mid-stride on asphalt

This isn't medical advice — persistent knee pain is worth getting looked at by a physio. But most IT band trouble in runners has the same root cause, and it's one you have a lot of control over: load.

What the IT band is, and why it hurts

The iliotibial band is a thick strip of connective tissue that runs down the outside of your thigh, from your hip to just below the knee. For years the standard story was that it ”rubs” over the bone and gets inflamed from friction. More recent thinking is that it's more of a compression and irritation problem in the tissue underneath, near the outside of the knee.

For a runner, the mechanism matters less than the pattern. Whatever the exact tissue mechanics, the pain almost always tracks one thing: how much load you've asked that area to absorb, relative to how much it's ready for.

Why runners get it

IT band syndrome is an overuse injury, which is a polite way of saying ”you did too much, too soon, too often.” The usual culprits:

A sudden jump in mileage. The classic trigger. You felt good, so you added a lot at once, and the tissue didn't get a vote.
Lots of downhill running. Downhills load the outside of the knee harder, which is why it flares on hilly races.
Piling on hard sessions without enough easy running or recovery around them.
Weak or tired hips and glutes, which change how your leg tracks with every stride, thousands of times a run.

Notice how many of those are training decisions rather than bad luck. That's the encouraging part.

What actually helps

The honest answer is less satisfying than a gadget, but it works: reduce the load, don't eliminate it, and rebuild gradually.

Runner's legs stepping up a flight of weathered stadium stairs

Cut back, don't stop dead. Drop to a level that doesn't provoke the pain and hold there, rather than resting completely and then jumping straight back to where you were.
Strengthen the hips and glutes. Stronger hips control how your leg tracks, and that's the lever with the best long-term evidence behind it.
Ease off the downhills while it settles.
Foam rolling and stretching can give short-term relief and they feel productive, but treat them as comfort, not a cure. The load management is what actually moves the needle.

If it isn't improving after a couple of sensible weeks, or the pain is sharp and constant, see a physio. That's not a failure; it's the fast route back.

How to stop it coming back

Prevention is the same lever as the fix: progress your training gradually, and respect recovery. Most flare-ups trace back to a spike — a week where the mileage or the hard running jumped ahead of what the body was ready for. Build in a way that your legs can keep up with, keep the majority of your running easy, and treat a big week as something you earn, not something you announce.

Where TrainPlan fits

The problem with managing load by hand is that spikes are hard to see from the inside. A plan written weeks ago doesn't know you added a hilly race and two hard sessions in the same week. TrainPlan builds your training from your own recent running rather than a generic ramp, and adjusts week to week based on how your sessions actually went — so the load climbs at a rate your body can absorb, and a bad week reshapes what comes next instead of stacking on top of it. You can see how the adaptive plan manages the build.

You can absolutely stay healthy without an app. But a lot of overuse injuries are just load spikes nobody caught in time, and that's a problem worth solving.