How cadence, stride, and pace fit together
Running speed comes down to just two things multiplied together: how often your feet land, and how far each step covers.
Speed = Cadence × Stride length
Cadence is steps per minute, counting both feet — a comfortable easy-run cadence is often somewhere in the 160s or 170s, and it climbs as pace quickens. Stride length here means the length of a single step, from one foot's landing to the other's — not a full left-right-left stride cycle, which some sources define as two steps and roughly double this number. Multiply the two together and you get speed in meters per minute, which converts directly into pace.
Worked example: a cadence of 170 spm and a stride length of 1.0 m gives a speed of 170 m/min. Converting that to pace: 1,000 ÷ 170 ≈ 5.88 minutes, or 5:53 per km, and 1,609.344 ÷ 170 ≈ 9.47 minutes, or 9:28 per mile — about 10.2 km/h. Change any one of cadence, stride, or pace and the other two shift with it, which is exactly what the calculator above solves for.
Because the three values are locked together this way, no single number tells the whole story on its own. Two runners can hit the exact same pace with very different form — one with a quick, short-stepping cadence, the other with a slower, more ground-covering stride — and neither approach is automatically more correct than the other.
What is a good running cadence?
The number most runners have heard is 180 steps per minute. It comes from an often-cited observation that elite distance runners at major competitions tended to cluster around that cadence, regardless of their pace. Over time it hardened into a popular target for recreational runners too — sometimes phrased as "90 to 95 steps per foot," which is the same thing counted one leg at a time.
The trouble is that 180 was never meant as a rule for everyone. Cadence is strongly tied to leg length and height — a taller runner with longer legs will typically cover more ground per step, so an efficient cadence for them can sit noticeably lower than 180. Cadence also rises naturally with pace: your cadence at an easy jog is almost always lower than your cadence in a 5K. Rather than chasing a fixed number, it's more useful to know your own current cadence at a few paces (this calculator can back it out from a recent GPS pace and an estimated stride length) and treat 180 as a loose reference rather than a verdict on your form.
Raising your cadence safely
A low cadence often goes hand in hand with overstriding — reaching the foot out in front of the body on every step, which increases braking forces and impact through the knee and shin. Many runners who work on cadence are really trying to fix overstriding, and a quicker, lighter turnover is often an easier cue to act on than "shorten your stride" directly.
If you want to raise your cadence, do it gradually. A common approach is to increase by about 5% at a time — for example, from 170 to roughly 178 — and hold that new cadence for a few weeks before nudging it up again. Jumping straight to a much higher number changes loading patterns quickly and can bring on its own aches, especially in the calves and Achilles.
The easiest way to practice a target cadence is to run to a steady click track at that beats-per-minute value, landing one foot on every beat. A simple online metronome set to your target spm works for this even though it's built for instrument practice — a click is a click. Cadence-matched playlists work the same way, using song tempo instead of a metronome beat. As your cadence rises at a given pace, expect your stride length to shorten on its own; you don't need to separately think about taking shorter steps.