Running Power Explained: Training with Watts
Your Stryd says 230W, your Garmin says 285W, and your COROS says 250W for the same run. Unlike cycling, running power is calculated, not measured. Here is what the numbers mean, why they disagree, and when watts actually help you train smarter.
- Running power is not directly measured like cycling power. It is estimated from accelerometers, barometric altitude, GPS, and body weight using proprietary algorithms. Different devices produce systematically different numbers for the same run.
- Stryd (foot pod), Garmin (wrist/chest), COROS (wrist), and Apple Watch each use different sensor placements and models. Stryd is the most consistent and widely validated, but no device measures true mechanical power output at the ground.
- Critical Power (CP) and running Functional Threshold Power (rFTPw) are the key anchor metrics for power-based training zones. They represent the boundary between sustainable and unsustainable intensity — analogous to lactate threshold for heart rate training.
- Power excels where pace fails: hills, wind, trails, and treadmills. On flat road races, pace remains the simpler and more reliable metric. The strongest use case for running power is maintaining even effort on variable terrain.
- Running power numbers cannot be compared between devices — a 250W reading on Stryd and 250W on Garmin represent different things. Always use a single device ecosystem for your training data and treat the numbers as internal reference points, not absolute values.
Table of Contents
What Is Running Power?
In cycling, power is a direct physical measurement: a strain gauge in the crank or pedal hub measures the torque you apply, multiplied by angular velocity, yielding watts of mechanical work. It is one of the most precise metrics in sports science, accurate to within 1-2%. Running power, by contrast, is an estimation. No commercially available running power device directly measures the forces between your foot and the ground in real time during normal running. Instead, every running power meter uses a mathematical model — fed by accelerometer data, barometric pressure changes, GPS speed, and your body weight — to estimate the metabolic or mechanical cost of your running.
The concept was first explored by researchers like C.T.M. Davies in the 1980s, who modeled the energetic cost of running as the sum of work done against gravity, air resistance, and kinetic energy changes. The 2016 launch of Stryd brought running power to the consumer market, followed by Garmin's Running Power Connect IQ app (2017), COROS's native implementation (2019), and Apple Watch's estimated running power (2023). Each vendor adapted the underlying physics differently, which is why the same run produces different watt values across devices.
What running power attempts to capture is the intensity of your effort — a single number that accounts for speed, gradient, wind, and terrain simultaneously. On a flat road at constant pace, power and pace tell you roughly the same thing. But on a hilly course, into a headwind, or on a technical trail, pace becomes unreliable as an effort indicator while power (in theory) stays consistent. This is the core value proposition: power as a universal effort metric that works where pace does not.
How Running Power Is Calculated
Running power models generally estimate the rate of mechanical work by summing the energy costs of several components. While each vendor's exact algorithm is proprietary, the general framework follows principles established in the biomechanics literature, particularly the work of Minetti (2002) and Kram & Taylor (1990).
The Component Model
Horizontal Kinetic Energy
The energy required to accelerate and decelerate your center of mass in the horizontal plane. Calculated from changes in speed over time using accelerometer and GPS data. This is the dominant component on flat terrain.
Vertical (Gravitational) Work
The work done against gravity when running uphill, calculated as mass x gravity x elevation gain. Derived from barometric altimeter data. On steep hills, this can exceed the horizontal component. On downhill sections, the model must estimate how much gravitational energy is recovered versus absorbed.
Air Resistance
Aerodynamic drag, modeled as 0.5 x Cd x A x rho x v-squared, where Cd is the drag coefficient, A is frontal area, rho is air density, and v is speed relative to the air. Stryd measures wind directly with an anemometer; other devices either ignore air resistance or estimate it from GPS-derived speed only, which misses headwind and tailwind.
Oscillatory Work
The energy spent in vertical oscillation — bouncing up and down with each stride. Measured by the accelerometer's vertical axis. Runners with higher vertical oscillation waste more energy and may show higher power at the same pace.
The critical difference between vendors lies in which components they include, how they weight them, and what sensors they use. Stryd's foot pod measures ground-level acceleration with high precision and includes a wind sensor. Garmin uses wrist-based accelerometry and optionally chest-strap data from the HRM-Pro, which provides running dynamics but no wind measurement. COROS relies on wrist accelerometry with their EvoLab algorithm. Apple Watch uses a combination of accelerometer and GPS data with a machine learning model.
A fundamental limitation of all running power models is that they estimate external mechanical work but cannot directly measure the internal metabolic cost. Two runners with different running economy producing the same mechanical work will have different oxygen consumption — the power number cannot distinguish between them. This is a key difference from cycling power, where mechanical output at the pedal is tightly coupled to metabolic demand regardless of pedaling technique.
Device Comparison: Stryd vs Garmin vs COROS vs Apple Watch
Choosing a running power device means choosing an ecosystem. The numbers are not interchangeable between platforms, so the decision locks you into a particular set of reference values. Here is how the major options compare.
| Device | Sensor Location | Wind Detection | Price Range | Zone System | Ecosystem |
|---|---|---|---|---|---|
| Stryd | Foot pod (shoe clip) | Yes (built-in anemometer) | $220-350 | CP-based auto zones | Stryd app + PowerCenter + compatible watches |
| Garmin Running Power | Wrist + optional HRM-Pro chest strap | No | Free (included with compatible watches) | Manual or auto (FTP-based) | Garmin Connect + native watch display |
| COROS | Wrist (built into COROS watches) | No | Free (included with COROS watches) | Threshold Power auto-detected | COROS app + EvoLab analytics |
| Apple Watch | Wrist (built-in sensors + GPS) | No | Free (watchOS 17+) | Manual setup in Workout app | Apple Health + Fitness app |
Stryd: The Dedicated Power Meter
Stryd is the only device purpose-built for running power measurement. The foot pod sits on your shoe, placing the accelerometer at ground level where it captures foot-ground interaction more accurately than a wrist sensor. The built-in wind sensor (anemometer) allows Stryd to adjust power for headwinds and tailwinds — a capability no wrist-based device offers. Stryd's Critical Power algorithm auto-calculates training zones from your run history, and their PowerCenter web platform provides detailed analytics including power duration curves and race power planning. Independent validation by Cerezuela-Espejo et al. (2020) found Stryd power correlated well (r = 0.911) with metabolic rate during level running. The main limitation is cost and the requirement to carry an extra device.
Garmin Running Power
Garmin offers running power either through the Connect IQ app (older approach) or natively on newer watches like the Forerunner 265/965 and Fenix 7+. When paired with the HRM-Pro chest strap, Garmin captures running dynamics (ground contact time, vertical oscillation, stride length) that feed into the power calculation. Without the chest strap, it relies solely on wrist-based accelerometry and GPS. Garmin's numbers tend to read 10-30% higher than Stryd for the same effort because their model includes a larger estimated metabolic overhead. Garmin power is best used as a trend metric within the Garmin ecosystem rather than compared to any other device's numbers.
COROS EvoLab Power
COROS integrates running power natively across their watch lineup (PACE 3, VERTIX 2, APEX 2). Their EvoLab algorithm uses wrist-based motion data and GPS to estimate power and automatically detects your threshold power from training data. COROS power values typically fall between Stryd and Garmin values. The platform provides training load analysis, fitness and fatigue tracking, and race predictions based on power data. Like Garmin, the absence of a wind sensor means COROS power does not account for aerodynamic conditions.
Apple Watch
Apple introduced running power estimation in watchOS 17, available on Apple Watch Series 8 and later. It uses the built-in accelerometer, gyroscope, and GPS with a machine learning model trained on metabolic cart data. Apple's implementation is the newest and least independently validated. Power data appears in the Workout app and Apple Health but currently lacks the detailed analytics ecosystem (power duration curves, auto-zones, CP tracking) that Stryd, Garmin, and COROS provide. For runners already in the Apple ecosystem who want a basic power reference, it is a zero-cost addition.
Key Metrics: CP, rFTPw, and Power Zones
Power-based training requires anchor metrics to set meaningful zones. The two primary concepts are Critical Power (CP) and running Functional Threshold Power (rFTPw). Though related, they come from different theoretical frameworks.
Critical Power (CP)
Critical Power is a mathematically derived threshold from the power-duration relationship, first described by Monod & Scherrer in 1965. It represents the highest power output that can theoretically be sustained indefinitely — the asymptote of your power-duration curve. In practice, CP corresponds to roughly a 30-40 minute all-out effort, close to but not identical to lactate threshold. The mathematics behind CP is elegant: the relationship between power (P) and time to exhaustion (t) follows the hyperbolic model: (P - CP) x t = W', where W' (pronounced "W-prime") is the fixed amount of work you can perform above CP before exhaustion. W' represents your anaerobic work capacity — your "battery" above threshold.
Stryd calculates CP automatically from your training history using the power-duration curve. A well-trained male distance runner might have a Stryd CP of 230-280W, while a well-trained female runner might be 180-230W. These values are highly individual and depend on body weight, fitness, and running economy. Jones et al. (2019) validated the CP concept for running, confirming that it closely approximates the maximal lactate steady state when properly modeled.
Running Functional Threshold Power (rFTPw)
rFTPw is the running equivalent of cycling's FTP — the power you can sustain for approximately one hour. While CP is a mathematical model parameter, rFTPw is typically estimated from a 20-30 minute time trial (then taking 95% of the average power for 20 minutes, or 100% for 30 minutes). Garmin and COROS use threshold power concepts similar to rFTPw for their zone calculations. For most runners, CP and rFTPw are within 3-5% of each other, with CP slightly higher because it represents a shorter sustainable duration.
Power Zones
Most power-based training systems use 5-7 zones derived from CP or rFTPw. Below is a typical zone structure used by Stryd and similar platforms.
| Zone | % of CP | Name | Purpose |
|---|---|---|---|
| 1 | < 80% | Easy / Recovery | Recovery runs, warm-up, cool-down. Builds aerobic base without stress. |
| 2 | 80-90% | Moderate / Aerobic | Standard easy runs, long runs. Primary aerobic development zone. |
| 3 | 90-100% | Threshold | Tempo runs, marathon pace. Sustainable hard effort at or near CP. |
| 4 | 100-115% | VO2 Max / Interval | Hard intervals (3-8 min). Develops aerobic power and VO2 Max. |
| 5 | > 115% | Anaerobic / Sprint | Short repeats (30s-2min). Develops speed, power, and anaerobic capacity. |
Testing your CP or rFTPw is straightforward: perform a 3-minute and a 9-minute all-out time trial (for CP calculation) or a single 20-30 minute time trial (for rFTPw). Stryd can also estimate CP from accumulated training data without a dedicated test — its algorithm analyzes your best efforts at various durations from normal training to construct the power-duration curve. Whichever method you use, retest every 4-8 weeks during focused training to track fitness changes.
Power vs Pace: When to Use Which
Running power and pace are not competing metrics — they are complementary tools suited to different situations. Understanding when each excels prevents you from over-complicating simple workouts or under-utilizing power where it genuinely helps.
| Scenario | Power | Pace | Better Metric |
|---|---|---|---|
| Flat road race (5K-Marathon) | Consistent but offers little advantage over pace on flat terrain | Direct, simple, proven. Splits are what matter for race time. | Pace |
| Hilly race or training | Automatically adjusts for gradient — even effort means varying pace | Misleading: slowing on uphills looks like fading, speeding downhill feels easy but may waste energy | Power |
| Trail and ultra running | Handles terrain changes, technical sections, and gradient seamlessly | Nearly useless — GPS pace on twisty trails is inaccurate, and pace varies wildly with terrain | Power |
| Treadmill running | Reflects effort accurately (especially Stryd, which measures foot pod acceleration independent of GPS) | Treadmill-displayed pace is often inaccurate by 5-10% | Power |
| Windy conditions | Only Stryd adjusts for wind. Other devices ignore it. | Does not account for wind resistance at all | Power (Stryd only) |
| Flat intervals (track) | Adds complexity without meaningful benefit over lap splits | Simple and precise — split times are the gold standard for track work | Pace |
| Monitoring fatigue over long runs | Power decoupling (pace drops while power stays constant) reveals fatigue patterns | Pace decline could be terrain, wind, or fatigue — harder to isolate the cause | Power |
The practical summary: if your running is predominantly flat road running and track work, pace does the job well and power adds unnecessary complexity. If you regularly run hills, trails, treadmills, or in variable weather, power provides a more consistent effort metric. Many experienced runners use both — pace for flat racing and intervals, power for hilly long runs and trail running. The transition from "pace-only" to "power-aware" does not need to be all-or-nothing.
The Grade Adjusted Pace Alternative
Grade Adjusted Pace (GAP), offered by Garmin and Strava, attempts to solve the same problem as power on hills by estimating what your pace would be on flat terrain. GAP has the advantage of being intuitive — it is still expressed in min/km or min/mile. However, GAP relies on elevation data quality (which can be poor with GPS-derived altitude) and does not account for wind, surface, or vertical oscillation. For runners who find power numbers unintuitive, GAP is a reasonable intermediate tool. For a detailed analysis of GAP, see our Grade Adjusted Pace article.
Training with Power
Once you have established your CP or rFTPw and set zones, power becomes a practical tool for several training applications.
Pacing with Power: Even Effort Strategy
The most impactful application of running power is pacing on variable terrain. The principle is simple: instead of targeting a constant pace (which means surging on downhills and crawling on uphills), target a constant power output. This produces an even physiological effort — your heart rate, oxygen consumption, and lactate production stay more consistent throughout the run. Research by Poole et al. (1988) on cycling and confirmed in running by Denadai et al. (2006) showed that even pacing strategies optimize glycogen utilization and delay fatigue compared to variable pacing at the same average speed.
For a hilly marathon, this means planning a target power rather than a target pace. If your CP is 260W and you plan to race at 90% CP, your target is 234W — hold that number regardless of whether you are going uphill (where your pace will slow) or downhill (where your pace will quicken). Your body does not care about your GPS pace; it cares about the rate of energy expenditure.
Monitoring Training Load and Fatigue
Power enables quantitative training load tracking through the concept of Training Stress Score (TSS) or its running equivalents (rTSS, Stryd's RSS). The formula integrates the intensity and duration of each run: a 60-minute easy run at 75% CP produces far less training stress than a 60-minute tempo at 95% CP, even though both lasted an hour. Tracking weekly TSS helps prevent the two most common training errors: under-recovery (chronic TSS too high) and stagnation (chronic TSS plateau).
Detecting Fatigue: Power-Heart Rate Decoupling
One of the most insightful power applications is monitoring the relationship between power and heart rate over time. In a fresh, well-rested state, your power-to-heart-rate ratio is relatively stable. As fatigue accumulates — either within a single long run or across a training block — heart rate rises while power output at the same perceived effort declines. This "decoupling" is a quantitative fatigue signal. A decoupling of greater than 5% during a long run suggests your aerobic fitness at that duration is still developing. Tracking this metric over months reveals whether your aerobic base is genuinely improving.
Tracking Fitness via CP/rFTPw Trends
Your Critical Power or rFTPw over time is a straightforward fitness indicator. Unlike VO2 Max estimates from watches (which depend on HR-pace algorithms and can be confounded by temperature, fatigue, and cardiac drift), CP is derived directly from your best actual performances at various durations. If your CP rises from 240W to 255W over a 12-week training block, that is an unambiguous fitness improvement — assuming consistent body weight. Stryd's Power Duration Curve provides a visual representation of this: the entire curve shifting upward means you are producing more power at every duration.
Limitations and Caveats
Running power is a useful tool, but it is important to understand what it cannot do and where its claims outrun the science.
Estimation, Not Measurement
The most fundamental limitation. Cycling power meters directly measure mechanical force. Running power devices estimate it from indirect sensor data. The accuracy of the estimate depends on model assumptions that may not hold for all runners, all terrains, or all conditions. Kipp et al. (2019) demonstrated that wrist-based power estimates had significantly higher variability than foot-pod estimates when validated against metabolic cost.
No Standardized Model
In cycling, a watt is a watt — a Stages power meter and a Garmin power meter produce interchangeable numbers because they both measure the same physical quantity (torque x angular velocity). In running, each vendor uses a different model with different inputs and assumptions. A 250W reading on Stryd, Garmin, and COROS does not represent the same thing. This fragmentation means running power lacks the universal comparability that makes cycling power so powerful.
Running Economy Is Invisible
Two runners at the same power output can have drastically different oxygen consumption — and therefore different sustainable durations — because of differences in running economy. Power does not capture tendon elasticity, neuromuscular efficiency, or biomechanical efficiency. A runner who improves their economy (through strength training or technique refinement) may get faster at the same power without the power number changing.
Weight Sensitivity
Most running power models include body weight as an input (either explicitly or implicitly through acceleration data). If you do not update your weight in the device settings, power readings will drift. A 3kg weight change can shift power by 3-5%. This also means power-to-weight ratio (W/kg), not absolute watts, is the more meaningful metric for comparing across runners of different sizes — similar to VO2 Max being expressed per kg.
Terrain and Surface Effects
Running on sand, grass, or soft trail consumes more energy than running on asphalt at the same speed, but the degree to which power models account for surface compliance varies by device. Stryd's foot pod captures some of this through ground contact dynamics, but wrist-based devices largely miss it. This means your power data may not fully reflect the additional cost of soft terrain.
The Overhead Problem
Some power models (notably Garmin) include an estimated metabolic overhead — the baseline energy cost of running beyond mechanical work (heat dissipation, respiratory work, etc.). Others (like Stryd) focus primarily on external mechanical power. This philosophical difference in what "running power" should represent explains much of the numerical gap between devices and remains an unresolved debate in the field.
None of these limitations make running power useless. They mean it should be used as one tool among several — complementing pace, heart rate, and perceived exertion — rather than as a single source of truth. The runners who benefit most from power are those who understand what it measures and what it does not, and who use it in the specific situations where it adds genuine value.
Getting Started with Running Power
If you have decided to incorporate running power into your training, here is a practical roadmap for getting started without overcomplicating things.
Choose Your Device Based on Your Needs
If you want the most accurate and full-featured running power experience with wind detection, choose Stryd. If you already own a Garmin or COROS watch and want to explore power without additional cost, use the built-in power metric. If you are an Apple Watch user, enable power in your workout settings. The most important rule is: pick one ecosystem and stay with it. Mixing devices makes your historical data meaningless.
Establish Your Baseline (CP or rFTPw)
Before doing anything with power zones, you need an anchor value. Option A: let your device auto-detect from 4-6 weeks of normal varied training (Stryd and COROS support this). Option B: perform a dedicated test — a 3-minute plus 9-minute time trial for CP, or a 30-minute time trial for rFTPw. Option C: use a recent race result to estimate. Do not skip this step — training by power without a calibrated threshold is like training by heart rate without knowing your max HR.
Start with Power for Easy Runs Only
The lowest-risk way to begin is using power to cap your easy run intensity. Set a power ceiling at 80% of your CP and run by feel within that limit. This prevents the common error of running "easy" runs too hard — a problem that power catches earlier than heart rate (which lags) or perceived exertion (which is subjective). Once you are comfortable reading power data in real time, expand to using it for tempo runs and long runs.
Use Power for Hilly Runs and Races
This is where power earns its keep. On your next hilly long run, set a target power and let pace fluctuate. Compare how you feel in the final third of the run versus your typical experience when pacing by pace alone. Most runners report feeling significantly fresher in the closing kilometers when they pace by power on hilly courses. For a hilly race, plan your power target as 85-92% of CP depending on race distance.
Review Power Duration Curve Monthly
If your platform provides a power duration curve (Stryd, Garmin, COROS all do in some form), review it monthly. A rising curve at durations relevant to your goal race means your fitness is improving. Plateaus suggest your training needs adjustment. This is often more informative than VO2 Max estimates because it is based on your actual performances, not algorithmic estimates.
Common Beginner Mistakes to Avoid
Do not compare your watt numbers to other runners — body weight, device, and running economy make absolute values meaningless for comparison. Do not obsess over power fluctuations during a run — look at lap or segment averages, not second-by-second data. Do not abandon pace entirely — on flat terrain, pace is still king. And do not change your training structure just because you added a power metric — the underlying physiology has not changed, only your measurement tool.
The runners who get the most from power are those who adopt it gradually, use it where it adds clear value, and resist the temptation to let a new number dictate their entire training philosophy. Power is a lens, not a prescription.
Frequently Asked Questions
What is a good running power?
There is no universal "good" running power number because values depend entirely on body weight, device, and running economy. A more meaningful metric is power-to-weight ratio (W/kg). For context, a well-trained male marathon runner might have a Critical Power of 4.0-4.5 W/kg on Stryd, while a recreational runner might be 2.5-3.5 W/kg. However, these numbers are device-specific — a Garmin power reading is not comparable to a Stryd reading. Focus on your own trends over time rather than any absolute target.
Is running power more accurate than pace?
"Accurate" depends on what you are measuring. Pace tells you exactly how fast you are covering ground — it is inherently precise. Power tells you approximately how hard you are working — it is an estimation of effort. On flat terrain with no wind, pace is more precise and more useful. On hills, trails, treadmills, or in wind, power provides a more consistent indicator of physiological effort. Neither is universally "more accurate" — they measure different things.
Do I need a Stryd to use running power?
No. Garmin, COROS, and Apple Watch all provide running power estimates at no additional cost beyond the watch itself. Stryd offers higher consistency (foot-pod placement is more reliable than wrist-based accelerometry), wind detection, and a more mature analytics platform. Whether the added accuracy and features justify the $220-350 investment depends on how seriously you plan to train by power and whether you run in conditions (hills, wind, trails) where power's advantages are most pronounced. For casual exploration of running power, your existing watch is sufficient.
What is Critical Power in running?
Critical Power (CP) is the highest power output you can theoretically sustain indefinitely — the mathematical asymptote of your power-duration curve. In practice, it corresponds roughly to a 30-40 minute maximal effort, close to your maximal lactate steady state. The concept originates from Monod and Scherrer (1965) and was validated for running by Jones et al. (2019). CP serves as the primary anchor for setting training zones in power-based training systems. It divides sustainable (below CP) from unsustainable (above CP) intensity.
Why is my Garmin power different from Stryd?
Garmin and Stryd use fundamentally different algorithms, sensor placements, and model assumptions. Garmin includes a larger estimated metabolic overhead component and uses wrist-based or chest-strap accelerometry, while Stryd uses foot-pod accelerometry and includes wind resistance data. Garmin power readings are typically 10-30% higher than Stryd for the same run. This is not an error — they are measuring different things. Never compare absolute numbers between devices. Pick one and use it consistently.
Should I train by power or heart rate?
They are complementary, not competing. Heart rate tells you what your cardiovascular system is doing in response to effort — it reflects internal physiological strain. Power tells you what mechanical work your body is producing — it reflects external output. Heart rate lags behind changes in effort by 30-120 seconds and is affected by temperature, caffeine, stress, and fatigue. Power responds instantaneously and is effort-specific. For setting initial intensity in workouts, power is superior. For monitoring cumulative fatigue and recovery status, heart rate provides information power cannot. Most sophisticated training approaches use both.
How do I calculate my running power zones?
First establish your CP or rFTPw through testing or auto-detection. Then apply percentage-based zones. A standard 5-zone system based on CP is: Zone 1 (Easy) below 80%, Zone 2 (Moderate) 80-90%, Zone 3 (Threshold) 90-100%, Zone 4 (VO2 Max) 100-115%, Zone 5 (Anaerobic) above 115%. Stryd calculates these automatically. On Garmin or COROS, you can set power zones manually or use their auto-detected threshold power. Retest or recalibrate every 4-8 weeks as your fitness changes.
Is running power useful for marathon training?
Yes — the marathon is arguably where running power provides the most value. Marathon pacing on hilly courses is notoriously difficult by pace alone because the natural tendency is to push too hard on uphills and not recover enough on downhills. A power-based pacing strategy targets a consistent effort (typically 85-90% CP) regardless of terrain, which optimizes glycogen usage and delays the fade in the final 10K. Stryd's Race Power Calculator specifically helps plan marathon target power based on your fitness profile.
Does body weight affect running power?
Yes, significantly. Heavier runners produce higher absolute power at the same pace because moving more mass requires more energy. This is why power-to-weight ratio (W/kg) is more meaningful than absolute watts for comparing fitness. If you lose or gain weight without updating your device settings, your power readings will be inaccurate. A 3kg weight change typically shifts power readings by 3-5%. Always keep your weight current in your power meter's settings.
Can I compare running power between devices?
No. Running power values are device-specific and not interchangeable. A 250W reading on Stryd, Garmin, and COROS represents three different things calculated by three different algorithms. This is unlike cycling where a watt is a watt across devices. If you switch devices, your historical power data becomes a different reference frame. You will need to re-establish your baseline CP/rFTPw on the new device. This is the single biggest limitation of the running power ecosystem.
What is W' (W-prime) and why does it matter?
W' (pronounced "W-prime") is the total amount of work you can perform above your Critical Power before exhaustion — essentially your anaerobic battery. It is measured in kilojoules (kJ) and is fixed for a given fitness state. If your CP is 250W and you run at 300W, you are draining W' at a rate of 50 joules per second. When W' reaches zero, you must slow to CP or below. Understanding W' helps with race tactics: it tells you how much above-threshold effort you can budget for surges, hills, or a final kick. Typical W' values for trained runners range from 15-25 kJ.
How long does it take to see running power benefits?
Most runners report noticeable benefits within 4-6 weeks of consistent use, primarily from improved pacing on hilly terrain and better easy run discipline. The device needs 2-4 weeks of varied training data to auto-calculate a reliable CP. Meaningful fitness tracking via power trends requires at least 8-12 weeks of data. The full benefit of power-based training — including refined zone calibration and power-duration curve analysis — typically develops over 3-6 months as you accumulate enough data points across different workout types and conditions.
Is Stryd validated by research?
Stryd has been the subject of several peer-reviewed validation studies. Cerezuela-Espejo et al. (2020) found that Stryd power correlated strongly (r = 0.911) with metabolic rate during level treadmill running. Garcia-Pinillos et al. (2019) validated Stryd's reliability across repeated trials, finding a coefficient of variation below 3%. Austin et al. (2021) compared Stryd to metabolic cost during uphill running and found reasonable accuracy for gradient-adjusted power. However, no study has found perfect agreement between Stryd power and true metabolic cost across all conditions — the estimation gap widens on steep hills and at very high speeds. Stryd is the best-validated running power device, but it remains an estimate.
Analyze Your Power Data
Upload a FIT file from your Garmin, COROS, or Stryd to see detailed power charts alongside heart rate, pace, and elevation — including per-lap power breakdowns and zone distribution.
Try the FIT Viewer