Skip to content
Spatly

Convert GPX to CSV

1

Add your GPX

Drop a GPX file anywhere on this page

.gpx · it never leaves the browser

2

Options

≈ 11 cm on the ground
Keep every vertex
00verticesunchanged
One column, every geometry type
3

Your CSV

Add a GPX file and the CSV appears here, with its feature counts and anything this pair cannot carry.

Converted in this tab. Your GPX is never uploaded — reading, converting and writing all run in the browser, so this works offline once the page has loaded.
— , —
FidelityGPX → CSV

What comes across, and what cannot

Preserved

  • Geometry — points come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
  • Every attribute becomes a column. The header is the union of all property keys across the file, so features with different fields still line up.
  • Row order matches feature order, so you can join the result back onto the original file.

Dropped

  • Lines and polygons, but only if you ask for it. The default WKT geometry column keeps every geometry type intact; switching to separate longitude and latitude columns can only describe a point, and anything else comes out with empty coordinate cells.
  • Time as a dimension. GPX's TimeStamp and TimeSpan elements are read as ordinary attributes, which is as close as CSV gets to a clock.
  • Elevation. A flat CSV has no third ordinate; keep the WKT geometry column if you need the Z value, because WKT encodes it.

GPS Exchange Format (GPX)

What GPS units and fitness apps speak. It has exactly three containers — waypoints, routes and tracks — so it holds points and lines but has no concept of an area, and only a fixed set of fields per point.

.gpx · application/gpx+xml

CSV (comma-separated values)

A spreadsheet, not a spatial format. It becomes spatial when two columns hold longitude and latitude, or when one column holds a WKT geometry — which is how anything other than a point survives the round trip.

.csv · .tsv · text/csv

AlsoCSV to GPXShapefile to CSVKML to CSVGPX to GeoJSONAll conversions
HowHow it works

Convert GPX to CSV, step by step

  1. Step 1

    Add your GPX

    Drop a GPX file anywhere on the page, paste it, point at a URL, or press Sample to start from real data. Several files at once are fine.

  2. Step 2

    Set what matters

    Coordinate precision and simplification on every pair, plus the handful of settings this one needs — a WKT column or longitude/latitude columns.

  3. Step 3

    Take the CSV

    Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.

PrivateRuns in your browser

Your data never leaves the page

Every conversion, measurement and export happens client-side. Nothing is uploaded, logged or stored — you can even use this offline once the page has loaded. Only “Open in Studio” sends data, and only after you sign in.

Go furtherTurn a GeoJSON into an interactive mapRead the guide
FAQQuestions

Good to know

What is preserved when converting GPX to CSV?
Geometry — points come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude. Every attribute becomes a column. The header is the union of all property keys across the file, so features with different fields still line up. Row order matches feature order, so you can join the result back onto the original file.
What is lost converting GPX to CSV?
Lines and polygons, but only if you ask for it. The default WKT geometry column keeps every geometry type intact; switching to separate longitude and latitude columns can only describe a point, and anything else comes out with empty coordinate cells. Time as a dimension. GPX's TimeStamp and TimeSpan elements are read as ordinary attributes, which is as close as CSV gets to a clock. Elevation. A flat CSV has no third ordinate; keep the WKT geometry column if you need the Z value, because WKT encodes it.
Do I get my waypoints and my track?
Both. Waypoints (<wpt>) become point features, tracks (<trk>) and routes (<rte>) become line features, and each track segment is kept as its own line so a paused recording does not join up into a straight line across the map.
Are elevation and time kept?
Elevation becomes the Z ordinate wherever the target format has one, and is dropped here because CSV is two-dimensional. Per-point timestamps are read as attributes; they are not a time dimension in CSV.
How is the geometry written into a flat table?
Two ways, and you pick. A single WKT column keeps every geometry type exactly — that is the default, and the one to use if you have lines or polygons. Separate longitude and latitude columns are friendlier to Excel and Google Sheets but can only describe a point.
What are the columns?
The union of every attribute key in the file, in first-seen order, plus the geometry column(s). Features missing a key get an empty cell rather than being dropped, so the row count always equals the feature count.
Is my file uploaded anywhere?
No. The GPX is read, converted and written entirely inside this page — there is no upload, no queue, no server-side copy and no size limit imposed by a plan. Large files are parsed in a background worker so the page stays responsive. The only action that transmits anything is Open in Studio, and that happens after you sign in and press it.
Is there a limit on file size or number of files?
There is no imposed limit; the practical ceiling is your browser's memory. Files over about 5 MB are handed to a web worker so the interface keeps responding, and you can drop several files at once — each is converted separately and the set can be downloaded as one zip.