FTP vs lactate threshold: what’s the difference?

Cyclists often use FTP and lactate threshold as if they’re the same. They’re related, but not identical—and knowing the difference helps you test smarter, set better training zones, and pace efforts with fewer surprises on race day.

Quick take: FTP is a field-based estimate of your highest sustainable power. Lactate threshold (especially MLSS) is a lab-derived physiological anchor. They should rhyme, but they won’t always match.

Definitions that matter

Here’s how the main terms fit together:

• FTP (functional threshold power): The highest power you can sustain steadily for a prolonged period, often approximated by a 40–60 minute effort. It’s a practical, field-friendly anchor to set training zones and pace efforts in watts.
• Lactate threshold: A physiological concept measured via blood lactate or gas exchange in the lab. Two common breakpoints:
  • LT1 (aerobic threshold): The first rise in lactate/ventilation above baseline. Good anchor for endurance intensity.
  • LT2 (anaerobic threshold/OBLA): A higher breakpoint associated with the onset of sustained lactate accumulation.
• MLSS (maximal lactate steady state): The highest power at which lactate remains stable (no rise >1 mmol/L between 10–30 min). This is the best lab analogue to the power you can hold for a long, hard TT.
• CP (critical power): A model-based endurance threshold derived from multiple maximal efforts. CP is the asymptote of your power–duration curve; efforts above CP draw on a finite battery (W′). CP often sits near, but can be slightly above, MLSS/FTP for some riders.

Rule of thumb: FTP ≈ MLSS ≈ CP for many athletes, but individual differences, protocols, heat, altitude, and fatigue can shift these by several watts.

Lab testing: lactate and gas exchange

Lab testing pinpoints physiological thresholds to guide training.

Typical protocols

• Graded lactate step test: 3–5 minute stages, increasing watts each step, with finger-prick lactate. Identifies LT1 and LT2 via lactate and ventilation changes.
• MLSS testing: Several constant-load efforts of 20–30 minutes on separate days or with long recoveries. The highest power where lactate stays stable is your MLSS.
• Gas exchange test: Measures ventilatory thresholds (VT1/VT2) via breathing data. Often aligns with LT1/LT2.

Pros

• Physiologically specific: You learn exactly where steady-state breaks down.
• Great for individualization: Useful when heart rate or RPE don’t match power, or after illness/injury.
• Early sensitivity: LT1/LT2 can shift before big changes in FTP are obvious.

Cons

• Access and cost: Requires a lab, calibrated analyzers, and experienced staff.
• Protocol variability: Different criteria can produce different “thresholds.”
• Transfer to road: Indoor ergometer values can read lower than outdoor power; temperature and position matter.

How to use lab results

• Set endurance work near HR and watts at LT1 (easy aerobic rides, base miles).
• Set threshold work at or just below MLSS/LT2 (95–100% of MLSS for 2×15–30 min, or 3×12–20 min).
• Monitor changes: Rising LT1 (at same HR) and stable MLSS at higher watts indicate improved efficiency and durability.

Field testing: FTP and CP in practice

Field tests are cheap, repeatable, and specific to your bike and roads.

Common protocols

• 40–60 minute TT: Gold standard for practical FTP. Warm up well, choose a steady climb/loop, pace evenly.
• 20 minute test: Maximal 20 min; FTP ≈ 0.95 × 20 min average power. The 0.95 factor is only a rough guess—some riders need 0.90–0.98.
• CP testing: Two or three maximal efforts on separate days (e.g., 3–5 min and 12–20 min). Use a CP calculator to get CP and W′.

Pros

• Specificity: Same position, crank, and conditions you race in.
• Frequency: Retest every 6–8 weeks, or after a training block.
• Actionable: Instantly updates watts for training zones and pacing.

Cons

• Pacing errors: Go out too hard and you’ll under-read FTP.
• Conditions matter: Heat, altitude, wind, and fatigue can shift outcomes by several percent.
• Single-number trap: FTP hides useful detail like W′ and time to exhaustion.

Make field tests more reliable

• Use steady terrain and similar environmental conditions when possible.
• Calibrate your power meter and keep tire pressure and drivetrain clean.
• Repeat the same protocol so changes reflect fitness, not noise.

How each metric guides your training

Setting training zones

Choose one anchor (FTP, MLSS, or CP) and be consistent. Example using FTP:

• Endurance (Z2): 60–70% of FTP. Conversational, minimal drift.
• Tempo: 76–88% of FTP. Sturdy aerobic work.
• Sweet spot: 88–94% of FTP. Time-efficient stimulus with manageable fatigue.
• Threshold: 95–100% of FTP. Classic 2×20, 3×12–16 min sessions.
• VO2max: 106–120% of FTP. 4–6×3–5 min with equal recovery.

Using CP is similar: set zones relative to CP, and use W′ to plan how much >CP work a session includes.

Pacing and fueling

• TTs and climbs ~30–60 min: Target 95–100% of FTP or near MLSS. Start 1–2% conservative for the first quarter.
• Long sportives: Keep most steady riding at or below LT1/upper Z2 to spare glycogen.
• Fueling: Endurance rides 40–60 g carbs/hour; tempo–threshold 60–90 g/hour; high-intensity 80–100+ g/hour if gut-trained. Hydrate to conditions.

Recovery and readiness

• Watch heart rate–power decoupling: If HR rises >5% relative to watts in Z2, back off or shorten the ride.
• Use RPE alongside numbers. If threshold feels like VO2max, you’re not ready to test or to hold MLSS.
• Schedule deloads every 3–4 weeks and retest after easier days, not after a smash-fest.

Making lab and field agree in the real world

• Map lab to road: After an MLSS result, do a 30–40 minute outdoor TT. If you can’t steady-state at MLSS watts, set training at the lower of the two until durability improves.
• Environment counts: Heat and altitude reduce sustainable watts; indoor power can be 2–5% lower than well-cooled outdoor efforts. Adjust targets accordingly.
• Retest rhythm: Field test every 6–8 weeks; lab every 8–16 weeks or when something feels off.

Quick decision guide

• Choose lab testing if you want precise thresholds, have plateaued, are returning from illness, or need health screening.
• Choose field testing if you need frequent, low-cost updates, and you race outdoors in variable conditions.
• Combine both to anchor physiology in the lab and execution on the road.

Sample 8-week block to raise both FTP and lactate threshold

Use your current FTP/MLSS/CP to scale.

• Weeks 1–2 (base + tempo): 2–3 endurance rides (60–70% FTP), 1–2 tempo sessions (3×15–20 min at 80–88% FTP), long ride in Z2 with the last 30 min at upper Z2/LT1.
• Weeks 3–4 (threshold focus): 2 threshold sessions per week (e.g., 3×12 min or 2×20 min at 95–100% FTP with 1:1 recovery), plus endurance. Optional sweet spot (3×12 at 90–94%) if fatigue is low.
• Week 5 (deload): Reduce volume by ~30–40%, keep some short strides/openers.
• Weeks 6–7 (VO2/CP lift): 1–2 VO2 sessions (5×3–4 min at 110–120% FTP, full recovery), 1 threshold or sweet spot session, endurance around LT1.
• Week 8 (tune + test): Easy early week, then a 40–60 min TT or CP tests to update numbers. Adjust zones and plan the next block.

Expect small but meaningful shifts: a rise in LT1 power and reduced HR at endurance pace, slightly higher MLSS/FTP, and better tolerance of near-threshold work.

Bottom line: Use lab metrics to understand the “why” and field metrics to nail the “how.” When FTP, MLSS, and CP tell a consistent story, your training zones, pacing, and recovery choices become much clearer—and your results follow.