Ramp Test vs 20-Minute FTP Test: Which One Should You Use?

The direct answer

If you are new to power testing, dislike judging a 20-minute effort, or only have a short slot indoors, start with a ramp test in the app that supplies it. You follow rising targets until you cannot continue. It is mentally simple, although the end is very hard.

If you regularly ride sustained climbs, time trials, long race efforts, or steady trainer intervals, the 20-minute test can suit you. It asks for more judgment: start too hard and you fade; start too easy and the final sprint can overstate the result.

For the full self-paced protocol, use this 20-minute FTP test at home. Once you choose, put the result into the FTP calculator.

Why the numbers can differ

The familiar 20-minute method is average power for the interval multiplied by 0.95. TrainerRoad's ramp protocol uses 75% of the best one-minute power, while noting that it can adjust the result when a rider does not follow the target closely.

These are estimates from different tests, not two paths to one secret true number. A ramp test can use different step sizes or a different formula depending on the app. Do not take a 75% rule from one platform and use it for every ramp file.

Your FTP setting is useful when it makes the intended workouts hard in the intended way, not when it wins an argument between test types.

The honest trade-offs

A ramp test is simple to begin because you do not choose the pace. Keep your cadence steady. Follow the rising target. Keep going until you cannot hold it. It suits riders who panic early or go too gently in a self-paced test.

The 20-minute test is closer to riding a long hard climb. It suits riders who know their own pace. It also shows poor cooling, fatigue, and pacing mistakes quickly. Add warm-up and cooldown and it takes longer too.

Neither test is magic. A rider with a big one-minute effort may get a ramp result that feels high for longer work. A cautious rider may leave too much in the tank in a 20-minute test. Nobody failed. The number just needs to meet real training.

Check the result against workouts

Use the same trainer, power source, fan, and test format when you retest. That makes a change easier to trust than switching methods and comparing raw numbers.

Then ride two or three suitable sessions. A threshold workout should be hard but doable with good pacing. Sweet-spot work should feel steady, not like a race. If you keep cracking, lower the setting a little. If several sessions feel plainly too easy, raise it carefully or retest.

For smart-trainer workouts, understand ERG mode before you decide the trainer is at fault. ERG holds a target but it cannot make an unrealistic FTP setting sensible.

Action plan: choose in 4 steps

1. 1

   Pick a ramp test if pacing is the biggest barrier. Pick the 20-minute test if you can hold a hard steady effort without big surges.

2. 2

   Use one protocol, one trainer, and one cooling setup for the next test block.

3. 3

   Calculate the result in the FTP calculator and begin with realistic workouts.

4. 4

   Let workout feel guide a small adjustment. Do not chase a bigger number because another test produced it.

Common mistakes

• Calling one test universally better

  Pick for your experience, time, and ability to pace rather than internet consensus.

• Applying 75% to every ramp test

  Ramp protocols vary. Use the formula provided by the specific app or test.

• Starting a 20-minute test too hard

  Build quickly but in control, then make small adjustments rather than repeated surges.

• Stopping a ramp test by choice

  Follow the prescribed target until you genuinely cannot maintain it.

• Switching test type every month

  Trends become harder to read when the protocol keeps changing.

• Treating a result as a verdict

  It is a starting setting. Check it against honest structured rides.

FAQ