How Cadence Affects Your Bounce (Vertical Oscillation)
What's the relationship between cadence and vertical oscillation?
Raising your cadence (steps per minute, or spm) generally lowers your vertical oscillation — the up-and-down bounce of your torso with each stride. This isn't a strict law of physics you can't escape, but it's a consistent pattern in running biomechanics: when you take more steps per minute at the same speed, each stride gets shorter, and a shorter stride tends to produce a flatter, less bouncy trajectory. Fewer, longer strides usually mean more time spent airborne, which means more vertical displacement per stride.
Think of it this way: your speed is a product of cadence and stride length. If you keep speed constant but increase cadence, stride length has to shrink. Shorter strides reduce the "launching" effect that sends your center of mass upward and forward on each push-off, so less energy goes into bounce and more stays directed toward forward motion.
Why does extra vertical oscillation waste energy?
Every centimeter your body rises and falls is a centimeter of energy spent fighting gravity instead of moving forward. Running is fundamentally a forward-motion activity, so vertical displacement is, biomechanically speaking, a energy cost you pay without a direct payoff in speed. Some vertical motion is unavoidable — you have to leave the ground to swing your legs through — but excessive bounce means you're paying more of that cost than necessary.
Runners who overstride (landing with the foot too far ahead of the hips) often show more vertical oscillation because the extended leg acts like a pole vault, redirecting forward momentum upward. This is one reason overstriding shows up repeatedly in discussions of running economy and injury risk — it affects both how much bounce you generate and how hard your joints absorb the landing.
What counts as efficient vertical oscillation?
Many gait-analysis tools and coaches cite roughly 6-9 cm as a common range associated with efficient distance running form, though this varies by runner size, speed, and individual mechanics. Elite runners at faster paces often sit toward the lower end of this range or below it; recreational runners at conversational paces often run higher.
These numbers are useful as a rough reference point, not a target you must hit exactly. A runner with naturally longer legs or a bounding stride pattern may have oscillation outside this range without any efficiency problem. The context — your pace, your typical mechanics, whether you feel efficient — matters more than matching a number precisely.
| Cadence range (spm) | Typical vertical oscillation pattern | Notes |
|---|---|---|
| Below 160 | Often higher (9-12+ cm) | More common with overstriding at easy paces |
| 160-175 | Moderate (7-9 cm) | Common recreational range |
| 175-185 | Often lower (6-8 cm) | Common trained/efficient range |
| 185+ | Often lowest (under 7 cm) | Common in faster racing paces, shorter strides |
These are general tendencies drawn from typical gait patterns, not fixed thresholds — individual variation is real, and a lower number isn't automatically "better" for every runner.
How much should you increase cadence to reduce bounce?
A commonly recommended approach is increasing cadence by about 5-10% from your current baseline, rather than jumping straight to a number like 180 spm. If you currently run at 155 spm, a 5-10% increase puts you around 163-171 spm — a meaningful but manageable shift.
Jumping too far too fast changes your stride mechanics abruptly, which can create new strain patterns in your calves and Achilles before your body adapts. A gradual approach — a few spm every one to two weeks — gives your tendons and muscles time to adjust to the shorter, quicker stride pattern.
A simple way to practice: run to a metronome app or a cadence-locked playlist set 5% above your natural rate for a portion of an easy run, then let it drop back for the rest. Over several weeks, extend how long you hold the higher cadence. This is a similar gradual-adaptation principle to how you'd find your optimal cadence rather than forcing one number onto every run.
Can a phone video measure vertical oscillation accurately?
Cadence is the biomechanic a single side-view phone video measures most reliably — you can count steps over time with good confidence regardless of camera quality. Vertical oscillation is harder. Estimating it from a phone video means tracking pixel displacement of your torso or head across frames, which is sensitive to camera angle, distance, frame rate, and even how steady the person holding the phone is.// A treadmill setup with a fixed camera at a consistent distance gives more consistent estimates than handheld filming, but even then, a phone shooting at 30-60 frames per second can't capture the fine-grained vertical motion the way a dedicated motion-capture lab or a high-speed camera at 120+ fps can.
So when an app or tool reports a vertical oscillation number from phone footage, treat it as a rough estimate — useful for tracking whether a number is trending up or down across your own runs, less useful as an absolute, lab-grade measurement you'd compare against population averages. Cadence numbers from the same video deserve more confidence than oscillation numbers from it.
StrideIQ, for instance, analyzes phone video primarily for cadence and general form patterns — it's a reasonable option for a quick check between runs, but it isn't a substitute for a lab treadmill assessment if you need precise oscillation or ground-contact-time data for a specific problem you're troubleshooting.
Does lower vertical oscillation always mean better running economy?
Not necessarily, and this is worth being honest about. Vertical oscillation correlates with running economy in a general sense across groups of runners, but it's one variable among several — stride length, ground contact time, arm carriage, and individual anatomy all interact. Two runners with identical oscillation numbers can have meaningfully different running economy because of differences elsewhere in their mechanics.
The research on deliberately manipulating cadence to reduce injury risk is also mixed. Some studies link higher cadence to reduced impact loading at the knee, which is relevant if you're managing knee arthritis and running or similar joint concerns, but cadence changes affect load distribution rather than eliminating load — they shift some stress from the knee toward the ankle and calf. That's part of why a moderate 5-10% adjustment, not an aggressive one, is the safer starting point; it's also why cadence tweaks show up in advice for plantar fasciitis, where reducing overstriding-related impact can help, but form change alone doesn't resolve the underlying tissue issue.
What can vertical oscillation and cadence data NOT tell you?
Cadence and oscillation numbers describe patterns, not diagnoses. A high oscillation number doesn't tell you why it's high — it could be overstriding, weak glute or calf strength, fatigue, terrain, or simply your natural mechanics at that pace. A phone video can flag a pattern worth investigating; it can't identify the cause or prescribe a fix with certainty.
These metrics also can't tell you whether you're ready to increase mileage or intensity, especially if you're coming back from injury — that depends on tissue healing, pain response, and load tolerance, which cadence data doesn't capture. If you're rebuilding after time off, questions like whether you're recovered enough to run require a broader assessment than a single form metric.
If you have persistent pain, a sudden change in your gait, or you're troubleshooting a recurring injury, a phone-based cadence check is not the right tool for that job — see a physical therapist or sports medicine physician for an individualized evaluation, and consider an in-person gait lab with high-speed cameras if you need precise oscillation or joint-angle data. Video-based form analysis is a screening and awareness tool, not a clinical assessment.
Frequently Asked Questions
Does increasing cadence always reduce vertical oscillation?
Usually, but not universally. At the same running speed, a higher cadence typically means a shorter stride, which tends to reduce bounce. However, individual mechanics vary, and some runners see smaller changes in oscillation than others when they adjust cadence.
What is a good vertical oscillation for running?
Roughly 6-9 cm is a commonly cited range associated with efficient distance running, but it varies by pace, leg length, and individual stride pattern. It's a rough reference, not a strict target everyone should hit.
How much should I raise my cadence to reduce bounce?
A gradual increase of about 5-10% above your current cadence is a commonly recommended starting point, adjusted over several weeks rather than all at once, to give your calves and Achilles time to adapt.
Can a phone app measure vertical oscillation accurately?
Phone video measures cadence reliably but estimates vertical oscillation with lower confidence, since it depends on camera angle, frame rate, and filming distance. Treat phone-based oscillation numbers as rough trend indicators rather than lab-grade measurements.
Is lower vertical oscillation always better for running economy?
Not necessarily. Oscillation correlates with running economy in general but interacts with stride length, ground contact time, and individual anatomy, so two runners with the same oscillation can have different running economy.
Sources
- American College of Sports Medicine — "Guidelines on running biomechanics and running economy"
- British Journal of Sports Medicine — "Research on cadence manipulation and running injury risk factors"
- American Academy of Orthopaedic Surgeons — "Running injury prevention and biomechanics guidance"
- Journal of Sports Sciences — "Studies on vertical oscillation and running economy in distance runners"