Functional Threshold Power demystified — what it means and how to use it in training
Functional Threshold Power (FTP) is the most important single number in modern cycling training. It's the cornerstone metric that defines your training zones, anchors your workout targets, tracks your fitness over time, and gives you a precise, objective measure of cycling performance that's independent of terrain, weather, or even whether you're indoors or out. Understanding FTP — what it is, how it's measured, how to use it, and how to update it as fitness changes — is fundamental to structured cycling training, whether you're racing criteriums, targeting a century, or just trying to get faster on your weekend rides. This guide walks through exactly what FTP means physiologically, why it matters for training, how to measure it accurately, how to translate it into training zones, how to use those zones to design productive workouts, how often to retest, and the common mistakes that cost athletes months of training productivity. By the end, you'll know exactly how to build your cycling training around this single powerful metric. For cyclists coming from running or triathlon backgrounds, think of FTP as the cycling equivalent of lactate threshold pace — a reference intensity anchoring training structure and fitness tracking across every other workout type.
FTP, or Functional Threshold Power, is defined as the highest average power output (in watts) that you can sustain for approximately one hour in a time-trial effort. It represents the boundary between sub-threshold aerobic work and supra-threshold anaerobic territory — the pace at which lactate production begins exceeding lactate clearance, meaning effort becomes progressively harder to sustain. Measured in watts and typically expressed as watts per kilogram of body weight (W/kg), FTP is the single most important training metric a cyclist has.
FTP defines your training zones and helps structure workouts based on your current fitness level. Without a reliable FTP, every training decision is a guess: how hard is a tempo effort? How much power should sweet spot target? When is an interval above threshold rather than at it? FTP turns these questions from subjective judgments into precise numerical targets, and that precision is what makes structured cycling training so much more effective than riding by feel alone.
FTP is used to define training zones and structure workouts with precision. By working at specific percentages of your FTP, you can target different physiological systems with dialed-in accuracy: Zone 2 at 56–75% for aerobic base; sweet spot at 84–97% for efficient threshold development; Zone 4/threshold at 95–105% for lactate threshold; VO2max at 106–120% for top-end aerobic power; anaerobic at 121%+ for capacity above threshold.
For example, sweet spot training is typically performed at around 85–95 percent of FTP, while threshold intervals are closer to 95–105 percent, and VO2max work sits at 110–120 percent. Each of these targets produces distinct adaptations, and using FTP-based percentages lets you hit the intended stimulus with far more precision than subjective effort alone would allow. This is why every serious cycling training platform — TrainerRoad, Zwift, Sufferfest, TrainingPeaks — builds its workouts around FTP percentages. An athlete with an accurate FTP can execute a prescribed workout precisely, producing exactly the intended stimulus. An athlete without accurate FTP can do the same workout and produce a completely different physiological response, because the effort they're putting out maps to a different zone than the workout targets.
As your fitness improves, your FTP changes. Regular testing — typically every 4–8 weeks during active training — ensures your training zones remain accurate. Using outdated values can lead to training that's either too easy (FTP set too low) or unsustainably hard (FTP set too high). Either failure mode compromises adaptation: too-easy training produces no stimulus; too-hard training produces overreach.
Consistency in testing and training helps track progress and ensures workouts stay aligned with current performance. A reasonable schedule: test at the start of a training block, retest after 4–6 weeks, and retest again before the next block begins. More frequent testing isn't usually necessary, and less frequent testing means some of your training is built on increasingly inaccurate numbers. If workout feedback consistently suggests your FTP is wrong — struggling to finish prescribed intervals, or sessions feeling suspiciously easy — retest immediately rather than waiting for the scheduled date. Modern cycling platforms also offer algorithmic FTP detection based on training data rather than formal tests, which can be a useful secondary signal but should be validated against an actual test at least twice a year.
Endurly generates structured cycling workouts based on your FTP and training goals — with zones, progressions, and retest scheduling built in.
Get Started Free