How to Use HR Zones for Real Training (Not Just Garmin's Defaults)

The Gap Between Having Zones and Using Them

Most athletes have heart rate zones configured on their Garmin. They set them up once, either when they first got the watch or after reading an article about it, and then they more or less forgot about them. The zones are there. The watch tracks them during every run. At the end of each session there is a little bar chart showing how long you spent in zone 1, 2, 3, 4, and 5.

And then nothing happens with that information.

This is the central problem with HR zones for most self-coached athletes: zones are used for recording, not for deciding. They capture what already happened. They do not change what you are about to do, or how you interpret last week's training, or whether the last three months of preparation are actually building the fitness you think they are.

The weekly zone distribution — the breakdown of total training time across all five zones for the previous seven days — is the single most useful summary of how you actually trained. Not pace. Not total mileage. Not training load in isolation. Zone distribution tells you the physiological character of your training: whether you spent the week building aerobic capacity, hammering your lactate threshold, grinding in the gray zone between easy and hard, or some deliberate mix of all three.

A coach reading a weekly zone distribution can immediately tell whether an athlete is following a polarized approach, a pyramidal approach, or a threshold-focused approach — and whether what actually happened matches what was planned. They can diagnose in two minutes whether an athlete is training too hard on easy days, not hard enough on hard days, or drifting toward the gray zone that produces mediocre results in both directions.

This article is about developing that same diagnostic lens for yourself. It covers why default zones fail most athletes, how to validate whether your zones are actually correct, how to read your weekly distribution as a training diagnostic, and how to move from passively recording zone data to actively using it for decisions. The technical setup for zones in Garmin Connect is covered in the zones setup guide — this article is about the strategy and methodology behind using them.

The Five Zone Methods and Why Default Zones Fail Most Athletes

Garmin, by default, sets your heart rate zones using a percentage of maximum heart rate, and it estimates your maximum heart rate using the formula 220 minus your age.

The 220-age formula is wrong for approximately half the population. Not slightly off — for many athletes it is wrong by 10-15 beats per minute. A 45-year-old with an actual maximum heart rate of 178 will have Garmin calculate 175 bpm and set zones accordingly. That is close enough that the error feels invisible. But a 45-year-old whose real max is 192 — not unusual for a lifelong athlete — has zones shifted by 17 beats, which means their "easy" zone 2 top end is actually sitting solidly in zone 3. They run every easy day too hard and wonder why their recovery never feels complete.

The formula is a population average. It describes the mean of a distribution with enormous variance. Your individual maximum heart rate is primarily genetic, and it does not follow the formula with any precision.

There are five commonly used methods for setting heart rate zones, each with different accuracy and different requirements.

Method	How zones are set	Accuracy	Best for
%MaxHR (220-age)	Estimated max HR using age formula	Low — population average, high individual error	Total beginners with no other data
%MaxHR (tested)	Tested max HR, zones as % of that	Medium — correct anchor, arbitrary zone boundaries	Athletes who know their true max
Karvonen (HRR)	Zones as % of heart rate reserve (max minus resting)	Medium-high — accounts for fitness level	Intermediate athletes with stable resting HR
LTHR-based	Zones set from lactate threshold heart rate	High — physiologically meaningful anchor	Trained athletes, threshold-focused training
MAF (Maffetone)	Single aerobic ceiling = 180 minus age ± adjustments	Varies — useful for base-building, rigid formula	Base phase, polarized training emphasis

The LTHR-based system is the most physiologically meaningful for trained athletes. Your lactate threshold heart rate — the rate above which blood lactate accumulates faster than you can clear it — is the most important boundary in endurance training. Setting zones around it rather than around your maximum HR means your zone boundaries actually correspond to meaningful physiological states.

The Karvonen method is a meaningful improvement over raw %MaxHR because it accounts for your resting heart rate. A fitter athlete with the same maximum HR as a sedentary person will have a lower resting HR and therefore a higher heart rate reserve. Karvonen spreads the zones across that reserve, so fitter athletes get appropriately higher zone thresholds for a given percentage — which is physiologically more accurate.

The key insight, though, is that no formula is a substitute for testing. The purpose of zone setup is to match your training intensities to your physiology, and your physiology is not a formula. You can use the HR zone calculator to compute zones from any of these methods, but the accuracy of the output is only as good as the accuracy of your anchor values — and the only way to get accurate anchor values is to measure them.

For a practical walkthrough of setting and updating zones in Garmin Connect, read the zone setup guide. What we are covering here is the upstream question: which method is right for your training, and how do you know when your zones are accurate?

How to Validate Your Zones Are Actually Correct

Setting zones by formula and validating them against your actual physiology are two different things. You can have perfectly calculated Karvonen zones and still have them wrong — because the inputs (max HR, resting HR, or LTHR) were inaccurate, or because your fitness has changed significantly since you last tested.

Here is how to tell whether your zones are set correctly.

The Easy-Run Perception Test

Go for a run that you intend to keep entirely in zone 2. At your zone 2 ceiling, you should be able to speak in complete sentences without pausing for breath. The effort should feel genuinely easy — not comfortable-but-working, but easy. You should be able to hold that pace for three or four hours without feeling like you are pushing.

If easy feels hard, your zones are set too high. This is the most common symptom of misconfigured zones among motivated athletes. If you are running at what Garmin labels zone 2 and you are breathing through your mouth, cutting sentences short, and feeling like you are working — your zone 2 ceiling is sitting above your actual aerobic threshold. Every easy run becomes a moderately hard run, you accumulate fatigue faster than you expect, and your hard sessions feel flat because you never fully recovered from your "easy" days.

If easy feels trivially slow — you feel like you could sprint at zone 2's upper end — your zones may be set too low, which is less common but happens with athletes who have recently gained significant fitness without updating their zones.

The Threshold Run Cross-Check

Garmin's lactate threshold detection identifies your threshold heart rate during hard efforts. You can also run a guided lactate threshold test from your device. Once you have an LTHR estimate, compare it to where your current zone boundaries sit.

In a five-zone system, your lactate threshold should fall at or near the top of zone 4 / bottom of zone 5. In Garmin's default system, this corresponds roughly to the zone 4 ceiling. If your LTHR lands in the middle of zone 3, your zones are set significantly too high. If it falls above zone 5, they are set too low.

The Race-Pace Reality Check

Your 10K race pace should feel like a sustained zone 4-5 effort — genuinely hard, something you can sustain for 40-55 minutes but not much longer. Your half-marathon pace should settle around zone 4. Your marathon pace for trained runners should sit at the top of zone 3 or low zone 4.

If your 10K race pace is showing as zone 3 on your Garmin, your zones are too high — what Garmin calls "threshold" work is actually your aerobic-moderate effort. If your easy-pace long runs are reading zone 4, your zones are too low.

Use the race pace predictor to cross-reference your predicted paces against your current fitness, then check where those paces fall in your zone distribution.

When to Use a Lab Test vs. a Field Test

A laboratory lactate test remains the gold standard for zone accuracy. An exercise physiologist measures blood lactate at multiple intensities, identifies the precise point at which it begins to accumulate, and sets your zones directly from physiology rather than inference. This is useful if you are a serious competitive athlete, have a history of zones feeling wrong despite repeated adjustments, or are building a season-long training block where zone accuracy is critical.

For most athletes, a well-executed field test — either a 30-minute time trial where you average your heart rate over the final 20 minutes and use that as a proxy LTHR, or Garmin's guided test — is accurate enough. The key is actually running the test rather than estimating.

Update your zones whenever your fitness changes meaningfully. After a strong 8-12 week training block, your LTHR and maximum HR may both shift. Running with stale zones negates most of the benefit of zone-based training.

Weekly Zone Distribution as Diagnostic

Once your zones are correctly set, the weekly time-in-zone summary becomes the most useful diagnostic tool in your Garmin data. It tells you not just what you did, but what kind of physiological work you actually performed.

Understanding zone distribution requires knowing the three major intensity models that endurance coaches use.

The Three Distribution Models

Polarized training concentrates the vast majority of training in zones 1-2, with a meaningful portion in zones 4-5, and almost nothing in zone 3. The name describes the two poles of intensity — easy and hard — with a gap in the middle. The research behind polarized training, driven largely by Stephen Seiler's work on elite endurance athletes, consistently shows that highly trained athletes across sports naturally distribute toward this pattern. The easy work builds and maintains the aerobic base. The hard work drives VO2 max and lactate threshold adaptation. Zone 3 — sometimes called the "gray zone" — is too hard to be truly aerobic and too easy to drive the adaptations of high-intensity work, so it produces mediocre results for its cost. Read the full breakdown in the polarized training guide.

Pyramidal training has the majority of time in zone 1-2, a meaningful chunk in zone 3, and less in zones 4-5. This is a moderate approach that acknowledges zone 3 work is not worthless — it builds threshold endurance — while still grounding the week in aerobic volume. It is often the natural distribution for athletes following a threshold-based training plan.

Threshold training pushes more volume into zone 3-4. This is sometimes deliberate — athletes specifically targeting lactate threshold development — and sometimes accidental. A lot of athletes end up here without intending to, because zone 3 feels productive without feeling unsustainably hard.

Here is what each model looks like in actual weekly numbers, for a runner logging 8 hours per week:

Model	Z1	Z2	Z3	Z4	Z5	Total easy (Z1-2)
Polarized	2h 30m	3h 30m	20m	1h 00m	40m	~75%
Pyramidal	1h 45m	3h 30m	1h 15m	1h 00m	30m	~65%
Threshold-focused	1h 00m	2h 30m	2h 30m	1h 30m	30m	~44%
Gray zone (accidental)	30m	1h 30m	4h 30m	1h 00m	30m	~25%

The gray zone row is not a deliberate training methodology — it is what happens when athletes do most of their running at "comfortable hard" pace. They are working too hard to access the aerobic adaptations of zone 2 and not hard enough to drive VO2 max or lactate threshold gains. This is the most common training error among motivated self-coached athletes, and it is almost invisible without looking at your weekly zone distribution.

Reading Your Distribution on Garmin

In Garmin Connect, the weekly time-in-zone summary is available under your training load and performance stats. On the watch itself, the training effect summary after each session shows zone contribution.

The diagnostic questions to ask when you open your weekly distribution:

Is zone 2 the dominant column? If not — if zone 3 or zone 4 is your biggest column — you are likely training with the wrong intensity profile for endurance development.
Is there a clear gap between your easy work and your hard work? A healthy week typically looks like a U-shape or a left-skewed pyramid — high on the left (Z1-2), lower in the middle (Z3), and a meaningful column of high intensity (Z4-5). If it looks like a bell curve centered on zone 3, you are in gray-zone territory.
Does the hard work match what you actually intended? A scheduled interval session at zone 4-5 should appear as a meaningful column in those zones. If your "interval session" shows mostly zone 3, you did not hit the intended intensity. This matters for adaptation — VO2 max gains require genuinely high-intensity stimulus.
Does the week's distribution match your current training phase? During base phase, almost nothing should be above zone 2. During a periodized build phase, you expect to see zone 4-5 growing. If you are in base phase and zone 3 is climbing, you are drifting toward gray zone.

This weekly read takes about two minutes once you know what you are looking at. The patterns repeat across weeks, so trends become visible quickly: whether you are progressively polarizing your training, whether gray zone creep is happening, whether your hard days are actually hard.

Using Zones for Training Decisions, Not Just Recording

This is where zone-based training shifts from a logging exercise to a coaching tool. There are three points in the training process where zone data should actively inform decisions: before the workout, during it, and after it.

Pre-Workout Zone Targeting

Every session should have an intended zone ceiling — not just a pace target, but an explicit heart rate boundary. An easy run is zone 2. A threshold run has a specific zone 4 target. A long run might be zone 2 with a 20-minute zone 3 progression at the end.

Setting the intended zones before you start creates a standard against which to measure what actually happened. It also gives you a real-time constraint during the workout — and this matters more than most athletes realize.

Pace-based training breaks down on hills, in heat, in headwinds, on tired legs, and in the early weeks of adapting to new training stress. Heart rate targets are robust across all of these conditions, because they reflect what the effort is actually costing your body rather than what the GPS says about your speed.

For running training plans and marathon preparation, zone targets on easy runs in particular are the single most effective tool for keeping those sessions actually easy — not just feeling easy, but physiologically easy.

Mid-Workout HR Ceiling

On easy days, treat the zone 2 ceiling as a hard ceiling. If your heart rate rises above it — on a hill, in heat, or because you unconsciously picked up the pace — slow down. Walk if you have to. This takes discipline for athletes who have pace expectations baked into their self-image. But zone 2 at 3 minutes per km slower than your usual easy pace is still zone 2, and the adaptation it drives is the same regardless of pace.

On hard days, use zone targets to confirm you are hitting the intended stimulus. If a session shows a lot of zone 3 when zone 4-5 was intended, you did not create the training stimulus the session was designed for.

The running power zones guide has additional context on using power alongside HR for intensity targeting — particularly useful in hilly terrain where HR lags behind effort by 30-60 seconds.

Post-Workout Zone Review

After each session, check the zone distribution in the training effect summary. The questions are simple:

Did the zones match the intent? Easy session: mostly Z1-2. Threshold session: meaningful Z4 with some Z3. VO2 max intervals: genuine Z5 presence.
Was there unexpected zone drift? A session that started in zone 2 and drifted to zone 3 over an hour signals cardiac drift — your heart rate climbing at constant pace — which typically indicates fatigue, heat, or dehydration. This is worth noting for your readiness assessment the next morning. The how to read your Garmin data like a coach guide covers how to integrate this with the broader morning readiness picture.
Did you hit the target on hard sessions? If your interval session was supposed to be zone 4-5 and it showed zone 3, either the target paces were too conservative or you were too fatigued to hit the intensity. Both are useful information.

The Weekly Review

Once a week, look at the full seven-day zone distribution alongside your training plan's intended distribution for that week. This five-minute review catches the patterns that individual session reviews miss — especially gray zone creep, which tends to happen one run at a time and only becomes visible when you see the week's aggregate.

Common Zone Errors and Their Data Fingerprints

Misconfigured zones show up in predictable patterns in your Garmin data. Here are the most common errors and what they look like.

Zones set too high. Easy runs feel hard. Zone 2 runs show as zone 3 in the distribution. Athletes feel chronically fatigued from "easy" training weeks. Training status often reads "Unproductive" or "Strained" despite reasonable load, because the system is detecting mismatch between supposed easy work and physiological cost. VO2 max tends to stagnate, because the athlete is too tired for quality hard sessions to produce adaptation.

Zones set too low. Hard sessions feel easier than expected. Zone 4 intervals never trigger the heavy breathing and burning sensation of genuine threshold work. Garmin's training effect after what should be a hard session reads "maintaining" rather than "improving." Race performance plateaus despite consistent training because the sessions are not creating the intended stimulus.

Outdated zones after a fitness improvement. This is common after a strong base-building block or a season of consistent training. Your LTHR climbs — you are fitter, and the pace you can sustain at threshold has improved — but your zones still reflect where you were six months ago. The symptom is that zone 3 feels genuinely easy, and you are hitting zone 4 targets with less perceived effort than expected. Update your zones whenever your fitness changes materially — at minimum, after every significant training block. Run another field test, or use Garmin's auto-detected threshold values after a hard run, and reset from there.

Wrong zone model for sport or goal. Using a purely aerobic MAF-based approach during a build phase targeting 5K performance will leave you under-stimulated for VO2 max development. Using a threshold-heavy distribution during base phase means you are accumulating fatigue without developing the deep aerobic base that supports harder work later. The zone method and distribution model should match your training phase and goal race distance.

The Multi-Sport Zone Question

If you train across more than one sport — run and cycle, or triathlon, or any combination — you need separate zones for each sport, and they will not be the same numbers.

Running typically produces higher heart rates than cycling at equivalent effort. The reasons are mechanical: running involves full-body weight-bearing muscle recruitment, impact absorption, and thermoregulatory demands that cycling does not. For most athletes, the difference between running zone 4 and cycling zone 4 is somewhere between 5 and 15 beats per minute — the cycling number is lower.

Swimming produces lower absolute heart rates than either, partly because of the horizontal position reducing cardiac workload and the water's thermoregulatory effect. HR-based zones for swimming are harder to use accurately and most swimmers do better with pace or power-based targeting.

This means that if you are training for a triathlon using a single set of heart rate zones across all three sports, you are almost certainly miscalibrated in at least two of them. Running at cycling zone 2 numbers is significantly over-stimulating. Cycling at running zone 2 numbers is likely under-stimulating.

Garmin supports per-sport heart rate zone configuration, and for multi-sport athletes this is not optional — it is essential for zone-based training to be meaningful. Set zones independently for running, cycling, and any other sport you train consistently. Test each sport separately. Use sport-specific maxHR or LTHR values as the anchor for each.

For runners who also cycle for cross-training, the practical rule is simple: do not use your running heart rate zones to guide your cycling, and vice versa. The numbers do not transfer. What feels like an easy zone 2 cycling effort by your running zones may actually be a zone 3+ cycling effort for your cardiovascular system, and vice versa.

The Garmin heart rate zones setup guide covers the technical steps for configuring per-sport zones in Garmin Connect if you have not done this yet.

When AI Coaching Helps With Zone-Based Training

The methodology described in this article — validating zones, reading weekly distributions, adjusting decisions based on zone data — is straightforward in concept. The challenge is consistency. Doing the weekly distribution review every single week, noticing the slow drift toward gray zone before it becomes a month-long pattern, catching when zones have gone stale after a fitness improvement, and integrating zone data with all the other signals your Garmin captures takes time and sustained attention.

This is the specific problem an AI coaching layer solves. Gneta reads your Garmin data continuously — including your heart rate zone metrics alongside HRV, readiness, training load, and sleep — and tracks your weekly distribution against your training phase and goals without you having to run the analysis manually every week. When zone drift is happening, the system surfaces it. When zones look stale relative to your current fitness trajectory, it flags that too.

For running athletes in particular, zone distribution is where the training quality signals live — not in pace, not in mileage, but in the physiological character of how you are actually spending your training time week by week. A consistent automated read of that distribution, interpreted against your training history, is the closest you get to having a coach glance at your training log and say "your easy days are too hard again — let's fix that before it catches up with you."

The continuous nature of that analysis is what makes it useful. A one-time zone audit is helpful. A system that notices the slow drift every week and keeps you honest about the distribution is what actually changes training outcomes.

If you want to understand the broader framework for reading all your Garmin metrics together — not just zones — the complete guide to reading your Garmin data like a coach covers the full system.

Putting It Together

Heart rate zones are only useful if they are accurate, and they are only actionable if you read them. Most athletes have neither — zones set by a flawed formula and data reviewed only as a log, not as a decision input.

The path forward is not complicated. Test your zones rather than estimating them. Validate them against perceived exertion and race data. Build the weekly distribution review into your training habit. Use zone ceilings as active constraints during sessions, not passive recording. Update your zones when your fitness changes.

Do those things and the zone distribution data your Garmin captures every week becomes what it was always supposed to be: a clear, honest summary of the physiological work you did, and a diagnostic tool for whether that work is building the fitness you need.

Ready to train with zone-based coaching that reads your weekly distribution continuously? See how Gneta works with your Garmin data or compare plans and pricing.

Related reading:

Features

Sports

Metrics

Compare