GPX Merger — Combine GPX Files

Field guide: GPX Merger

Multi-day tours, a watch that crashed mid-ride, a commute recorded in two halves — sooner or later every runner, cyclist and hiker has a pile of GPX files that should be one. This merger combines any number of GPX files into a single valid GPX 1.1 document: tracks keep their names (or inherit the filename), waypoints are pooled, and — the detail most mergers miss — tracks are ordered by their first timestamp, so a Day 2 file selected before Day 1 still comes out in chronological order.

Each track stays a separate <trk> element rather than being welded into one segment. That's deliberate: Strava, Komoot and Garmin Connect interpret a multi-track file correctly, while force-joining tracks creates a fake straight-line segment between your hotel and the next morning's trailhead — inflating distance and corrupting pace analysis. Total combined distance is computed (haversine, point to point) so you can sanity-check the merge before downloading. Files are parsed in your browser; your training data never uploads anywhere.

Field tips

• Order doesn't matter when your files have timestamps — selection order is ignored in favour of recorded time. Files without timestamps keep selection order.
• Merging then re-uploading to Strava? Strava reads the first track's name as the activity name — rename your files meaningfully before merging.
• If your goal is one continuous track (e.g., for a route-builder that ignores multiple <trk> elements), merge here, then run the output through a desktop editor that joins segments explicitly — automatic joining creates phantom straight lines.

Conversions run locally in your browser and follow the cited specifications. Always verify critical output in the target application; for survey-grade or legal data, confirm coordinate systems and datums with your GIS team.