Fit file to gpx file conversions (repairs)
This tool will convert a garmin .fit activity file into a gpx file, even if the .fit file is corrupted and will not upload to your favourite activity logging websites. As long as there is enough data in there, this tool will extract all readable points. When an error is found, it will continue looking for the next valid point (as long as there is no more than a 2 hour gap between valid points). The .fit file must be from a recorded activity (cycle, run, swim etc.) because this tool requires points that contain a date and location in order to work. The .gpx file will contain elevation, heart rate and cadence data if present in the .fit file, so it can be uploaded directly to Strava or similar activity logging sites.
Please select your FIT file for conversion.
Fit file to csv file conversions
Fit files (including corrupted files) can be converted to csv files - which can then be used in spreadsheets (if you want).
Convert a fit file to csv file format.
Privacy Policy
We do not ask for any personal details from you, so we do not retain any. We keep a log of the uses of this tool in order to ensure that the server is able to cope with the level of demand. This means recording ip address, date, time of use etc. If you agree with us retaining this information, you may use this tool.
Recovering lost / corrupted fit files from Garmin devices
This tool was originally designed to convert CORRUPTED fit files into gpx files - files that would not be read by other websites, such as Strava.
So here are a few details on how this is done. If you have a fit file already, and it will not upload to your chosen website / program, then just try the above tool. If you have 'lost' your activity file (garmin device crashed for example, leaving the activity missing) try plugging your device into a PC. Look for any .fit files from the correct date. In my case these were in the wrong folder, and were corrupt so the garmin device did not list them. Copy the file to the PC, try the tool above.
Recent change history
- 25th August 2017 - Skip point records if lat / lon not set (no satellite signal)
- 25th August 2017 - Do not create output file if less than 2 points could be recovered
- 5th September 2017 - fix bug causing erroneous points in output
- 6th September 2017 - add warning messages for points / dates that differ too much from previous
- 6th September 2017 - use gmt0 timezone for all output points
- 6th September 2017 - prevent empty trkseg records being placed in output file
- 11th September 2017 - ignore error when date/time of first point is earlier than date/time in file header
- 26th September 2017 - allow time jumps up to 14 days forwards, or 24hrs back - but with warning for out of sequence timestamps
- 18th October 2017 - allow position jumps if accompanied by time jump (activity starts in one location, resumed later in another)
- 23rd November 2017 - add details of csv file format to csv conversion results page
- 2nd February 2018 - Show power off/on events, and manual start and stop, but not autopause to limit spurious output
- 9th February 2018 - Show user profile summary if present