I spent two years at 155 steps per minute, wondering why my legs felt heavy. Here is what I learned about cadence, the 180 myth, and what really helped.
By Alex · 8 min read
For my first two years of running, I never thought about cadence. I just ran the way my legs wanted to move. It turned out that they wanted to move at about 155 steps per minute, which is at the low end of what most coaches consider efficient.
Once I started paying attention to it, my running changed. Not suddenly, but step by step. Fewer impact problems, a smoother stride, and less struggling on hilly ground. Here is what I have learned.
Cadence is your step rate — the number of steps you take per minute. Most running watches record it automatically. You will see it as SPM (steps per minute), or sometimes as strides per minute, which counts only one foot and is therefore half the SPM number.
A quick check: count how many times your right foot hits the ground in 30 seconds, then multiply by 4. That is your cadence.
You have probably heard that 180 steps per minute is the magic number. That idea comes from Jack Daniels, who watched elite runners at the 1984 Olympics and found that almost all of them ran at 180 or above.
Here is the problem: those were elite athletes racing, not training. And "180" turned into a rule for every runner at every pace, which was never the intention.
The reality:
So no, you do not have to force yourself to 180. But if you are well below your natural efficient range, there is probably room to improve.
Cadence changes your stride in ways that directly affect your injury risk and your efficiency.
A low cadence often comes with overstriding — landing with your foot too far in front of your body. When your foot lands out in front of you, it works like a brake. On every step you slow down slightly, then speed up again.
Overstriding also increases the forces going through your knee and hip. It is a common part of the picture in runner's knee, IT band problems and shin splints.
A higher cadence naturally brings your foot down closer to underneath your body, which reduces that braking force.
A lower cadence usually means more bounce — more up-and-down movement with each step. That energy is not moving you forward. It is wasted.
Raising your cadence slightly tends to reduce the bounce and smooth out your stride.
Research shows again and again that raising your cadence by even 5-10% moves load away from the knee and hip toward the ankle and calf. For runners with knee problems, that can matter.
I had knee discomfort that kept coming back during my first big training block. Cadence was not the only cause, but improving it was part of what helped.
There is no perfect number, but here is a practical guide:
Your cadence also changes naturally with your pace. Running faster usually means a higher cadence. Easy runs might sit at 165-170, while a hard tempo or interval session might reach 175-185.
Use the Pace Calculator to find your training zones, then check your cadence at each effort level. The pattern tells you more than one single number.
The worst way to improve your cadence is to think about it constantly on every run. That is exhausting, and it usually damages other parts of your form.
Here is what actually works:
If you are at 160 SPM, do not try to jump to 180. Aim for 168. That is 8 extra steps, and your body can adapt to it without rebuilding your whole stride.
Fast changes in cadence can stress your calves and Achilles tendons, because they change how and when your ankle absorbs impact. Go slowly.
Metronome apps for runners are free and genuinely useful. Set one to your target cadence and run to the beat for part of an easy run. Not the whole run — 5-10 minutes of focused work is enough.
Over several weeks the new rhythm becomes natural, and you stop having to think about it.
"Quick feet" drills — short, fast steps on the spot or over flat ground — train your muscles and nerves to work faster. Add them to your warm-up 2-3 times a week. 20-30 seconds at a time is plenty.
A playlist built around a certain number of beats per minute is an easy way to guide your cadence. Many runners find this more natural than a metronome, because the beat stays in the background.
Running uphill naturally shortens your stride and raises your cadence. Adding some hilly ground to your training helps build the mechanics you are looking for.
For route planning, our Elevation Finder lets you check how much climbing your training routes contain.
One mistake I made early on was expecting one cadence target for every run. That is not how it works.
These are approximate. The point is that your easy-day cadence will naturally be lower than your race-day cadence, and that is completely fine.
You are not only chasing numbers. These are the real signs that cadence work is helping:
The improvements are small, but they add up. After a few months of deliberate work, I noticed that my form held together much better in the second half of long runs, which is when it matters most.
Cadence is a useful tool, not a goal in itself. It is one signal among many.
If your current cadence is working well — no repeated injuries, running feels efficient, your times are improving — then you probably have bigger things to work on. Put pace training, discipline on easy days and fueling first, before you spend weeks worrying about SPM.
But if you keep having knee or hip problems, or your stride feels clumsy and over-long, cadence is worth a look. A few targeted changes can make a real difference without changing everything else.
Start by checking your current cadence. Most running watches show it. See where you are. If you are in the 155-165 range and running feels harder than it should, a small increase is worth trying.
And whatever your number is, make sure the rest of your training is right too. Check your paces at TrainPace and give your body the right mix of easy days, workouts and recovery. Cadence is one piece of the picture, not the whole picture.
Every page on this site has a Markdown mirror at the same path with a .md suffix (for example /calculator.md), and honors an Accept: text/markdown request header on the HTML URL. The calculations here are also available as callable tools through a free public MCP server — no account or API key.