Convert KMZ to GeoJSON
From the Google Earth archive to a GeoJSON for web maps and code, no unzipping by hand.
Nothing is uploaded
QGIS plugin
AI Agent for QGIS
Skip the converter next time: ask AI Agent in QGIS to convert, reproject and load your files.
AI Segmentation
AI EditGuide
How it works, formats and limits.
About this tool
From the Google Earth archive to a GeoJSON for web maps and code, no unzipping by hand. Free, and the file never leaves your browser.
How the conversion works
- Choose a .kmz file or drop it on the page.
- The page unzips the archive in memory, reads the doc.kml inside, and writes each Placemark as a GeoJSON Feature: Point, LineString, Polygon or their Multi types, with name, description, folder and ExtendedData as properties.
- Download the .geojson and use it in QGIS, Leaflet, Mapbox, geojson.io or your own code.
How each part is mapped
RFC 7946 GeoJSON, longitude first, WGS 84.
| KMZ | GeoJSON |
|---|---|
| doc.kml inside the archive | Read as the source; doc.kml at the root wins, otherwise the first .kml found. |
| Placemark with a Point, LineString or Polygon | A Feature with the same geometry type. |
| MultiGeometry | The matching Multi geometry, or a GeometryCollection when the parts are of different kinds. |
| name, description | Properties name and description. |
| ExtendedData | One property per field. |
| Icons, overlays, styles | Left out. |
What it does not do
- Icons, ground overlays and styles are dropped: GeoJSON has no place for them.
- NetworkLinks are not followed.
- Files up to 50 MB.
Frequently asked questions
Short answers to what people ask most.
Does my file get uploaded?
No. The conversion runs in your browser tab. Nothing is sent, and closing the tab clears it.
Do I need to unzip the KMZ first?
No. The page unzips it in memory and reads the KML inside.
Is the output valid for Leaflet or Mapbox?
Yes. It is a FeatureCollection in WGS 84 with longitude first, which both load as is.
Are the ExtendedData fields kept?
Yes, each field becomes a property of the feature, in both the Data and the SchemaData spellings.