Skip to content
Spatly

Convert KMZ to GeoJSON

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
3

Your GeoJSON

Add a KMZ archive and the GeoJSON 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.
— , —
FidelityKMZ → GeoJSON

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.
  • Feature order is preserved, so a row in the output is the same feature as the row in your input.

Dropped

  • Styling. KMZ carries Style and StyleMap elements — icon, colour, line width, fill — and GeoJSON has nowhere to put them, so they are dropped. Style the data on the map instead.
  • Time as a dimension. KMZ's TimeStamp and TimeSpan elements are read as ordinary attributes, which is as close as GeoJSON gets to a clock.
  • 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 GeoJSON.

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

GeoJSON (RFC 7946)

The web's lingua franca for vector data: plain JSON, WGS84 longitude/latitude, every geometry type, and an untyped property bag per feature. It carries no styling — colour and symbology belong to the map, not the file.

.geojson · .json · application/geo+json

AlsoShapefile to GeoJSONKML to GeoJSONKMZ to KMLKMZ to GPXAll conversions
HowHow it works

Convert KMZ to GeoJSON, 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.

  3. Step 3

    Take the GeoJSON

    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 GeoJSON?
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. Feature order is preserved, so a row in the output is the same feature as the row in your input.
What is lost converting KMZ to GeoJSON?
Styling. KMZ carries Style and StyleMap elements — icon, colour, line width, fill — and GeoJSON has nowhere to put them, so they are dropped. Style the data on the map instead. Time as a dimension. KMZ's TimeStamp and TimeSpan elements are read as ordinary attributes, which is as close as GeoJSON gets to a clock. 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 GeoJSON.
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 GeoJSON, which has no way to reference them. Only the placemarks, their geometry and their attributes come out.
Is the GeoJSON valid RFC 7946?
Yes: a single FeatureCollection, coordinates as [longitude, latitude], no CRS member — the RFC dropped it and mandates WGS84. Use the GeoJSON editor afterwards if you also want winding order and ring closure checked.
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.