Garmin Running Cadence

Home » Garmin Features » Running Dynamics » Cadence

Plain English: Cadence is how many steps per minute a runner takes, counting both feet, and it rises naturally with speed, so the number means very little unless compared at the same effort level.

In practice: Cadence is one of the metrics I periodically monitor, ranging from two-hour runs to five-minute VO2 max intervals. The most practically useful thing I have done as a result is to incorporate efforts to maintain race cadence during training, which appears to reduce injury by lowering impact per foot strike. What the data showed me is that Garmin does not flag that my cadence falls disproportionately when I fatigue, compared to stride length, making it an earlier warning of gait breakdown that tends to precede injury for me than stride length alone does.

Quick answers

What is a good running cadence on Garmin?
Most recreational runners fall between 140 and 165 spm at easy paces, with trained athletes typically registering 165 to 180 spm at controlled efforts. The 180 spm figure is widely cited but derives from elite race-pace observations and is not an appropriate target for slower or less-experienced runners.

Should I be trying to hit 180 steps per minute?
The 180 spm figure derives from Jack Daniels’ observations of elite runners at the 1984 Olympics and does not apply universally to recreational runners at slower paces. A more practical target is five to ten per cent above a runner’s own freely chosen cadence at a given training effort, not a fixed universal number.

Why does my cadence drop towards the end of a long run?
Neuromuscular fatigue reduces the rate at which motor units can be recruited to sustain stride frequency, resulting in a progressive decline in cadence that typically accompanies lengthening of ground contact time and rising vertical oscillation. This is a recognised physiological response to cumulative effort, not a form breakdown, and resolves with adequate recovery.

Why is my cadence different when I use a chest strap versus just the watch?
Chest strap and wrist accelerometers are calibrated independently and produce systematically different absolute values; the discrepancy does not indicate a fault in either device. Mixing the two data sources within a single trend dataset creates a step change that resembles a training-induced change but is a sensor-change artefact; use one sensor type consistently.

---

Cadence – a deep dive

When Cadence Is Actually Useful

• In my early running days, I used Garmin’s metronome alongside the cadence readout to gradually raise my entire cadence range, a few steps per minute at a time over several months, which remains by far the most effective form change I have made.
• Cadence is one of my primary data fields across all distances. I use it to set and adjust pace in real time, deliberately targeting cadence changes rather than stride length because that is the lever I can actually tweak consciously mid-run.
• I have noticed that my cadence falls disproportionately when I fatigue relative to stride length, and this tends to precede injury, although the apparent link is not perfect. Still, a sustained, unexpected drop in cadence is now the signal I act on first.
• I have used cadence to play to my strengths: I am more aerobically capable than I am muscularly strong, so raising cadence to go faster loads the cardiovascular system, where I have capacity, whereas pushing stride length demands muscular force I do not always have, particularly late in a race or long run.

Introduction

Cadence is the rate at which a runner takes steps, expressed as the total number of steps per minute, counting both feet. It tells an athlete how quickly the feet are turning over at any given moment during a run and serves as a primary indicator of running stride frequency.

Cadence, within Garmin’s Running Dynamics suite, is defined in Garmin’s manuals as “the number of steps per minute. It displays the total steps (right and left combined).” A reading of 170 spm means the runner is taking 170 individual steps, 85 with each foot, every minute. The metric is among the most established in running biomechanics, predating wearable technology by several decades, and it sits alongside ground contact time, vertical oscillation, stride length, ground contact time balance, and vertical ratio in the six-metric suite Garmin introduced in 2014. Cadence is the most widely available of the six metrics: it can be recorded from a chest strap, a waist-worn pod, the watch’s own wrist accelerometer, or a footpod, depending on the device and accessory in use. The principal limitation of cadence as a standalone metric is its dependence on pace: cadence rises naturally as a runner moves faster, which means a reading taken during an easy recovery run is not directly comparable to one recorded at threshold effort or during a race.

What cadence actually means

