Repair a broken activity file

Look at the map of an otherwise-clean activity and you'll sometimes see one glitch: the line shoots kilometres off-course in a single frame, then snaps straight back, as if the recording briefly teleported and returned. That's a GPS spike — one point where the implied speed is impossible both arriving at it and leaving it, while the route on either side is completely plausible. It's a common failure mode when a device loses and reacquires satellite lock mid-recording, especially under tree cover, in a tunnel, or between tall buildings. Because the defect is isolated to a single point, the fix is narrow and safe: FitFileHub's repair tool checks the speed implied between each point and its neighbors on both sides, flags any point where both the incoming and outgoing speed are impossible, and removes just that point. Nothing else in the track is touched — your recorded time and distance stay accurate everywhere except the one glitch. You see exactly which point was flagged, with the jump visible on the map preview, before you approve the fix. This is a distinct defect from a stretch of consistently bad readings across several consecutive points — that's a sustained implausible-speed segment, not a spike, and it needs a different kind of fix since there's no single point to delete cleanly. If your file has a run of bad points rather than one clean outlier, the implausible-speed page covers that case instead. Nothing about your route is uploaded to check for this — the scan runs entirely in your browser. Free for files up to 25 MB, three at a time, no account needed.