GPX to CSV Converter

About this tool

GPX to CSV turns a GPX file — the XML format that GPS watches, bike computers, phone apps and mapping tools export — into a clean CSV table you can open in a spreadsheet or import anywhere. Paste the file contents and you get one row per point with these columns:

point_type, name, latitude, longitude, elevation_m, time

plus a speed_kmh column when you enable it, and heart_rate_bpm, cadence_rpm, power_w and temperature_c columns whenever the file carries those Garmin-style sensor extensions. Coordinates and elevations are copied through verbatim, so nothing is rounded or reformatted, and every field is RFC-4180 escaped so names containing commas or quotes stay intact.

Everything runs locally in your browser — the GPX never leaves your device.

Worked example

Input (a two-point track):

<gpx><trk><trkseg>
  <trkpt lat="40.000000" lon="-105.000000"><ele>1600</ele><time>2024-03-09T08:00:00Z</time></trkpt>
  <trkpt lat="40.001000" lon="-105.000000"><ele>1610</ele><time>2024-03-09T08:01:00Z</time></trkpt>
</trkseg></trk></gpx>

Output (defaults — comma delimiter, header on, ISO time):

point_type,name,latitude,longitude,elevation_m,time
track,,40.000000,-105.000000,1600,2024-03-09T08:00:00Z
track,,40.001000,-105.000000,1610,2024-03-09T08:01:00Z

Tick Add derived speed and a speed_kmh column is appended — the two points are ~111 m apart over 60 s, so the second row reads about 6.68 km/h (the first row is blank because speed needs a previous point).

Options

• Point types — keep everything (all) or restrict rows to track points (<trkpt>), route points (<rtept>), or waypoints (<wpt>).
• Delimiter — comma, semicolon (handy for comma-decimal locales), tab (TSV), or pipe.
• Include header row — turn the column-name row off for a headerless CSV.
• Time column — iso keeps the original UTC timestamp text, unix converts to epoch seconds, none drops the time column.
• Derived speed — adds speed_kmh computed from consecutive timestamps (great-circle distance ÷ elapsed time) along each track segment / route.

Limits & edge cases

• Points need valid lat/lon attributes to appear; a point missing either is skipped.
• Sensor columns appear only when at least one included point actually carries that channel, so the CSV never has a column of blanks.
• Derived speed is a point-to-point estimate from the raw timestamps — it is not smoothed and does not use a Doppler/GPS speed field if the device recorded one.
• unix time needs parseable timestamps; if a <time> value can't be read as a date you'll get an error (switch to iso to keep the original text).
• GPX timestamps are UTC by spec — there is no local-timezone option because that would need a timezone/DST database the tool doesn't ship.

FAQ