Convert GPX to CSV and turn recorded tracks and waypoints into rows you can sort, chart and share with non-GIS colleagues. Files are read entirely on your device, so private running or fieldwork routes stay private.
Drop a file here, or click to browse
KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more
No GPX file to hand? Download a sample GPX file (100 points) and drop it above to see the conversion.
Every format stores different things, so a conversion is never perfectly loss-free. Here is exactly what carries over when you convert GPX to CSV, and what to watch for.
| What | GPX → CSV | |
|---|---|---|
| Geometry | Changes | Point features become X and Y columns; lines and polygons are written to a WKT geometry column, so no shape is lost in the table. |
| Attributes | Kept | Every column and full field name moves from GPX into CSV untouched. |
| Styling & labels | Kept | Neither GPX nor CSV stores visual styling, so there is nothing to lose, the geometry and data carry straight over. |
| Coordinate system | Changes | CSV stores raw coordinates without a CRS tag, so note the coordinate system separately for whoever opens the file. |
| Elevation (Z) | Changes | Z values, if present, appear as an extra column rather than 3D geometry. |
| File structure | Kept | A single, self-contained .csv file you can move around on its own. |
GPX is what your Garmin, running watch or app like Strava and Komoot writes when it records a hike or ride. It packs waypoints, routes and tracks into XML, which is great for devices but awkward for analysis. CSV flips that. Once your points sit in plain rows, you can open them in Excel, load them with pandas, or feed them to a script or API. So people convert GPX to CSV to crunch track logs, tidy up waypoint lists, filter by time, or hand coordinates to non-GPS tools. It turns navigation data into a simple table anyone can read.
GPX is already defined in WGS84 longitude/latitude (EPSG:4326), so no guessing is needed on the way in.
CSV stores raw coordinates without a CRS tag, so make a note of the coordinate system for whoever opens the file next. A quick CRS check before you download saves the classic "my GPX data is in the wrong place" surprise; the guide on coordinate systems and EPSG codes goes deeper.
GPX stores three kinds of geometry: waypoints, routes and tracks. CSV is flat, so each output row is just one point with its longitude and latitude. Track structure and the link between points and their parent track can flatten out. Also, GPX already carries few attributes, so extra fields like elevation or timestamp only appear as columns if they were in the source. Check that lon/lat columns survived before mapping the CSV again.
GPX files typically come out of Garmin, Strava, Komoot, QGIS, GPSBabel. Once you convert to CSV, the file opens in Microsoft Excel, Google Sheets, LibreOffice Calc, and any script or database import. The CSV output follows the standard specification exactly, so those programs read it without any special import settings.
A GPX file records where you went: waypoints, plus ordered tracks and routes straight off a watch or handheld unit. CSV is where that trail becomes analysable. Once each recorded point sits in its own row, you can sort, filter and chart it in a spreadsheet or with pandas. In practice, this pairing turns a Strava or Garmin export into a plain table. That means distance, speed and elevation math without any mapping software open.
Only if the GPX recorded them. GPX carries limited attributes, so fields like elevation or time appear as CSV columns when present in the source, otherwise you get just coordinates.
Yes. The output is plain rows of values, so Excel, Google Sheets and pandas all read it directly, and you can sort, filter or chart your track points there.
Yes. GPX trackpoints usually carry elevation and a time tag, and both become their own columns. Waypoint names and descriptions map to columns too. Any point missing those tags simply leaves the cell blank.
A GPX track is one connected line made of many trackpoints. Each point becomes a single row of latitude, longitude and its attributes. Keep the row order intact, because that sequence is what defines the path when you rebuild or chart it later.
A CSV file opens in Excel, Google Sheets, LibreOffice and any database. Because the output follows the standard specification, any tool that supports CSV will read it without special settings.
No conversion is perfectly loss-free because each format stores different things, but nothing important is lost: point coordinates become X/Y columns and any lines or polygons are saved as WKT text, so the geometry survives in the table.
