FTP Calculator

Functional Threshold Power (FTP) is a practical estimate of the highest power you can sustain in a quasi-steady state for about one hour. It is not a perfect biological marker, but it is one of the most useful field anchors for setting training intensity in cycling.

In real training, FTP works best as a planning baseline. It helps you set zone targets, structure interval sessions, and monitor progression across a block. It should not be treated as a fixed identity score or a direct substitute for lab testing. Day-to-day changes in sleep, heat, fueling, and fatigue can move your measured value even when your long-term fitness is stable.

The most reliable use pattern is repeatability. Use the same protocol, similar warm-up style, and similar environmental conditions when possible. That consistency improves trend quality and reduces noise, especially when you compare values month to month instead of reacting to one isolated test day.

Different testing formats estimate FTP from efforts with different physiological demands. A 20-minute test typically uses a 95% multiplier, while 2x8-minute, 5-minute, and ramp formats use different correction factors. Those methods are useful but not interchangeable by default, and each introduces different error sources.

Longer tests generally reduce uncertainty from short-duration anaerobic contribution, while shorter tests can be more sensitive to pacing errors and individual physiology. Ramp-based methods are fast and practical, but they can overestimate or underestimate threshold in riders whose anaerobic profile is far from average.

Because of those differences, protocol consistency matters as much as protocol choice. If you switch protocols every month, it becomes hard to tell whether your change came from adaptation or from method variation. Pick a method you can execute well, then repeat it with discipline.

The calculator applies common protocol multipliers used in cycling practice. These are coaching estimates designed for field usability. They are useful only when the underlying test is maximal, paced correctly, and performed under repeatable conditions.

If you see large jumps between methods, do not assume immediate fitness change. First check pacing, freshness, and method differences. Then compare results over several tests before adjusting your block targets.

W/kg is useful because it normalizes power to body mass and helps compare riders, especially for climbing-oriented performance. But it should be read together with absolute power. On flat courses at higher speed, aerodynamics and absolute watts often matter as much as or more than W/kg.

This is why category labels are context labels, not judgments. The same W/kg can lead to different race outcomes depending on terrain, drafting, tactical demands, and event duration. Use category outputs to orient your training, not to overfit your identity to one number.

For better interpretation, combine W/kg trend with workout completion quality, heart-rate response, and recovery markers. If W/kg increases but session durability worsens, the adaptation may not yet be race-ready.

TSS is often misunderstood because riders enter average power when the model expects Normalized Power (NP). NP captures variable effort cost better than average power, so using average power can understate the strain of stochastic rides.

This calculator explicitly labels NP and uses standard IF and TSS logic. IF compares session intensity to FTP. TSS then combines intensity and duration so two rides of different lengths can be compared on one workload scale.

Use TSS for load planning, not in isolation. A high score can be appropriate in race-prep weeks and inappropriate in recovery weeks. Context from your mesocycle always matters.

Sweet Spot work is commonly programmed around 88 to 94% of FTP. The range is popular because it can deliver meaningful aerobic and muscular stimulus while remaining more repeatable than frequent threshold-max sessions.

Sweet Spot is not a magic zone, and it should not replace endurance volume, recovery rides, or high-intensity work. Its value is operational: you can accumulate quality work with manageable fatigue when periodized correctly.

In practice, use the calculated range as a starting point, then refine by RPE, heart-rate drift, and completion quality. If multiple sessions feel unsustainably hard at the prescribed range, update FTP assumptions before increasing volume.

Scenario: Rider completes a 20-minute test at 250 W, body mass 70 kg. Estimated FTP is 238 W, W/kg is 3.40, and Sweet Spot is 209 to 224 W. If the rider logs NP 200 W for 60 minutes, IF is 0.84 and TSS is 71. This is a moderate session load that usually fits within a build week when recovery is managed.

How to apply this: schedule one threshold-focused day (Zone 4), one Sweet Spot day, and at least one endurance day with controlled intensity. Keep hard days separated by easier riding or complete recovery depending on fatigue response.

After two to four weeks, retest using the same method and compare both numbers and execution quality. If FTP rises but interval completion quality drops sharply, hold progression and check fueling, sleep, and cumulative stress before increasing intensity again.

Most FTP planning mistakes are process errors. Common examples are comparing different test formats as if they are identical, using average power in a model that expects NP, and changing FTP too often based on one hard or one easy day. These mistakes create training noise and make progression harder to read.

Before changing your zones, run a short quality check: was the test maximal, was pacing controlled, was the warm-up comparable, and did external conditions differ substantially from previous tests? If those checks are weak, treat the result as provisional.

For the same reason, avoid over-precise language in coaching decisions. A one- to two-watt difference is usually less meaningful than adherence quality, recovery consistency, and the ability to complete target sessions with good form.