FTP Tests for Cyclists
There is no single perfect FTP test—only different protocols with different tradeoffs. This guide helps you choose the right test, execute it properly, and use the result to set training zones that actually match your ability.
Why Cyclists Test FTP
Functional Threshold Power (FTP) is the foundation of structured cycling training. Without a reasonably accurate FTP, your training zones are guesswork. Workouts become either too easy to trigger adaptation or too hard to complete—and you have no reliable way to measure whether training is working.
FTP testing serves three purposes:
- Setting training zones — so every workout targets the right intensity
- Tracking progress — comparing results over months and seasons
- Validating training — checking whether your current approach is producing results
The test itself is not the point. The point is the training decisions you make with the result. A perfect test followed by poor zone interpretation is worse than a rough estimate followed by intelligent application.
The Main FTP Test Types
Every FTP test tries to answer the same question: what power can you sustain at your aerobic limit? But they approach it differently, and each has strengths and weaknesses.
The Ramp Test
How it works
Power increases by a fixed amount (usually 20W) every minute until you can no longer hold the target. FTP is estimated as 75% of your peak one-minute power during the test.
Duration
10–25 minutes total depending on fitness. The hard part is only the final 3–5 minutes.
- Easy to execute—no pacing required
- Short and repeatable
- Low psychological barrier
- Built into most smart trainers
- Overestimates for anaerobically strong riders
- Doesn't test sustained power at all
- 75% multiplier is a rough average, not individual
- Result influenced by sprint ability
The ramp test is popular because it's easy. But "easy to execute" doesn't mean "most accurate." If your training zones from a ramp test make threshold sessions feel impossible, the test likely overestimated your FTP.
The 20-Minute Test
How it works
After a warm-up (often including a 5-minute hard effort to pre-fatigue anaerobic stores), you ride as hard as you can sustain for exactly 20 minutes. FTP is estimated as 95% of your average power.
Duration
45–60 minutes total including warm-up and cool-down. The 20-minute effort is mentally and physically demanding.
- Tests sustained power directly
- More reflective of real riding demands
- Well-validated protocol
- Works indoors and outdoors
- Pacing is hard—start too fast and you blow up
- Psychologically demanding
- 95% multiplier varies between riders
- Requires motivation and experience
The 20-minute test is the most commonly recommended protocol and works well for most riders. The main challenge is pacing: if you start 10W too hard, the final five minutes become a survival exercise and the result is unreliable. Experienced testers learn to start conservatively and build.
Longer Steady-State Tests (30–60 Minutes)
How it works
Ride at the hardest power you can sustain for 30, 40, or 60 minutes. Average power over the full duration is your FTP estimate (no correction factor needed for efforts ≥40 minutes).
Duration
60–90 minutes total. The sustained effort itself lasts 30–60 minutes—this is a serious physical and mental commitment.
- Most direct measurement of what FTP represents
- No correction factor needed at 40–60 minutes
- Hardest to inflate with anaerobic contribution
- Mirrors real-world sustained efforts
- Extremely demanding psychologically
- Difficult to pace correctly
- Requires significant recovery afterward
- Impractical for frequent retesting
Longer tests are the most accurate but the least practical. They're best suited for experienced riders who need precise values—like those preparing for time trials or specific race targets. Most riders don't need to do these regularly. A well-executed 20-minute test is accurate enough for training zone purposes.
Ramp Test vs 20-Minute Test vs Steady-State
Here's how the three main protocols compare across the dimensions that matter most for choosing one:
| Factor | Ramp Test | 20-Minute Test | Steady-State (40–60 min) |
|---|---|---|---|
| Ease of execution | Very easy | Moderate | Hard |
| Pacing skill required | None | Significant | Very significant |
| Accuracy for most riders | Moderate (tends to overestimate) | Good | Very good |
| Risk of inflated result | High (anaerobic riders) | Moderate | Low |
| Recovery cost | Low | Moderate | High |
| Best for | Beginners, frequent retesting | Most trained cyclists | TT specialists, precise calibration |
No test is objectively "best." The right test is the one you can execute well, repeat consistently, and whose result produces training zones that feel correct during workouts.
How to Choose the Right FTP Test
Your choice depends on experience, testing goals, and what kind of rider you are:
New to structured training?
Start with a ramp test. It requires no pacing skill and gives you a usable starting FTP. Adjust down by 3–5% if threshold workouts feel too hard. Once you're comfortable with testing, switch to a 20-minute protocol.
Experienced rider with good pacing?
The 20-minute test is your best default. It balances accuracy with practicality. Do the 5-minute hard effort before the 20-minute block to blunt anaerobic contribution. Use 95% of average power as your FTP.
Strong sprinter or anaerobic rider?
Avoid the ramp test—it will almost certainly overestimate your FTP. Use a 20-minute test with the 5-minute pre-fatigue, or better yet, a 30–40 minute steady-state effort. Your zones need to reflect your aerobic ceiling, not your kick.
Targeting a specific race or TT?
Use a steady-state test at race duration when possible. If your target event is 40 minutes, a 40-minute max effort gives you the most relevant data. This also doubles as race-pace practice.
Whatever test you choose, consistency matters more than the protocol. If you always use the same test under similar conditions, your results will be comparable over time even if the absolute number is slightly off.
When to Test FTP
Testing too often wastes training time and recovery. Testing too rarely means your zones drift out of alignment with your actual fitness. Here's a practical schedule:
- Every 6–8 weeks — at the end of a training block, before starting a new phase
- After a recovery week — test when rested, not when fatigued from training load
- When workouts feel wrong — if threshold sessions are consistently too easy or impossible, your FTP has shifted
- At the start of a season — establish a baseline before beginning structured work
Between formal tests, you can track FTP trends from workout data. If you complete 2×20 at your current FTP with controlled heart rate and can talk in short phrases, your FTP has likely risen. Platforms that track your power-duration curve can estimate changes automatically.
How to Prepare for an FTP Test
A good FTP test measures your current fitness, not your current fatigue. Preparation makes the difference between a valid result and a number you can't trust:
48 Hours Before
- No hard efforts or intensity
- Easy spin or complete rest
- Normal sleep schedule
- Stay hydrated
Test Day
- Eat a normal pre-ride meal 2–3 hours before
- Same caffeine routine as usual
- Proper warm-up (15–20 minutes)
- Same equipment, same environment
If you're testing indoors, use a fan, keep the room cool, and ensure your trainer is calibrated. Small environmental differences (heat, tire pressure, calibration) can shift results by 5–10W—enough to distort your training zones.
How to Avoid Invalid Results
An FTP test only means something if the result is valid. These are the most common ways riders end up with a number they can't use:
- Testing when fatigued — if you had a hard week of training, your result reflects your fatigue, not your fitness
- Poor pacing — starting the 20-minute test 15W too high and dying at minute 12 gives a useless average
- Wrong test for your profile — a ramp test for a diesel rider underestimates; for a sprinter, it overestimates
- Inconsistent conditions — testing in a 30°C room one time and a 18°C room the next makes comparison meaningless
- Ego-driven testing — chasing a specific number rather than riding the test honestly produces inflated results that hurt training quality
- Testing too often — weekly testing burns recovery on measurement instead of adaptation and creates noise in your data
The best test result is one that makes your next six weeks of training effective. A slightly lower but honest FTP produces better training stimulus than an inflated number that makes every session a survival exercise.
What to Do After Your FTP Test
The test is only step one. What matters is how you use the result:
- Update your training zones — recalculate all zones based on the new FTP. Your training zones determine every workout's intensity, so this step is non-negotiable.
- Validate with a workout — within the first week, do a threshold session (like 2×15 at FTP). If you can complete it with difficulty but without collapsing, your FTP is set correctly. If it's impossible, reduce by 3–5%.
- Record the context — note the date, protocol used, conditions (indoor/outdoor, temperature, freshness level), and any factors that might have influenced the result.
- Compare trends, not individual numbers — a single FTP value means little in isolation. Track it over months to see whether your training is producing consistent improvement.
- Consider your power-to-weight ratio — raw FTP tells you absolute power, but W/kg tells you how that power translates to climbing and real-world performance.
If your FTP has changed significantly (more than 5%), take a careful look at whether the change is real or a testing artifact. Sudden jumps often reflect better test execution rather than actual fitness gains. Gradual, consistent improvement over months is the pattern that reflects genuine adaptation.