Skip to content

Elevation Profile Generator

An elevation profile with ascent and descent from a GPX track, from the elevations your file already carries: drawn by distance, coloured by steepness, with its climbs listed and the route on a map. Files without elevations get a terrain estimate, labelled as one.

GPX file
No file chosen

Which elevations are used

Most GPX files already carry an elevation per point, recorded by a watch or written by the planning tool that made the route. This tool uses those by default and smooths them with a 5 m threshold, the same method as the GPX Simplifier, the Flyover and the Route Packet, so the ascent here is the ascent you will see there. The Course Analyzer and the Planner smooth heights along the line instead, so on rolling ground their ascent can differ from this one by a few per cent. Small gaps are carried forward from the previous point.

Reading the chart

The chart is drawn by distance, so a stretch where your watch recorded more often is not stretched out. Its colour is the steepness over about 200 metres, up or down, in the Course Analyzer's classes: under 4%, 4–8%, 8–12%, 12–20% and 20% or more. Point at it, tap it or use the arrow keys, and the map shows where you are. The climbs are the Course Analyzer's too: each rise that the route does not interrupt with a real descent, with its gain, length and average grade. Switch between metres and feet at any time; the downloads follow.

Downloads

The PNG and SVG carry the title, both axes, the steepness key and the source of the elevations, so a picture shared on its own still says what it shows. When the terrain estimate is shown, you can also download a copy of your GPX with the estimate written into it, for an app that should show the same profile; your file itself is never changed.

When to estimate from terrain

If a file has no elevations, gives 0 m for every point (a device that recorded none), or fewer than half its points carry one, elevations are sampled from a digital elevation model along the route instead, and the result is labelled as an estimate. You can also request the estimate for any file to compare it with what the file says.

Treat the estimate with care. The terrain model is a grid of cells about 26 m across at mid-latitudes; where a trail crosses a steep slope, the cells beside it sit well above and below the path, and a series sampled along it gains climb the trail does not have. So the estimate comes from TrailSplits' elevation profile, the method behind the climb of every route on TrailSplits: the terrain is sampled every 20 m along your route (a little further apart on very long routes) and averaged over 100 m either side before the climb is counted. Measured on 64 hilly routes against lidar and the climbs published for them, its median came within 5%; any one route can differ more. The heights are placed on your own route, so its distance stays your file's. When that service does not answer, the page samples the terrain itself every 50 m and averages it over 200 m; on 23 hilly test routes that came within 15% of the route's own climb for 20. On flat routes, such as city marathons, either estimate is unreliable: bridges, buildings and water in the model can add several times the real climb.

Privacy

Your GPX file is not uploaded. Showing your file's elevations makes no network request for the profile; the map loads its tiles for the area of your route. A terrain estimate sends the line of your route (its coordinates only: no heights, times, names or other data from the file) to TrailSplits' elevation service. If that service does not answer, the page asks TrailSplits' terrain tiles for heights at points along the route; no other terrain host is asked.

Frequently asked questions

How do I make an elevation profile from a GPX file?

Choose the file above. The profile, ascent, descent and climbs come from the elevations in your file, and you can download the chart as PNG or SVG, in metres or feet.

Why does the ascent differ from one tool to another?

Ascent depends on how heights are smoothed. Here the file's heights are counted with a 5 m threshold, the same as the GPX Simplifier, the Flyover and the Route Packet. The Course Analyzer and the Planner smooth heights along the line, so on rolling ground their ascent can differ by a few per cent.

What if my GPX has no elevation data?

When a file has no elevations, gives 0 m for every point, or carries them on fewer than half its points, the page says so and estimates heights from a terrain model along your route, labelled as an estimate. On 64 hilly test routes its median came within 5% of lidar and published climbs; any one route can differ more.

Can I add elevation to a GPX file?

Yes, as a copy: when the terrain estimate is shown, download a copy of your GPX with the estimate written into it. Your file itself is never changed.

Is my GPX file uploaded?

No. Showing your file's own elevations makes no request for the profile. A terrain estimate sends only the line of your route (its coordinates; no heights, times or names) to TrailSplits' elevation service.