Which Zwift FTP test to take: Standard, Ramp, Lite, or Elite Verification

The four tests, and the only real decision among them

You are choosing between two. FTP Test (Standard) stacks a warmup, a ramp effort, a 5-minute effort and a 20-minute effort, and derives FTP from that final 20 minutes. The two ramp tests are the same progressive ramp, split by rider weight. Elite Racing Verification is a race-categorisation tool, not a training one [Zwift Support 2026].

Zwift's options table is precise. FTP Test (Standard) is listed for general FTP assessment, its format given as warmup, ramp effort, 5-minute effort and 20-minute effort, with the note that FTP is based on the final 20-minute segment. Both ramp tests are described identically as a progressive ramp test, carrying the same note: FTP may display as 100 at the start, and the final FTP is calculated during the workout [Zwift Support 2026]. The difference sits in the intended-for column, not the format column.

The Elite Racing Verification Test is the odd one out; ignore it unless you have been asked for it. Zwift lists it for elite racing pre-verification, describes the format as multiple timed efforts, and notes that ERG mode is not used during this test [Zwift Support 2026]. It exists to substantiate a performance claim for race categorisation, not to set training zones. Whichever you pick, note that Zwift uses FTP only during workouts, so the number moves your workout targets and nothing else.

Lite is a weight split at 60 kg, not a short cut

Zwift describes both ramp tests in identical language. The standard FTP Ramp Test is intended for riders 60 kg or over and more experienced riders; FTP Ramp Test (Lite) is intended for riders under 60 kg and newer riders [Zwift Support 2026]. Lite is not shorter, not easier, and not less valid.

The name misleads almost everyone. Riders read Lite as the quick version and pick it to save an evening, or avoid it assuming a lightweight test yields a lightweight number. The two rows differ only in who each test is for, and Zwift gives two criteria on each side: a body-weight threshold at 60 kg, and a rider-experience judgement [Zwift Support 2026].

Splitting a ramp on body weight is defensible, though Zwift does not publish its reasoning. A ramp raises load in absolute watts, so a fixed step is a far larger relative demand on a 55 kg rider than on an 85 kg one — the lighter rider is effectively riding a steeper ramp. Ramp rate is not a neutral choice. Michalik and colleagues [Michalik et al. 2019] put the same men through two ramp rates and recorded peak power of 341 watts on the slower protocol against 393 watts on the faster one, a gap of 51.69 watts, or roughly 15%. Because a ramp derives FTP from that peak, a steeper relative ramp inflates the number you take home.

The practical instruction is dull and load-bearing: pick by Zwift's stated criteria, then stay on that test. A rider who takes the standard ramp in March and Lite in June has changed method, not fitness, and any movement in the number is uninterpretable. That matters most near the 60 kg line.

ERG does not run the test, and the 20-minute segment is not fresh

Two corrections that change how you ride. ERG does not hold your target during an FTP test — Zwift keeps resistance neutral and you shift gears manually, which makes the on-or-off question close to moot [Zwift Support 2026]. And Zwift has no standalone 20-minute test: that effort arrives after a ramp effort and a 5-minute effort.

Zwift is explicit. In ERG mode during an FTP test you still shift gears manually to adjust resistance, because Zwift does not automatically adjust resistance during FTP test intervals — resistance stays neutral so you control cadence and power output throughout [Zwift Support 2026]. Riders hunting for the correct ERG setting are hoping the trainer will pace the effort for them. It will not.

Since cadence is yours too, do not go hunting for an optimal rpm. Mater and colleagues [Mater et al. 2021] reviewed cycling cadence and neuromuscular function, reporting that heterogeneity in the cadences selected, the assessment methods and the populations studied made comparison across studies difficult. The literature does not hand you a single best cadence. Ride what you habitually ride, and keep it consistent between tests.

The second correction matters more. The only route to a 20-minute test on Zwift is FTP Test (Standard), and its 20-minute segment is preceded inside the same workout by a ramp effort and a 5-minute effort [Zwift Support 2026]. That is not a warm-up; it is prior severe-intensity work. Chorley and colleagues [Chorley et al. 2021] modelled the recovery of W-prime, the finite work capacity above critical power, and found it reconstitutes bi-exponentially with a slow-component time constant of 388 seconds — rising to 716 seconds after a second maximal effort, and at three minutes the second recovery had restored about 9% less than the first. Capacity spent earlier is only partly back when the 20 minutes begins.

The consequence is comparability. Warm-up structure alone shifts the FTP a 20-minute test reports [Tramontin et al. 2022], and a preceding ramp plus 5-minute effort is a much larger difference than a warm-up. Compare a Zwift Standard result only to previous Zwift Standard results.

Choosing tonight, and when not to test at all

If dread is what has stopped you, take the ramp matching your weight — it front-loads easy and concentrates the hard part into the last few minutes. If you want a number anchored in sustained work, take Standard and pace it evenly. If you already ride with power, you may need neither [Zwift Support 2026].

