Developer tool

KMZ to GeoJSON Converter

Convert Google Earth KMZ archives into GeoJSON for Leaflet, Mapbox, QGIS and PostGIS.

KMZ GeoJSON
PrivConvert
Privacy-first conversion
No files stored
In-memory processing
Deleted instantly
No sign-up needed

Complete the security check to begin

About Converting KMZ to GeoJSON

A KMZ is not really its own format — it is a ZIP archive with a KML document inside it, named doc.kml, alongside any icons or overlays the map uses. That is what Google Earth hands you when you save a project, and it is why dropping the file straight into Leaflet, Mapbox GL, OpenLayers, D3 or a PostGIS import fails: those tools all speak GeoJSON, and a KMZ looks to them like a binary archive. This converter opens the archive, reads the KML inside it, and re-expresses your placemarks, paths and polygons as a GeoJSON FeatureCollection.

The geometry mapping is direct: a KML Point becomes a GeoJSON Point, a LineString becomes a LineString, and a Polygon with inner boundaries keeps its holes. Placemark names and descriptions are carried into each feature’s properties object so nothing that identifies your features is lost. What does not survive is the presentation layer — KML styles, icon images and screen overlays have no GeoJSON equivalent, because GeoJSON deliberately describes geometry and attributes only, and leaves styling to the map library.

Common use cases

  • Loading a Google Earth project into a Leaflet, Mapbox GL or OpenLayers web map
  • Importing field survey data into PostGIS, QGIS or a data pipeline that expects GeoJSON
  • Turning a shared KMZ of sites or boundaries into something you can query with code
  • Feeding coordinates into a Python or JavaScript analysis without writing a KML parser
  • Publishing map data as an API response, where GeoJSON is the standard payload

Tips for best results

  • Coordinate order flips between the two formats: KML writes longitude,latitude,altitude while GeoJSON writes [longitude, latitude]. Both put longitude first, which is the opposite of how people usually say a coordinate aloud, and the converter handles it either way.
  • If your KMZ contains several .kml files, the one named doc.kml is used — that is the entry Google Earth itself treats as the document root.
  • Altitude values in the source are preserved as the optional third element of each coordinate, so elevation profiles survive.
  • The archive is inspected without being unpacked to disk, and the declared size of the inner KML is checked before any decompression happens, so a maliciously compressed file is rejected rather than expanded.

How to Convert KMZ to GeoJSON Online

Converting KMZ to GeoJSON with PrivConvert takes three quick steps and no software to install. What you gain with GeoJSON: parsed natively by every web language and mapping library.

1
Upload your KMZ file

Drag and drop your file into the upload area, click to browse your device, or paste a URL to a file hosted online. You can upload files up to 250 MB and batch convert up to 20 files at once.

2
Automatic conversion

Once uploaded, the conversion from KMZ to GeoJSON starts automatically. The process runs entirely in an isolated environment - your data never leaves the secure pipeline.

3
Download your GeoJSON file

Your converted file is ready instantly. Click the download button to save it to your device. The file is deleted from memory immediately after download.

What makes this KMZ-to-GeoJSON converter different

Privacy here is not a checkbox. Every KMZ-to-GeoJSON conversion is engineered so your data never lingers, leaks or gets reused.

Encrypted transfers

Every upload and download is protected with TLS 1.3, so your file cannot be intercepted on the way to the server or back to you.

No account required

Convert instantly with no sign-up, no email and no profiling cookies. We never build a profile around you or the files you convert.

Works on any device

Runs in any modern browser on Windows, macOS, Linux, Android and iOS — no install, plugin or desktop software needed.

Fast in-memory processing

Each job runs in an isolated in-memory sandbox, so most conversions finish in seconds instead of waiting in a queue.

KMZ vs GeoJSON - Format Comparison

FeatureKMZGeoJSON
File extension.kmz.geojson
Supported by PrivConvertYes (as input)Yes (as output)
Privacy-safe conversionIn-memory, zero storage
Max file size250 MB per file
Batch supportUp to 20 files simultaneously

Built for people who value their privacy

From one-off files to daily batches, thousands of people rely on PrivConvert precisely because it keeps nothing once the job is done.

250 MB Max file size
450+ Conversion tools
0 sec File retention
100% Free to use

Frequently Asked Questions

How do I convert KMZ to GeoJSON?
Upload your .kmz file above, complete the quick security check, and a GeoJSON FeatureCollection is generated instantly. No install or sign-up required.
Do polygon holes survive the conversion?
Yes. A KML Polygon with inner boundaries becomes a GeoJSON Polygon with those rings preserved as holes, rather than being flattened into separate shapes.
What is the difference between KML and KMZ?
KML is a single XML document. KMZ is a ZIP archive containing that document as doc.kml plus any images or overlays it references. KMZ exists because it is one compact file you can email, where a KML with separate icon files is several.
Why did my styling disappear?
GeoJSON has no styling syntax at all — by design. It carries geometry and properties, and the map library decides how to draw them. Style your features in Leaflet or Mapbox instead, keyed off the properties that were preserved.
Are Placemark names kept?
Yes. Each Placemark’s name and description become entries in that feature’s GeoJSON properties object, so you can label and popup from them directly.
Is my map data uploaded anywhere permanent?
No. The archive is read in memory, converted, and discarded the moment your download is ready. Nothing is stored and no coordinates are logged.

Further Reading