How to Read an Elevation Profile
Understand the elevation profile of any run or ride — grade, total gain, how hills change your pace, and why GPS elevation is noisy — then read your own GPX in the browser.
An elevation profile is the side-on picture of a route: distance runs along the bottom, height runs up the side, and the line between them shows every climb and descent you will meet. Learning to read it is the difference between being surprised by a wall at kilometre 30 and pacing it deliberately.
Grade is the number that matters
Grade (or gradient) is how steep a section is, written as a percentage: the height gained divided by the horizontal distance covered. A 100 m climb over 1,000 m of road is a 10% grade. On a profile, a short steep ramp and a long gentle drag can gain the same height, but they feel completely different — which is why grade, not just total gain, drives effort.
How hills change your pace
Running uphill costs extra energy roughly in proportion to the grade, while running downhill gives only a fraction of it back (and steep descents actually cost energy through braking). That asymmetry is why your average pace on a hilly route is slower than on the flat even when your effort is identical. Grade-adjusted pace corrects for this by converting every uphill and downhill second into its flat-equivalent, so you can compare a mountain run to a track session honestly.
The grade-adjusted pace calculator does that conversion for a single segment, and the GPX analyzer draws the whole profile from your own file, colours it by gradient, and projects a grade-adjusted finish time for the course.
Reading total gain — and trusting it
Total elevation gain is the sum of every uphill metre on the route. It is a good measure of how hard a course is, but it is famously unreliable in raw GPS data: altitude is the least accurate thing a watch records, so the signal jitters by a few metres even on flat ground. Quality tools apply a small smoothing threshold before adding up the climbs, which is why the same ride can read 600 m on one app and 750 m on another. When you analyse your own file, a tool that filters this noise will give a figure much closer to reality.
Putting it to use
Before a race, look at where the steep grades fall: climbs early are best taken conservatively, and long descents are a chance to recover, not to hammer. Drop your course file into the GPX analyzer to see the climbs ranked by length and steepness, then plan an effort that respects the terrain rather than the flat-ground splits on your watch.
Questions
What does an elevation profile show?
It plots height above sea level (vertical axis) against distance travelled (horizontal axis), so you can see where the climbs and descents fall along a route and how steep each one is.
What is a “good” amount of elevation gain?
There is no universal number — it depends on the route. As a rough feel, under ~10 m of gain per km is gently rolling, 10–20 m/km is hilly, and over 30 m/km is genuinely mountainous terrain.
Why is the elevation in my GPS file so noisy?
Consumer GPS estimates altitude less accurately than position, so raw data jitters by a few metres point-to-point. Good analysis tools smooth this before totalling gain, which is why two apps can report different climbing for the same ride.