Knowing your FTP matters only as much as the test you used to find it. A poorly executed protocol — or the wrong protocol for your physiology — produces a number that misaligns every training zone you build from it. This chapter covers the three most widely used FTP test formats, explains the physiology behind each, and gives you a repeatable execution process for all of them.

Why Protocol Choice Matters

FTP is defined as the highest average power you can sustain for roughly sixty minutes. No protocol measures that directly — each one estimates it through a shorter, harder effort and applies a correction factor or curve-fitting logic. The correction factor is not universal. Different riders express power differently across durations, so the protocol that gives one athlete an accurate estimate can overestimate or underestimate for another.

Choose a protocol based on:

Your training history. New riders often lack the pacing discipline for long efforts.
Your power-duration curve shape. Riders with a strong sprint and high anaerobic capacity tend to inflate ramp test results.
Your testing goals. Frequent re-testing favors low-fatigue protocols. Annual benchmarking favors accuracy over convenience.
Available equipment. All three protocols work on a smart trainer or power meter. Avoid testing outdoors unless you have a flat, traffic-free course and reliable power data.

The Ramp Test

How It Works

The ramp test uses a stepped protocol: power increases by a fixed increment — typically every minute — until you cannot complete a full step. Your peak one-minute power is then used to calculate estimated FTP, most commonly by multiplying it by a set factor (often around 0.75, though this varies by platform).

The logic is that your one-minute peak in an all-out, fully-depleted state correlates predictably with sustained aerobic power. The test is largely self-pacing-free: you simply hold each step until you cannot.

Execution

Warm up for ten to fifteen minutes, including two or three short accelerations above your expected FTP.
Start the ramp at a low wattage — well below your current FTP estimate.
Hold each step fully. Do not bail early because it feels hard; the test only works if you reach genuine failure.
When you can no longer complete a full step, stop. Record your highest completed one-minute average.
Apply your platform's correction factor, or use the FTP estimator to calculate from peak power.

Who It Suits

The ramp test is the best option for beginners, time-crunched riders, and anyone who struggles to pace a sustained effort accurately. Total test time is typically under thirty minutes including warm-up.

Limitations

Riders with a high anaerobic capacity — a large W' (W-prime) — can push through additional steps on accumulated anaerobic energy rather than aerobic power. This inflates the peak one-minute number and produces an FTP estimate that is too high, leading to zones that feel impossible in training. If you find your prescribed intervals consistently unachievable after a ramp test, this is the likely cause.

The 20-Minute Test

How It Works

Ride as hard as possible, at the most even pace you can sustain, for exactly twenty minutes. Take 95% of that average power as your FTP estimate. The 5% reduction accounts for the fact that twenty minutes is shorter than sixty, and most riders can sustain slightly more power over twenty minutes than they could for a full hour.

This is the most widely referenced protocol in structured training literature and produces accurate results for riders who can pace well.

Execution

Warm up for twenty to thirty minutes. Include a five-minute hard effort at roughly 95–100% of your current FTP estimate, then easy riding for five minutes before the test. The pre-effort depletes glycolytic reserves so the twenty-minute effort is more aerobically representative.
Start the test conservatively. The most common mistake is going out too hard in the first five minutes and dying in the last five. Aim for a power output you can hold negative-split or even-split.
Ride for exactly twenty minutes. Record average power for the full interval.
Multiply average power by 0.95. That is your new FTP estimate.
Cool down for at least ten minutes.

Pacing the Effort

If you have a previous FTP estimate, target roughly 100–105% of it for the first ten minutes, then reassess. If you have no reference, use perceived exertion: the effort should feel like an eight out of ten — very hard but controlled, not a sprint. You should be able to produce complete sentences with difficulty, not comfortably.

Avoid variable power. Surging and recovering wastes energy and inflates your average. A flat course or a trainer set to ERG mode for the warm-up (switched off for the test itself) helps.

Who It Suits

Riders with at least several months of structured training who understand pacing. The 20-minute test rewards athletes who can commit to a hard, steady effort and not fade. It is less suitable for beginners who have no reference point for pacing.

Limitations

The 0.95 correction factor is an average, not a law. If your power-duration curve drops off steeply — meaning you are relatively better at shorter efforts — your actual FTP will be lower than the estimate suggests. If you are a pure diesel engine who barely fades, 0.95 may slightly underestimate your FTP.

The Long-Form 60-Minute Test

How It Works

Ride at maximum sustainable power for sixty minutes. Your average power for the full hour is your FTP — no correction factor needed. This is the most accurate protocol by definition, because it matches the original definition of FTP directly.

Execution

Warm up for fifteen to twenty minutes at easy pace.
Commit to a pacing strategy before you start. If you have a previous FTP estimate, begin at that wattage or slightly below. You can increase if you feel strong after twenty minutes.
Ride for sixty minutes, holding the highest steady power you can sustain without fading significantly in the final ten minutes.
Record average power for the full sixty minutes. That number is your FTP.
Cool down thoroughly — this test is genuinely fatiguing.

Pacing the Effort

Pace conservatively for the first fifteen minutes. The most common error is the same as in the 20-minute test but amplified: early aggression leads to a collapse in the final quarter. A good sixty-minute test should feel progressively harder but never desperate until the last few minutes.

Who It Suits

Experienced riders, racers, and athletes preparing for long events where sustained power accuracy is critical. Also useful for riders who have repeatedly gotten inaccurate results from shorter protocols due to extreme power curve shapes.

Limitations

This test is hard. It requires significant motivation, good pacing skill, and adequate recovery afterward. Most athletes should not run this protocol more than two or three times per year. It is also unsuitable for beginners because the effort is long enough that pacing errors compound significantly.

Comparing the Three Protocols

Protocol	Duration	Correction Factor	Best For
Ramp	15–20 min total	Yes (varies)	Beginners, frequent testing
20-minute	40–55 min total	Yes (×0.95)	Most trained riders
60-minute	75–90 min total	None	Experienced, accuracy-focused

Practical Rules for Any FTP Test

Rest before you test. Run the protocol after at least one full rest day, ideally two. Testing on accumulated fatigue produces a deflated result.
Control variables. Same time of day, same hydration, same nutrition timing. Caffeine affects perceived exertion; use it or avoid it consistently.
Test, don't race. An FTP test should feel like a controlled scientific effort, not a competitive event. Emotional pacing (going harder because a segment feels easy) is how tests get ruined.
Retest regularly. FTP changes with training. Retest every six to eight weeks during a training block, or whenever your prescribed intensities consistently feel wrong in either direction.
Cross-check your result. After testing, use the FTP estimator to see how your new number compares to power outputs from recent hard efforts. A result that diverges sharply from recent ride data deserves scrutiny.

For context on what your FTP number means for zone setup and training structure, return to the complete FTP guide.