FTP Test Cycling: How to Measure Your Functional Threshold Power Accurately
6 min read
Learn how to measure cycling FTP with a calibrated power meter, repeatable warm-up, controlled setup, and a well-paced 20-minute test.
On this page
Photo by Juan Pablo on Unsplash.
Measure FTP with a calibrated power meter, a set warm-up, and one repeatable protocol. Then update zones only when the result fits your riding.
FTP is a practical threshold used to set training zones, compare progress, and pace hard work. The number is useful only when the test is repeatable, because small measurement errors can shift every power target built from it. In N+One terms: treat FTP as a regularly refreshed system input, not a fixed label.
A good FTP test starts before the hard effort. Use the same power meter or trainer, the same warm-up, and the same broad pre-test routine each time.
If you change devices, roads, fans, tire setup, or time of day, the test may track those changes instead of fitness. Start with clean power meter setup before you treat the result as a new training anchor.
In summer, heat can make an indoor test feel much harder than the same power outdoors. Use strong airflow, keep bottles close, and avoid testing in a hot room if you will compare the result with cooler past tests.
Use the same meter or smart trainer for each test.
Zero-offset or calibrate before the warm-up.
Test after a lighter day, not after hard intervals.
Keep food, drink, fan setup, and route consistent.
A cleaner setup makes the measured FTP more useful for your next training choice.
Reduce input variance so changes reflect fitness, not test noise.
Photo by Arthur Colas on Unsplash.
The common field test is a maximal 20-minute effort, with FTP estimated as 95% of mean power. It is simple, but it asks for sound pacing and a real willingness to sit with discomfort.
Ramp tests are easier to run indoors because the load rises in steps until you stop. They can be useful, but the conversion to FTP depends on the test design and the software rules behind it.
Critical power testing uses several hard efforts to model the power-duration curve. That can show more than one FTP number, especially when paired with how your power profile changes across short and long efforts.
Pick one test format before the block starts.
Use the 20-minute test if you can pace well.
Use ramp testing when repeatable indoor setup matters most.
Do not compare protocols as if they are the same test.
FTP is best measured with a calibrated power meter and a repeatable protocol (commonly a 20‑minute maximal effort or a lab 60‑minute/crit…
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Your warm-up should raise breathing, wake the legs, and leave you ready rather than drained. Go easy first, add steady work, then add a few short hard efforts before the test begins.
For the 20-minute effort, the first minutes should feel controlled. If you start at a power you can only hold briefly, the final average will fall and the test will understate your best steady output.
A small negative split is often cleaner than a heroic start. The same skill helps in racing, especially when you use power-based pacing for time trials instead of chasing early speed.
Warm up for 20–30 minutes.
Start the test a touch below target feel.
Hold steady pressure through the middle.
Lift effort only when you can still finish cleanly.
Pacing well turns the test from a suffer score into a better training input.
Prepare the system predictably so output reflects threshold, not early fatigue.
Power smoothing helps you ride, but it should not be the only data you keep. Use short smoothing on the head unit, then calculate the test from the raw file afterward.
Spikes, dropouts, stops, and coasting can bend the average if they sit inside the test window. Trim only obvious artifacts, and do not remove hard but real work just because it looks messy.
If your number jumps after one standout ride, do not assume your whole training system must change at once. Compare the test with recent threshold work, longer rides, and why FTP can drift without a formal test.
Use smoothing for feedback, not final math.
Keep the raw power file after the ride.
Remove clear stops or signal faults only.
Cross-check the result with recent hard sessions.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- 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...
- Why Your FTP Plateaus After Year Two — FTP plateaus when early gains slow and your training inputs stop matching the adaptation you need. Diagnose the cause, then make one clear correction.
- Sweet Spot Training: Maximum Gain, Sustainable Fatigue — Sweet spot training (88–94% FTP) delivers high aerobic gains with manageable fatigue—ideal for time-crunched cyclists. Learn interval design, periodi...
Most riders do not need constant formal testing. A test makes most sense after a clear training block, after steady missed targets, or when hard sessions feel too easy for more than a few rides.
When the result is plausible, update zones and keep the next week simple. Do not rewrite the whole season because one test was great or rough.
FTP is still only a snapshot. For long events, pair the number with durability after long rides and the way power holds after fatigue builds.
Retest after a planned block or clear signal.
Keep the protocol and setup the same.
Change zones only when the result fits recent rides.
Watch how threshold feels during the next week.
The best FTP update is one your next sessions can support.
Refresh the training system when your measured input shifts beyond expected test noise.
FTP is a useful field anchor, not a full map of your physiology. It does not replace lab testing, and it does not explain every gap between sprint power, climbing power, and long-course stamina.
A criterium rider, track sprinter, and long-course triathlete may share the same FTP but need very different work. Use event demands, repeat hard efforts, and the durability story behind FTP before you judge fitness from one number.
If you tested while ill, under-fueled, overheated, or on a suspect device, hold the old zones for now. Repeat the test when the setup is cleaner and your body is ready.
Treat FTP as one anchor, not the whole map.
Add event-specific metrics for sprints or surges.
Do not change zones after a compromised test.
Repeat the test before reacting to a strange result.
Pre-test, 48–24 hours: reduce volume and avoid hard intervals. Confirm your power meter or trainer is charged, paired, and zero-offset or calibrated.
Morning of test: eat your normal pre-ride meal and drink as you usually would. Keep the same broad routine you used before past tests.
Warm-up, 20–30 minutes: spin easy, add several steady efforts, include a few short hard bursts, then ride easy before the test starts.
20-minute maximal effort: begin slightly conservative, hold steady pressure, avoid surges, and record second-by-second power from the same device.
Cool-down and data handling: spin easy, save the raw file, trim clear stops or signal faults, and calculate 95% of mean 20-minute power.
Follow-up: if the number conflicts with recent hard rides, keep current zones and repeat under the same conditions before changing training targets.
Your next move: choose one repeatable FTP protocol, control the setup, pace the effort evenly, and update zones only when the result matches recent riding.
Not always. A ramp test is easier to run and repeat indoors, while a 20-minute test gives useful pacing practice. Pick the one you can repeat cleanly, then avoid comparing results across protocols as if they are identical.
Usually, no. If the test was affected by heat, poor sleep, illness, fueling, or device issues, keep your current zones and retest under cleaner conditions.
You can, but only if the numbers match how indoor sessions feel. Some riders see different indoor and outdoor power because cooling, position, and setup change the work.
Trust the wider pattern. If threshold workouts are repeatedly too hard or too easy, recent training may be a better signal than a single test file.