100% private — files never leave your browser
Merge GPX Files
Stitch several .gpx recordings into a single track that loads as one activity everywhere. Files are ordered by start time and their points concatenated — nothing smoothed, nothing dropped — with elevation, timestamps and heart rate carrying straight through. The merge runs entirely in your browser.
add as many as you like — they will be sorted by start time and stitched together
How to merge GPX files
- 1
Add your files
Drag two or more .gpx files onto the box above, or click to browse and select them together. Each file is read locally on the spot.
- 2
Check the order
Files are sorted automatically by track start time. Recordings without timestamps keep the order of the list, so give those a quick look before merging.
- 3
Merge
The merge runs in a background worker on your device. The combined track appears on the map with total distance, duration and ascent, so you can confirm the join before saving.
- 4
Download
Click download and the merged .gpx is saved straight from memory. Your original files stay untouched on disk.
Why merge GPX files?
GPS devices love saving one ride as several files. You stop for lunch and the watch auto-saves; the cycling computer's battery dies on a climb and it reboots into a new recording; an interval session ends up scattered across files after a sync hiccup. Each fragment then uploads as its own half-activity — split maps, broken distance totals, two entries for one day. Merging first restores the day as a single coherent track.
Merging comes up on the planning side too. Routes researched section by section — one file per day of a bike tour, a trail stitched together from several sources — are easier to share, email or load onto a device as one continuous course than as a folder of parts.
And because GPX is plain-text XML, plenty of riders merge files simply to keep an archive tidy: one file per trip, per month or per route collection, instead of a camera roll of scattered .gpx fragments.
How the merger works
The tool reads every file you add, orders the tracks by start time, and concatenates their points into one track. Per-point data — elevation, timestamps and the Garmin TrackPointExtension channels for heart rate, cadence and power — is carried over exactly as recorded. Files whose tracks carry no timestamps are merged in the order shown in the list.
One honest caveat: if two recordings overlap in time — two devices on the same ride, for example — the merge keeps every point and interleaves them by timestamp. The line renders slightly denser, total distance comes out a little long, and nothing is silently deleted. Merge recordings that follow each other in time and the join is seamless.
When a desktop tool is the better answer
This merge is honest concatenation. If you also need gap removal, duplicate-point cleanup, GPS glitch repair or elevation re-sampling, a desktop editor gives you that control — GPS Track Editor, Garmin BaseCamp and QGIS all do those jobs, at the cost of installing and learning them.
Content type matters too: merging a planned route with a recorded track, or waypoints into a track, produces a file most software will render oddly. And if the files are genuinely different activities — Saturday's run and Sunday's ride — no merge can make them a sensible single activity. Keep those separate.
Your files never leave this browser
This tool — like every tool on this site — runs entirely as client-side JavaScript. The file you drop is parsed in a Web Worker on your own device, converted in memory and handed straight back to you as a download. There is no upload endpoint, no server-side conversion service and no temporary storage: you can watch the network tab in your browser's developer tools and confirm that no file bytes are transmitted anywhere.
That matters more with fitness data than with most files. A GPS track is a precise log of where you were, at what time, and how hard your heart was working — home address, training habits, favorite routes and race schedule all in one file. Keeping conversion on-device means third-party converters never get a copy of that log, and the tool keeps working identically on a plane, in a basement, or anywhere else without signal.
Frequently asked questions
Every point is kept and ordered by timestamp, so an overlapping section draws as a doubled-up line and total distance comes out longer than either single recording. The merger never deletes points to tidy this up — what your devices recorded is what you get.