Guide
Heart-Rate Zones vs. Pace Zones: Which Should Runners Use?
Every runner with a GPS watch owns two competing speedometers. One reads your pace — what you're actually producing. The other reads your heart rate — what that production is costing you. Both come wrapped in five coloured zones, both promise to tell you how hard to run, and on plenty of days they flatly contradict each other. This guide explains what each system really measures, when each one lies, and how to decide — session by session — which number deserves your attention.
Input vs. output: what each system measures
The core difference fits in one sentence: pace measures output, heart rate measures input.
Pace is the external result — metres covered per second, the thing race clocks reward. When a training plan says "run 5:00 /km", it's prescribing an exact output, and a pace zone checks whether you delivered it. Heart rate is the internal cost — how hard your cardiovascular system is working to produce that output. The same 5:00 /km might cost you 145 bpm on a cool morning after a rest day and 158 bpm on a warm evening at the end of a hard week. The pace didn't change; the price did.
Neither number is "more true". They answer different questions: "What am I producing?" (pace) versus "What is it costing me?" (heart rate). Good training control is mostly about knowing which question the session in front of you is asking.
Why heart rate lies in intervals
Heart rate has two built-in distortions that matter enormously for fast running:
- Lag. Heart rate doesn't jump to the effort — it climbs towards it, typically taking one to three minutes to stabilise after a pace change. Start a 3-minute interval at 10K effort and your heart rate spends most of the rep still catching up; by the time it reads "correct", the rep is over. Chase the target number instead, and you'll surge way past the intended effort in the first minute — the classic way to ruin an interval session. For repetitions under about 90 seconds, heart rate is close to meaningless as a control signal.
- Cardiac drift. Hold a perfectly steady pace for 40+ minutes, especially in warmth, and your heart rate creeps upward anyway — a few beats per 10 minutes — as you dehydrate and divert blood to the skin for cooling. Same output, rising input. On a long run controlled purely by a heart-rate ceiling, drift forces you to slow down kilometre after kilometre even though nothing about the muscular effort changed.
Add day-to-day noise — sleep, caffeine, stress, heat, a looming illness can move resting and submax heart rate by 5–10 bpm — and you see why prescribing precise work by heart rate alone is shaky. Pace has no lag and no drift: 4:30 /km is 4:30 /km, the moment you run it.
Where heart rate wins
None of that makes heart rate useless — it makes it a specialist. The very "flaws" above are information:
- Heat and humidity. On a hot day, your usual easy pace genuinely costs more. Pace zones don't know about weather; your heart rate does. Running by effort/heart rate in the heat is honest; forcing the usual pace is how easy days quietly become moderate ones.
- Fatigue and base building. In easy-volume phases, the goal is the input: keep the internal load low so you can absorb lots of running. A heart-rate cap on easy days catches the slow upward creep in effort that pace alone hides — especially when accumulated fatigue means your usual easy pace is no longer easy.
- Hills and trails. Pace zones assume flat, even ground. On a 10% climb, "easy pace" is meaningless — effort is what you're managing, and heart rate is a decent effort proxy exactly where pace stops being one.
- An early-warning system. Unusually high heart rate at a familiar easy pace is one of the cheapest signals you'll get of incoming illness, under-recovery or heat stress. That's not a bug in the metric; it's the metric doing its job.
Which tool for which session
| Session type | Better tool | Why |
|---|---|---|
| Easy & recovery runs | Heart rate | The goal is capped internal load; an HR ceiling keeps "easy" honest on tired legs and warm days |
| Long runs | Both | Pace band as the plan, HR as the tell-tale — steady drift is normal, a jump means back off |
| Threshold sessions | Pace | The target is a specific output; HR spends half the rep lagging its way into the zone |
| Intervals (2–5 min) | Pace | Reps end before HR stabilises; chasing the number front-loads the effort |
| Short reps (<90 s) | Pace only | HR never catches up within the rep — it's noise at this duration |
| Hot or humid days | Heart rate | The same pace costs more in heat; effort is the thing to manage, and HR tracks it |
| Hills & trails | Heart rate / effort | Pace zones assume flat ground; on climbs and rough terrain only the cost is comparable |
| Races | Pace + feel | Adrenaline inflates HR from the gun; the clock is the goal, so the clock is the guide |
The pattern behind the table: the faster and shorter the work, the more pace deserves control; the easier and longer the run — or the harsher the conditions — the more heart rate deserves it.
Using both together
The two systems are better partners than rivals. A simple division of labour that works for most runners:
- Prescribe quality by pace, police easy days by heart rate. Workouts get pace targets; easy runs get an HR ceiling and whatever pace that produces today is the right pace today.
- Watch the pairing, not either number alone. Pace-at-heart-rate is the most underrated fitness metric there is: if 5:30 /km used to cost 150 bpm and now costs 140, you got fitter — no race required. The reverse pairing (usual pace, unusually high cost) is your cue to take an easy day seriously.
- In races, leave HR on the recording but off the screen. It's useful forensics afterwards; during the race it mostly feeds doubt.
Setting your pace zones: a worked example
Pace zones need one input: your threshold pace, roughly the pace you could race for about an hour. No lab test needed — a recent 10K in the 45–60 minute range is close enough to read it straight off the clock. Say you ran a 10K in 47:30: that's 47:30 ÷ 10 = 4:45 /km. Feed that into the pace zones calculator and its multipliers return your five training ranges:
- Easy 5:42–6:39 /km — the bulk of your weekly volume
- Marathon 4:59–5:14 /km — steady long-run quality
- Threshold 4:39–4:51 /km — controlled hard, "comfortably uncomfortable"
- Interval 4:17–4:31 /km — VO2max work, 2–5 minute reps
- Repetition 4:02–4:17 /km — short, fast, full recoveries
Those five ranges are the pace-side half of everything this guide discussed: quality sessions get their targets from the bottom three bands, and if you also wear a heart-rate strap, your easy-day ceiling simply enforces the top one. The full logic of the five zones — what each one trains and how to build a week around them — is in the training pace zones guide.
Common mistakes
- Building heart-rate zones on 220 minus age. The formula is a population average with individual error bars of ±20 bpm — two same-aged runners can have genuinely different maxima by that much. Zones hung on a guessed maximum are miscalibrated from day one, and every session inherits the error. If you use HR zones, anchor them to observed data (a field test or the highest values you've actually recorded); if you use pace zones, anchor them to a real race. Never anchor anything to your birthday.
- Chasing zone borders. Zones are bands, not targets. Runners with a 150 bpm easy ceiling who surge and slow to ride at exactly 149, or who treat the top of the threshold pace band as the "real" session, are optimising the display instead of the training. Aim for the middle of the band and let the number wobble — the adaptation doesn't know about the border.
- Trusting wrist heart rate during hard running. Optical wrist sensors are decent at steady efforts and notoriously flaky during intervals, cold weather and sweaty summer sessions — dropouts and "lock-on" to your cadence (reading ~170–180 when your real HR is far lower) are common. If HR guides your training, a chest strap is the price of admission.
- Never updating either system. Fitness moves, so both zone sets go stale. Re-anchor pace zones after any honest race (a threshold that improved 10 s/km changes every band), and revisit HR zones if your observed max or resting values shift. Stale zones don't just mistrain you — they hide the very progress that would have motivated you.
Set your zones now
If you have any recent race result, you're one minute away from usable pace zones: enter your threshold pace into the pace zones calculator and you'll get all five bands, in min/km or min/mi. Run your quality by those numbers, put a heart-rate ceiling on your easy days if you have a strap — and let each speedometer do the one job it's actually good at.