Strava heart rate zones wrong: how one bad max HR cascades through your whole dashboard

How Strava sets your heart-rate zones

Strava derives all five heart-rate zones from one anchor: your maximum heart rate. By default it estimates that max as 220 minus your age, or 190 bpm if no age is on file. Every zone boundary is then a fixed percentage of that single number, so the anchor decides where every zone line falls.

There are two common ways to build heart-rate zones, and Strava's default is the weaker one. The first method anchors zones to maximum heart rate and sets each boundary as a percentage of it. The second anchors to lactate threshold heart rate (LTHR) — the heart rate at your sustainable threshold — which Joe Friel's framework treats as the more individualized reference because it tracks a metabolic event rather than an age-based ceiling [Friel 2018]. Strava ships with the max-HR method on by default and offers a custom-zone editor with draggable boundaries for mapping in LTHR-based zones. Out of the box, though, the numbers are percentages of an estimated max.

That makes the max-HR value the master input. If Strava has your max at 185, every zone scales to 185; if your true max is 198, every line should sit roughly 13 bpm higher than where Strava drew it. The 220-age estimate that seeds this is statistically convenient and individually unreliable — Tanaka and colleagues analyzed 351 studies covering 18,712 subjects and found it systematically underestimates max HR in older adults, with a standard error near 10 bpm even in their improved 208 minus 0.7-times-age equation [Tanaka et al. 2001]. A 10-to-20 bpm miss is ordinary, not a worst case.

Heart-rate zones are also not a substitute for what power measures. Heart rate is an input-lagging signal: intensity drives it, it doesn't define intensity, and it drifts with heat, fatigue, caffeine, and dehydration. Strava records the stream honestly; it just scales it against whatever max you gave it. The configuration is the difference between zones that describe your physiology and zones that describe an arithmetic guess about your age.

The cascade: wrong max HR becomes wrong zones, wrong Relative Effort, wrong Fitness

A wrong max HR doesn't stay contained in the zone chart. It rescales your time-in-zone splits, which inflates or deflates Relative Effort [Meyer 2018], which is the load input Strava feeds its Fitness curve when you ride without power. One bad number propagates through three layers of the dashboard.

Start at the source. A max HR set 15 bpm too low pushes every zone boundary down, so an honest endurance effort that should read mid-zone-2 gets logged as low zone 3. Your time-in-zone splits now misreport where you actually trained. The watts and the perceived effort didn't change; the ruler did.

Relative Effort is the next domino. It sums your weighted time-in-each-zone, with higher zones counting for far more per minute [Meyer 2018], so shifting minutes from zone 2 up into zone 3 mechanically lifts the score. This is the focused case our companion piece on why Relative Effort runs high on easy rides walks through in detail — a low max HR inflating the number on genuinely easy days. The broader point is that the same misconfiguration can also deflate the score if the max is set too high, reading hard work as easy. The direction depends on which way the max is wrong; the unreliability is the constant.

The last domino is the Fitness curve. When you ride without a power meter, Strava uses Relative Effort as the load input to the 42-day Fitness average and 7-day Freshness average that underlie its Banister-derived chart [Hellard et al. 2007, Allen et al. 2019]. If Relative Effort is systematically inflated by a low max HR, your Fitness line climbs faster than your actual training justifies; if it's deflated, your hard blocks barely register. The chart that's supposed to tell you whether you're building or burying yourself is only as honest as the max HR three layers upstream.

How to set your zones from real data, not a formula

Replace the formula-derived max with the highest heart rate you've actually hit in a hard, warmed-up effort over the last few months. Then either let Strava rebuild zones from that max or enter custom boundaries from a threshold test. The goal is zones anchored to observed physiology, not to 220 minus your age [Tanaka et al. 2001].

Find your real max first. Scroll your last few months of hard rides and look for the peak heart rate at the end of a maximal effort — the top of a 5-minute climb, the final 30 seconds of an all-out sprint, the last rep of a VO2 set. That observed peak beats any formula because the formula's standard error is roughly 10 bpm and its individual miss can be double that [Tanaka et al. 2001]. If your hardest efforts keep topping out at 192 while Strava has you at 178, your max is wrong by 14 bpm and so is every zone built on it.

Then decide how to anchor the zones. The simpler path is to correct the max HR in Strava's settings and let it regenerate the percentage-based zones. The more individualized path, if you've done a threshold field test, is to set custom zone boundaries from your LTHR — Friel's framework anchors the threshold zones to that value rather than to max [Friel 2018], and Strava's custom-zone editor lets you drag each boundary to match. Either is a defensible upgrade over the default; the threshold-anchored version is more precise if you have the test data, but a corrected max is most of the win for most riders.

