What Functional Threshold Power means, how to test it, and how to use FTP zones in cycling training without treating one number as absolute truth.
FTP is a practical estimate of sustainable cycling power. Use it to set power zones and track progress, but keep the full training context in view.
FTP is useful, but it does not describe everything. Durability, sprint power, VO2max, technique, fuelling, and recovery still matter.
Functional Threshold Power (FTP) is a practical power anchor for structured cycling training. It helps set power zones, choose realistic targets, and track whether your sustainable riding power is changing over time.
The value of FTP is that it gives cycling intensity a stable reference. Speed changes with wind, surface, drafting, and gradient; power gives a cleaner view of the work you are producing.
This article explains what FTP means, how to test it, how to turn it into training zones, how often to update it, and how to avoid the common mistakes that make FTP-based training less useful.
FTP, or Functional Threshold Power, is an estimate of the highest average power you can hold for a long, hard, controlled effort. It is often described as roughly one-hour power, but in real athletes the exact duration can be shorter or longer depending on testing method, fatigue resistance, and training history.
FTP is related to threshold physiology, but it is not the same as a laboratory lactate threshold. A 20-minute test with a correction factor, a ramp test, a long steady effort, and an automatic platform estimate can all produce slightly different numbers. For training, the goal is not a perfect laboratory value; it is a repeatable working estimate that makes workout targets fit the intended effort.
FTP gives power-based training a clear reference point. Instead of guessing whether a ride is easy, tempo, sweet spot, threshold, or above threshold, you can connect the target watts to your current ability. That makes interval sessions easier to prescribe, easier to repeat, and easier to adjust when fitness changes.
FTP is still only one marker of cycling fitness. It does not fully describe sprint power, VO2max, durability after several hours, handling skill, climbing position, nutrition, or race tactics. A higher FTP is useful, but the trend is more meaningful when it matches better workout quality, better recovery, and better riding performance.
Around FTP, aerobic energy production does most of the work, with an important anaerobic contribution. Lactate production and clearance are both high, breathing is heavy, and the effort is hard but still organised. Heart rate and blood lactate values differ between athletes, so fixed numbers such as 4 mmol/L or a single heart-rate percentage should not be treated as universal boundaries.
Training near FTP can improve sustainable aerobic power, lactate transport and use, mitochondrial function, and tolerance for long controlled efforts. Those adaptations are trainable, but they depend on consistency, recovery, total programme design, genetics, age, and training background. FTP is therefore a useful guide, not a guarantee of one specific adaptation timeline.
FTP is used to turn cycling intensity into zones. For example, endurance rides often sit well below FTP, tempo rides are moderately hard, sweet spot sits just below threshold, threshold intervals sit around FTP, and VO2max intervals sit clearly above it. The percentages give structure, while perceived effort and execution quality tell you whether the target is realistic today.
This is why power-based plans use FTP as a central setting. The same 250-watt interval can be easy for one rider and impossible for another. Expressing the workout as a percentage of FTP makes the prescription relative to the rider. It is still normal to adjust for heat, fatigue, altitude, indoor cooling, illness, and day-to-day readiness.
Most cycling power-zone systems are built from FTP. Exact boundaries vary by model, but a common structure looks like this:
These zones are practical ranges, not clean biological boxes. Sweet spot overlaps tempo and threshold, and different riders may feel the same percentage differently. Use the zones to guide the session, then check breathing, cadence, repeat quality, and recovery to confirm that the workout is doing what it is supposed to do.
Update FTP when fitness has clearly changed or when your workout targets no longer match the intended effort. Testing every four to eight weeks can be useful during a focused training block, but it is not a rule. A small change in form does not always need an immediate retest.
Consistency matters more than constant testing. Compare tests in similar conditions, with similar equipment, similar cooling, and similar fatigue. If threshold intervals become impossible for several sessions in a row, your FTP may be set too high. If every hard session feels suspiciously easy, it may be too low. Formal tests, recent best efforts, and automatic estimates are all signals, not final truth.
There are several ways to estimate FTP. Each has trade-offs between repeatability, pacing skill, mental load, and how well it matches your real riding:
No single protocol is perfect for everyone. The best test is the one you can repeat honestly under similar conditions and then use to set training that feels right. Switching methods every time makes trends harder to interpret.
A classic 20-minute FTP test is simple, but it should be done rested and with a clear pacing plan:
The hardest part is pacing. Starting too hard usually gives a lower average by the end; starting too cautiously can leave power unused. Indoor testing is easier to standardise, while outdoor testing may feel more specific. Use the same environment when you want clean comparisons over time.
Once you have a current FTP estimate, use it as a practical training reference:
FTP should guide training, not dominate it. If you are tired, overheated, sick, under-fuelled, or riding in poor cooling indoors, the correct target may need to come down. If the workout goal is technique, cadence, recovery, or long aerobic volume, hitting an exact watt number is less important than completing the session well.
Most FTP problems come from treating one number as more exact than it really is:
Watts per kilogram depends on sex, age, body mass, equipment, testing method, and training background. Tables can give context, but they are not personal targets. On flat terrain, absolute power often matters more; on climbs, W/kg becomes more important. Your own trend is usually more useful than a rating chart.
Beginners may improve quickly, while experienced cyclists often improve more slowly. Fixed yearly percentages are unreliable because progress depends on starting level, consistency, recovery, training design, body-mass changes, and how FTP is tested.
Indoors is easier to standardise, especially for cooling, traffic, terrain, and uninterrupted effort. Outdoors may better match real riding position and motivation. Neither is automatically better for everyone. Use the same environment when you want comparable trends.
Yes. FTP can rise during a build phase, dip during illness or a break, and stabilise during maintenance. A small change is normal. A large change should be checked against fatigue, testing conditions, equipment calibration, and recent training history.
Training Stress Score (TSS) uses FTP to estimate the load of a cycling session. In the common model, 60 minutes at FTP equals 100 TSS. This is useful for comparing sessions, but it does not mean two rides with the same TSS create the same fatigue or adaptation.
Metrics such as ATL, CTL, and ramp rate are modelled summaries, not direct measurements of readiness. If FTP is wrong, the model becomes distorted. Even when FTP is accurate, sleep, nutrition, stress, illness, heat, and muscle soreness still matter.
FTP is one of the most useful numbers in cycling because it turns power into workable training zones. It helps you set targets, compare sessions, and notice when your sustainable output is changing.
But FTP is an estimate, not an identity. Use it together with perceived effort, heart rate, workout quality, recovery, and the demands of your event. A realistic FTP makes training clearer; an inflated or outdated FTP makes training noisier.
Use Endurly to build structured cycling sessions around your current FTP, training goal, and available time.
Get Started Free