KMZ / KML to GeoJSON Converter

Turn Google Earth KMZ or KML into GeoJSON for web maps, Python and databases. Attributes and folders preserved, nothing uploaded.

100% in your browserNo upload, no sign-upAttributes preservedChoose the output CRS
Drop your KMZ / KML file here or click to choose

Accepted: .kmz, .kml. Up to 20.0 MB, converted on your device.

Your file never leaves your device. Nothing is stored on any server.

GeoJSON is the format web developers, data scientists and modern GIS tools reach for first. Drop a KMZ or KML from Google Earth, Google My Maps or a drone mapping app and get a FeatureCollection with the same points, lines and polygons, every attribute as a property and the folder path kept, ready for Leaflet, MapLibre, GeoPandas, PostGIS or a GitHub repository.

How to convert KMZ to GeoJSON

Drop a .kmz or .kml file. The converter unzips it if needed, parses every placemark including nested folders, and shows them on the map.

Check the layer counts and attribute table. Attributes stored as HTML tables in descriptions are already split into fields.

Click Convert and download the .geojson. Use it in your web map, load it with GeoPandas or open it in QGIS.

What is a KMZ file?

A KMZ file is a zipped KML file. Google Earth saves placemarks, paths and polygons as KMZ so that the KML document and any icons or photos it references travel together in a single compressed file. Inside the archive you will usually find a doc.kml plus an images folder.

What is a GeoJSON file?

GeoJSON is a JSON-based format for geographic features, defined in RFC 7946. It is the native format of web mapping libraries such as Leaflet and MapLibre and is supported by QGIS, ArcGIS, PostGIS and most modern tools. Coordinates are always longitude/latitude in WGS84.

Why use this converter

Attributes are preserved

Attributes are preserved: placemark names, ExtendedData fields and even the key/value tables that Google Earth hides inside HTML descriptions are written as columns.

Folders kept as a property

The folder path of each placemark is written to a folder property, so you can filter or style features by the folders you organised in Google Earth.

Complete geometry support

Points, LineStrings, Polygons with holes, MultiGeometry and gx:Track recordings are converted to the matching GeoJSON geometry types, with 3D coordinates kept when present.

Nothing is uploaded

Everything runs in your browser. Your files are never uploaded, so confidential survey, cadastral or forestry data stays on your computer.

Frequently asked questions

Do I keep my attributes when converting KMZ to GeoJSON?

Yes. Placemark name, description, ExtendedData and Schema fields become properties on each feature. Description fields that contain an HTML table are split into separate properties, one per table row, and the folder path is stored in a folder property.

Which coordinate system does the output use?

WGS84 longitude/latitude (EPSG:4326). KML uses the same system, so no reprojection is required and coordinates match Google Earth exactly. If you need a projected dataset, use the KMZ to Shapefile converter and pick a UTM zone.

My KMZ contains several folders and mixed geometry types. Is that a problem?

No. GeoJSON allows mixed geometry in one FeatureCollection, so all features are written to one file with a folder property showing where each came from. MultiGeometry placemarks become MultiPoint, MultiLineString, MultiPolygon or GeometryCollection features as appropriate.

Is the KMZ to GeoJSON converter free? Is my file uploaded?

Free, no sign-up, and no upload. Unzipping, parsing and writing all happen in your browser, so the data never leaves your computer.

Can I open the GeoJSON in QGIS, ArcGIS or a web map?

Yes. The output is a standard RFC 7946 FeatureCollection that opens in QGIS, ArcGIS Pro, geojson.io and any web mapping library, and can be loaded by GeoPandas, PostGIS (ST_GeomFromGeoJSON) or Turf.js.

Are icons, styles and images from the KMZ included?

No. GeoJSON has no standard for styling or embedded images, so only geometry and attributes are converted. Style URLs are not written as properties; if you need colours, apply them in your map library based on the attributes.