Power Zone Calculator

Turn FTP into clear zone ranges so each workout targets the right physiological adaptation.

Enter FTP

Use the FTP value from your latest valid test.

Environment
Need FTP first? Open FTP Calculator

Calculate your power zones

Enter FTP and submit to generate Coggan training zones, target wattages, and Sweet Spot range.

Power Zone Calculator Method Guide

Evidence-based guide to FTP-derived power zones, indoor versus outdoor execution, target wattage selection, and practical weekly planning.

1) What power zones solve in real cycling training

Power zones translate one anchor value, usually FTP, into workout ranges with clear physiological intent. That translation matters because most riders do not fail from lack of motivation. They fail from poor load distribution, inconsistent execution, and unclear day-to-day intensity targets. A zone model improves repeatability by turning “ride hard” into measurable workloads.

For amateur cyclists, this is especially useful because weekly schedules are constrained by work, travel, and recovery variability. Power zones help you protect easy days, structure quality days, and keep training stress aligned with your available recovery. In practice, this prevents the common pattern of riding too hard on endurance days and arriving underprepared for threshold sessions.

Power zones are not magic. They are a decision framework. The framework works when FTP is reasonably current, sessions are fueled appropriately, and workouts are interpreted with context from perceived exertion and heart-rate response. Use zones as the backbone of planning, then refine individual sessions based on readiness and environmental conditions.

  • Zones reduce decision noise and improve week-to-week consistency.
  • The value comes from execution quality, not from the table alone.
  • Use power zones with recovery and fueling discipline for best outcomes.

Practical framing

Treat zone outputs as training targets, not as identity labels.

2) Formula A: converting FTP into zone boundaries

Each power zone is computed as a percentage interval of FTP. The equation is the same for every zone; only the multipliers change. For example, Endurance (Z2) uses lower multipliers than Threshold (Z4), and Neuromuscular (Z7) is open-ended because sprint work does not have a meaningful fixed ceiling in this model.

This mathematical simplicity is one reason zones are useful at scale. Coaches and athletes can recalculate instantly after an FTP update and keep a consistent structure across platforms. The difficult part is not the arithmetic. The difficult part is preserving protocol consistency so the FTP anchor is stable enough to support decisions.

FTP to zone equations

Pzone,low=a×FTPP_{zone,low} = a \times FTP
Pzone,high=b×FTPP_{zone,high} = b \times FTP

Where:

  • Pzone,lowP_{zone,low}lower boundary of a zone in watts
  • Pzone,highP_{zone,high}upper boundary of a zone in watts
  • a,ba,bzone-specific coefficients (for example 0.56 and 0.75 for Z2)
  • FTPFTPfunctional threshold power in watts

The model is linear with respect to FTP. A change in FTP scales every zone boundary automatically.

Example: FTP = 250 W gives Z2 low = 0.56 x 250 = 140 W and Z2 high = 0.75 x 250 = 188 W. Z4 becomes 228-263 W from 0.91-1.05 multipliers.

3) Formula B: selecting one actionable target inside each zone

A zone range is informative, but most athletes need one practical number during an interval. To reduce indecision, this calculator provides a target wattage. For bounded zones, the target is the midpoint of the range. For open-ended Z7, the target defaults to the zone minimum because a true midpoint is undefined.

This strategy is intentionally conservative. It avoids forcing athletes to ride near the upper bound on every interval, which can inflate fatigue and reduce completion quality. You can still bias high or low depending on freshness, but the midpoint gives a stable default for most sessions.

Target wattage rule

Ptarget=Plow+Phigh2(bounded zones)P_{target} = \frac{P_{low} + P_{high}}{2} \quad (\text{bounded zones})
Ptarget=Plow(open-ended zones)P_{target} = P_{low} \quad (\text{open-ended zones})

Where:

  • PtargetP_{target}displayed target wattage
  • PlowP_{low}zone lower boundary in watts
  • PhighP_{high}zone upper boundary in watts

This rule standardizes execution and limits decision friction during workouts.

Example: Z4 range 228-263 W yields midpoint target 246 W. Z7 uses the lower bound as target because the upper value is open.

Primary Sources for This Section

4) Formula C: indoor versus outdoor effective FTP

Riders often experience indoor and outdoor differences in sustainable power. Causes include airflow, thermal strain, trainer setup, motivation profile, and positional differences. To handle this without rewriting the zone framework, the calculator supports an indoor mode that reduces effective FTP by a configurable percentage.

The default reduction is 5%, bounded between 0 and 10%. This is a practical execution setting, not a universal physiological law. Some athletes need no adjustment, while others consistently perform better outdoors. The correct choice is the one that improves completion quality across repeated sessions in your environment.

