What Is Cadence Drift and Why It Happens Late in a Run
Cadence drift is the tendency for your step rate — the number of steps you take per minute (spm) — to gradually decline as a run goes on, usually as fatigue accumulates in the second half of a long run or race. It's not a single dramatic event; it's a slow slide, often just a few spm lower by mile 10 than it was at mile 1, but it tends to show up alongside other changes in form that matter more than the number itself.
What exactly is cadence drift?
Cadence drift means your step rate at the end of a run is measurably lower than it was at the start, even if your effort level feels the same or higher. If you started a long run at 172 spm and you're down to 164 spm by the final few miles, that's drift. It's a within-run pattern, distinct from your baseline cadence, which is the number you'd measure on a fresh, easy-paced run.
Cadence itself is the most reliable thing a phone video or running watch can measure — it's a simple count of foot strikes over time, so confidence in the number is high. What's less certain is exactly what a given amount of drift means for your injury risk or performance on any single day. Some drift is normal fatigue physiology; a lot of drift, especially paired with a big change in how your foot is landing, is worth paying attention to.
Why does cadence drop late in a run?
The main driver is muscular fatigue. As your calves, quads, and hip stabilizers tire, they generate less force per push-off, and one common compensation is to spend more time in the air per stride and more time in ground contact per step — both of which pull cadence down even if you're not consciously trying to slow down.
Stride length is the other half of the equation. Speed is roughly cadence multiplied by stride length, so if your pace stays similar while cadence drops, stride length has to increase to compensate — often through slight overstriding, where the foot lands further out in front of your hips than it did earlier in the run. You can get a feel for whether this is happening by checking your foot strike position relative to your knee on video; see how to measure foot strike angle for a way to check that from a side-on clip.
Dehydration, low glycogen, downhill sections, and simply running longer than your current fitness supports can all accelerate drift. It's a fatigue signal more than a technique flaw on its own.
How does cadence drift show up in your form?
Drift rarely travels alone. As cadence falls late in a run, a few related changes tend to show up together:
- Ground contact time often lengthens slightly, since fatigued muscles don't reload as quickly. A phone video can give a rough estimate of this, but true ground contact time numbers need high-speed or lab capture to be accurate — see what a good ground contact time balance looks like for context on why phone estimates carry lower confidence here.
- Stride length increases modestly to hold pace, which can nudge foot strike further from under the hips — worth checking against how to tell if you overstride from video.
- Posture can lean back or slump forward as core and hip muscles fatigue, changing how load travels down the leg.
None of this means every runner who drifts will get hurt. The evidence linking cadence changes directly to injury is mixed — some runners tolerate significant late-run form changes with no issues, while others notice new aches (shins, knees, feet) after runs where drift was pronounced. If you're getting sore feet after long runs, why your feet hurt after running covers some of the more common contributors, of which fatigue-related form drift is one.
How can you monitor cadence drift?
You need at least two cadence readings from the same run — early and late — to see drift at all. A few practical ways to get that:
| Method | What it captures | Reliability | Best for |
|---|---|---|---|
| GPS running watch with cadence | Continuous spm throughout the run | High for cadence itself | Runners who want passive, ongoing tracking |
| Footpod or foot-mounted sensor | Cadence plus rough stride metrics | High for cadence, moderate for the rest | Data-curious runners wanting more detail |
| Phone video (short clips at intervals) | Cadence from counting steps in a clip; rough form snapshot | High for cadence, lower for angles/contact time | Spot-checks without buying hardware |
| Metronome or audio cue app | Doesn't measure drift, but gives a target to run against | N/A (a tool, not a measurement) | Actively holding cadence steady mid-run |
A simple low-tech option: film 10-15 seconds of yourself running at the start of a long run and another clip in the final mile, then count steps in each clip and compare. An app like StrideIQ can do this cadence count for you from a single phone video, which is a reasonable way to get a quick before/after check — but for continuous tracking across an entire run, a cadence-capable watch or footpod will give you more data points than periodic video clips can.
What strategies help you hold a steady cadence?
A commonly cited reference range for cadence is roughly 170-180 spm, but this is a broad guideline, not a universal target — cadence varies with height, pace, and leg length, and plenty of efficient runners sit outside that band. The more useful goal for drift specifically is consistency relative to your own baseline, not hitting a number.
- Practice cadence awareness on tired legs. In training, do the last 10-15 minutes of a long run at slightly faster turnover on purpose, so your body has practice resisting the drift pattern.
- Use an audio metronome for the back half of long runs. Setting a beat a few spm above your natural late-run cadence gives you something concrete to match instead of relying on feel when you're fatigued.
- Shorten your stride slightly when you feel form breaking down, rather than trying to force the same stride length at a slower turnover — quick, shorter steps are usually easier to sustain than long ones as fatigue builds.
- Build fatigue-resistance directly, through longer easy runs and strength work for calves, glutes, and hips, since drift is fundamentally a fatigue symptom, not a cadence problem you can fix by cadence drills alone.
- Fuel and hydrate on schedule during runs over 90 minutes; glycogen depletion is a known contributor to late-run form breakdown.
What can cadence tracking NOT tell you?
Cadence numbers, whether from a watch or a phone video, tell you about step rate and roughly how it changes — that's about it. They don't diagnose why you're drifting, whether your specific drift pattern is dangerous for you, or what's happening at your knee or ankle joint in three-dimensional detail. A phone video gives a reasonably confident cadence count but only a rough estimate of things like ground contact time, vertical oscillation, or true joint angles, since those need high-speed or multi-camera capture to measure accurately.
Cadence drift also isn't inherently a problem to be eliminated — some drift with fatigue is normal and doesn't predict injury on its own. If you're dealing with recurring pain, new soreness, or you're returning from an injury, form and cadence checks are a starting point for curiosity, not a diagnosis or a treatment plan. A physical therapist, sports medicine physician, or an in-person running gait lab can assess joint mechanics, muscle strength imbalances, and load history in ways a single video or watch reading cannot, and that's the right next step if drift is showing up alongside pain rather than just fatigue.
Frequently Asked Questions
What is cadence drift during a run?
Cadence drift is when your step rate (steps per minute) gradually declines over the course of a run, typically in the second half, as muscular fatigue sets in. It's measured by comparing your cadence early in the run to your cadence later on.
Is some cadence drift normal?
Yes. A modest drop of a few steps per minute over a long run is a common fatigue response and doesn't automatically indicate a problem. Large or sudden drift paired with new pain is more worth paying attention to.
What cadence should I aim for?
A commonly cited reference range is roughly 170-180 spm, but this varies by height, pace, and individual biomechanics. Consistency relative to your own baseline matters more for spotting drift than hitting a fixed number.
Does cadence drift cause injury?
The evidence linking cadence changes directly to injury is mixed. Drift is a fatigue signal that can coincide with overstriding or longer ground contact time, but it doesn't mean injury is guaranteed, and it isn't a diagnosis on its own.
Can a phone video measure cadence drift accurately?
Phone video gives a fairly reliable cadence count if you film short clips at different points in a run. It's less reliable for related metrics like ground contact time or joint angles, which need high-speed or lab-grade capture for accuracy.
Sources
- American Academy of Orthopaedic Surgeons — "Running Injuries and Prevention"
- British Journal of Sports Medicine — "Running biomechanics and injury risk: a review"
- American College of Sports Medicine — "Guidelines on Running Gait and Fatigue"
- American Physical Therapy Association — "Understanding Running Gait Changes and Overuse Injury"