Which columns does the CSV contain?

Each row has type (trackpoint or waypoint), name, latitude, longitude, elevation in metres, and an ISO 8601 timestamp. Fields that are absent in the source are left blank rather than guessed.

Does it keep the order of my track?

Yes. Track points are emitted in document order, segment by segment, so the CSV preserves the exact sequence of your recorded path for distance, speed or elevation analysis.

How are values with commas handled?

Any field containing a comma, quote or newline is wrapped in double quotes and internal quotes are doubled, following RFC 4180. This keeps names with commas from breaking the column layout in spreadsheets.

Can I compute speed or distance from this?

Yes. With latitude, longitude, elevation and timestamp per point you can compute distance with the haversine formula and speed from consecutive timestamps in a spreadsheet or pandas, which is a common reason to flatten GPX to CSV.

Is my GPS data uploaded anywhere?

No. The conversion runs entirely in your browser with DOMParser and string building. Your precise location history never leaves your device and is never logged.

GPX to CSV Converter

GPX stores your GPS data as nested XML, which is awkward to analyse directly. Flattening it to CSV gives you a plain table — one row per point — that Excel, Google Sheets, pandas and database loaders all read natively. This free converter does that in your browser, so you can analyse a hike or drive without uploading your private location history.

How it works

The converter walks the GPX and writes one CSV row per point:

DOMParser reads the GPX and collects every trkpt (track point) and wpt (waypoint) in document order.
For each point it pulls the lat and lon attributes and the optional child ele (elevation in metres) and time (ISO 8601 timestamp).
It writes a header row — type,name,latitude,longitude,elevation_m,time — then one row per point, with the type column marking it as a trackpoint or waypoint.
Fields containing commas, quotes or newlines are quoted per RFC 4180 so the table stays aligned.

The result is a clean, ordered table ready for analysis.

Tips and example

A track point like:

<trkpt lat="48.20" lon="16.37"><ele>170</ele><time>2026-06-06T08:00:00Z</time></trkpt>

becomes the CSV row trackpoint,,48.20,16.37,170,2026-06-06T08:00:00Z. With latitude, longitude and time on every row you can compute distance between consecutive points (haversine) and divide by the time delta to get speed — the usual reason for flattening GPX.

Everything runs locally; your GPS data is never uploaded.