Environmental effects are not theoretical. Published data shows that cycling performance and reliability can differ across indoor and outdoor contexts and across weather conditions. Instead of ignoring that variability, the model makes the assumption explicit so training targets remain realistic and auditable.

Environment-adjusted FTP

FTPeffective=FTP(outdoor)FTP_{effective} = FTP \quad (\text{outdoor})
FTPeffective=FTP×(1r100)(indoor)FTP_{effective} = FTP \times \left(1 - \frac{r}{100}\right) \quad (\text{indoor})

Where:

  • FTPeffectiveFTP_{effective}FTP used by the calculator for zone math
  • FTPFTPinput FTP from recent testing history
  • rrindoor reduction percentage (default 5; range 0-10)

Use indoor reduction only when it improves repeatability and session completion indoors.

Example: FTP 250 W with indoor reduction 5% gives effective FTP 238 W. All zone boundaries and targets are then computed from 238 W.

Execution check

If indoor threshold workouts repeatedly fail while outdoor sessions pass, adjust indoor FTP assumptions before adding more intensity.

5) Formula D: Sweet Spot as a practical sub-threshold lane

Sweet Spot is explicitly included because many amateur cyclists use it for time-efficient quality work. It typically sits below threshold but above classic endurance intensity, often balancing stimulus and repeatability better than frequent threshold-max sessions.

The key coaching point is dosage. Sweet Spot is productive when blended with enough low-intensity volume and appropriate recovery. Overusing it can create chronic fatigue and flatten adaptation. That is why the calculator surfaces Sweet Spot as one lane inside a broader weekly structure, not as a full training system.

Sweet Spot equations

PSS,low=0.88×FTPeffectiveP_{SS,low} = 0.88 \times FTP_{effective}
PSS,high=0.94×FTPeffectiveP_{SS,high} = 0.94 \times FTP_{effective}

Where:

  • PSS,lowP_{SS,low}Sweet Spot lower boundary in watts
  • PSS,highP_{SS,high}Sweet Spot upper boundary in watts
  • FTPeffectiveFTP_{effective}environment-adjusted FTP used by the calculator

Sweet Spot is a planning target, not a fixed biological threshold.

Example: effective FTP 238 W gives Sweet Spot 209-224 W with midpoint target 217 W for sustained interval sets.

6) Weekly application: using zones without overtraining

Most amateur cyclists improve by keeping weekly intensity distribution disciplined. A common pattern is high volume in Z1-Z2, selected quality work in Sweet Spot or threshold, and limited high-intensity intervals in Z5-Z6. The exact split should reflect your race calendar, fatigue profile, and available hours.

A practical weekly structure might include one long Z2 ride, one Sweet Spot or threshold session, one shorter high-intensity workout, and one or two easy recovery rides. The objective is not to maximize daily suffering. The objective is to accumulate repeatable high-quality work over months.

Use your zone outputs with session feedback. If prescribed power is repeatedly unattainable at normal recovery levels, reassess FTP assumptions, sleep quality, thermal conditions, and fueling. The strongest plans are adaptable while still respecting structure.

  • Prioritize consistency over occasional maximal days.
  • Keep true recovery rides easy enough to preserve quality sessions.
  • Use heart-rate and RPE trends to validate power-target realism.

7) Session workload estimate from target watts and duration

The session planner output includes an estimated work value in kilojoules. This is intentionally simple and transparent. It is useful for comparing planned sessions before you ride, especially when two sessions differ in duration and intensity. Many cyclists find this easier to interpret than abstract score systems when deciding whether a week is escalating too quickly.

For a coach or self-coached rider, kJ helps frame progression. If two threshold sessions look similar in duration but one carries significantly higher target watts, you can quantify the jump before committing. This can prevent accidental overload and improve week-to-week planning quality, especially for riders balancing training with non-sport stress.

This metric should be used as a planning aid, not as a standalone readiness indicator. Always interpret with context: completion quality, heart-rate behavior, sleep, and perceived exertion. A mathematically similar workload can feel very different depending on recovery state and environment.

Mechanical work estimate

WorkkJ=Ptarget×tseconds1000Work_{kJ} = \frac{P_{target} \times t_{seconds}}{1000}

Where:

  • WorkkJWork_{kJ}estimated mechanical work in kilojoules
  • PtargetP_{target}selected target power in watts
  • tsecondst_{seconds}session duration in seconds

Work estimate supports planning comparisons and progression control across sessions.

