We made this page after juggling messy GPS files and spreadsheets. Whether you’re exporting runs from a watch, planning a delivery route, or cleaning survey logs, you can convert privately in your browser — no uploads, no waiting.
Everything runs locally using modern web APIs and open libraries.
| Format | Best For | Pros | Watch Outs |
|---|---|---|---|
| GPX | Universal tracks/waypoints | Simple XML; supported by most apps/devices | File size can grow with many points |
| KML | Google Earth, styled routes | Rich styling; easy map viewing | Heavier XML; styling may vary across apps |
| TCX | Fitness workouts | Good for laps, cadence, heart rate | App support varies vs GPX |
| FIT | Garmin & modern wearables | Efficient binary; detailed sensor data | Binary; needs decoder to view/edit |
time — ISO timestamplat, lon — WGS84 coordinatesele — elevation (m)speed — m/s or km/hhr — heart rate (bpm)cadence — steps/rpmdist — cumulative distance (m)lap / segment — optional groupingDon’t have all fields? That’s okay — the converter will include what’s present.
-90 ≤ lat ≤ 90 and -180 ≤ lon ≤ 180.Fitness & Coaching: Merge weekly FIT/TCX files → export to CSV → pivot laps, pace, heart rate trends.
Field Operations: Convert GPS logs to XLSX → filter by time window → generate GPX route for handoff.
Delivery & Service: Build KML with styled LineString → share route previews with the team.
Research & GIS: Export GPX → clean with spreadsheet formulas → import into QGIS/ArcGIS.
Do my files upload anywhere? No — everything runs locally in your browser.
My FIT file won’t parse. Some devices write variants — try re-exporting from the vendor app, then upload again.
Data looks shifted or empty. Check time zones and column headers; ensure lat/lon are numeric.
Very large files feel slow. Close heavy tabs; consider splitting routes or downsampling points.