Cadence measures stride frequency: a higher value indicates faster leg turnover, while a lower value indicates a longer stride cycle at the same speed. Because cadence and stride length are mathematically linked at any given pace, so that increasing one requires decreasing the other, a runner raising cadence from 160 to 170 spm at constant speed must shorten each stride proportionately. For most recreational runners, cadence at easy to moderate paces ranges from 140 to 165 spm; trained athletes typically register 165 to 180 spm during controlled efforts. A figure of 180 spm is widely cited as an efficiency target, originating from Jack Daniels’ observations of elite runners at the 1984 Olympics. Still, subsequent research has not supported it as a universal optimum for recreational runners. Garmin displays cadence against a colour-coded percentile gauge, and the boundaries differ by watch generation. The Forerunner 265, 965 and 165 manuals give red below 153 spm, orange 153 to 163, green 164 to 173, blue 174 to 183 and purple above 183; the Forerunner 570 and 970, Venu X1 and Instinct 3 manuals move them to red below 151, orange 151 to 162, green 163 to 173, blue 174 to 185 and purple above 185. Garmin says the zones are percentiles of the runners it has researched, with red and orange typical of less experienced or slower runners and green, blue and purple of more experienced or faster ones, and that taller runners typically have slightly slower cadences. A runner at an easy pace will frequently register red or orange while threshold efforts register green or blue in the same training block, which is normal and not a form signal. Age and sex do not materially affect appropriate cadence at a given speed; height has a modest indirect influence, as taller runners tend to have longer natural stride lengths and may prefer a slightly lower cadence at equivalent effort.

Garmin colour	Cadence range (spm), current and older manuals	Typical runner profile	Interpretation note
Purple	Above 185 (older: above 183)	Elite or fast club runner at race effort	Uncommon at easy pace; normal at 5km race effort for trained runners
Blue	174 to 185 (older: 174 to 183)	Trained runner at threshold or tempo effort	Expected at hard efforts; at easy pace may indicate short, choppy stride
Green	163 to 173 (older: 164 to 173)	Recreational to club runner at moderate effort	Typical target range for easy to moderate running in trained athletes
Orange	151 to 162 (older: 153 to 163)	Recreational runner at easy or recovery pace	Normal at genuinely easy effort; not a form problem in isolation
Red	Below 151 (older: below 153)	Beginner runner or any runner at very slow pace	Review in context of pace; low cadence at slow speed is expected, not a fault

Current boundaries from the Forerunner 970 manual; older ones from the Forerunner 965 manual. Zone colour at any given reading reflects effort level as much as running form, so readings should be compared at equivalent paces across sessions, not across different effort levels within a single run.

How Garmin calculates cadence

Stated: Garmin says cadence is the total steps per minute, right and left combined, that it comes from the watch’s accelerometer or from a compatible accessory, that the watch switches to its own sensor automatically when an accessory is not connected, and that the colour zones are percentiles of the runners Garmin has researched. Inferred: the sensor registers each foot contact as an impulse in the vertical and fore-and-aft acceleration signal, and the interval between successive impulses gives the step rate, reported over a short rolling window; the wrist version counts arm swings as a proxy for foot strikes, which is why it drifts when arm and leg rhythm decouple. Unknown: the length of the rolling window, how steps are counted when one arm is still, and whether the two sensor positions share one calibration.

The location of the accelerometer varies by sensor type: a chest strap (HRM-Run, HRM-Tri, HRM-Pro, HRM-Pro Plus, HRM 600, HRM-Fit) detects torso movement, the Running Dynamics Pod detects movement at the waistband, and the watch’s wrist accelerometer detects arm swing. Each sensor type produces its own absolute values.

Cadence is recorded continuously throughout any running activity and requires no additional conditions beyond an active running gait. It is valid on a treadmill because it depends entirely on accelerometer data rather than GPS-derived speed. Garmin notes that some running dynamics metrics do not appear while walking; cadence itself continues, but the ground contact metrics stop.

What affects the cadence reading

Sensor position introduces a systematic difference in absolute values: chest, waist-pod, and wrist measurements are not interchangeable, and switching sensor type mid-training block creates a step change in the trend dataset that resembles a training-induced change but is an artefact of sensor change. Footwear and running surface have modest effects, since highly cushioned shoes and soft terrain such as grass or sand marginally alter the accelerometer signal, but neither is large enough to materially affect practical interpretation. Hills affect cadence in both directions: uphill running typically reduces cadence as stride length contracts, while downhill running may increase it as the runner shortens steps to control braking forces.

