Zone 2 Based on LTHR vs Max HR: Which Method to Use

You set your Garmin to Zone 2 for easy runs. The watch beeps at 128 bpm — but your coach says easy running should sit around 145. Both numbers claim to be Zone 2. The conflict is not your fitness; it is the method behind the zone.

Most wearables default to max heart rate percentages, often derived from 220 minus age. Running coaches and sports scientists more often anchor zones to lactate threshold heart rate (LTHR), because threshold marks the boundary where aerobic metabolism starts losing ground to glycolytic stress. Same athlete, same workout intent, different math — and the gap can be 15–20 beats per minute.

This article compares LTHR-based and max-HR-based Zone 2 boundaries, shows what Garmin does out of the box, walks through a side-by-side example, and explains when a threshold test is worth the effort.

Two Different Reference Points

Max HR methods define zones as percentages of your highest observed (or estimated) heart rate. The classic age formula — 220 minus age — is a population average with a wide individual spread. A measured max from a hard 5K or ramp test is better, but max HR still describes a ceiling, not where your aerobic system transitions to harder work.

LTHR methods define zones relative to the heart rate at lactate threshold — roughly the highest effort you can sustain for 30–60 minutes in a trained runner. Joe Friel's widely used running model places Zone 2 at 85–89% of LTHR. That range targets true aerobic base work: below the intensity where lactate starts accumulating faster than you clear it.

The practical consequence: max-HR Zone 2 often sits lower in absolute beats than LTHR Zone 2 for the same person. If you follow the lower range while your physiology supports a higher one, easy runs feel artificially slow. Follow the higher range without knowing your real threshold, and "easy" days become moderate-intensity sessions that never fully recover.

Garmin Defaults and What They Assume

Fresh Garmin accounts typically calculate heart rate zones as percentages of max HR. If you never update the profile, max HR often defaults to 220 minus age. Zone 2 in Garmin's five-zone model is commonly set to 60–70% of max HR — the same band used in many general-fitness charts.

Garmin also supports lactate threshold heart rate as a zone basis. You can enter LTHR manually after a field test, accept a Garmin-estimated threshold from certain watch models after qualifying runs, or switch zone type to heart rate reserve (% HRR) in Garmin Connect. Each option reshuffles the numbers.

Three common failure modes with Garmin Zone 2:

• Stale max HR: still set to 220 minus age when your true max is 8–12 beats higher or lower
• Wrong zone type: using % max HR while training plans assume LTHR percentages
• Auto-detected LTHR drift: Garmin's estimated threshold can lag after a fitness jump or overestimate after heat-stressed runs

Before trusting any zone alarm, open Garmin Connect → Settings → User Settings → Heart Rate Zones and confirm which basis is active. A zone alert is only as good as the reference value underneath it.

Side-by-Side Example: Same Athlete, Different Zone 2

Consider a 38-year-old runner with measured max HR of 186 bpm, resting HR of 52 bpm, and LTHR of 168 bpm from a 30-minute time trial. Here is how common methods set Zone 2:

• 220 − age (60–70%): max estimate 182 → Zone 2 = 109–127 bpm
• Measured max HR (60–70%): 186 → Zone 2 = 112–130 bpm
• Karvonen / HRR (60–70%): reserve 134 → Zone 2 = 132–146 bpm
• LTHR — Friel running model (85–89%): 168 → Zone 2 = 143–150 bpm

The spread is 109–150 bpm — a 41-beat window labeled the same zone. At 145 bpm, the LTHR method says solid Zone 2; the age-based max HR method says high Zone 3 or above. That is not a rounding error. It is a methodology mismatch that changes every easy-run decision.

Run the same inputs through the Zone 2 Running Calculator and the Heart Rate Zones Calculator to see your own ranges across methods. If two methods disagree by more than 10 beats, treat the default watch zones as a starting guess, not a prescription.

When LTHR Testing Is Worth It

You do not need a lab lactate cart to get useful LTHR. A well-executed field test — Joe Friel's 30-minute all-out time trial is the standard — gives a threshold heart rate accurate enough for zone boundaries. Average HR from the final 20 minutes of that effort is a common LTHR estimate.

LTHR testing pays off when:

• You train by heart rate at least three days per week and easy-day discipline matters for your plan
• Max HR formulas and your real easy-run heart rate clearly disagree (easy pace still reads "too high" on the watch)
• You are building aerobic base before race-specific work and want easy runs to stay genuinely easy
• You use structured plans that reference threshold percentages — Friel, TrainerRoad running adaptations, or similar
• Your max HR is unusually high or low relative to age, which breaks 220-minus-age badly

