Repair a broken activity file
Your file never leaves your device — conversion happens here in your browser.
Two consecutive points, identical in both time and position, add nothing to a track — no distance, no new information, just a redundant row that pads the file and, in some tools, quietly confuses a pace calculation that expects each point to represent forward progress. This is narrower than it sounds: FitFileHub only flags a duplicate when time and position both match exactly on consecutive points, so a genuine pause where you stood still usually looks different from the kind of duplication this catches, which tends to come from a device double-writing a sample, a merge combining overlapping exports, or a converter re-processing the same segment twice. The fix is mechanical and low-risk: when the repair tool finds a run of points sharing identical time and position, it keeps the first and removes the rest, leaving the track exactly as recorded everywhere else. Nothing about pace, elevation, or sensor readings is recalculated or smoothed — only the redundant rows are dropped. As with every check this tool runs, you see the count and location of duplicates found before anything is removed, and a file with none is reported as clean rather than modified for the sake of it. Duplicate points are also worth checking after a merge — combining two files that overlap at the seam is one of the more common ways a track ends up with a run of identical points right at the join, which is why this check pairs naturally with FitFileHub's merge tool rather than being something you'd only run on a raw device export. Runs fully client-side, in your browser — your route data is never uploaded. Free for files up to 25 MB, three per batch.
Questions
What exactly counts as a duplicate point?
Two or more consecutive points sharing the exact same timestamp and the exact same position. Points that are merely close, or a genuine pause recorded intentionally, generally don't match both conditions exactly.
Will a stationary moment, like waiting at a light, get removed as a duplicate?
Usually not — this check requires an exact match on both time and position for consecutive points, which is narrower than simply standing still for a while.
Why do duplicate points show up after merging files?
When two files overlap at the point they're joined, the seam often ends up with a run of points that were recorded in both original files, producing exact duplicates right at the join.
Does removing duplicates change my total recorded distance?
No — duplicates by definition add no distance, since they share the same position as the point next to them. Removing them cleans up the file without altering your stats.