Functional threshold power is only useful if you measure it accurately. Use the wrong test for your current fitness level, recovery state, or psychological makeup and you will either inflate your FTP, loading every subsequent workout with intensity you cannot sustain, or underestimate it, leaving weeks of training stuck in zones that do not stress the adaptations you are chasing.
Three field protocols dominate how cyclists and triathletes test FTP outside a laboratory: the ramp test, the 20-minute test, and the 8-minute test. Each one estimates the same underlying physiological ceiling, the highest power output you can maintain at a metabolic steady state, but they do it through fundamentally different mechanisms, and they are not interchangeable.
This article breaks down how each protocol works, what the numbers actually represent, who each test suits, and how to choose between them.
What FTP Actually Measures
Before comparing protocols, it helps to be precise about the target. FTP is commonly defined as the highest average power you can sustain for approximately sixty minutes. In practice, most athletes cannot execute a maximal sixty-minute effort in training, the physical and motivational demand is too high, and the recovery cost is enormous.
Field protocols sidestep this by using shorter, more reproducible efforts and applying correction factors to estimate the sixty-minute ceiling. The correction factors are derived empirically, not from first principles, which is one reason different protocols can produce meaningfully different numbers for the same athlete on the same day.
FTP sits close to the second lactate threshold, the intensity at which blood lactate accumulation begins to exceed clearance capacity. It is not identical to VT2 or MLSS (maximal lactate steady state), though those concepts are closely related. For practical training purposes, FTP defines the boundary between sustainable high intensity and unsustainable glycolytic work, which is why it anchors zone structures across virtually every endurance training framework.
The Ramp Test
How It Works
The ramp test is a maximal incremental effort. You start at a low power output, typically around 50–60% of your estimated FTP, and increase by a fixed amount every minute (commonly 20W, though variations exist). You ride until you can no longer maintain the target power, then stop.
Your FTP is estimated at 75% of your best one-minute power. If your best minute averaged 320W, the formula returns an FTP of 240W.
The 75% coefficient is the result of population-level averaging. It works reasonably well for athletes whose physiology sits near the middle of the distribution, and less well for those at the extremes.
What the Test Stresses
The ramp test is primarily a test of aerobic power and VO₂max-adjacent capacity. Because power increases continuously without a sustained moderate effort prior, the protocol rewards athletes with high aerobic ceilings relative to their threshold. Riders with a large VO₂max-to-FTP gap, often those newer to structured training or those with naturally high aerobic capacity, tend to record ramp test numbers that overestimate their actual FTP.
Conversely, athletes who are specifically adapted to sustained threshold efforts — experienced time trialists, Ironman-focused triathletes — often find the ramp test underestimates their true threshold because their strength lies in metabolic efficiency over duration rather than peak aerobic output over one minute.
Pros
The ramp test is the most athlete-friendly protocol. It requires no pacing judgment. You simply ride until you cannot, which eliminates the single largest source of error in longer tests: going out too hard or too conservatively. It is also lower in recovery cost than a true maximal sustained effort, making it practical to repeat more frequently.
Cons
The 75% coefficient is a population average, not a personal constant. Athletes with high VO₂max relative to FTP can see FTP inflated by 8–12%; athletes with high fractional utilization can see it deflated. The test also does not train the neuromuscular and psychological capacity for sustained threshold work, which some coaches argue is itself a reason to use a longer protocol at least periodically.
The 20-Minute Test
How It Works
The 20-minute test is the closest field approximation to the true sixty-minute FTP effort. After a structured warm-up that includes a five-minute hard blowout effort to clear fast-twitch muscle fatigue, you ride as hard as you can sustain for exactly twenty minutes. FTP is calculated as 95% of your average power for that effort.
The 5% discount accounts for the difference in maximal sustainable power over twenty minutes versus sixty — on average, athletes can produce approximately 5% more power at twenty minutes than at sixty, though the spread around this average is wide.
What the Test Stresses
The 20-minute test is a direct test of threshold capacity. It requires you to hold near-maximal sustainable power continuously, which demands precise pacing, pain tolerance, and the specific physiological adaptations — mitochondrial density, lactate clearance, slow-twitch motor unit recruitment, that FTP training is designed to develop.
This is both the test's strength and its primary challenge: it demands exactly the qualities it is trying to measure. Athletes who are poorly rested, under-fueled, or who have not practiced threshold efforts will execute the test poorly, producing an FTP estimate that underrepresents their actual fitness.
Pros
The 20-minute test is the most valid field protocol for athletes who have threshold-specific training history. When executed well, it correlates closely with laboratory MLSS measurements and produces FTP numbers that are directly usable for time trial pacing, triathlon ride segments, and threshold interval prescription. It also closely simulates the demands of a 40km time trial, making it inherently sport-specific for cycling.
Cons
Pacing is genuinely difficult, especially for athletes without experience in sustained maximal efforts. Starting ten to fifteen watts too hard in the first five minutes will cause premature lactate accumulation that cannot be reversed, collapsing the second half of the effort. The test also carries meaningful recovery cost — especially the five-minute blowout that precedes it, which limits how frequently it can be performed without disrupting training continuity.
The 8-Minute Test
How It Works
The 8-minute protocol addresses the pacing difficulty of the 20-minute test by shortening the sustained effort but performing it twice. After a warm-up, you complete two maximal 8-minute efforts separated by ten minutes of easy recovery. FTP is estimated at 90% of the average of the two best 8-minute average power figures.
Some coaches use 90% of only the best of the two efforts. The two-effort version is generally more conservative and arguably more reliable, since the second effort under partial fatigue provides a more reproducible signal.
What the Test Stresses
Like the 20-minute test, the 8-minute protocol targets threshold capacity directly, but the shorter duration means it sits at a higher relative intensity, closer to the VO₂max zone. The 90% correction is larger than the 20-minute test's 5% discount, which reflects how much more power athletes can sustain for 8 minutes versus 60. The accuracy of this correction is similarly variable across individual athletes.
Pros
The 8-minute format is more psychologically approachable than a single 20-minute effort. Knowing the effort ends in under ten minutes makes it easier to commit fully, particularly for less experienced athletes. The dual-effort structure also provides a built-in quality check: if the two power figures diverge significantly, pacing or fatigue issues can be identified.
Cons
The protocol produces the loosest estimate of the three. The 90% correction factor assumes a standard aerobic profile; athletes with high anaerobic capacity will overestimate FTP, sometimes significantly. The 8-minute duration also introduces more variability from wind, road gradient (on a non-controlled outdoor course), and momentary power fluctuations. For precise zone calibration, particularly in a data-driven training environment, the 20-minute test or ramp test typically produces more reliable inputs.
Side-by-Side Comparison
| Ramp Test | 20-Minute Test | 8-Minute Test | |
|---|---|---|---|
| Duration | 15–25 min (varies with fitness) | ~45 min (warm-up included) | ~55 min (warm-up + recovery) |
| FTP Coefficient | 75% of best 1-min power | 95% of 20-min average | 90% of 8-min average |
| Pacing Required | None | High | Moderate |
| Recovery Cost | Low | High | Moderate |
| Best For | Beginners, frequent retesting | Experienced athletes, time trialists | Athletes uncomfortable with 20-min |
| Main Weakness | Overestimates for high VO₂max athletes | Pacing errors collapse accuracy | Loosest estimate of the three |
| Repeatability | High | Moderate | Moderate |
Which Test Should You Use?
The honest answer is that the best test is the one you can execute consistently and honestly over multiple testing cycles. Precision in a single test matters less than comparability between tests — what you want is a reliable signal of whether fitness is improving, and for that you need a protocol you run the same way every time.
That said, certain profiles suit certain tests.
If you are new to structured training or returning from a significant break, the ramp test is the practical starting point. The absence of pacing judgment removes the most common source of error, and the lower recovery cost means a bad execution does not cost a week of quality training.
If you have consistent threshold training history and want the most valid FTP number — particularly for time trial pacing or Ironman bike segment planning, the 20-minute test is the most appropriate protocol. Run it with the full warm-up, take the five-minute blowout seriously, and treat the pacing of the sustained effort as a skill in itself.
If you find the 20-minute test psychologically difficult to execute well, or if you are training in a context where outdoor gradient variability makes sustained power hard to control, the 8-minute test offers a workable alternative, with the understanding that the estimate is slightly less precise.
One practical note: if you use a smart trainer and a platform that offers automated ramp test protocols, the ramp test's accuracy improves meaningfully in that environment. Controlled resistance eliminates the pacing variable almost entirely, and the reproducibility becomes genuinely high.
How Often Should You Test FTP?
Testing FTP too frequently adds recovery cost without proportional information gain. Most periodized training blocks run four to eight weeks before FTP is likely to have shifted meaningfully. A practical cadence is once per training block, roughly every four to six weeks, timed to coincide with a scheduled rest week so the test does not disrupt loading weeks.
After significant illness, a prolonged break, or a major race, an FTP retest is warranted regardless of schedule. Zones calibrated to a fitness level you no longer hold are either undertrained (if fitness declined) or overtrained (if fitness improved), neither of which serves adaptation.
FTP Test Protocols Compared
Three protocols. One number. Very different paths.
Best 1-min power × 75%
Best for: beginners, frequent retesting, smart trainers
20-min average power × 95%
Best for: experienced athletes, time trialists, Ironman prep
Avg of 2 × 8-min efforts × 90%
Best for: athletes who struggle to pace 20-min sustained efforts
Frequently Asked Questions
Does it matter whether I test indoors or outdoors?
For consistency, it matters significantly. Outdoor testing introduces variables, wind, gradient, pacing errors on variable terrain, that inflate test-to-test noise. If you train primarily with power indoors, test indoors. If you race and train outdoors, an outdoor test on a controlled course provides more sport-specific data. The key is consistency: pick one environment and use it every time.
Why does my ramp test FTP feel too high for my threshold intervals?
This is one of the most common complaints with the ramp test and usually signals that your VO₂max-to-FTP ratio is high, the ramp rewards aerobic ceiling more than threshold economy. If you consistently cannot hold your ramp-test-derived FTP for 20-minute intervals, discount it by 3-5% and monitor whether workout completion improves.
Can I use heart rate instead of power for FTP testing?
Heart rate-based FTP estimation is significantly less precise. Heart rate drifts with temperature, hydration, fatigue, and caffeine, and lacks the direct mechanical specificity of power. If power is unavailable, heart rate at threshold (LTHR, lactate threshold heart rate) can be estimated from a similar protocol, but it should be treated as a rough guide rather than a precise zone anchor.
How do I know if I've set up my warm-up correctly for the 20-minute test?
The five-minute blowout effort before the 20-minute test is not optional — it clears residual aerobic inhibition and primes the physiological systems you will rely on during the test. It should be genuinely hard: 110–120% of your expected FTP. Follow it with at least five minutes of easy spinning before beginning the 20-minute effort.
Should I use the same FTP for running and cycling?
No. FTP is modality-specific. Cycling FTP and running threshold pace reflect the same underlying concept, sustainable intensity at lactate threshold, but the specific neuromuscular recruitment patterns, muscle mass engaged, and efficiency factors differ between disciplines. Test and calibrate each separately, particularly if you are a triathlete managing multiple sport-specific training zones.