Example: 217 W Sweet Spot target for 60 minutes gives Work = (217 x 3600) / 1000 = 781 kJ.

Primary Sources for This Section

8) Power zones and heart-rate context should be used together

Power is an external workload metric. Heart rate is an internal response metric. They answer different questions and work best together. During short intervals, power is usually the better pacing anchor because heart rate lags. During long steady rides, heart-rate drift adds valuable context about thermal strain, hydration, and fatigue.

If you repeatedly hit target watts but see unusually high internal strain, the right next step is usually environment and recovery troubleshooting, not immediate zone inflation. Conversely, if heart rate stays unusually low while power targets are easy, it may be time to reassess FTP with a consistent protocol.

Combining these signals improves decision quality and reduces false conclusions. Keep your zone model stable first, then investigate repeated mismatches across multiple sessions before changing core assumptions.

  • Use power for pacing precision and heart rate for physiological context.
  • Evaluate repeated patterns before changing FTP or zone assumptions.
  • Preserve easy-day discipline to support high-quality hard days.

9) Worked example: outdoor and indoor outputs for the same rider

Rider profile: FTP 250 W, body mass 70 kg. Outdoor mode gives effective FTP 250 W and W/kg 3.57. Core zone outputs become Z2 = 140-188 W, Z4 = 228-263 W, and Sweet Spot = 220-235 W. Midpoint targets are 164 W in Z2, 246 W in Z4, and 228 W in Sweet Spot.

Switching to indoor mode with a 5% adjustment gives effective FTP 238 W and W/kg 3.40. Zone targets shift downward, which can improve completion quality on trainer-based sessions if heat and airflow control are limited. This is not reducing ambition. It is matching workload to context so adaptation is sustainable.

Training implication: if outdoor threshold sessions succeed but indoor threshold sessions fail at equivalent nominal watts, preserve the same weekly intent and apply indoor effective FTP. Re-evaluate after your next testing block and indoor setup changes (for example airflow and cooling).

10) Quality-control checklist and common mistakes

Most zone errors come from process drift, not formula bugs. Common mistakes include using stale FTP values, overusing hard zones, ignoring indoor-outdoor mismatch, and treating one missed session as proof that all zones are wrong. These patterns create noise and lead to avoidable training frustration.

Before changing your zones, run a short audit: Is FTP recent? Was the test protocol consistent? Are missed sessions isolated or repeated under similar conditions? Are fueling, sleep, and heat management adequate? This sequence avoids reactive adjustments and improves decision quality.

Your goal is not perfect precision on every ride. Your goal is robust training decisions over weeks. When you combine transparent formulas, realistic assumptions, and disciplined execution, zone models become reliable tools for long-term progression.

  • Re-test FTP on a consistent protocol cadence.
  • Adjust indoor assumptions only when repeated evidence supports it.
  • Act on patterns across sessions, not single-session outliers.

Do not over-interpret

A one- or two-watt difference is less important than trend direction, execution quality, and recovery tolerance.

Interpretation

  • Each zone exists for a specific training purpose. More intensity is not always better.
  • Zone quality depends on current FTP accuracy; stale FTP values produce stale zones.
  • Track time-in-zone distribution across weeks to balance fatigue and adaptation.

What to Do Next

  • Use Zone 2 volume as the base of weekly training load.
  • Schedule threshold and VO2 work with recovery spacing based on current readiness.
  • Rebuild zones after each valid FTP update.

Methodology

Version v2.0
Updated 2026-03-03
Owner Cycling Regimen Editorial
  • Coggan Zone Framework

    Zone boundaries are derived from FTP percentages and aligned with common structured training practice.

  • Execution Guidance

    Training outcomes depend on repeating high-quality sessions inside intended zone bands.

    Read source
  • Documentation and Versioning

    Formula governance and update notes are published in methodology resources.

    Read source

Frequently Asked Questions

How often should I update power zones?

Update zones every time FTP changes materially, typically every 4 to 8 weeks.

Can I train only with Zone 2?

Zone 2 is foundational but not sufficient for all goals. Include threshold and high-intensity work as appropriate.

Should indoor and outdoor zones be identical?

Not always. If your indoor and outdoor FTP differ consistently, maintain separate zones for each context.

What is the difference between power zones and heart rate zones?

Power zones represent external workload in watts, while heart rate zones represent internal strain response. Use both together for better pacing and fatigue awareness. See /tools/heart-rate-zones.

Disclaimer: This calculator provides estimates based on published exercise science models. Results are not medical advice. Individual physiology, health status, and environmental conditions affect real-world outcomes. Consult a qualified healthcare provider or certified coach before making training decisions based on these outputs.