Elevation-Adjusted Pace Calculator

Running uphill requires you to lift your body weight against gravity on every stride, which is metabolically expensive and directly increases oxygen demand at a given pace. Running downhill lets gravity do some of that work, so it's genuinely faster for a given effort — but only up to a point, because steep descents require increasing eccentric braking force in your legs to avoid losing control, which limits how much time you can actually save. This calculator uses a smaller per-foot benefit for descent (7.5 sec/mile per 100 ft) than penalty for climb (12.5 sec/mile per 100 ft) to reflect that asymmetry.

This calculator works from your course's total elevation gain and loss, not a detailed grade profile, so it produces one average pace adjustment for the whole course rather than adjusting mile-by-mile. A course with one concentrated steep climb and otherwise flat terrain will feel harder in that section and easier elsewhere than this single average number suggests, even though the total time adjustment across the whole course should be in the right ballpark.

Yes — for a true out-and-back or closed-loop course that starts and ends at the same elevation, total elevation gain and total elevation loss should be approximately equal (small differences come from GPS/barometric measurement noise). For a point-to-point course, gain and loss can differ substantially depending on whether the net elevation trends up or down over the route.

No — elevation gain and loss here refer to the up-and-down terrain profile of the course, not the absolute altitude above sea level. Running at high altitude (thin air, reduced oxygen availability) is a separate physiological effect from climbing and descending hills, and this calculator does not model it; a course that's both hilly and at high elevation would be harder than this tool's estimate alone suggests.