Home » Garmin Features » Physiology Metrics » Lactate Threshold

Lactate Threshold

Lactate threshold is the pace or heart rate at which the body begins to struggle to maintain the effort — beyond it, fatigue accumulates. A higher threshold means running faster for longer before that tipping point arrives.

In practice: Knowing your lactate threshold is fundamentally important for any endurance athlete looking to perform well. It is a foundational metric for other Garmin insights and essential for setting heart rate training zones for both training and racing. It is physically challenging to determine manually, but a manual test will likely yield a more accurate result than Garmin’s automated detection, which is susceptible to environmental and data-quality issues. Training slightly above lactate threshold puts you in VO2 max territory — a productive training zone and close to a 5K PB effort level. At half-marathon distance and above, you typically do not want to approach your lactate threshold on race day at all. Threshold improves with training at around that level; slower running contributes little if anything to threshold development. For endurance athletes, some training at threshold is required to improve it, which makes understanding the exact level all the more important. Run a maximal 10K, your Lactate Threshold heart rate is the average heart rate for the last 20 minutes.

Frequently Asked Questions

What is lactate threshold on Garmin?

Garmin Lactate Threshold identifies the exercise intensity above which effort becomes progressively unsustainable — the point at which the body produces more lactate than it can clear. Garmin expresses it as both a heart rate value and a running pace within an athlete’s training zones.

How does Garmin detect lactate threshold automatically?

Garmin uses Firstbeat Analytics to identify the point at which the relationship between heart rate and pace shifts, indicating the transition from aerobic to anaerobic metabolism. The algorithm requires an outdoor run in which the athlete sustains intensity above the estimated threshold for at least ten minutes, with both GPS and heart rate data present.

How accurate is Garmin’s lactate threshold estimate?

Research on non-invasive threshold methods finds agreement within approximately five to ten beats per minute of invasive lab testing in trained endurance athletes, with greater error in untrained populations. Trend reliability is more practically useful than absolute accuracy — consistent conditions matter more than the raw figure.

How do I improve my lactate threshold on Garmin?

The most effective method is sustained tempo running at or just below the threshold heart rate or pace for twenty to forty minutes, or threshold intervals of eight to fifteen minutes with brief recovery. One session per week builds aerobic capacity; two per week is appropriate during a focused threshold block with adequate recovery between them.

---

Lactate Threshold — A Deep Dive

When Lactate Threshold Is Actually Useful

• Over many years, I used lactate threshold tests as the primary method for determining heart rate training zones. That remains a sound approach, but power-based training and accurate running pace now offer easier, often more precise alternatives for zone setting.
• For 5K racing and parkrun, I let heart rate climb to a natural quasi-plateau early in the race, then aim to hold it just above that level for the remainder. It works reasonably well, but changes in effort — climbing a hill, for example — take 20 to 30 seconds to show in heart rate, so it is an imperfect real-time tool.
• A known anaerobic lactate threshold can be used to derive your aerobic threshold, which is a useful anchor point for longer training runs — the intensity you want to build your easy and medium-long runs around.
• Lactate threshold varies by sport. My running threshold is about 3 bpm higher than in other disciplines; my swimming threshold is significantly lower. Threshold figures are only useful if you know which sport they apply to — cross-sport comparisons are wrong.

Garmin Lactate Threshold identifies the exercise intensity above which effort becomes progressively unsustainable — the point at which the body produces more lactate than it can clear and fatigue begins to accumulate. Training at and around this intensity produces the greatest aerobic gains; training consistently above it without adequate recovery leads to breakdown rather than adaptation.

Garmin expresses lactate threshold as both a heart rate and a running pace, placing it within an athlete’s broader training zones. The primary limitation is that the estimate is derived from heart rate data and VO2 max modelling rather than blood sampling, and it remains sensitive to the quality of the heart rate input on which it depends.

What the Number Actually Means

Lactate threshold represents the upper boundary of sustainable aerobic effort. Below it, the aerobic system processes lactate as fast as it is produced, and an athlete can maintain the pace for extended periods. Above it, lactate accumulates progressively and performance at that intensity is time-limited. A higher threshold — at a greater percentage of VO2 max or at a faster absolute pace — indicates a more developed aerobic base. In recreational runners, it typically falls between 75 and 90 per cent of maximum heart rate; training history is the dominant determinant, and age reduces VO2 max without altering the percentage at which threshold occurs.

How Garmin Calculates It

Garmin uses Firstbeat Analytics to estimate lactate threshold by identifying the point at which the relationship between heart rate and pace shifts, indicating the transition from aerobic to anaerobic metabolism — a non-invasive proxy for the physical measurement made during laboratory blood lactate testing. The algorithm requires an outdoor run in which the athlete maintains a pace that raises their heart rate above the estimated threshold for at least 10 minutes. GPS pace data and heart rate data are both required; the feature does not update from treadmill runs unless a calibrated footpod is supplying pace data to the watch.

