KMZ to Shapefile Converter
Convert KMZ and KML files to ESRI Shapefile for free. Files stay on your device, attributes are kept, and you choose the coordinate system.
Accepted: .kmz, .kml. Up to 20.0 MB, converted on your device.
Your file never leaves your device. Nothing is stored on any server.
Drop a KMZ or KML file exported from Google Earth, a GPS app or a field survey tool. The converter unzips it, reads every placemark including nested folders and multi-part geometries, and writes standard shapefiles that open directly in QGIS, ArcGIS, AutoCAD Map and Global Mapper.
How to convert KMZ to Shapefile
Select or drag a .kmz or .kml file. The map preview shows every placemark so you can confirm the file was read correctly.
Pick the output coordinate system. WGS84 is the default; choose the recommended UTM zone if you need distances and areas in metres.
Click Convert and download a ZIP with one shapefile per geometry type (.shp, .shx, .dbf, .prj, .cpg) plus a field mapping file.
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 Shapefile?
The ESRI Shapefile is the most widely supported vector format in GIS. A "shapefile" is really a set of files with the same base name: .shp holds the geometry, .shx the index, .dbf the attribute table, .prj the coordinate system and .cpg the text encoding. Each shapefile stores a single geometry type, which is why a mixed KML becomes several shapefiles.
Why use this converter
Nothing is uploaded
Everything runs in your browser. Your files are never uploaded, so confidential survey, cadastral or forestry data stays on your computer.
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.
Mixed geometry and folders handled
Mixed geometries are handled automatically. Points, lines and polygons are separated into their own layers, and you can split by folder as well.
Correct coordinate system
Choose the coordinate system for the output: WGS84, Web Mercator or the correct UTM zone for your area, with a proper .prj file so QGIS and ArcGIS read it correctly.
Frequently asked questions
Will my attributes be lost when converting KMZ to shapefile?
No. Placemark names, ExtendedData and SchemaData fields are written to the .dbf table. If your KMZ stores attributes as an HTML table inside the description (common for files exported from ArcGIS or QGIS), each row becomes a column. Field names longer than 10 characters are shortened, and a field_mapping.csv in the download lists the original names.
What coordinate system does the shapefile use?
KMZ files are always WGS84 latitude/longitude, and that is the default output (EPSG:4326). You can switch to Web Mercator (EPSG:3857) or let the tool recommend the UTM zone for your data, for example UTM 49S for Java or UTM 43N for Delhi. A .prj file is always included.
My KMZ has several folders and mixed geometry. What happens?
A shapefile can hold only one geometry type, so the converter writes separate _points, _lines and _polygons shapefiles and skips the ones that would be empty. Tick "Split by folder" to additionally get one set of shapefiles per top-level folder. The folder path is also kept as an attribute.
Is the KMZ to SHP converter free, and are my files uploaded?
It is free with no account. The conversion runs in your browser using JavaScript, so the file never leaves your computer. You can even use it offline once the page has loaded. Files up to 20 MB are supported today.
Can I open the result in QGIS or ArcGIS?
Yes. The output is a standard ESRI shapefile with a .prj coordinate system file and a .cpg file declaring UTF-8 text, so names in Bahasa Indonesia, Hindi, Chinese or any other language display correctly. Drag the ZIP into QGIS, or unzip it and add the .shp in ArcGIS Pro or ArcMap.
Does it handle polygons with holes and MultiGeometry?
Yes. Inner boundaries become polygon holes with the correct ring orientation, MultiGeometry placemarks are written as multi-part shapes, and gx:Track elements from GPS recordings are converted to lines.
What about elevation (altitude) values?
By default altitude is dropped and 2D shapefiles are written, which is what most users expect. Tick "Keep Z values" to write PointZ, PolyLineZ and PolygonZ shapes instead.