Convert GeoJSON to KMZ to get a compressed, single-file version of your layer that emails well and opens in Google Earth by double-click. Both the conversion and the zipping happen inside this page.
Drop a file here, or click to browse
KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more
No GeoJSON file to hand? Download a sample GeoJSON 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 GeoJSON to KMZ, and what to watch for.
| What | GeoJSON → KMZ | |
|---|---|---|
| Geometry | Kept | Points, lines and polygons are preserved exactly, including multi-part shapes. |
| Attributes | Kept | Every column and full field name moves from GeoJSON into KMZ untouched. |
| Styling & labels | Changes | KMZ supports styling; features are written with clean default styling and a name label you can restyle in Google Earth. |
| Coordinate system | Changes | KMZ 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 GeoJSON into KMZ wherever the source records them. |
| File structure | Kept | One compact .kmz (a zipped KML), easy to email and quick to open in Google Earth. |
GeoJSON is the working format of web maps. It lives inside Leaflet, Mapbox and OpenLayers, and it moves cleanly through web APIs. However, most people cannot open a raw .geojson file, and it carries no icons or overlays. KMZ solves the handoff. It wraps your KML in a single small archive that Google Earth opens with a double click. So teams convert GeoJSON to KMZ to turn live web data into a finished map they can email. For example, you can package field points from an API and share them, custom icons and ground overlays included, as one tidy file.
GeoJSON is already defined in WGS84 longitude/latitude (EPSG:4326), so no guessing is needed on the way in.
KMZ 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 GeoJSON data is in the wrong place" surprise; the guide on coordinate systems and EPSG codes goes deeper.
Check your coordinates first. RFC 7946 GeoJSON is defined in WGS84 lon/lat, which is exactly what KML inside the KMZ expects, so points usually land correctly. However, if your GeoJSON was written in another projection, reproject it to EPSG:4326 before converting. Also remember KMZ is a zipped container. The download is one .kmz, not loose files, so do not unzip it before opening it in Google Earth.
GeoJSON files typically come out of Leaflet, Mapbox GL, OpenLayers, QGIS, GDAL. Once you convert to KMZ, the file opens in Google Earth Pro and Google Earth for web by a simple double-click, plus QGIS and ArcGIS Pro. The KMZ output follows the standard specification exactly, so those programs read it without any special import settings.
GeoJSON is the format a Leaflet layer or a web API usually hands you, plain text full of features and their properties. KMZ is what Google Earth opens by default, a zipped KML you can email as a single file. Converting rewrites each GeoJSON feature as a placemark, then packs the resulting KML into that one archive. Because Google Earth will not read GeoJSON directly, this step is how data from the browser mapping stack reaches a 3D globe.
Yes, attribute properties carry into the KML inside the KMZ, where Google Earth shows them in each placemark's description balloon. Very rich or deeply nested JSON values may be flattened to plain text.
KMZ is a KML document zipped into a ZIP archive. This tool re-zips it on the way out, so it stays small and can bundle icons and overlays. Open it directly in Google Earth, ArcGIS or QGIS without unzipping.
Each feature's properties become the placemark description and ExtendedData, so your attributes stay attached. Google Earth shows them in the balloon when you click a placemark. Nested objects and arrays are flattened to plain text values.
Standard GeoJSON carries geometry and properties but no styling, so colors and icons from your Leaflet or Mapbox map do not travel across. Google Earth applies its default placemark style instead. You can then restyle points, paths and polygons inside Earth itself.
A KMZ file opens in Google Earth by double-click, plus QGIS and ArcGIS. Because the output follows the standard specification, any tool that supports KMZ will read it without special settings.
No conversion is perfectly loss-free because each format stores different things, but geometry and attributes are preserved; only presentation-level styling (which KMZ does not store) is left behind.
