Add your KMZ
Drop a KMZ archive anywhere on this page
.kmz · it never leaves the browser
Options
Your GPX
Add a KMZ archive and the GPX appears here, with its feature counts and anything this pair cannot carry.
What comes across, and what cannot
Preserved
- Geometry — points and lines come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
- Names come across as the waypoint or track name; elevation is kept where a Z ordinate exists.
- Elevation (the Z ordinate) is preserved where the source has one.
Dropped
- Styling. KMZ carries Style and StyleMap elements — icon, colour, line width, fill — and GPX has nowhere to put them, so they are dropped. Style the data on the map instead.
- Areas. GPX has no polygon type, so each ring is written as a closed track: the shape survives, the fact that it encloses an area does not.
- Most attributes. GPX defines a fixed vocabulary per point — name, description, elevation, time — and anything outside it has no home, so only the name field is carried across.
- The archive's payload. A KMZ bundles icons, overlay images and any other resource its KML references; only the KML document is read, so those files stay behind in the zip and are not represented in the GPX.
KMZ (zipped KML)
A zip archive containing one KML document plus the images and icons it references. Reading one means unzipping it and reading the KML inside — which this tool does for you, in the browser.
.kmz · application/vnd.google-earth.kmz
GPS Exchange Format (GPX)
What GPS units and fitness apps speak. It has exactly three containers — waypoints, routes and tracks — so it holds points and lines but has no concept of an area, and only a fixed set of fields per point.
.gpx · application/gpx+xml
Convert KMZ to GPX, step by step
- Step 1
Add your KMZ
Drop a KMZ archive anywhere on the page, paste it, point at a URL, or press Sample to start from real data. Several files at once are fine.
- Step 2
Set what matters
Coordinate precision and simplification on every pair, plus the handful of settings this one needs — waypoints or tracks.
- Step 3
Take the GPX
Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.
Your data never leaves the page
Every conversion, measurement and export happens client-side. Nothing is uploaded, logged or stored — you can even use this offline once the page has loaded. Only “Open in Studio” sends data, and only after you sign in.
Good to know
- What is preserved when converting KMZ to GPX?
- Geometry — points and lines come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude. Names come across as the waypoint or track name; elevation is kept where a Z ordinate exists. Elevation (the Z ordinate) is preserved where the source has one.
- What is lost converting KMZ to GPX?
- Styling. KMZ carries Style and StyleMap elements — icon, colour, line width, fill — and GPX has nowhere to put them, so they are dropped. Style the data on the map instead. Areas. GPX has no polygon type, so each ring is written as a closed track: the shape survives, the fact that it encloses an area does not. Most attributes. GPX defines a fixed vocabulary per point — name, description, elevation, time — and anything outside it has no home, so only the name field is carried across. The archive's payload. A KMZ bundles icons, overlay images and any other resource its KML references; only the KML document is read, so those files stay behind in the zip and are not represented in the GPX.
- What is the difference between KMZ and KML?
- A KMZ is a zip archive with one KML document inside it, plus any icons or overlay images that document points at. The tool unzips it in the browser and reads the KML — you never have to unzip it yourself.
- What happens to the images inside the archive?
- Icon and overlay images stay in the archive and are not carried into GPX, which has no way to reference them. Only the placemarks, their geometry and their attributes come out.
- Waypoints or tracks?
- Both, and you decide. Left on automatic, points become <wpt> waypoints and lines become <trk> tracks. Force waypoints and every vertex of every line is written as a separate waypoint; force tracks and your points are threaded, in order, into a single track — which is how you turn a list of stops into a route a GPS unit will follow.
- Will it load on my Garmin or in Strava?
- The output is GPX 1.1 with the standard namespace and no extensions, which is the dialect Garmin, Wahoo, Strava, Komoot and OsmAnd all accept. Elevation is written as <ele> when the source has a Z ordinate.
- Is my file uploaded anywhere?
- No. The KMZ is read, converted and written entirely inside this page — there is no upload, no queue, no server-side copy and no size limit imposed by a plan. Large files are parsed in a background worker so the page stays responsive. The only action that transmits anything is Open in Studio, and that happens after you sign in and press it.
- Is there a limit on file size or number of files?
- There is no imposed limit; the practical ceiling is your browser's memory. Files over about 5 MB are handed to a web worker so the interface keeps responding, and you can drop several files at once — each is converted separately and the set can be downloaded as one zip.