Heart Rate Zones for Running: Why Your Watch Is Probably Wrong

Your running watch shows five coloured zones. Zone 2 is where the influencers say you should spend 80% of your time. Zone 4 is threshold. Zone 5 is where you suffer during intervals.

The problem: for most runners, those zones are built on a number that's probably wrong by 10–20 beats.

The formula most watches use to estimate maximum heart rate is 220 − age. It is convenient, widely used, and demonstrably inaccurate. The standard deviation of actual max HR around this formula is approximately ±12 beats per minute — meaning for any individual runner, the true max HR could be 12 bpm higher or lower than predicted. That error shifts every zone boundary by the same amount.

I ran three months at what my watch told me was Zone 2. After a lab test, I discovered my actual max HR was 191 — not the 178 the formula predicted. Every single "easy" run had been in physiological Zone 3. My aerobic base building had been undermined from day one. The zones were precise on screen. They were wrong for my body.

How heart rate zones actually work

Heart rate zones are a way of segmenting exercise intensity based on the percentage of your maximum heart rate. The underlying physiology is real: different intensities produce different metabolic responses, and those responses correspond loosely to HR ranges.

The zones are meaningful. The problem is the denominator: everything depends on max HR being accurate.

The max HR problem

The 220 − age formula has a standard deviation of ±12 bpm in most research populations. For a 40-year-old runner, the formula predicts max HR of 180. Their actual max HR could be anywhere from 168 to 192 — a 24-beat range. A runner at the high end (192) would have their Zone 2 ceiling at ~134 bpm. A runner at the low end (168) would have their Zone 2 ceiling at ~118 bpm.

The Tanaka formula (208 − 0.7 × age) is marginally more accurate for older runners but has similar variance problems for individuals.

What a 12 bpm error actually means: If your true max HR is 191 but your watch assumes 178, your "Zone 2" ceiling shows as 124 bpm (70% of 178) when your actual Zone 2 ceiling is 134 bpm (70% of 191). You could be running at 130 bpm — what your watch calls Zone 3, bordering Zone 4 — while actually still in aerobic Zone 2. Or the inverse: you think you're in Zone 2 but you're physiologically in Zone 3.

One zone shift in the wrong direction for months of easy runs means either undertraining (too easy, not enough aerobic stimulus) or chronic accumulation of excess fatigue (too hard, accumulating ATL without recovery).

How to find your actual max HR

Option 1: Lab test. A VO2max test with a sports physiologist will measure your true max HR directly. Most accurate, most expensive.

Option 2: Field test. After a thorough warmup (20+ minutes easy), run 2–3 minutes at maximum effort uphill or in a time trial. The highest HR recorded in the final 30 seconds approximates your max. Requires full effort and is only safe for healthy, trained runners.

Option 3: Race data. Look at your HR in the final kilometre of a hard 5K or 10K run at maximum effort. This typically reaches 95–100% of true max HR and is the most practical estimate for most runners.

Option 4: Accept the uncertainty and use pace instead. This is the most practical approach for the majority of self-coached runners.

Why VDOT pace zones are more reliable

The VDOT system derives training intensities from your actual race performance — not from an estimated physiological parameter. If you ran a 10K in 48:00, your VDOT is approximately 50, and your training paces are calibrated directly to the fitness that produced that result.

There's no estimation error in the starting point. Your race result is an objective measurement.

The practical difference: if your max HR estimate is wrong by 12 bpm, your VDOT paces are unaffected. They're calibrated to your race performance, not to your heart rate.

This is why Jack Daniels' system uses pace rather than HR as the primary training intensity guide — pace is directly measurable, HR is not (or at least not without error).

When heart rate IS the right tool

HR zones are not useless — they're the wrong primary tool for most structured training situations, but the right secondary tool in specific contexts.

Heat and humidity. On a hot day, cardiac drift means your HR at a given pace will be 5–15 bpm higher than on a cool day. Running by pace in 32°C heat accumulates more stress than the same pace in 15°C. On hot days, run by HR (targeting your normal easy-run HR) and let pace be the outcome.

Altitude. Similar drift effect — HR runs higher at altitude for the same pace. Use HR as the governor, not pace.

Early base-building. When fitness is changing rapidly in the first 4–6 weeks of a training block, pace zones from a 3-month-old race result may lag behind actual current fitness. HR can help calibrate whether easy runs are genuinely easy during this window.

