Fix corrupt FIT timestamps
A file that leaps into the future will not import. This walks the clock and rebases wild jumps.
Files stay on this device
1Select a file
2Jump
3Run
Select a file first.
Your file is processed in your browser and never uploaded.
What this format is
Corrupt time fixer: a FIT that suddenly leaps years ahead will not import. This walks the file and rebases wild jumps.
How to get the file
- From Garmin Connect
- 1. If Connect refuses the file, try this then import again.
- From Strava
- 1. Same — fix locally, then upload.
What is kept and what is lost
| Kept | Lost or missing |
|---|---|
| GPS and sensors | The bogus future timestamps |
Questions
What counts as corrupt?
A timestamp that jumps farther than the threshold (default 120 seconds) relative to the typical interval of the file.
Are GPS and sensors rewritten?
No. Only the clocks on those records.
When should I use Repair FIT instead?
When the file will not decode at all. Use this when it decodes but the dates are nonsense.