Lactate Threshold Running: Tempo Pace, Testing, and Garmin LT Detection

Your watch says lactate threshold pace is 4:52/km. Your last 10K averaged 4:48/km. Your tempo runs at 4:55 feel sustainable for 25 minutes but wreck your legs for three days. Three data points, three different stories — and your training zones drift with whichever number you trust this week.

Lactate threshold (LT) — also called anaerobic threshold, maximal lactate steady state (MLSS), or the intensity at the second ventilatory threshold (VT2) — is the highest steady-state intensity you can hold before lactate accumulation outpaces clearance. It is the anchor for tempo runs, threshold intervals, and most heart rate zone models. Get LT wrong and every downstream workout is misprescribed.

This article covers LT physiology in plain terms, how to run a 20–30 minute field test, how training paces relate to LT as percentages, how Garmin and COROS estimate threshold from wrist data, and when to override the algorithm with your own test result.

What Lactate Threshold Actually Is

During aerobic running, muscle fibers produce lactate continuously. At low intensity, lactate is cleared by the liver, heart, and slow-twitch fibers as fast as it appears — blood lactate stays near resting levels (roughly 1–1.5 mmol/L). As intensity rises, lactate production accelerates. LT marks the inflection where lactate begins rising non-linearly — traditionally defined at ~4 mmol/L in lab step tests, though individual thresholds range from 2–6 mmol/L depending on athlete and protocol.

Above LT, lactate accumulates even during steady effort. You can still run above LT for minutes to an hour depending on how far above — but it is not indefinitely sustainable. Below LT, in theory, you could run for hours given fuel and durability.

Practical correlates runners can feel without a lab:

• VT2 / second ventilatory threshold: breathing shifts from rhythmic to strained; talking in full sentences becomes difficult
• RPE: roughly 7–8/10 — hard but controlled, not sprinting
• Duration: the pace you could hold for approximately 45–60 minutes in a race scenario — often close to 10K to 15K race pace for trained runners, or one-hour race pace in some models

LT is trainable. Consistent threshold work raises the pace and heart rate at which lactate spikes — one reason tempo runs appear in every serious 10K-to-marathon plan. It is also specific: LT pace on flat roads differs from trails; heat and altitude shift the heart rate at a given LT pace by 5–15 bpm.

LT Heart Rate vs LT Pace

Lactate threshold heart rate (LTHR) and lactate threshold pace (LT pace) describe the same physiological boundary through different lenses. LTHR is typically 85–92% of max HR for trained runners — highly individual. LT pace is the running speed at that intensity.

Why both matter:

• Pace is actionable on the track or flat road — you hit splits
• Heart rate adjusts for heat, hills, fatigue, and cardiac drift on longer threshold efforts
• Together they catch decoupling — if LT pace now produces HR 8 bpm above normal LTHR, something changed (fitness, stress, dehydration, or stale zones)

Most five-zone HR models anchor Zone 4 (threshold) to 95–105% of LTHR. Zone 2 ceiling sits near 85% LTHR. The gap between them is narrow — 5–10 bpm for many runners — which is why moderate runs bleed into threshold territory so easily. Use the Heart Rate Zones Calculator after you have a tested LTHR, not a default formula, for decision-grade zones.

The 20–30 Minute Tempo Test (Field Protocol)

The classic runner field test: a 30-minute time trial at the hardest steady effort you can sustain for the full duration — or a 20-minute test scaled to 30 minutes with a correction factor. This approximates LT pace because maximal lactate steady state correlates with roughly one-hour race effort; a 30-min all-out effort sits slightly above MLSS but averages near it when done correctly.

30-minute test protocol

1. Rest: 48+ hours after last hard session; normal sleep and hydration
2. Warm-up: 15 min easy jog + 4 × 20 sec strides + 2 min easy
3. Test: 30 min on flat, measured course (track, bike path, treadmill at 0–1% incline). Start controlled — minute 1 should not feel like minute 20. Aim for even effort; slight negative split acceptable
4. Record: average pace for the full 30 min = LT pace estimate. Average HR for minutes 10–30 = LTHR estimate (discard first 10 min of HR due to lag and ramp)
5. Cool-down: 10–15 min easy jog mandatory

20-minute test (Joe Friel protocol)

Same setup, but 20 min all-out steady. LT pace estimate = average 20-min pace × 0.95 (or divide 20-min distance by 0.95 to get corrected 30-min equivalent pace). LTHR = average HR for the final 15 minutes of the 20-min test. The 5% correction accounts for the shorter duration sitting slightly above true MLSS.

Example results

Wear a chest strap for the test — wrist HR lags and smooths, producing LTHR errors of 5–10 bpm. Pace on a measured track eliminates GPS noise. Re-test every 8–12 weeks during build phases; after illness or 4+ weeks detraining; after a breakthrough race that suggests fitness moved.

LT Pace as Percentage of Threshold

Once LT pace is established, other training intensities scale as percentages or offsets — not from max HR alone, but from threshold as the hub:

These offsets vary by athlete — fast-twitch-dominant runners may have 5K pace only 12 sec/km faster than LT; elite marathoners may hold LT within 3 sec/km of marathon pace. Race results refine the table better than formulas. Plug recent 5K and 10K times into the Race Predictor and cross-check against your LT test.

For structured tempo sessions — continuous 20–40 min or cruise intervals — see the Tempo Run Guide. Tempo at LT pace builds lactate clearance; tempo above LT (10K pace) shifts toward VO2 stimulus and belongs in shorter reps, not 40-min continuous blocks.

Garmin Lactate Threshold Detection

Garmin (Firstbeat Analytics) estimates lactate threshold pace and heart rate from a mix of:

