How it works
pace at altitude = sea-level pace × (1 + VO₂max loss)
This page keeps the calculation centered on one relationship: pace at altitude = sea-level pace × (1 + VO₂max loss). Inputs are normalized before the final display, which keeps mile, kilometer, pace, speed, or zone outputs from drifting because of rounding. Use the number as a consistent model output, then layer in terrain, weather, recovery, and race execution. Keep the fixed reference values in view: 1%, 1000 m, 1500 m, 6.3%, 2%, 6–12%, 2000–3000 m, 1991.Maximal oxygen uptake falls as you climb, and your sustainable running pace falls with it. The decline runs in two phases: up to 1500 m the loss is small — 1% per 1000 m — and above 1500 m it accelerates to 6.3% per additional 1000 m. In code terms the loss fraction is `0.01 × (altitude ÷ 1000)` below 1500 m, and `0.015 + 0.063 × ((altitude − 1500) ÷ 1000)` above it. At 2000 m that totals 1.5% + 6.3% × 0.5 = 4.65%, so a 5:00/km sea-level pace becomes 5:00 × 1.0465 ≈ 5:14/km. Altitude → pace slowdown — the exact two-phase model this calculator uses: | Altitude | Phase | Pace slowdown | | --- | --- | --- | | 500 m | ~1%/1000 m | 0.50% | | 1000 m | ~1%/1000 m | 1.00% | | 1500 m | break point | 1.50% | | 2000 m | ~6.3%/1000 m | 4.65% | | 2500 m | ~6.3%/1000 m | 7.80% | | 3000 m | ~6.3%/1000 m | 10.95% | Pace slowdown at common race altitudes, computed from the same constants: | Venue | Altitude | Slowdown | | --- | --- | --- | | Denver, CO | 1609 m | 2.2% | | Albuquerque, NM | 1619 m | 2.2% | | Boulder, CO | 1655 m | 2.5% | | Mexico City | 2240 m | 6.2% | | Leadville, CO | 3094 m | 11.5% | The model assumes you are not yet acclimatised; after one to three weeks at altitude the penalty shrinks as your body adapts (more red blood cells, better oxygen handling), though it rarely disappears entirely. On hilly mountain courses, layer the altitude penalty on top of the grade-adjusted pace calculator, and for hot, high venues pair it with the heat-adjusted pace calculator. Individual responses vary widely, so treat the figure as a planning estimate rather than a guarantee.
Sources
- Péronnet, Thibault & Cousineau (1991) Péronnet, F., Thibault, G., & Cousineau, D. (1991). “A theoretical analysis of the effect of altitude on running performance.” Journal of Applied Physiology 70(1), 399–404.
- VO₂ max decline with altitude Wehrlin, J. P., & Hallén, J. (2006). “Linear decrease in VO₂max and performance with increasing altitude in endurance athletes.” Eur. J. Appl. Physiol. 96, 404–412 — ~6–7% VO₂max loss per 1000 m at higher altitude.
- di Prampero (1986) di Prampero, P. E. (1986). “The energy cost of human locomotion on land and in water.” International Journal of Sports Medicine 7(2), 55–72 — maximal sustainable running velocity is directly proportional to maximal sustainable aerobic power (VO₂) and inversely proportional to the energy cost of running, so a VO₂max loss translates to a similar pace loss.
FAQ
When should I use the altitude adjusted pace calculator?
Use it when you want a fast planning number before a run, race, workout, or gear decision. It gives you a consistent estimate without asking you to create an account. Keep the fixed reference values in view: 1500 m, 1%, 1000 m, 6%, 2500–3000 m, 6–10%.
What inputs matter most?
The best result comes from honest, current inputs. Recent race times, realistic body measurements, accurate workout data, and the correct unit setting matter more than perfect formatting. Keep the fixed reference values in view: 1609 m, 5280, 2.2%, 5:00, 5:07, 40:00, 10, 40:53.
How should I read the result?
Treat the output as a planning reference, not a promise. Use it to compare options, set a target range, or sanity-check your watch data before making the final call. Keep the fixed reference values in view: ~2%, 4:00, 00 m, 5 m, 4:05, ~2240 m, ~6.2%, 15 m.
Does this work in miles and kilometers?
Yes. PacerRunning is written for US runners first, so miles are easy to use, but metric conversions are kept alongside them where the tool needs both views. Keep the fixed reference values in view: 1%, 1000 m, 1500 m, 6.3%, ~2000 m.
Why might my real-world result differ?
Terrain, wind, heat, sleep, fueling, training fatigue, and measurement error can all move the real outcome away from the estimate. The Altitude Adjusted Pace altitude adjusted pace calculator cannot see those details.
Can beginners use it?
Yes. You do not need advanced training knowledge. Enter the numbers you know, read the result as a guide, and keep your effort comfortable when you are unsure.
Can competitive runners use it too?
Yes. Faster runners can use the same output to check pacing, compare workouts, and keep training zones aligned with a recent performance.
Is this professional advice?
No. The result is general information for training and planning. For medical concerns, injury questions, nutrition treatment, or a personal race plan, work with a qualified professional.
When should I use the altitude adjusted pace calculator?
Use it when you want a fast planning number before a run, race, workout, or gear decision. It gives you a consistent estimate without asking you to create an account.
Altitude Adjusted Pace Calculator results are estimates from the entered data and the cited method. They are useful for planning and comparison, but they are not a diagnosis, prescription, guaranteed race result, or substitute for a coach or clinician.