KMZ to CSV Converter
Extract coordinates and attributes from a KMZ into a CSV you can open in Excel or Google Sheets. Free, private, and nothing is uploaded.
Accepted: .kmz, .kml. Up to 20.0 MB, converted on your device.
Your file never leaves your device. Nothing is stored on any server.
When a colleague sends a KMZ of sample plots, boreholes or shops, you often just need the coordinates and names in a spreadsheet. This converter opens the KMZ, reads every placemark including those in nested folders, and writes a CSV with one row per feature: latitude and longitude for points, the geometry as WKT for lines and polygons, and every attribute as a column.
How to convert KMZ to CSV
Drop a .kmz or .kml file. The preview lists how many points, lines and polygons were found and shows the first rows of the attribute table.
Review the columns in the attribute table; HTML description tables are already split into separate fields.
Click Convert and download the .csv. Open it in Excel, Google Sheets, LibreOffice or import it into a database.
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 CSV / Excel file?
A CSV or Excel spreadsheet is the simplest way to store point data: one row per location with latitude and longitude columns, plus any number of attribute columns. GPS units, survey forms and field apps often export this way. Lines and polygons can be represented with a WKT column.
Why use this converter
Ready for Excel
The CSV is UTF-8 with a byte order mark and Windows line endings, so Excel opens it directly with names in Bahasa Indonesia, Hindi, Chinese or any other language displayed correctly.
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.
Lines and polygons too
Points get latitude and longitude columns. Lines and polygons are written as WKT (Well-Known Text) in a wkt column, which QGIS, PostGIS and this site can read back.
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
Which attributes end up in the CSV?
All of them: the placemark name, description, every ExtendedData and Schema field, plus a folder column with the folder path. If the description contains an HTML table, its rows are split into separate columns so you do not have to clean up HTML in Excel.
In what coordinate system are the latitude and longitude values?
WGS84 decimal degrees, exactly as stored in the KMZ, with latitude and longitude in separate columns. That is the format Excel maps, Google Sheets, Power BI and most GPS software expect.
My KMZ has folders and both points and polygons. How is that represented?
Everything goes into one CSV. A folder column records where each placemark came from, points have latitude and longitude, and lines and polygons have their geometry in a wkt column. If you would rather have separate tables, convert to shapefile first and then export each layer.
Is the KMZ to CSV converter free, and is my file uploaded?
Yes, it is free, and no. Reading the KMZ and writing the CSV happen in your browser, so your placemarks are never sent to a server.
Can I get the CSV back into QGIS or ArcGIS?
Yes. In QGIS use "Add Delimited Text Layer" and choose the latitude and longitude columns, or the wkt column for lines and polygons. ArcGIS reads point CSVs via "XY Table to Point". You can also convert the CSV back to KML on this site.
What about altitude values?
The CSV is written in 2D: latitude, longitude and WKT without altitude. If you need the Z values, convert to shapefile with "Keep Z values" ticked or to GeoJSON, which keeps 3D coordinates.