Skip to content

Convert KMZ to KML

1

Add your KMZ

Drop a KMZ archive anywhere on this page

.kmz · it never leaves the browser

2

Options

≈ 11 cm on the ground
Keep every vertex
00verticesunchanged
Becomes <name>; the rest goes into ExtendedData.
Becomes the balloon text.
3

Your KML

Add a KMZ archive and the KML appears here, with its feature counts and anything this pair cannot carry.

Converted in this tab. Your KMZ is never uploaded — reading, converting and writing all run in the browser, so this works offline once the page has loaded.
— , —
FidelityKMZKML

What comes across, and what cannot

Preserved

  • Geometry — points, lines and polygons come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
  • Every attribute survives, with its name intact.
  • Elevation (the Z ordinate) is preserved where the source has one.

Dropped

  • 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 KML.

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

Keyhole Markup Language (KML)

The XML format Google Earth popularised. Placemarks carry a name, a description balloon, a geometry and — unlike GeoJSON — presentation: styles, icons, colours, altitude modes and time stamps.

.kml · application/vnd.google-earth.kml+xml

HowHow it works

Convert KMZ to KML, step by step

  1. 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.

  2. Step 2

    Set what matters

    Coordinate precision and simplification on every pair, plus the handful of settings this one needs — which field becomes the placemark name and description.

  3. Step 3

    Take the KML

    Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.

PrivateRuns in your browser

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.

Go furtherTurn a GeoJSON into an interactive mapRead the guide
FAQQuestions

Good to know

What is preserved when converting KMZ to KML?
Geometry — points, lines and polygons come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude. Every attribute survives, with its name intact. Elevation (the Z ordinate) is preserved where the source has one.
What is lost converting KMZ to KML?
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 KML.
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 KML, which has no way to reference them. Only the placemarks, their geometry and their attributes come out.
Which field becomes the placemark name?
Whichever you choose in step 2. The tool pre-selects a field called name, title or label if it finds one; every other attribute is written into <ExtendedData> so Google Earth shows it in the balloon. You can also nominate a field to become the <description>.
Will the output open in Google Earth?
Yes — the file is KML 2.2 with a single <Document>, one <Placemark> per feature and no vendor extensions, which is what Google Earth, Google My Maps, QGIS and ArcGIS all read.
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.