Pace is the dominant variable: a difference of 10 to 20 spm between easy and race effort in the same runner is typical and reflects normal biomechanical adaptation rather than measurement error. Treadmill running tends to produce a lower cadence than overground running at equivalent effort because the moving belt partially drives foot turnover mechanics, allowing some runners to adopt a longer, slower stride; the cadence reading is metrologically valid in this context, but the value is not directly comparable to outdoor sessions.

How accurate is Garmin cadence

Chest strap and pod cadence measurements are generally within one to two steps per minute of values derived from video analysis at controlled paces, an error magnitude unlikely to affect practical training decisions. Wrist-based cadence is reliable during steady-state running on flat terrain but less precise during acceleration, sharp directional changes, and on trails, where arm movement decouples from the foot-strike rhythm. Independent characterisation of wrist-based error under varied ecological conditions is limited as of early 2026; testing reported on dcrainmaker.com and elsewhere indicates acceptable accuracy for road running, but greater scepticism is warranted on technical trails.

The more important distinction is between absolute accuracy and trend reliability. Absolute accuracy, meaning how closely the reading matches a laboratory ground truth, matters less than whether consistent changes in a single runner’s cadence dataset reflect real changes in running mechanics. Trend reliability is strong for chest and pod sensors within a stable dataset, provided the same sensor type is used consistently. Research supporting cadence optimisation as a training target is robust; what the evidence does not establish is any specific spm threshold that improves running economy across all runners.

Competitor equivalents

• Polar measures cadence natively on the Vantage V3 and Vantage M3 from the wrist, with real-time and post-run displays, but offers no colour-coded percentile zone system, and further dynamics metrics require a paired Stryd foot pod rather than Polar’s own sensors.
• Apple Watch (Series 6 and later, watchOS 9 and later) measures cadence natively alongside stride length, ground contact time, and vertical oscillation, available in real-time workout views and in the Fitness and Health apps post-run, but offers no percentile zone display.
• Coros (PACE 3, PACE Pro, APEX 2, APEX 2 Pro, VERTIX 2 and VERTIX 2S, on firmware from September 2025) measures cadence natively from the wrist in Road Run and Track Run modes; absolute values have not been independently validated against Garmin’s, and no percentile system is offered.
• Suunto (Race, Suunto 9 series) provides native wrist cadence but no proprietary dynamics accessory ecosystem or percentile display; additional stride metrics require a paired Stryd foot pod.
• Wahoo does not manufacture a wrist-worn running watch and offers no equivalent running cadence metric.

Which Garmin devices support cadence

Cadence on its own is the one running dynamic every Garmin running watch has always shown from the wrist, including the Forerunner 55, 70, 165 and 170, Vivoactive 6 and Venu 3 and 4. Any watch that pairs an ANT+ running dynamics accessory has shown it alongside the other Running Dynamics metrics via a chest strap or pod since the suite’s introduction in 2014. What arrived in March 2023 with the Forerunner 265 and 965, and by firmware for the Fenix 7, Epix Gen 2, Forerunner 255 and 955, Enduro 2, Quatix 7 and MARQ Gen 2, was the rest of the suite from the wrist: stride length, vertical oscillation, vertical ratio and ground contact time without an accessory, and every current Garmin running watch since includes it. Ground contact time balance and step speed loss still need an accessory, and the Forerunner 165 and 170, Venu 3 and 4 and Vivoactive 6 cannot pair one. The cadence colour gauge appears on the Forerunner 165 upwards, per the manuals.

Where to find cadence on Garmin

• Activity data field: add Cadence, Average Cadence or Lap Cadence to any data screen through the activity’s Data Screens settings; the live field shows the current rolling step rate throughout a recorded run.
• Running dynamics data screen: the full set of dynamics with the colour gauge on the primary metric, which can be set to cadence, during the run.
• Activity summary on the watch: average cadence in the run’s summary pages after saving.
• Garmin Connect app, activity detail: the Running Dynamics section shows average and maximum cadence, a cadence-over-time graph aligned with the pace trace and the zone breakdown; no Connect Plus subscription is required.
• Garmin Connect app, trends: the Performance Stats section charts average cadence across activities over time.
• Garmin Connect web: cadence appears under the Running Dynamics tab in the activity detail; the historical cadence chart is less complete than in the app.
• Not available as a glance, watch face complication or Morning Report item, because it exists only inside a recorded activity.

