Convert KMZ to CSV to unpack a zipped Google Earth file straight into spreadsheet rows, skipping the manual unzip entirely. Decompression and parsing run inside the page, so the archive is never uploaded.
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 CSV, and what to watch for.
| What | KMZ → CSV | |
|---|---|---|
| Geometry | Changes | Point features become X and Y columns; lines and polygons are written to a WKT geometry column, so no shape is lost in the table. |
| Attributes | Kept | Every column and full field name moves from KMZ into CSV untouched. |
| Styling & labels | Dropped | KMZ colours, icons and description balloons are presentation, not data. CSV stores the underlying features, so styling is dropped (the geometry and attributes remain). |
| Coordinate system | Changes | CSV stores raw coordinates without a CRS tag, so note the coordinate system separately for whoever opens the file. |
| Elevation (Z) | Changes | Z values, if present, appear as an extra column rather than 3D geometry. |
| File structure | Kept | A single, self-contained .csv file you can move around on its own. |
A KMZ is a zipped Google Earth map, often full of placemarks, tours and overlays. That is great for viewing, but hard to analyze. So people convert KMZ to CSV to pull the placemark coordinates and labels into a plain table. Then you can open the rows in Excel or Google Sheets, sort and filter them, or edit attributes by hand. A CSV also feeds cleanly into scripts and APIs. For example, load it with pandas to batch-process points, or push the same table back into QGIS as map layers.
KMZ is already defined in WGS84 longitude/latitude (EPSG:4326), so no guessing is needed on the way in.
CSV stores raw coordinates without a CRS tag, so make a note of the coordinate system for whoever opens the file next. 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.
A KMZ is a ZIP archive, so this tool opens it and reads the KML inside first. Then it writes each placemark as a row with longitude and latitude columns. However, KMZ styling, icons and ground overlays do not fit a flat table, so they drop out. Also, lines and polygons flatten awkwardly into text, so CSV suits point placemarks best. Check that your key labels landed in columns before you rely on the file.
KMZ files typically come out of Google Earth, Google Maps, QGIS, ArcGIS. Once you convert to CSV, the file opens in Microsoft Excel, Google Sheets, LibreOffice Calc, and any script or database import. The CSV output follows the standard specification exactly, so those programs read it without any special import settings.
A KMZ usually starts life as a saved Google Earth map, a zipped bundle of placemarks and styling. CSV is where that same data becomes analyzable rows. This conversion unzips the archive, reads the map features inside, and lays out their coordinates and labels as spreadsheet columns. In practice you do it when a colleague sends a Google Earth file but you need the points in Excel, pandas, or a database. That means pulling geometry out of a viewer and into a table.
Yes, placemark names and description text become columns alongside the longitude and latitude values. Styling, icons and overlays are dropped, since a flat CSV table cannot hold them.
Yes. The output is plain comma-separated text, so it opens directly in Excel or Google Sheets, and reads cleanly with pandas for scripting.
CSV stores one row per feature, so each line or polygon is written with its geometry as a WKT string in a column. Simple placemarks give a clean latitude and longitude pair. More complex shapes keep their full vertex list in that WKT field, which QGIS or pandas can read back.
Yes. Each placemark's name and any ExtendedData fields from the original Google Earth map turn into their own CSV columns. Custom icons, ground overlays, and styling do not survive, because a spreadsheet holds text and numbers only. Once open in Excel or Google Sheets, you can sort and filter those attributes directly.
A CSV file opens in Excel, Google Sheets, LibreOffice and any database. Because the output follows the standard specification, any tool that supports CSV 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 CSV stores the underlying data, not its presentation; the placemarks and their information are kept.
