What a GPX File Reveals Before You Share It

A GPX file looks harmless. It is a small text file your watch or phone app exports when you finish a run, a ride, or a hike. You attach it to a message, upload it to a forum, or share it with a training partner, and the conversation moves on.

But that file is plain XML anyone can open in a text editor. Every point of your movement sits inside it with coordinates, and most apps add a timestamp and elevation to each point. This guide shows what a GPX track actually exposes, field by field, so you can decide what to strip before the file leaves your hands. If you want to check a real file right now, open our GPX privacy inspector and drop the file in. It parses everything locally in your browser and nothing is uploaded.

A GPX file is a diary written in coordinates

GPX stands for GPS Exchange Format. It has been the standard way to move GPS data between apps and devices since 2002, and version 1.1 from 2004 is still current. The format stores three kinds of data: waypoints (single named places), routes (planned stops in order), and tracks (recorded breadcrumb trails with hundreds or thousands of points).

A typical recorded activity is a track. Each track point, called a trkpt, carries latitude and longitude as attributes. Inside the point element there are usually two more fields: ele for elevation in meters and time for the timestamp in UTC. That combination is what makes the file so revealing. Position alone shows a line on a map. Position plus time replays your whole outing minute by minute.

File headers add context too. The root element names the app or device that created the file, and the track often has a name like “Morning Run” plus the date. None of this is encrypted, compressed, or hidden. If you can open the file, you can read all of it. Photos hide the same kind of leak: read how to check photos for location data before sharing pictures from the same trip.

Timestamps turn a line into a full replay

The timestamp is the most underestimated field in a GPX file. Without it, a recipient sees where you went. With it, they see when you left, how long each section took, where you stopped, and when you got back.

Speed falls out of the same data with simple arithmetic. Distance between two consecutive points divided by the seconds between their timestamps gives pace for runners and speed for cyclists and drivers. Rest stops show up as clusters of points with barely changing coordinates and advancing clocks. A ten-minute stop at one address halfway through a ride is visible to anyone who looks.

Timestamps also anchor your routine. A file recorded every weekday at 7:40 AM tells a story about when you leave the house. A Saturday track that starts at a different address tells another. One file is a single outing. A handful of files shared over time is a pattern of life. If someone may be following you without consent, read how to detect if your phone is being tracked.

Start and end points often mark your front door

The most direct privacy leak in a GPX file is also the simplest: the first and last points. Most people press start at home and stop when they return. Those two points, precise to a few meters, sit at the top and bottom of every raw export.

Mapping communities learned this lesson years ago. OpenStreetMap warns contributors that a trace uploaded from home reveals where they live, and recommends trimming track ends near home and work before uploading. The same advice applies to any file you share privately, because a recipient can zoom into the endpoints just as easily as a stranger on a public site.

Trimming ten or twenty points from each end usually moves the visible start to a nearby street or junction instead of your doorstep. It costs nothing in terms of the route itself, and it removes the single most sensitive pair of coordinates in the file.

Elevation, waypoints, and names leak smaller details

Elevation looks innocent. It records how high each point is above sea level, and it is needed for climbing stats. On its own it reveals little. Combined with timestamps, though, it confirms effort and can fingerprint a route: the exact elevation profile of a loop is nearly unique, which makes the track searchable against public segment databases even after you remove your name.

Waypoints deserve a closer look before sharing. These are places you or your app marked by hand, and they often carry personal names: “Mom’s house”, “physio”, “secret parking”. Route points from planned navigation can hold similar notes. Rename anything personal to neutral labels, or delete waypoints you do not need to share.

Finally, check the file header and track name. The creator field names your device or app, and a track named “Lunch run from office” plus a timestamp says where you work and when you take lunch. These are small edits that take seconds.

Platform privacy settings do not clean the file

Many sport platforms let you hide the start and end of an activity map, or hide the whole map from other users. That is useful inside the platform, but it does not change the underlying data. Strava’s own help center states that map visibility controls apply to activities on Strava only and are not carried to other services with your activities. Export the file, and the full original track comes with it.

The same gap exists everywhere. A private link on one service becomes a public file the moment someone downloads and re-uploads it. The only version you fully control is the file itself. Clean that file before it travels, and platform settings become a second layer instead of your only layer.

How to share a GPX file safely

A safe sharing routine has four steps and takes about a minute.

First, open the file in an inspector instead of guessing. Our GPX privacy inspector shows the point count, time range, and a preview table with coordinates, elevation, and timestamps, all parsed locally in your browser.

Second, strip what the recipient does not need. Remove timestamps if the route shape is enough. Remove elevation unless climbing data matters. These fields are optional in the GPX format, so the file stays valid without them.

Third, trim the track ends. Remove enough points from the start and finish to move the visible endpoints away from home, work, and other private addresses. Ten points is a starting value; dense city tracks may need more.

Fourth, open the cleaned copy and verify it. Check the new first and last points on a map, scan waypoint names, and confirm the file still loads in your app. Then send the cleaned file, not the original, and keep the original in your own archive.

What stripping cannot do

Stripping fields limits specific hidden data. It does not change the route shape, and a distinctive route can still be recognisable. A loop that starts at one isolated house, a track around a small private lake, or a commute between two fixed points identifies itself by geometry alone.

Recipients can also combine your file with other information: your name on the message, photos from the same day, or public segments matching the route. No cleaning step controls what happens after sending. Share the minimum that serves the purpose, with people you trust, and treat every upload to a public site as permanent.