When conditions for an update are not met — because the run was too short, too easy, or conducted indoors without a footpod — the stored value carries forward from the most recent qualifying session. The watch displays a notification when a new estimate is calculated after a qualifying run.

What Affects the Reading

Heat and altitude both raise heart rate at any given pace, causing the algorithm to estimate a lower threshold pace than reflects true fitness. An athlete running in conditions more than five degrees above their normal training conditions, or at significant elevation in the first several days, should expect a suppressed estimate until conditions normalise. Wrist-based heart rate introduces lag and noise that can distort the algorithm’s reading of the aerobic-anaerobic transition; a chest strap yields a cleaner signal and more stable estimates, particularly during tempo-paced efforts where heart rate changes rapidly.

Illness and accumulated fatigue both elevate exercise heart rate, suppressing the estimated threshold pace. The stored value in these conditions reflects fitness on that day rather than underlying capacity. Caffeine, beta-blockers, and other substances that affect heart rate can shift the apparent transition point; the algorithm has no mechanism to detect the effects of medications or stimulants on heart rate.

How Accurate Is It

Direct laboratory measurement uses blood sampling during a structured laboratory fitness test. Garmin’s non-invasive method is a validated proxy. Research examining non-invasive threshold methods has found agreement within approximately five to ten beats per minute of invasive threshold in trained endurance athletes, with greater error in untrained populations where the aerobic-anaerobic transition is less clearly defined.

Trend reliability is more practically relevant than absolute accuracy for most athletes. An estimate consistently five beats per minute below a laboratory value remains useful for tracking training progress, provided the conditions under which each estimate is made are comparable. Estimates taken after changes in heat, altitude, illness, or sensor type should not be compared directly to prior baseline values.

Competitor Equivalents

• Polar offers a Threshold Heart Rate derived from a specific guided field test in Polar Flow, which requires a separate scheduled session rather than passive detection during regular training runs.
• Apple Watch does not display a lactate threshold estimate; Cardio Fitness (VO2 max) is Apple’s primary indicator of aerobic fitness.
• Coros provides Threshold Pace and Threshold Heart Rate within its training zones framework, though its documentation does not specify the modelling approach used.
• Suunto does not expose a specific lactate threshold figure in the Suunto app as of early 2026; its fitness features provide aerobic capacity information but not a discrete threshold value.
• Wahoo’s SYSTM platform incorporates a threshold concept through its Four Dimensional Power profile, which is cycling-specific and derived from structured test efforts rather than passive detection.

Which Garmin Devices Support It

Garmin introduced lactate threshold estimation in 2014 on the Forerunner 620, the first consumer running watch to offer automated threshold detection without a laboratory test. The feature is available on all current mid-tier and above devices carrying the full Firstbeat training intelligence suite: the Fenix 8 series (including Enduro 3, Tactix 8, and Fenix E), Forerunner 970, Forerunner 570, Venu 4, Venu X1, and prior-generation flagships, including the Forerunner 965, Forerunner 265, and Epix Pro Gen 2. The Forerunner 165 and Forerunner 55 do not support threshold detection; the Instinct 3 supports VO2 max estimation but lacks the threshold detection algorithm.

Where to Find It

• Watch — Performance Stats widget — heart rate and pace values displayed as the current estimate; on unified firmware devices, the estimate also appears contextually within the Training Status widget.
• Garmin Connect Mobile — Performance section — found under the More tab; historical trend data available showing both heart rate and pace components with the date of the most recent qualifying estimate.
• Garmin Connect Web — Health Stats — current value displayed; historical visualisation is more limited than in the mobile app.
• No subscription required — lactate threshold data is available on all Garmin Connect tiers.

Common Problems and Misreadings

A threshold estimate lower than expected after a hard tempo run is usually caused by heart rate lag from a wrist sensor during the effort. See FAQ above for detail.

Athletes who train primarily on treadmills often find the estimate absent or stale. The feature requires GPS pace data by default; pairing a calibrated footpod allows indoor sessions to qualify, provided the footpod has been calibrated over outdoor runs first.

A threshold estimate that declines during heavy training is often misread as fitness regression. Accumulated fatigue elevates exercise heart rate, which suppresses the estimated threshold pace. The value typically recovers following a taper or rest week. Reading the metric alongside Training Load and Recovery Time reduces this misinterpretation.

Lactate Threshold Heart Rate (LTHR) is a commonly used term and is physiologically similar to VT2, MLSS, AnT, and LT2. There are other, lower, thresholds called AeT, LT1 and VT1. Consumer sports science refers to the higher threshold.

How to Improve It

