GPX Elevation Gain Calculator
GPX Elevation Gain Calculator
Open a GPX track · See total climb · Read any segment
.gpx files only · stays on your device, never leaves your browser
Enter two distances along the track (in miles) to read the gain, loss, and net change between them. Or click two spots on the chart below.
Paste two coordinates as lat, lon in decimal degrees. Each one snaps to the nearest point on your track, and the readout shows where it landed and how far off the line it sits.
What This Tool Does
Distance tells you how far. Elevation tells you how hard. A flat 12-mile day and a 12-mile day with 4,000 feet of climbing are not the same day, and the difference is the thing your legs feel.
Open a GPX track and this tool reads the elevation data in the file, then gives you total gain, total loss, your high and low points, net change, and the full length of the track. It draws an elevation profile of the whole route so you can see where the climbing actually happens.
Switch to point-to-point mode and it reads the gain and loss for just that stretch. Name the two ends however you have them: type mileages, paste coordinates, or click two spots on the profile. Useful when you want to know what a single day, or the climb to one pass, is going to cost you.
Miles and feet by default, kilometers and meters on the toggle. Everything runs in your browser and your GPX file never leaves your device.
How to Use It
- Click Open and select your GPX track file, or drag it into the drop zone
- The tool reads the track and shows total gain, loss, high point, low point, net change, and length
- The elevation profile draws the whole route automatically
- Switch to km if you want metric; miles is the default
- To read a single segment, switch to Point to Point, then either enter a from and to mileage, paste two coordinates, or click two spots on the profile
- The gain, loss, net change, and distance for that segment appear instantly, and the profile shades the stretch you picked
🥾 Need to know where that climb falls on your track? The GPX Distance Finder turns any coordinate into a mileage from the start and to the end. Both tools resolve coordinates the same way, so a waypoint pasted into one lands at the same spot in the other.
Smoothing, and Why Two Tools Disagree About the Same Trail
A GPS wobbles by a few feet even when it's sitting still, and every one of those wobbles looks like a small climb. Summed across tens of thousands of track points, they add up to thousands of feet nobody walked.
The smoothing threshold is the tool's answer. At 0 feet it counts every rise, however small. Raise it and small reversals are ignored until the profile has genuinely turned around by that much. Six settings run from 0 to 20 feet, and the sub-label under Total Gain always tells you which one produced the number on screen.
Here is what that looks like on one real Colorado track, against the same file read by Gaia GPS:
| Smoothing | Total gain | Above Gaia |
|---|---|---|
| 0 ft | 13,547 ft | +42% |
| 10 ft | 11,516 ft | +21% |
| 15 ft | 11,348 ft | +19% |
| 20 ft | 10,932 ft | +14% |
| Gaia GPS | 9,552 ft | — |
Two things are worth reading off that table. Almost all the correction happens by 10 feet, which strips 2,031 feet of jitter. Everything past that removes another 584 feet across two more settings, and by then you're filtering real terrain rather than noise.
The other is that the numbers flatten out well above Gaia and never reach it. Turning the threshold up further won't close that gap, because the gap isn't noise.
This tool sums the elevation values recorded in your file. Gaia and CalTopo generally compute gain from their own terrain models instead, looking up the height of the ground beneath each point. Those are different questions. A device-recorded elevation trace and a terrain-model lookup can differ by 10 to 40% on the same track, and neither is wrong.
So use the threshold to see how much of your total is real climbing rather than to chase another app's figure. Comparing two settings on the same file tells you the shape of your uncertainty, which is more useful for planning than any single number.
One number does cross-check cleanly: Net Change. It's simply the last elevation minus the first, with no filtering on either side, so it doesn't move when you change the threshold. On the track above, this tool and Gaia agree on net to within 15 feet out of 3,000. If net ever disagrees between two apps, something is genuinely wrong with the file or the endpoints.
Net change also carries a sign, and the sign depends on which end of the track the file starts at. A track recorded east to west reports the mirror image of the same route walked west to east: gain and loss swap places, and net flips. Worth checking before comparing against anything else.
Reading Coordinates Instead of Mileages
Point-to-point accepts a pair of coordinates in decimal degrees, like 39.123456, -106.041234. Each one snaps to the nearest point on your loaded track and the readout tells you two things: where along the track it landed, and how far off the line it sits.
That second number is the check that matters. A waypoint a few hundred feet off the track is normal. Half a mile or more turns the reading red, which usually means the wrong coordinates or a track that doesn't cover that area.
Switching between distances and coordinates keeps the same segment. Enter mileages, switch to coordinates, and the fields show you the coordinates at those exact points on the track. It works in the other direction too, so you can click two spots on the profile and read off the coordinates for them.
When a GPX Has No Elevation Data
Some GPX files record only latitude and longitude. When that happens, this tool tells you so rather than guessing.
If you see the no-elevation notice, re-export your track from Gaia GPS, CalTopo, or your GPS device with elevation included, then open it again. Most mapping tools include elevation by default or offer it as an export option.
Track density matters as much as the elevation values themselves. A sparse track never samples the tops and bottoms of small rollers, so it reads low no matter what the smoothing is set to. The tool shows the point count when a file loads, which tells you how much to trust the total.
Who Built This and Why
Hiking America builds navigation tools for long-distance hikers, primarily for the American Discovery Trail and the Great American Rail-Trail. Knowing the climbing ahead is part of planning any long route, and reading it off a raw GPX file by hand is tedious. So we built this.
If you're planning a long-distance hike and want to know more about our GPS tracks and waypoint data, hikingamerica.com is the place to start.
Is There a Tool You Wish Existed?
We build these because we needed them. If there's a calculation you keep doing by hand, tell us about it.
A free tool from Hiking America: navigation resources for the American Discovery Trail and the Great American Rail-Trail.