Convert KMZ to GeoJSON and turn a compressed Google Earth layer into web-ready JSON in one step. Your archive is unzipped and translated on-device; no server ever sees it.
Drop a file here, or click to browse
KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more
No KMZ file to hand? Download a sample KMZ file (100 points) and drop it above to see the conversion.
Every format stores different things, so a conversion is never perfectly loss-free. Here is exactly what carries over when you convert KMZ to GeoJSON, and what to watch for.
| What | KMZ → GeoJSON | |
|---|---|---|
| Geometry | Kept | Points, lines and polygons are preserved exactly, including multi-part shapes. |
| Attributes | Kept | Every column and full field name moves from KMZ into GeoJSON untouched. |
| Styling & labels | Dropped | KMZ colours, icons and description balloons are presentation, not data. GeoJSON stores the underlying features, so styling is dropped (the geometry and attributes remain). |
| Coordinate system | Changes | GeoJSON is defined in WGS84 (EPSG:4326), so data is reprojected to lon/lat on the way out. |
| Elevation (Z) | Kept | 3D Z values carry from KMZ into GeoJSON wherever the source records them. |
| File structure | Kept | A single, self-contained .geojson file you can move around on its own. |
A KMZ file is a zipped Google Earth map. Inside sits a KML document, sometimes with icons, images and ground overlays. That packaging is great for emailing a finished map. However, it does not fit a web app. GeoJSON is what the modern web-mapping stack actually reads. So people convert KMZ to GeoJSON to move placemarks and paths out of Google Earth and into a live map. For example, you can render the features directly in Leaflet, Mapbox GL or OpenLayers, pass them through a web API, or track the plain-text output in version control.
KMZ is already defined in WGS84 longitude/latitude (EPSG:4326), so no guessing is needed on the way in.
GeoJSON is defined in WGS84 (EPSG:4326), so the output is reprojected to longitude/latitude, exactly what Google Earth and web maps expect. A quick CRS check before you download saves the classic "my KMZ data is in the wrong place" surprise; the guide on coordinate systems and EPSG codes goes deeper.
The KMZ is a ZIP archive, so this tool opens it and reads the KML inside first. Check that the KML holds real vector features, not just image overlays or bundled icons. GeoJSON stores geometry and attributes, not KML styling. So colors, icon graphics and label styles from Google Earth will not carry into the GeoJSON. Expect coordinates in WGS84 lon/lat.
KMZ files typically come out of Google Earth, Google Maps, QGIS, ArcGIS. Once you convert to GeoJSON, the file opens in web maps built on Leaflet, Mapbox GL or OpenLayers, and desktop tools like QGIS. The GeoJSON output follows the standard specification exactly, so those programs read it without any special import settings.
A KMZ is the zipped map you export from Google Earth, with placemarks and paths tucked inside a compressed KML. GeoJSON is what a web map wants to read directly. This conversion opens that archive, pulls out the features, and rewrites them as plain JSON. In practice you do it when a Google Earth deliverable needs to appear in a Leaflet or Mapbox layer, or feed a web API. Because both sit in WGS84 lon/lat, the coordinates carry across cleanly.
No. GeoJSON stores geometry and attribute data, not KML style rules. So placemark colors, custom icons and label formatting are dropped, and you restyle the features in your web map instead.
The tool reads the KML document inside the ZIP and extracts its vector features. Bundled images, custom icon files and ground overlays are not written into the GeoJSON, since GeoJSON only carries geometry and attributes.
GeoJSON stores only geometry and attributes, so packaged icons, ground overlays and photos are not carried into the output. Placemark names and descriptions survive as feature properties. If you relied on custom Google Earth symbols, expect to restyle them in Leaflet or Mapbox GL afterward.
GeoJSON has no folder concept, so nested Google Earth folders are flattened into one FeatureCollection. Mixed geometry types like points, lines and polygons can coexist in that single collection, which OpenLayers and QGIS both read without complaint. If you need the grouping back, keep a folder name as a property before converting.
A GeoJSON file opens in web maps (Leaflet, Mapbox, OpenLayers) and QGIS. Because the output follows the standard specification, any tool that supports GeoJSON will read it without special settings.
No conversion is perfectly loss-free because each format stores different things, but Google Earth styling (colours and icons) is dropped because GeoJSON stores the underlying data, not its presentation; the placemarks and their information are kept.
