How to Avoid Injury During Marathon Training
How common is injury during marathon training?
More common than most training plans let on. Studies on marathon training injury rates report incidence ranging from roughly 30% to over 90%, depending on how researchers define "injury" and which population they track. The wide range reflects methodology differences, not that injury is random — but the consistent finding across studies is that most marathon injuries are overuse injuries tied to training load errors, not sudden trauma. That distinction matters because overuse injuries are largely preventable through how you build mileage, not through a single form fix.
The most frequently injured areas in marathon training are the knee, lower leg (shin splints, calf strains), and foot (plantar fasciitis), largely because the marathon's defining stress is repetitive: thousands of nearly identical impacts over weeks. Your job during training isn't to eliminate all risk — it's to keep the rate of loading increase within what your tendons, bones, and muscles can adapt to.
How much should you increase your weekly mileage?
The common guideline is the "10% rule": don't raise your weekly mileage by more than about 10% from one week to the next. It's a useful heuristic, not a scientifically precise threshold — research hasn't confirmed 10% as a hard biological limit, and some runners tolerate faster increases while others need more caution. Treat it as a ceiling, not a target you must hit every week.
What matters more than the exact percentage is avoiding sustained spikes. A jump from 25 to 40 miles in a single week is a common precursor to bone stress injuries and tendinopathy, regardless of what percentage that represents. Build gradually, and when in doubt, add mileage to your longest run before adding more running days.
Fueling matters here too — under-fueling long runs impairs the tissue recovery you need to absorb the next block of training; see how to fuel for long runs for specifics.
Why do cutback weeks matter, and how often should you take one?
A cutback week — dropping total mileage by roughly 20-30% for one week — gives connective tissue time to catch up with the adaptation your muscles made faster. Most marathon plans build this in every 3rd or 4th week. Skipping cutback weeks because you "feel fine" is one of the most common ways injury-prone runners talk themselves into a stress fracture or tendinopathy flare eight weeks before race day.
| Week type | Frequency | Mileage change | Purpose |
|---|---|---|---|
| Build week | Weeks 1-3 of each cycle | +5-10% vs. prior week | Progressive overload |
| Cutback week | Every 3rd-4th week | -20-30% vs. peak week | Tissue recovery, adaptation |
| Taper (final 2-3 weeks pre-race) | Once, before marathon | -20-60%, decreasing weekly | Glycogen/tissue restoration |
Cutback weeks aren't rest weeks — you're still running — but they're the mechanism that lets an 18-week plan add mileage without adding proportional injury risk.
What strength training actually reduces injury risk in marathon training?
Two sessions per week of strength work focused on the hip, glutes, and calf/Achilles complex is the combination most consistently linked to lower injury rates in runners, according to sports-medicine and physiotherapy guidance. Priorities:
- Single-leg strength: step-ups, single-leg squats, split squats — 3 sets of 8-12 reps. Running is a single-leg sport; bilateral squats alone don't fully train the stability marathon running demands.
- Calf and Achilles capacity: standing and seated calf raises, progressing to single-leg — 3 sets of 12-15 reps, 2-3x/week. The lower leg absorbs enormous repetitive load in a marathon buildup.
- Hip abductor and glute work: side planks with leg lift, clamshells, single-leg bridges — targets the hip control that, when weak, is associated with knee and IT band symptoms.
This doesn't need to be a separate gym day. 20-25 minutes after an easy run, twice a week, is enough to matter. Strength training won't guarantee you avoid injury, but the evidence for it as a risk-reduction tool is stronger than for almost any other single intervention, including stretching.
How does running form change under fatigue, and what should you watch for?
Form degrades predictably in the back half of long runs: cadence (steps per minute) tends to drop, stride length often increases as runners unconsciously reach for pace, and vertical bounce can increase as glutes and calves fatigue. This combination — lower cadence plus overstriding — is associated with higher impact loading at the knee and shin, though it's a tendency, not a guaranteed injury pathway for any individual runner.
Cadence is the one metric a phone video, filmed from the side during a long run, can measure with real reliability — just count steps over 30-60 seconds or use an app. Most recreational marathoners run in the 155-175 spm range; if yours drops sharply in the final miles of a long run, that's a signal worth noting, not a diagnosis. Ground-contact time and vertical oscillation are harder to pin down from a single phone angle — a side-view phone video gives a rough estimate at best, and true joint angles need lab-grade multi-camera capture. A tool like StrideIQ can give you a quick cadence and form check from phone video, which is useful for spotting fatigue-related changes over a training block, but it's not a substitute for an in-person gait lab or physio assessment if something actually hurts.
If you're tracking effort more precisely, running power can help contextualize whether form changes reflect fatigue or just pace — see what is a good running power number for how that metric works.
What are the early warning signs of an overuse injury?
Catching these early is the single highest-leverage thing you can do, because overuse injuries are far easier to manage at the "nagging ache" stage than at the "can't run" stage.
- Pain that's worse at the start of a run, then fades: often tendon-related; still worth monitoring, don't ignore because it "warms up."
- Pain that gets worse during a run and lingers after: a stronger signal to back off mileage immediately.
- Pinpoint bone pain, especially on the shin or foot, that worsens with impact: a possible early bone stress reaction — stop running and get it assessed rather than testing it further.
- Asymmetric soreness (one side consistently sorer than the other) after most runs, unrelated to a single hard effort.
- Sleep-disrupting pain or pain that changes your gait even walking.
Any of the last three warrants seeing a physio or sports medicine doctor before your next scheduled long run, not after. This isn't a diagnosis and it isn't a substitute for a proper rehab plan — a clinician needs to assess load, history, and tissue specifics to guide a safe return-to-run timeline.
What can training plans and form checks NOT tell you?
A training plan, a mileage rule, and a phone-video form check are all risk-reduction tools, not guarantees. They can't account for your individual bone density, prior injury history, sleep quality, or how your specific job or life stress is affecting recovery capacity that week — factors that meaningfully change injury risk between two runners on the identical plan.
Form analysis from a single phone video is genuinely useful for cadence trends and gross stride patterns, but it can't measure joint loading, tissue stress, or diagnose the cause of pain. Evidence on whether "correcting" foot strike or stride mechanics actually reduces injury risk is mixed — some studies show benefit for specific individuals, others show no clear effect across groups. Treat form feedback as one input, not a fix.
If you have pain that persists beyond a few days, worsens during runs, or changes how you walk, see a physio or sports medicine physician for an in-person assessment — that's the only way to get an actual diagnosis and individualized return-to-run plan. And after the race itself, recovery deserves its own attention; see how long to recover from a marathon and how to cool down after running for what that process should look like.
Frequently Asked Questions
What is the 10% rule in marathon training?
It's a common guideline suggesting you shouldn't increase your weekly mileage by more than about 10% from one week to the next. It's a heuristic, not a scientifically validated threshold — some runners can handle bigger jumps, others need more caution, so treat it as a rough ceiling rather than a strict rule.
How often should I take a cutback week during marathon training?
Most marathon plans schedule a cutback week every 3rd or 4th week, reducing mileage by roughly 20-30% from the prior peak. This gives connective tissue time to adapt to the load increase rather than accumulating stress week over week.
What percentage of marathon runners get injured during training?
Studies report injury rates ranging widely, from roughly 30% up to over 90% depending on the injury definition and population studied. Most of these are overuse injuries linked to training load errors rather than acute trauma.
Can a running form check prevent marathon injuries?
Form feedback, including cadence tracking from a phone video, can help you spot fatigue-related changes like dropping cadence late in long runs. It's a useful input, not a guarantee — it can't diagnose pain or replace an in-person physio or gait lab assessment.
What early symptoms during marathon training should I not ignore?
Pain that worsens during a run and lingers afterward, pinpoint bone pain on the shin or foot, and pain that changes your walking gait are all signals to stop and see a physio or sports medicine doctor before your next long run.
Sources
- American College of Sports Medicine — "Progression of Exercise Guidelines and Injury Prevention in Distance Runners"
- American Academy of Orthopaedic Surgeons — "Marathon Training: Common Running Injuries and Prevention"
- British Journal of Sports Medicine — "Running-Related Injuries: Risk Factors and Training Load Research"
- American Physical Therapy Association — "Strength Training Guidance for Injury Prevention in Runners"