Common problems and misreadings

The most frequent misreading is comparing cadence across runs of different intensities. A runner recording 158 spm on an easy long run and 174 spm during a 10km race has not experienced a form change: lower cadence at lower effort is a normal biomechanical response to reduced speed demand, as noted in What Affects the Reading. Meaningful comparisons require controlling for pace, from easy runs to easy runs and from threshold efforts to threshold efforts.

Discrepancies between wrist and chest-strap cadence values are not a fault in either device. They reflect the systematic calibration difference between sensor positions discussed in What Affects the Reading. Switching between sensor types creates a visible step change in the trend dataset that carries no physiological meaning; treat the two series as distinct and use one sensor type consistently within any trend dataset. See Quick answers above.

Cadence declining across a long run, or registering lower than expected after a hard training block, typically reflects neuromuscular fatigue rather than a sensor fault. As cumulative effort increases, stride frequency drops, ground contact time lengthens, and vertical oscillation rises, a recognised fatigue signature that resolves with adequate recovery and is not a form problem requiring intervention. See Quick answers above.

How to improve cadence

The principal evidence-based mechanism for cadence adjustment is gradual step-rate elevation above a runner’s freely chosen cadence. Heiderscheit and colleagues demonstrated that increasing step rate five to ten per cent above preferred cadence reduces loading at the knee and hip without increasing oxygen consumption. A practical approach is to identify a target cadence five per cent above the current preferred cadence at a defined effort level and to practise holding it during portions of easy runs, typically ten to fifteen minutes at a time, using an audio metronome set to the target beat rate. Abrupt large increases risk overloading the calf and Achilles complex; raise cadence incrementally and set the target specific to a given training pace, not derived from race effort.

Short accelerations of approximately 20 to 30 seconds at controlled fast effort, commonly called strides, provide a low-volume neuromuscular stimulus for faster leg turnover. Including four to six strides at the end of easy runs, two to three times per week, builds familiarity with higher step rates without meaningful added training stress.

Scientific basis

Heiderscheit, B.C., Chumanov, E.S., Michalski, M.P., Wille, C.M. and Ryan, M.B. (2011). Effects of step rate manipulation on joint mechanics during running. Medicine and Science in Sports and Exercise, 43(2), 296 to 302. PMID 20581720. Increasing step rate five to ten per cent above preferred cadence reduced knee and hip loading without raising oxygen consumption; the whole of the How to Improve It section rests on this paper.

Moore, I.S. (2016). Is there an economical running technique? A review of modifiable biomechanical factors affecting running economy. Sports Medicine, 46(6), 793 to 807. PMID 26816209. The review that finds no universal optimum cadence for recreational runners, which is why this page treats 180 spm as an observation about elites rather than a target.

How cadence connects to other Garmin features

Cadence and Stride Length are mathematically inseparable: stride length is pace divided by cadence, so any cadence error propagates into the stride length figure, and any change in one at constant pace requires an inverse change in the other. Cadence and Ground Contact Time (GCT) move in predictable opposition as pace changes, since rising cadence compresses the available foot contact time, and the two metrics are most informative when read together.

Vertical Oscillation tends to decrease as cadence increases because higher step frequency reduces the height of each ballistic phase, while Vertical Ratio, which divides vertical oscillation by stride length, incorporates cadence indirectly and is degraded by cadence instability such as that seen during wrist-based measurement on technical terrain. Running Power draws on the same accelerometer hardware as the dynamics suite.

Running Economy, available with the HRM 600, uses the strap’s running dynamics, which include cadence, alongside ground contact time balance and step speed loss; it is unavailable from wrist-based dynamics alone. Step Speed Loss captures braking at each foot contact and is higher in runners with low cadence and pronounced braking per stride, making cadence and step speed loss complementary rather than redundant signals.