FTP Tests Compared: 20-Minute vs Ramp Test
5 min read
Compare the 20-minute FTP test and ramp test, learn what each measures, and choose the right protocol for consistent cycling training zones.
On this page
Photo by Quan-You Zhang on Unsplash.
Both tests estimate FTP, but they measure different capacities. Pick one protocol, repeat it, and use the result with care.
FTP tests are useful because they turn hard riding into training targets. The key is not finding a perfect number; it is using a sound, repeatable method that fits your riding and your next training block.
Photo by Ben Neal on Unsplash.
Functional Threshold Power is a practical estimate, not a fixed lab truth. Riders use it to set zones, track change, and shape workouts around a shared anchor.
A good test gives your training system a clean input. A poor setup can make the number look like fitness changed, when the test itself changed.
If you are new to this process, start with a broader guide to measuring threshold power before comparing protocols. Also make sure your device setup is sound, because clean power meter setup matters before any FTP test has meaning.
Treat FTP as an estimate, not an absolute truth.
Use testing to set zones and track change.
Pick a test that fits your goal and effort tolerance.
Keep equipment and warm-up the same each time.
In N+One terms: the test is a calibration tool, so match it to the training system it will guide.
The test is a calibration tool. Pick the one that best matches the training system you will feed with that number.
The 20-minute test asks you to ride one hard, steady effort. The common coaching convention is to use about 95% of mean 20-minute power as the FTP estimate.
The ramp test raises power in short steps until you can no longer hold the target. That peak result is then mapped into an FTP estimate by your coach or platform.
These tests can disagree because they ask different questions. One samples sustained hard riding, while the other samples peak output during a graded test to failure.
20-minute: sustained effort and pacing skill.
Ramp: short stepped increases to failure.
Do not expect both tests to return the same number.
Compare future tests only against the same protocol.
20‑minute and ramp tests target different physiological outputs: sustained high‑intensity power versus maximal incremental/peak power.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
The 20-minute test maps well to riders who need long, steady power. It also teaches pacing, which helps if your goals include climbs, time trials, or late-season threshold work.
Its weak point is the execution cost. Start too hard, fade badly, or hold back too much, and the mean power will mislead your zones.
The ramp test is shorter and simpler to pace. It suits frequent checks, busy weeks, and riders who struggle to judge a maximal steady effort.
Its weak point is the conversion step. If you want to know how your power holds after long work, pair testing with durability beyond one FTP number.
Use 20-minute testing when pacing practice matters.
Use ramp testing when low-burden checks matter.
Avoid switching methods inside one training block.
If the result feels wrong, review setup before changing zones.
In N+One terms: keep the training aim steady, while the test choice changes the calibration input.
Keep the intensity target, but know that the calibration input changes the number you train from.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Maximum Gains, Minimum Time — Evidence-Based Training for Busy Cyclists — Time-crunched? Use science-backed, time-efficient training (polarized, sweet spot, HIIT) plus real-time adaptation to get measurable gains without en...
- eFTP Updates After Breakthrough Rides: Confidence Thresholds Explained — A clear protocol for deciding whether a breakthrough ride should update your eFTP, with confidence thresholds, repeat testing, and zone adjustment gu...
- FTP Estimate Drift in N+One: Why Your Number Moves Without a Formal Test — Learn why your N+One FTP estimate can drift without a formal test, when to treat it as noise, and the clear one-week response to validate the change.
Choose the test by the job you need it to do. If your next block is built around steady pressure, the 20-minute test is often the clearer match.
If your schedule is tight, the ramp test can be a better fit. It gives a repeatable check without asking for a long maximal effort.
For hilly goals, look at how your power changes across different durations, not just one test. A climb-specific power profile can show gaps that FTP alone hides.
When progress slows, do not blame the athlete first. Review recovery, test method, and whether your workouts still match the trait you want to build.
Pick 20-minute for steady threshold goals.
Pick ramp for easier retesting cycles.
Log which method made each FTP number.
Do not mix conversion rules mid-block.
After testing, set zones from the method you used. Then judge the first week by workout feel, power control, and how well you recover between sessions.
If the test felt off, start slightly conservative rather than forcing every interval. This keeps the next few workouts useful while you check the signal.
Use the new number to guide the right workout type, not just harder targets. For example, sub-threshold and over-under work stress different skills around threshold.
Track the trend across repeated tests. One standout day can be useful, but a pattern across blocks gives a better guide for training decisions.
Use the same conversion method after each test.
Start conservatively if the result felt unusual.
Reassess after the first week of workouts.
Retest after a full training block when possible.
If you want day-to-day guidance without second-guessing, let N+One translate your latest testing context into one clear next decision.
If you want day-to-day guidance without second-guessing, let N+One translate your latest testing context into one clear next decision.
Preparation: In the day or two before testing, skip hard training, eat normally, and use the same bike, power source, warm-up, and route or trainer setup.
20-minute test: Warm up well, include a few short efforts, then ride one maximal 20-minute effort with steady pacing. Record mean power and apply the coaching convention your system uses.
Ramp test: Warm up in a standard way, then raise power in regular short steps until failure. Use the peak result and apply your platform or coach conversion.
Immediate plan: Set zones from that method only. If the test felt unusually taxing or unusually easy, start the first week a little conservative and reassess after several sessions.
Next test: Repeat the same protocol after a clear training block, so the next number reflects change rather than a new test format.
Both tests estimate FTP, but they measure different capacities. Use the 20-minute test when sustained pacing is the point, use the ramp test when you need a shorter repeatable check, and keep the same protocol when you compare progress.
Not automatically. It answers a different question and then converts that result into an FTP estimate. It can work well if you repeat the same protocol and use the same conversion each time.
Not right away. First check sleep, recovery, equipment setup, warm-up, and pacing. Your threshold did not disappear; the inputs around the test may have shifted.
You can note both numbers, but avoid treating them as the same measurement. Use one method for trend tracking, especially inside one training block.
If you can pace a hard steady effort, choose the 20-minute test. If you need a shorter low-burden check, choose the ramp test and keep that method for your next reassessment.