This is the data-layer discipline the broader case for training with Strava keeps returning to: the platform syncs your numbers faithfully but doesn't audit whether their inputs are right, and using Strava as a training tool rather than a journal means owning the configuration it leaves on autopilot. Setting your zones from a real observed peak takes a few minutes and quietly corrects every future ride at the source.

What to re-check after you fix the zones

Correcting your max HR fixes future rides, but it generally won't rewrite the scores already sitting on past activities. Re-check your time-in-zone on the next few rides, watch whether Relative Effort now matches your perceived effort, and treat the Fitness curve's pre-fix history as scored against the old ruler.

Past scores mostly stay as they were. Strava computes Relative Effort when an activity is processed, so changing your max HR generally does not retroactively recompute the numbers on rides you've already uploaded. That means your Fitness curve carries a seam: the weeks before the fix were scored against the wrong max, the weeks after against the right one. Don't read a discontinuity at the changeover as a real fitness change — it's the ruler switching, not your body.

On the next handful of rides, run three independent checks that don't depend on the zones being perfect. Does time-in-zone now match what the ride actually felt like? Does Relative Effort track your perceived effort, where Foster's session-RPE is the cheapest valid internal-load metric in cycling [Haddad et al. 2017]? If you have a power meter, does normalized power agree with the heart-rate story [Allen et al. 2019]? When all three line up, your zones are anchored correctly.

One caveat the new zones won't fix: cardiovascular drift. Even with a perfect max, heart rate climbs 5-10% over the first 60-90 minutes of a long or warm ride at constant power [Coyle & González-Alonso 2001], so a long endurance ride will still post a higher Relative Effort than its steady effort suggests. That's expected physiology, not a configuration error. Correcting your zones fixes the systematic bias; it doesn't make a heart-rate score immune to the things heart rate does on long days.

Quick answers

Sources cited in this guide

1. 01
   Tanaka et al. 2001. Age-predicted maximal heart rate revisited. Journal of the American College of Cardiology.
2. 02
   Meyer 2018. Quantifying Effort through Heart Rate Data. Strava Engineering.
3. 03
   Hellard et al. 2007. Assessing the limitations of the Banister model in monitoring training. Journal of Sports Sciences.
4. 04
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
5. 05
   Friel 2018. The Cyclist's Training Bible (5th ed.). VeloPress.
6. 06
   Haddad et al. 2017. Session-RPE Method for Training Load Monitoring: Validity, Ecological Usefulness, and Influencing Factors. Frontiers in Neuroscience.
7. 07
   Coyle & González-Alonso 2001. Cardiovascular drift during prolonged exercise: new perspectives. Exercise and Sport Sciences Reviews.

More inside Training with Strava

Other articles in this series

1. 01

   What your Strava Fitness number means (and if yours is good)

   Strava Fitness is CTL — a 42-day weighted load average. What the number means, why it is personal, and the decisions to make from it.

   →
2. 02

   Apps that connect to Strava: read vs display

   How to tell which training apps actually read your Strava data and adapt versus the ones that only display your rides.

   →
3. 03

   Is Strava Premium worth it for a self-coached cyclist?

   What Strava Premium gives a training-focused rider, what it doesn't (no coaching), and when the free Intervals.icu chart beats paying.

   →
4. 04

   Relative Effort vs TSS: which to trust by workout

   A per-workout-type rule for when to trust Strava Relative Effort vs power-based TSS, and why they are not the same units.

   →
5. 05

   How to set up Strava for training: one-time configuration

   Configure Strava once for training: real FTP and max HR, honest zones, one sensor stack, and feed privacy that protects your plan.

   →
6. 06

   Strava segments as fitness tests: map efforts to tests

   Use Strava segments as scheduled benchmark tests: which profiles map to which test, how to schedule every 4-6 weeks, and controlling variables.

   →
7. 07

   What to look at on Strava after a ride: 4 metrics

   A 30-second post-ride routine: the four Strava metrics that matter after every ride, the ones to ignore, and why.

   →
8. 08

   Strava Fitness going down while training hard: the decay math

   Why your Strava Fitness (CTL) drops even when you train hard: the 42-day EWMA decay math, the real causes, and when a falling line is correct.

   →
9. 09

   Strava indoor power vs outdoor HR: Fitness chart jumps

   Mixing power-based TSS and HR-based Relative Effort splices incompatible units into your Strava Fitness chart. Why it jumps and how to fix it.

   →
10. 10

    Heart rate drift on long rides at same power: what it means

    Why heart rate climbs at flat power on long rides — cardiovascular drift, aerobic decoupling (Pw:HR) as a durability signal, and what to do.

    →
11. 11

    Why your Strava Relative Effort is high on easy rides

    Relative Effort can spike on a genuinely easy ride — usually a mis-set max HR, not lost fitness. What inflates it on Strava and what to do.

    →