Running FTP calculator

Functional Threshold Power (FTP) is the highest power output you can sustain for approximately one hour. It represents the boundary between sustainable aerobic effort and unsustainable anaerobic accumulation — the intensity above which fatigue accumulates rapidly.

For runners, FTP serves as a performance anchor: it sets the reference point from which all training zones, race pacing targets, and session intensity decisions are derived. A higher FTP means you can run faster at the same relative effort, and it reflects improvements in both aerobic capacity and muscular endurance.

Unlike VO2max, which represents a physiological ceiling, FTP reflects how much of that ceiling you can actually use in sustained performance. Two runners with identical VO2max values can have meaningfully different FTPs depending on lactate threshold, running economy, and training history (Joyner and Coyle).

The gold standard is a maximal one-hour effort, but this is impractical for most runners. The two most common field alternatives are:

20-minute test: After a thorough warm-up (15-20 minutes including strides), run as hard as you can sustain for 20 minutes on a flat course. FTP is estimated as 95% of the average power. This test is widely used but requires disciplined pacing — starting too fast inflates the average and overestimates FTP.

30-minute test: Same protocol but held for 30 minutes. The longer duration reduces the correction factor needed and often produces more stable estimates. Average power from a well-paced 30-minute effort closely approximates FTP directly.

Race-result method: If you have a recent race result (within 4-8 weeks), the calculator can derive FTP from race pace and duration using intensity-duration relationships. This avoids a dedicated test session but assumes the race was a true maximal effort.

FTP structures your entire training week by defining intensity zones. The key zones for running are:

Easy/recovery (below 75% FTP): Most of your weekly volume should be here. This builds aerobic base without excessive fatigue. Easy running should feel genuinely comfortable.

Tempo (75-90% FTP): Sustained efforts in this range build muscular endurance and fatigue resistance. Marathon pace typically falls here for competitive runners.

Threshold (90-105% FTP): The zone that directly improves FTP itself. Cruise intervals (e.g., 3-4 x 10 min at threshold with 2 min recovery) are the primary training stimulus here (Buchheit and Laursen).

VO2max (105-120% FTP): Short intense intervals (3-5 min efforts) that develop maximal aerobic capacity. Use sparingly — 1-2 sessions per week maximum.

A well-structured training week typically follows a polarized or pyramidal distribution: 75-80% easy, 10-15% tempo/threshold, and 5-10% high intensity.

These three metrics are interconnected but measure different things. VO2max is the maximum oxygen your body can process — the ceiling of aerobic capacity. Lactate threshold is the intensity at which lactate production exceeds clearance — the sustainable effort boundary. FTP is the practical field expression of that threshold in watts.

Elite runners typically sustain FTP at 85-90% of VO2max, while recreational runners may only sustain 70-80%. This gap explains why two runners with similar VO2max can perform very differently in races: the one with a higher FTP-to-VO2max ratio uses more of their aerobic ceiling for sustained performance (Faude et al.).

Training that improves FTP often targets the lactate threshold directly through tempo and threshold-pace work. Training that improves VO2max uses shorter, more intense intervals. Both contribute to overall endurance performance, but for most runners, improving FTP has the largest impact on race times at 10K and beyond.

Running FTP is a threshold-style field estimate. It helps organize intensity zones and pacing decisions around a reproducible effort anchor.

It is not a direct laboratory diagnosis. Endurance performance still depends on economy, threshold durability, and execution context (Joyner and Coyle).

CP is a formal model construct from the power-duration relationship. FTP is a practical threshold proxy used in training systems. In running practice they are often treated similarly, but their derivation methods differ (Poole et al.).

The projections table supports two behaviors. Non-race methods use FTP intensity bands for all distances. Race-result mode keeps your entered distance/time exact and projects the remaining rows from the anchor.

Each race row includes a target watts band from the model's FTP percentage range. Use it as a pacing guardrail, then adjust by course profile, wind, and heat on race day.

For threshold and interval planning, combine watts with perceived effort and session quality checks rather than forcing one absolute number every day (Buchheit and Laursen).

Running and cycling thresholds are not interchangeable. Both should be tested in their own movement context. Use this page only for running-specific zones and pacing decisions.

Avoid setting zones from one noisy workout. Use representative tests, recheck every few weeks, and keep weather/terrain in mind before updating all training intensities.

VO2max shown on this page is a rough model-derived context value, not a laboratory measurement (Faude et al.; Daniels).