KMZ input
Open a KMZ archive without unpacking it first. The converter reads the first KML entry it finds.
Merge GPX Files
Combine GPX, KML and KMZ routes into fewer files. Keep separate tracks together in GPX and KML outputs.
More actions
Related tools
Your statistics
0
Conversions
0
Files processed
0 km / 0 mi
Distance
-
Most used mode
0
Files merged
In browser
Processing
How to convert GPS routes
The video could not load. You can still follow the instructions below.
Click Select files to add your routes, then Add files for more. GPX, KML and KMZ are accepted. Check every filename before merging. Each track stays a separate track in the merged output.
Route conversion options
Route map
Check track lines and waypoint markers on street or topographic maps. Use Fit routes and Fullscreen for a closer look.
Distance and point counts
See the total track distance in kilometers and miles, alongside track-point and waypoint counts.
Show 3 moreShow less
Combine route files
Collect tracks and waypoints from several files into GPX and KML outputs. Separate tracks remain separate.
Separate track exports
Split a file into its parsed tracks or points. Multiple segments inside one track stay together.
Modes keep their own files
Switch between the four modes without mixing their file lists. Files remain available for this page session.
Frequently asked questions
How do I merge GPX files?
Add the files in Merge routes mode, review the map and click Convert. Download the combined GPX or KML result, or both together in a ZIP.
Can I mix GPX, KML and KMZ inputs?
Yes. Merge routes accepts all three formats. The GPX result includes compatible points and lines. KML can include other parsed geometry, so the two results may contain different features.
Does merging make one continuous track?
No. It collects features into a file and keeps tracks separate. It does not add a line between endpoints, remove overlapping points or sort recordings by timestamp.
How is the combined distance measured?
The displayed distance is the sum of distances within the uploaded tracks. Gaps between separate tracks are excluded. The calculation uses coordinates rather than elevation.
Show 2 moreShow less
What order does the output use?
GPX lists waypoints before tracks, preserving upload order within each group. KML keeps parsed features in upload order. The tool does not reorder by recording date.
Are my files uploaded when merging?
Route files are read and converted in your browser. The map preview fetches tiles from OpenStreetMap or OpenTopoMap, which receives your IP address and the map area requested. Conversion counters are stored in this browser.
Technical details
Parsing route files
GPX and KML XML are parsed into GeoJSON before conversion. GPX output writes points, lines and multi-line tracks. Unsupported geometry is skipped in that output.
Opening KMZ archives
JSZip reads the archive and uses its first KML file. Embedded images, overlays and models are not copied into the converted route.
Show 4 moreShow less
Merge and split boundaries
Merge keeps tracks and waypoints separate. GPX lists waypoints before tracks, with upload order preserved within each group. It does not connect track endpoints. Split writes one GPX per feature, so one track with several segments remains one result.
What GPX output retains
Each file can be up to 10 MiB. GPX output keeps coordinates, names, elevation and timestamps supplied by the parsed tracks and waypoints. Device extensions, KML styling, embedded images and polygons are not included in GPX output.
Distance calculation
The Haversine formula adds the distance between consecutive coordinates within each track segment. Elevation and gaps between separate segments do not contribute. Sparse recordings can miss bends in the real route.
Map rendering
GeoJSON supplies tracks and waypoint markers to the Leaflet preview. Street tiles come from OpenStreetMap and topographic tiles from OpenTopoMap. Conversion counters are saved locally.