The most effective method for raising lactate threshold is sustained tempo running — continuous efforts at or just below the threshold heart rate or pace for twenty to forty minutes. This intensity is typically described as comfortably hard: sustainable for the duration but not conversational. One threshold session per week is a standard prescription for athletes building aerobic capacity; two sessions per week are appropriate during a focused threshold block with adequate recovery between them. Threshold intervals of eight to fifteen minutes with brief recovery provide a comparable stimulus for athletes who find sustaining a continuous tempo difficult.

Long aerobic runs at a comfortable pace improve the body’s ability to use fat as fuel and sustain effort at higher intensities, allowing the aerobic system to handle more work before lactate accumulates. Threshold improvement comes from both dedicated threshold work and the underlying aerobic base that supports it; adding threshold intensity without maintaining easy running volume is a common error that limits adaptation.

Other Points

Aerobic fitness markers, including lactate threshold, are associated with cardiovascular and all-cause mortality risk in longitudinal studies. Kokkinos et al. (2010), published in Circulation, found that higher exercise capacity was among the strongest independent predictors of survival in a cohort of over 15,000 veterans, independent of other cardiovascular risk factors.

Lactate threshold declines more slowly during inactivity than VO2 max. Threshold-related fitness adaptations begin to reduce measurably within two to three weeks of complete detraining, but meaningful threshold decline typically requires four to eight weeks of inactivity. Athletes returning from short breaks of less than two weeks generally retain most of their threshold fitness.

Frequently Asked Questions

• Is hitting the wall the same as exceeding lactate threshold? No. Hitting the wall is glycogen depletion; exceeding lactate threshold is lactate accumulation driven by intensity. The mechanisms are unrelated. Lactate clears within minutes of reducing pace; glycogen depletion requires ingested carbohydrate to resolve.
• Why does Garmin show a different lactate threshold from a lab test? Laboratory testing uses blood sampling to identify the precise point at which lactate begins to accumulate; Garmin uses a non-invasive heart rate and pace analysis as a proxy. The two methods measure related but not identical phenomena. Expect a margin of several beats per minute; the Garmin estimate is useful for tracking relative change rather than replacing a laboratory baseline.
• How often does Garmin update the lactate threshold estimate? The estimate updates after any qualifying outdoor run in which the athlete sustains intensity above the current estimated threshold for at least ten minutes. There is no fixed schedule. Athletes who train primarily at easy paces may go several weeks without a new estimate.
• Can the lactate threshold be entered manually? Yes. Go to User Profile in the Garmin Connect app, find Physiological Metrics, and enter the heart rate figure from a laboratory or field test. Disable auto-detect to preserve the manually entered value.
• Does lactate threshold apply to cycling on Garmin? No. Garmin’s lactate threshold detection is specific to running and uses GPS pace as a primary input. The cycling equivalent is Functional Threshold Power (FTP), calculated from power output rather than pace-matched heart rate analysis.
• Will treadmill running affect the lactate threshold estimate? Treadmill runs do not update the estimate by default. Pairing a calibrated footpod that broadcasts pace to the watch allows treadmill sessions to qualify, provided the footpod calibration is accurate.

Scientific Basis

Kindermann, W., Simon, G., Keul, J. (1979). The significance of the aerobic-anaerobic transition for the determination of work load intensities during endurance training. European Journal of Applied Physiology. Foundational paper defining the aerobic-anaerobic threshold concept on which non-invasive estimation methods are based.

Conconi, F., et al. (1982). Determination of the anaerobic threshold by a non-invasive field test in runners. Journal of Applied Physiology. Describes a non-invasive heart rate and pace method for identifying the anaerobic threshold — the methodological basis most closely related to Garmin’s approach.

Seiler, S., Kjerland, G.Ø. (2006). Quantifying training intensity distribution in elite endurance athletes: Is there evidence for an optimal distribution? Scandinavian Journal of Medicine and Science in Sports. Provides the evidence base for intensity zone frameworks built around lactate threshold, directly relevant to how Garmin uses the threshold to define training zones.

Firstbeat Technologies (2014). Automated Fitness Level (VO2max) Estimation with Heart Rate and Speed Data. Firstbeat white paper. Describes the Firstbeat modelling framework within which lactate threshold estimation operates on Garmin devices.

How It Connects to Other Features

Lactate threshold is a primary input into Training Status, which uses its relationship with recent Training Load to assess whether fitness is improving or declining — an outdated threshold value will corrupt that assessment.

The threshold heart rate also defines the aerobic-anaerobic zone boundary used by Training Effect to classify each session, and by Daily Suggested Workouts to prescribe threshold efforts.

VO2 max is a dependency: the Firstbeat engine uses the VO2 max estimate when calculating threshold, so an inaccurate VO2 max propagates error into the threshold figure. Race Predictor draws on both metrics to generate finishing time estimates for distances from 10 kilometres to the marathon.