How to Fix a Corrupted FIT File (and What Can Be Saved)
FIT files corrupt in well-understood ways: batteries dying mid-recording, transfers cut short, checksums failing. Here is how to diagnose the damage, what repair can and cannot recover, and how to prevent it.
The ride of the month is on the device. The export is a file that nothing will open — the platform says error, the viewer says invalid, the file size looks wrong. Almost every corrupted FIT file tells one of three stories, and each story has a different ending.
What corruption actually is
A FIT file is written sequentially: a header first, then definition and data messages in order, and a checksum at the very end. The format is strict on purpose — a device or platform can verify the whole file by reading that final CRC. The flip side: when anything disturbs the tail of the file, the checksum fails and strict readers reject the entire file, even when 95% of the recording before the damage is perfectly intact.
That is the essence of most "corrupted" FIT files: not a file full of garbage, but a file whose ending betrays its beginning. Repair is the art of re-establishing the ending.
The three stories, and their endings
Story 1: The battery died mid-recording
The device was writing records when the power cut. The file on the watch ends abruptly — no lap-close, no session, no checksum. The bytes are healthy up to the power cut.
Ending: mostly recoverable. The watch saved what it saved; a repair rebuilds the header and checksum around everything that exists. What was never written — the last moments before the power cut, sometimes the final lap summary — is genuinely gone. No tool on earth can restore samples the device never saved, and any that claims otherwise is lying to you.
First move before any tool: check the device. Many units finalize a recoverable file on reboot, and a fresh export may come out clean.
Story 2: The transfer was cut short
The recording was fine; the copy was not. A cable unplugged a moment too early, a Bluetooth sync interrupted, a cloud drive that synced half a file. The original on the device is intact — the copy on your computer is the amputee.
Ending: recoverable by re-export. This is the happiest case: go back to the device (or the platform's original-files archive) and export again. Repair is only needed when the device has since overwritten the original — in which case the repair tool rebuilds the trailer around the transferred portion.
Story 3: The bytes went bad in storage
Aging flash storage, a bad sector, a re-save by some other tool that crashed mid-write. The file's middle is damaged, not just its end. These are the rare ones, and the ones where the damage report gets interesting.
Ending: partial recovery, honestly reported. The repair walks the file message by message. Everything readable up to the first wall of garbage is recovered; a good tool then tells you exactly where the wall was, rather than pretending the file came through whole. You get your ride up to the damage point, with a straight face about the rest.
Running the repair
The FIT repair tool does this work in your browser — the damaged file never leaves your device, which matters as much here as anywhere: a corrupt file still contains everywhere you have been.
The workflow: drop the file in, read the diagnosis (what was found, what was rebuilt, where any damage sits), and download the repaired copy. The original is never modified. Then:
- Open the result in the FIT viewer and confirm the track and timing look right.
- Upload it as a new activity; if it duplicates the broken original's entry, delete the old one first (why platforms silently drop near-duplicates).
- If the plan is analysis rather than re-upload, carry on to FIT to GPX or a merge with the ride's other half (merging split activities).
What repair cannot do
Honesty is the whole policy on this site, so: a repair tool rebuilds structure — headers, message framing, checksums — around surviving data. It cannot invent data. A zero-byte file has nothing to rebuild. A recording that died at the summit has no summit in it. Repair's promise is that damage stays as small as the damage actually was, not one record larger.
Prevention beats repair
- Sync soon after riding. Files sitting on device storage for weeks are exposed to every reboot, crash and storage glitch the device has in it.
- Eject properly. The two seconds of waiting for a USB transfer to finish is the cheapest data insurance available.
- Keep battery margin on long sessions; many devices write increasingly fragile files below a few percent.
- Archive originals once. Export FIT files to a folder you back up, and treat every platform copy — including repaired ones — as disposable. (Why originals matter)
A season of FIT files is a season of your life's locations and heartbeats. Treat the originals accordingly.
Frequently asked questions
Three causes cover most cases: the device lost power while still writing, a transfer to the computer was cut short, or the storage itself flipped bytes. Because FIT keeps its checksum at the very end of the file, any of these can make the whole file unreadable even when most of the data is intact.