KMZ input
Open a KMZ archive without unpacking it first. The converter reads the first KML entry it finds.
Convert KML and KMZ route files to GPX. Preview tracks and waypoints before downloading.
More actions
The video could not load. You can still follow the instructions below.
Click Select files and choose KML or KMZ files from your device. You can also drag files onto the page. Wait for each file to appear in the list. Your original files remain unchanged.
Open a KMZ archive without unpacking it first. The converter reads the first KML entry it finds.
Check track lines and waypoint markers on street or topographic maps. Use Fit routes and Fullscreen for a closer look.
See the total track distance in kilometers and miles, alongside track-point and waypoint counts.
Collect tracks and waypoints from several files into GPX and KML outputs. Separate tracks remain separate.
Split a file into its parsed tracks or points. Multiple segments inside one track stay together.
Switch between the four modes without mixing their file lists. Files remain available for this page session.
Add a KML or KMZ file in KML to GPX mode. Check its route on the map, click Convert and download the GPX result.
Yes. It opens the ZIP archive and reads the first KML file it finds. Images, overlays and 3D models inside the KMZ are not included in the GPX output.
The output uses GPX 1.1 with waypoints and tracks. Import rules vary between applications. Check the file in your target app, particularly if it requires timestamps or specific device fields.
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.
GPX output supports points and lines. Polygons and other unsupported geometry are skipped. A file containing only unsupported geometry cannot be converted to a usable GPX route.
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.
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.
JSZip reads the archive and uses its first KML file. Embedded images, overlays and models are not copied into the converted route.
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.
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.
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.
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.