Every page ranking for this question compares protocols on accuracy and stops there. Tolerability is what riders actually decide on, and it is a legitimate criterion. I have taken the ramp, and it is not bad at all if you want a quicker and somewhat accurate number — you are only really in pain for the last few minutes rather than facing a full 20-minute effort. An abandoned or badly paced 20-minute effort produces a falsely low FTP, and short estimates are noisy against genuine sustained efforts: individually the two have disagreed by 40 to 60 watts [Borszcz et al. 2018]. The best test is the one you finish.

State the trade honestly. The ramp is also the protocol most likely to hand you a number you cannot hold for an hour, particularly if you sprint well — our guide on why a ramp test FTP comes out too high covers that mechanism. A ramp result is partly an artifact of the step size you happened to ride [Michalik et al. 2019], which is why somewhat accurate is the right ceiling. Zwift's own troubleshooting agrees: if your workouts feel too difficult, your FTP may be set too high.

There is also the option of not testing. Zwift states that without a completed FTP test it estimates your FTP from your weight and the fitness level profile you selected, and that once you have started riding it estimates from your power data [Zwift Support 2026]. That is the broader frame our pillar on estimating FTP without a forced test works in — your threshold is already implied by the efforts sitting in your ride history. The limit of Zwift's version is its window: it sees Zwift rides, and uses the result only inside Zwift workouts.

AdaptCycling fits a Critical Power model to the mean-maximal-power curve built from your whole Strava history, indoor and outdoor, so the estimate rests on dozens of efforts across months rather than one evening's willingness to suffer. A Zwift test simply joins that curve. Whichever protocol you pick, run it roughly twice a year rather than every six weeks — our guide on how often to test FTP makes that case.

Quick answers

Sources cited in this guide

1. 01
   Zwift Support 2026. FTP Test. Zwift Support.
2. 02
   Michalik et al. 2019. Influence of Intensity RAMP Incremental Test on Peak Power, Post-Exercise Blood Lactate, and Heart Rate Recovery in Males: Cross-Over Study. International Journal of Environmental Research and Public Health.
3. 03
   Chorley et al. 2021. Bi-exponential modelling of W-prime reconstitution kinetics in trained cyclists. European Journal of Applied Physiology.
4. 04
   Mater et al. 2021. Effect of Cycling Cadence on Neuromuscular Function: A Systematic Review of Acute and Chronic Alterations. International Journal of Environmental Research and Public Health.
5. 05
   Tramontin et al. 2022. Functional Threshold Power Estimated from a 20-minute Time-trial Test is Warm-up-dependent. International Journal of Sports Medicine.
6. 06
   Borszcz et al. 2018. Functional Threshold Power in Cyclists: Validity of the Concept and Physiological Responses. International Journal of Sports Medicine.

More inside FTP without a test

Other articles in this series

1. 01

   Indoor vs outdoor FTP: why the numbers differ

   Why your indoor FTP reads lower than outdoor — heat, cooling, motivation, and power-source differences — and whether to keep two numbers.

   →
2. 02

   How to estimate FTP without a power meter

   Estimating FTP from heart rate, RPE, and Strava when you don't own a power meter — how close you can get and where the method breaks down.

   →
3. 03

   20-minute vs 8-minute FTP test: which to use

   How the 20-minute and 8-minute FTP tests differ, the multipliers each uses, and which one fits your riding — plus why both are only protocols.

   →
4. 04

   Why cycling apps show you different FTP numbers

   Strava, Xert, Intervals.icu, and TrainingPeaks can each report a different FTP. Why the estimates diverge and which one to trust.

   →
5. 05

   Is your ramp test FTP too high? Why it happens

   Ramp tests overestimate FTP for anaerobically-gifted riders and underestimate it for diesels. Why the 75% rule misfires and how to correct it.

   →
6. 06

   How often should you test your FTP?

   How often to re-test FTP as a self-coached cyclist — twice a year, not every six weeks — and why modeled estimates change the cadence.

   →
7. 07

   Critical Power vs FTP: which number should you trust?

   CP and FTP track each other across a group but can differ 20-36W for you specifically. Why there is no correction factor, and which to anchor to.

   →
8. 08

   Can you actually hold your FTP for an hour?

   Published time-to-exhaustion at FTP runs 34 to 51 minutes across studies, never 60, and the individual spread is wide. Why the hour is a bad test.

   →
9. 09

   FTP stopped improving: are you a non-responder?

   Non-responder labels flip for 45% of people depending only on the statistics used. What a flat FTP usually means instead, and what to check first.

   →
10. 10

    Durability: why your power fades late in long rides

    What durability is, why the kJ threshold your app uses is arbitrary, and the honest evidence on whether it is independent of FTP or trainable.

    →