• Detected threshold efforts during runs — sustained segments near inferred VT2
• Race and hard workout history
• Heart rate vs pace relationship across the training load
• Optional guided test: 10-min warm-up, then increasing pace until failure (on select devices)

Garmin updates LT automatically when new qualifying efforts appear. Runners report accuracy within 5–10 sec/km of field tests when training is consistent and HR data is clean — chest strap on hard days, steady routes, no chronic moderate-everything patterns that confuse the model.

Where Garmin LT drifts wrong:

• Insufficient hard data: new watch, mostly easy running — estimate defaults to formula from age and max HR
• Bad wrist HR on intervals: noisy data produces false threshold detection or none at all
• Stale fitness: LT not updated after 8 weeks of improved training; old value persists until a new hard effort triggers recalculation
• Heat and hills: algorithm may interpret elevated HR at moderate pace as lower LT pace than reality, or vice versa on cold flat days
• Manual override ignored: you can set LT manually in Garmin Connect; auto-detection may later overwrite if not locked in device settings

Practical approach: run a 30-min field test. Compare to Garmin LT. If within 5 sec/km and 3 bpm, use Garmin for convenience and re-check quarterly. If offset exceeds 10 sec/km or 5 bpm, manually enter field test values into Connect and into the HR Zones Calculator. For LTHR vs max-HR zone models, read Zone 2: LTHR vs Max HR.

COROS and Other Platform LT Estimates

COROS EvoLab estimates lactate threshold similarly — pace and HR from detected threshold segments and race performances. COROS offers a structured track test in-app (1000m intervals escalating until failure) that some runners find more repeatable than free-form 30-min efforts.

Independent comparisons show COROS and Garmin LT estimates converge for the same athlete when fed the same training — differences are more often protocol and data quality than brand superiority. COROS may update less aggressively between sparse hard sessions; Garmin may jump after a single parkrun PR. Neither replaces a deliberate test before a race build.

Apple Watch, Polar, and Suunto use comparable pace-HR regression models. Treat all auto-LT values as hypotheses to validate, not ground truth.

Field Test vs Watch: Decision Matrix

Training at and Around LT

Threshold training improves the pace at which lactate spikes — but dose matters:

• Continuous tempo: 20–40 min at LT pace, once weekly in build phase. Full warm-up and cool-down. HR settles at 95–100% LTHR by minute 10.
• Cruise intervals: 3–4 × 8–10 min at LT − 5 sec/km with 2–3 min jog — same stimulus, lower monotony, easier pacing on tired legs.
• Threshold repeats: 4–5 × 1 km at LT to LT − 5 sec/km, 400m jog — develops repeatability for 10K racing.

Limit threshold volume to one primary session per week for most amateur runners (50 km/week range). Two threshold days produce strong short-term gains and disproportionate fatigue — classic overreach pattern before plateau or injury. Polarized base phases may omit continuous tempo entirely for 4–6 weeks; threshold blocks intensify 8–10 weeks pre-race.

Common LT Testing and Training Mistakes

Starting the test too fast: minute-1 heroics produce minute-25 blow-up; average pace lands above true LT. First 5 minutes should feel almost conservative.

Using wrist HR for LTHR: smooths peaks; LTHR reads 5–8 bpm low. Chest strap or known offset correction required.

Testing on hills or treadmill without correction: incline and belt change metabolic cost; LT pace is not portable without adjustment.

Confusing 10K race pace with LT: for trained runners they are close (within 5–15 sec/km); for beginners a 10K may sit well above MLSS because the race is short. Use race data as a check, not a blind substitute.

Never re-testing: LT pace rises with fitness. Zones stuck at last year's test make easy runs too hard and intervals too easy.

Final Takeaway

Lactate threshold is the highest intensity you can sustain before lactate accumulates faster than you clear it — the anchor for tempo pace, LTHR, and most zone models. A 20–30 minute field test on flat terrain with a chest strap gives you LT pace and LTHR accurate enough for training decisions; lab tests refine further but are not mandatory.

Garmin and COROS auto-detect LT from training history when you feed them clean hard efforts. When watch values disagree with race results or RPE, trust the field test and update manually. Scale easy runs, marathon pace, tempo, and intervals as offsets from LT — not from generic max-HR percentages alone.

→ Tempo run guide · → Calculate HR zones from LTHR

FAQ

How often should I test lactate threshold?

Every 8–12 weeks during active training blocks, after a breakthrough race suggesting fitness changed, or when tempo pace at your current LT feels consistently too easy or too hard for 20+ minutes. During base maintenance with no quality work, LT shifts slowly — one test entering a build phase suffices. Avoid testing when sick, heat-stressed, or within 72 hours of a hard long run.

Is lactate threshold the same as FTP for cyclists?

Conceptually similar — both approximate maximal lactate steady state / one-hour sustainable power. Running LT pace and cycling FTP are not numerically convertible because sport-specific economy differs. Triathletes should test separately on the run and the bike; do not import bike FTP formulas to run pace.

Why does my Garmin LT pace differ from my 10K race pace?

For many trained runners, LT pace is 5–15 sec/km slower than 10K race pace over 40–50 minutes of racing — though shorter 10Ks blur the gap. If Garmin LT is 30+ sec/km slower than 10K pace, the watch may lack recent hard data or mis-detected threshold from noisy HR. If LT equals 10K pace exactly, the estimate may be aggressive. Validate with a 30-min test.

Can I improve lactate threshold without a lab?

Yes. Weekly tempo runs at or slightly below LT pace, threshold intervals, and adequate easy volume raise LT over 6–12 weeks — measurable as faster LT pace or higher LTHR at the same pace in repeat field tests. Strength training and hill work support but do not replace threshold-specific running.