Setting Cycling Training Zones: Ramp Test vs 20‑Minute FTP Test
5 min read
Ramp test vs 20-minute FTP test: learn what each measures, how results affect cycling power zones, and which test to use for your next training block.
On this page
Photo by Tingkai Meng on Unsplash.
Ramp tests are quick FTP estimates from peak power; 20-minute tests use sustained power. Pick the test that matches your next training need.
Both tests can set cycling training zones, but they do not ask the same question. A ramp test rises step by step until you stop, then turns the final test signal into an FTP estimate. A 20-minute FTP test uses a hard sustained effort, then scales that mean power into a working threshold estimate. Your next move is simple: use a ramp test for a quick, lower-disruption update, and use a 20-minute test when sustained pacing matters most.
Photo by SportShot EventPhotography on Unsplash.
The ramp test is an incremental check that raises power until you can no longer hold the demand. Training apps and labs then convert the last completed work into an FTP proxy.
A 20-minute FTP test asks for one hard, even effort that you can hold without fading early. That makes pacing part of the test, not a side issue.
Neither result is the whole truth. If your new number shifts many zones at once, use zone changes after a big FTP jump before you load the next block.
Ramp test: best for a quick, lower-stress update.
20-minute test: best for sustained threshold checks.
Do not compare ramp peak power with 20-minute mean power.
Keep one method through a short training block.
Use the test that gives the signal your next sessions need.
In N+One terms: match the test to your output target, not to the number you hope to see.
PubMed-indexed literature compares cycling test protocols, conversion methods, and reliability, but the details matter. Warm-up, step size, fatigue, device choice, and pacing can all change the result.
That means no single field test is best for every rider and goal. If a field FTP and lab threshold disagree, use why lab and field thresholds split to decide which number should guide training.
The sound coaching move is not to chase one perfect label. Repeat the same protocol under similar conditions, then judge whether the zones work on the bike.
Use the same warm-up when you retest.
Keep the same power source and trainer mode.
Treat a new protocol as a new baseline.
Use lab testing when precision is the main goal.
Ramp test: brief, incremental increases to failure; lower acute fatigue and quick to run.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
A ramp-derived FTP can set hard interval targets that feel sharp if your peak power is stronger than your steady power. A 20-minute test can give steadier threshold and sweet-spot targets when pacing is central.
These shifts matter because zones guide session design, not just charts. Use smarter power-zone structure if you need the full map from FTP to workout targets.
If you change test type, keep the first week conservative while the system settles. Your threshold did not disappear; your recovery inputs, test signal, and zone math changed.
Lower high-intensity volume by 10–20% after switching tests.
Check breathing and RPE in early threshold work.
Do not raise all zones from one peak result alone.
Use steady work to confirm sustained targets.
Let the first week prove the number before you build around it.
In N+One terms: the test is one input, while the ride response tells you whether the plan fits.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Tempo Riding for Cyclists: The Most Misused Zone in Endurance Training — Tempo is often misused by cyclists as either hidden threshold work or vague easy riding. Learn how to find it, program it, and adjust this week.
- Running Heart Rate Zones vs Cycling Heart Rate Zones: Why They Are Different — Running and cycling heart-rate zones differ because posture, muscle use, and load change the response. Learn how to set bike-specific HR zones.
- Heart Rate Zones for Mitochondrial Adaptation in Cycling — How to use heart rate zones for mitochondrial adaptation in cycling: practical Zone 2 rules, session templates, and adaptive coaching tips.
Test quality starts before the effort. Use the same bike, meter, warm-up, route or trainer setup, and time of day whenever you repeat the test.
For a ramp test, follow the protocol exactly and avoid changing step rules mid-test. For a 20-minute test, start firm but controlled, then build only if you can hold the line.
Power should lead the test, but heart rate and perceived effort help flag odd days. If heat still lingers in early autumn, compare power against heart-rate zones in hot conditions before you overreact.
Test after an easy day, not deep fatigue.
Calibrate the power meter or trainer first.
Log RPE, heart rate, and conditions.
Cool down before judging the result.
Repeat the same test in 4–8 weeks.
After the test, set zones from the method your app or coach uses, then check the first workouts. The number should make threshold work hard, controlled, and repeatable.
Long endurance rides add another check. If power drifts away from effort late in the ride, review power drift on long endurance rides before changing FTP again.
Do not let one test pull every ride into the middle. Keep easy work easy, and use guardrails for zone 2 volume when shorter daylight compresses autumn training.
Use the new FTP as provisional for one week.
Keep easy rides clearly easy.
Check one controlled threshold session.
Adjust only if several signals agree.
A good FTP estimate improves the next session, not just the dashboard.
Day 1 — Choose the test that matches your goal. Use a ramp test for a quick peak-power check, or a 20-minute test for sustained threshold work.
Day 1 — Schedule the test after an easy recovery day. Reduce training volume by 20% the day before, and keep the warm-up plan written down.
Day 2 — For a ramp test, warm up normally, then follow the incremental steps until failure. Record the peak value exactly as the protocol defines it.
Day 2 — For a 20-minute test, warm up the same way, ride one maximal sustained 20-minute effort, and record mean power.
Day 2 — Calibrate devices before testing. Log power, heart rate, perceived effort, room or weather conditions, and any pacing mistakes.
Day 3 — Ride easy for 45–60 minutes, or rest fully if you feel unusually flat. Do not judge the number while tired.
Days 4–7 — Apply the zones from your chosen method. If you switched test types, reduce high-intensity session targets by 10–20% for one week.
Reassessment — Repeat the same protocol under similar conditions in 4–8 weeks, so you track real change instead of test noise.
Ramp tests are quick FTP estimates from peak power, while 20-minute FTP tests use sustained power and pacing. Use the ramp test when you need a fast, lower-disruption update; use the 20-minute test when your next block depends on steady threshold work. Then verify the zones in training before you add load.
No. It can be useful when you need a quick update, but the converted number should be checked in training. Treat it as a working estimate, not a verdict.
Not right away. First check fatigue, pacing, device setup, and conditions. A lower but repeatable number often gives better sessions than an inflated target.
Heart rate is a strong cross-check for endurance work, but it lags during short intervals. Use power to anchor FTP-based sessions, then use heart rate and RPE to spot mismatch.
Retest when your workouts no longer match the zones, or after a focused block. Keep the same protocol so the trend is useful.