Open, convert and repair a FIT file
A .fit file from a Garmin watch holds the whole activity, but it only opens in the software that wrote it. This page reads it here, in your browser: the activity at a glance, the same track as GPX or CSV, and a repaired copy when the file was cut short or its checksum no longer matches. What is inside a FIT file, and how FIT to GPX works, is described below.
What goes in, what comes out
- In: a .fit activity file from a watch, a bike computer or a Garmin Connect export folder.
- Out: a GPX 1.1 track (with elevation, time and heart rate), a per sample CSV, a per activity CSV, and a repaired .fit when the file needed it.
- Also shown: the activity type, date, distance, time, heart rate and the watch model. The serial number is masked and is left out of every export.
What this page does not do
- A byte level repair rebuilds the header and the checksum and cuts the file at the last complete message. It cannot bring back data that was never written, so a truncated file stays shorter than it should be.
- Nothing is re-encoded: this page does not write activities back into FIT, so a repaired file is the original bytes with a correct container.
- GPX coordinates are written exactly as the device recorded them (WGS-84). A track that came from Amap, Baidu or Xingzhe needs the offset fix first. Track offset fix
Where the file goes
Nowhere. The file is read by this page, in your browser: there is no upload endpoint on this site, no request carries the file, and nothing is stored. That is also why the page keeps working offline once it is loaded.
Track offset fix · Export a summary for ChatGPT · All tools · Check which watches support it