How to Increase Running Mileage Without Getting Hurt

Why spikes — not miles — cause injuries, and the progression habits that actually protect you

Updated October 20262 minute read

Most running injuries follow a sudden change in load, not high mileage itself: this week doing much more than your recent normal is the pattern that precedes injury. Build with one variable at a time, hold a down week every three to four weeks, and treat the 10% rule as a rough guide — not a guarantee. Sleep and fueling raise how much load you can absorb.

Runner on a quiet tree-lined city street in morning light
Photo: mak_-jp / Pexels

The real rule: spikes, not miles

Ask what causes running injuries and most answers are wrong in the same way — too much focus on how much you run, not enough on how fast that changed. Reviews of training-error research point at the same pattern over and over: injuries follow sudden changes in load. The 20-mile-a-week runner who jumps to 32 is at more risk than the 60-mile-a-week runner holding steady.

The useful mental model is this week versus your recent normal. Sports scientists call it the acute:chronic workload ratio; in plain words: your body has a budget set by what you've consistently done the last month or so. Spend close to budget and you adapt. Spend way over it and the bill arrives — usually as shin splints, runner's knee, or an angry Achilles, and in the worst case a stress fracture.

The 10% rule, honestly

"Never add more than 10% a week" is the most-quoted rule in running — and the direct evidence for it is thin. Studies comparing 10%-rule runners to faster-progressing groups found similar injury rates. So treat it as what it is: a decent brake that keeps you from doing something dramatic, not a force field. Some weeks 10% is too much (coming back tired, poor sleep, new shoes, added speed work); some phases you can absorb more.

The habits that do the protecting

  • One variable per week. Distance, intensity, frequency, terrain, or footwear — change one. Adding hill repeats the same week you extend your long run is the classic self-inflicted injury.
  • Down weeks every 3–4 weeks. Cut volume 20–30% and let bone and tendon — the slow adapters — catch up. Build, build, build, absorb.
  • Long run under control. Keep it roughly a third or less of weekly volume; a 14-mile long run inside a 25-mile week is a spike hiding inside a reasonable total.
  • Sleep and fueling count as training. Under-sleeping and under-eating shrink the load budget — running science keeps finding that recovery states change how much training the same body tolerates. Protect them during a build like you'd protect the long run.

When pain shows up mid-build

It usually whispers first. Use the traffic-light pain rules: mild, stable, settles in a day — train on with care. Climbing, stride- changing, or morning-after pain — cut back now, because two easy weeks early beats two lost months later. Focal bone pain — stop and get the right eval.

Building toward something big?

A race build compresses all of this — the marathon training injury-prevention guide applies these rules to a real calendar, and strength training for runners is the cheapest way to raise your load budget. If your history is "every build ends in the same injury," one visit with a running-focused PT to design the progression is worth more than any generic plan — how to find one, and for locals, the Bay Area running PT directory.

Frequently asked questions

Find a cash-pay PT near you

No referral needed — browse therapists and request an appointment directly.

Ready to feel better?

Compare verified cash-pay physical therapists by specialty, price, and availability — then book online.

Browse running PTs