Recovery monitoring. Elevated resting HR (5+ bpm above baseline) is a reliable signal of insufficient recovery, illness, or excessive training stress — information that CTL/ATL/TSB doesn't capture.

The rule: Use pace as the primary intensity guide for quality sessions (T, I, R pace). Use HR as the primary guide when external conditions make pace unreliable (heat, altitude, significant hills). Use resting HR as a daily recovery signal regardless.

The 80/20 rule and Zone 2 training

The "80/20" or polarised training model — popularised by exercise scientist Stephen Seiler — recommends spending approximately 80% of training volume at low intensity (Zone 1–2) and 20% at high intensity (Zone 4–5), with minimal time in Zone 3.

The underlying research is solid. The practical problem for most runners is that Zone 3 is psychologically comfortable — not easy, not hard, but sustainable and feels productive. Runners who aim for Zone 2 often drift into Zone 3 within 20 minutes because genuine Zone 2 effort feels almost embarrassingly slow.

In VDOT terms, this maps directly to the E pace principle: your easy runs should be at E pace, which will feel slower than you think is appropriate. The physiological benefit comes from the accumulated aerobic stimulus at the correct intensity — not from "working hard enough."

A runner whose Zone 2 estimate is wrong by one zone is also unknowingly violating the 80/20 principle — not because they're ignoring the advice, but because the zones themselves are miscalibrated.

Putting it together: a practical approach

1. Calculate your VDOT from your most recent race result. Use this for all quality sessions — T, I, and R pace work.

2. Estimate your max HR as best you can — from a hard race, a field test, or lab measurement. Use it to set your Zone 1–2 boundaries for easy runs.

3. Run easy runs by feel and HR, not pace. On easy days, your HR should be below ~75% of your estimated max HR. If it consistently drifts above this at your "easy" pace, slow down.

4. Use HR as a heat and altitude correction. On days when conditions differ significantly from your training baseline, let HR govern the effort.

5. Trust pace for quality. T-pace sessions, I-pace intervals, and R-pace repetitions should be run to pace targets derived from VDOT. Don't let HR talk you into slowing down on a threshold session — the point of the session is the intensity, not the HR number.

6. Track resting HR daily. Elevation of 5+ bpm above your personal baseline is a signal worth noting — reduce intensity that day or rest.

Why adaptive plans handle this better

Static plans give you the same zones and the same paces regardless of whether your max HR is accurate, whether it's a hot day, or whether your fitness has shifted since your last race.

Adaptive training plans account for both pace-based and physiological signals. When your recent performance data suggests your VDOT has moved, paces update. When your CTL, ATL, and TSB indicate accumulated fatigue, intensity is managed down. The plan responds to what's actually happening — not to what it assumed three months ago when you set it up.

Heart rate zones are a useful map of exercise intensity. The problem is most runners are using a map drawn for someone else. Your max HR, your cardiac drift tendencies, your response to heat — these are individual. A training system built on your actual race performance accounts for that individuality automatically.

Frequently Asked Questions

What are the 5 heart rate zones for running?

The five heart rate zones for running are: Zone 1 (50–60% max HR) — very easy recovery; Zone 2 (60–70% max HR) — easy aerobic base building; Zone 3 (70–80% max HR) — moderate aerobic effort; Zone 4 (80–90% max HR) — threshold and tempo work; Zone 5 (90–100% max HR) — maximum effort intervals. However, these zones are only meaningful if your maximum heart rate is accurate — and for most runners using formula-based estimates, it isn't.

Is Zone 2 the same as easy pace in running?

Approximately, but not reliably. Zone 2 (roughly 60–70% of max HR) overlaps with Daniels' E pace for most runners, but the correspondence breaks down when max HR is estimated rather than measured. A runner whose true max HR is 185 bpm but whose watch assumes 178 bpm will have every zone shifted — making their "Zone 2" actually closer to Zone 3 physiologically.

Should I train by heart rate or pace?

Pace-based training using VDOT is more reliable for structured race preparation because it's derived from your actual race performance rather than an estimated physiological parameter. Heart rate is valuable as a secondary signal — particularly for easy runs in heat or altitude where pace becomes misleading — but should not be the primary intensity guide for threshold or interval sessions where precision matters most.