LTHR testing is lower priority when you mostly train by pace and effort, your easy runs already feel conversational at the watch's Zone 2, or you are in a short race-prep block where pace targets matter more than HR anchors.

Limitations of Each Method

Max HR and 220 − age

The age formula carries a standard deviation of roughly 10–12 bpm in healthy adults. Two 40-year-olds both assigned max HR of 180 may actually peak at 168 and 192. Percentage zones amplify that error: 5% of a wrong max HR can shift Zone 2 by 9 beats.

Max HR also drifts with fatigue, medication, heat, and detraining — but zone settings usually stay fixed until you manually update them. A method tied only to max HR cannot capture that your threshold moved after eight weeks of base building even if max HR stayed flat.

LTHR field tests

A 30-minute time trial requires pacing skill. Start too fast and LTHR reads high; sandbag the effort and it reads low. Heat, caffeine, sleep debt, and cardiac drift during the test all nudge the result. Retest every 6–8 weeks in a build phase, or after major fitness changes.

LTHR is sport-specific. A cycling threshold test does not automatically transfer to running LTHR — running threshold is typically a few beats higher for the same athlete. Use a running-specific test for running zones.

Wrist optical heart rate

Even perfect zone math fails if the sensor lags or spikes. Cold weather, intervals, and tight watch straps distort wrist readings. Validate zones on steady easy runs with a chest strap before locking in alarms. If optical HR runs 5–8 beats low at easy pace, your watch may show Zone 1 while you are actually in Zone 2 by chest strap — or the reverse.

Practical Decision Framework

Use this sequence instead of picking the method that feels convenient:

1. Set a real max HR from a recent hard effort or chest-strap data — not 220 minus age unless you have no better signal.
2. Run a threshold field test if easy runs by feel do not match your watch zones, or if you train primarily by HR.
3. Enter LTHR into Garmin and switch zone type to lactate threshold if the watch supports it.
4. Cross-check with pace and RPE: Zone 2 should be conversational. If you cannot speak in sentences, the zone — or the sensor — is wrong regardless of method.
5. Track trends over 4–6 weeks: faster pace at the same Zone 2 HR means the anchor is working. Chronic drift into higher zones on easy days means your ceiling or threshold setting needs review.

For most committed distance runners, LTHR-based Zone 2 produces better easy-day targeting than max HR percentages. Max HR methods remain acceptable for beginners, casual joggers, or athletes who mainly use pace — as long as they understand the zones are approximate.

Final Takeaway

Zone 2 is not a universal heart rate band. It is a training intent — aerobic base with low glycolytic stress — and lactate threshold is the reference that best expresses that intent for runners. Max HR and 220-minus-age are simpler, but simplicity costs precision when the formula does not match your physiology.

Check your Garmin zone type, compare methods with a calculator, and invest in one threshold field test if easy runs and watch alerts keep fighting each other. The goal is not a perfect number. It is a Zone 2 range tight enough that you can trust it on Tuesday morning when you are deciding whether to back off or push.

→ Calculate your Zone 2 range · → Compare all HR zone methods

FAQ

Can I use Garmin's auto-detected lactate threshold instead of a field test?

Garmin's estimated LTHR from wrist data is a reasonable starting point for steady runners who log regular outdoor runs. It tends to lag after fitness breakthroughs and can skew after hot or hilly sessions. Treat it as a draft value: compare against a 30-minute time trial or a recent race effort at threshold effort. If the two are within 3–4 bpm, use the Garmin value and re-check monthly. If they diverge more, manual entry from a field test is more reliable.

Why is my LTHR Zone 2 higher than 70% of my max HR?

Because lactate threshold sits well below max HR in most trained runners — often 85–92% of max — and Zone 2 is defined as a band just under that threshold. Seventy percent of max HR is a generic population shortcut, not a physiological boundary. A runner with max HR 186 and LTHR 168 has threshold at 90% of max; 85–89% of LTHR naturally lands near 143–150 bpm, which is 77–81% of max. Both percentages are "correct" within their own models — they just answer different questions.

How often should I retest LTHR?

Every 6–8 weeks during an aerobic build phase, or after a noticeable fitness change — a new half-marathon PR, a long break, or a sustained block of high-volume easy running. Outside build phases, one test at the start of a training cycle is often enough. Update Garmin and your calculators the same day you accept a new value so zone alerts and training logs stay consistent.