GPX Merger
Combine tracks, routes and waypoints from two or more GPX files locally in your browser while keeping each source element separate.
By Aryan Khan, Founder & Editor · Updated October 2026
Merging happens locally in your browser. Original track, route and waypoint elements are preserved as separate GPX elements.
For example, three day-files of 48 KB, 120 KB and 35 KB combine into one 203 KB archive of the trip — every track still separate inside, nothing stitched into a fake continuous line.
How to use GPX Merger
A union, not a weld:
The GPX Merger combines tracks, routes and waypoints from two or more GPX files into a single file, locally in your browser, keeping each source element separate. Drop the files and download the union — one trip archive instead of fragments, without pretending separate outings were continuous.
- 1Select at least two GPX files.
- 2Click merge and download.
- 3Open the merged file in your GPS app or MapBench GPX viewer to verify it.
What people use GPX Merger for
1. Trip archives
A week of day-files becomes the trip's single GPX — the file you share, back up and load into the GPX Route Stats for totals.
2. Combining device outputs
Watch file plus phone backup plus the route you planned: three sources, one document, each part still identifiable.
3. Building a trail library file
A club's season of hikes merged per-region gives newcomers one download per area instead of forty fragments.
4. Pre-processing for other tools
Analyzers that take one file get the merged union — point counts, boxes and spans then describe the whole set at once.
Worked examples
File A's morning track and file B's evening track enter the merge as two <trk> elements. A viewer draws both; a stats tool sums both; nobody's software draws a phantom straight line from the morning's end to the evening's start across the lunch break.
Campsites saved on the phone, summits from the watch, the bothy from a friend's file: waypoints pool into one <wpt> set — the trip's gazetteer in a single document.
What combines, what stays distinct
The merge is a set union at the element level.
| Element | Merge behaviour |
|---|---|
| Tracks (<trk>) | All carried over, as separate tracks |
| Segments (<trkseg>) | Stay inside their own track — never joined across files |
| Routes (<rte>) | All carried over, as separate routes |
| Waypoints (<wpt>) | Pooled into the combined file |
| Metadata | The merged file gets a fresh header; the sources' internal data rides with their elements |
Nothing is resampled, re-timed or re-ordered within an element — merging changes the container, not the recordings. Duplicate points across overlapping files remain duplicates; cleaning is the deduplication family's job.
Combine several GPX files while keeping their elements separate
Trips recorded across multiple days or devices often end up as separate GPX files. The merger collects tracks, routes and waypoints from each selected file into one new GPX document, making it easier to archive or open the set together.
It does not force every track into one continuous line because that can create false segments between unrelated endpoints. If you need a single cleaned track, merge first and then use a dedicated track-editing workflow that understands gaps and timestamps.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for GPX Merger:
- For big CSVs, fix the coordinate columns first and map a sample before mapping everything: auto-detection is good but not magical, and one swapped column renders a beautiful map of the wrong ocean.
- Keep the original file even after converting: GPX→GeoJSON drops timestamps' context, KML→GeoJSON drops styling, and every pipeline has a lossy edge. Originals are cheap; re-acquisition is not.
Limits & appropriate use
File formats support different combinations of geometry, timestamps, properties and styling. Converting between them can lose information, so keep the original and inspect the output before sharing or using it.
Capabilities differ by workspace: check the accepted format and the operations actually offered on this page. Some tools process files locally but may request map tiles or other services over the network; large or specialised datasets may require dedicated GIS software.
- Cadastral/legal formats → jurisdictional land-registry exports.
- Point clouds and rasters → desktop GIS with proper spatial indexes.
- Certified tracks (evidence, insurance) → chain-of-custody originals, untouched.
Data & methodology
The browser parses each GPX document and serializes its track, route and waypoint elements into a new GPX 1.1 document.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Bounding box
- The minimal rectangle enclosing a dataset; the instant sanity check.
- GeoJSON
- JSON geographic format; the web-mapping native dialect.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Map Files. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- The browser parses each GPX document and serializes its track, route and waypoint elements into a new GPX 1.1 document.
- Before relying on the answer
- Inspect the accepted file format and the fields reported by this specific tool. Keep a copy of the original file before converting or editing it.
- What the result cannot establish
- File geometry and recorded timestamps can be incomplete. Verify row or point counts and inspect the exported file in your target application.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Does merging connect tracks into one continuous line?
No. It preserves tracks, routes and waypoints as separate GPX elements inside one file.
Are files uploaded?
No. Parsing and merging happen locally in the browser.
Is my uploaded map file sent to a server?
Where a page says browser-first or local processing, the file is handled in your browser. Check the individual tool note for any external-service dependency.
What should I do if a file will not load?
Check that the file type is supported, the structure is valid and the file is within the stated size limits. Converting to GeoJSON, GPX, KML or CSV can also help.
Will converting a file preserve every property?
Not always. Geographic formats support different geometry, style and metadata features, so inspect the output before relying on it.
In what order do elements appear?
By source file, in the order you add them — each file's contents intact. Chronology inside the merged file follows your file order, so add day-files in date order for a tidy archive.
Same-named tracks?
They coexist; GPX readers distinguish tracks by position and content, not only by name. Rename before merging if your library software sorts by name.
Extensions (heart rate, power)?
Trackpoints carry their extension data with them — the channels survive merging because the points themselves are copied whole.
One file ends where another begins — joined?
No: proximity is not stitched. Two tracks that happen to touch remain two tracks, which is the truth of how they were recorded.
How many files at once?
As many as your browser's memory comfortably holds — a season of ordinary recordings is fine; a decade of 1-second tracks belongs to desktop tooling.
Does merging change timestamps?
No — every stamp is copied as recorded. If the sources disagree about clocks, that was true before the merge and stays visible after.
Related tools and resources
Totals of the union: GPX Route Stats; count it: the GPX Track Point Counter; box it: the GPX Bounding Box Tool.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our gis files hub
GPX Merger sits in the gis files cluster, alongside 64 other tools that answer neighbouring questions with different methods or datasets. It also belongs to the GPX tools family.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
KML vs. GeoJSON vs. GPX: Choosing the Right Map File Format — The practical differences between three common geographic file formats — when to use each, what can be lost in conversion, and how to move between them.