KML to Shapefile Converter
Common when features are drawn in Google Earth but downstream GIS work (ArcGIS, QGIS) demands shapefile.
Common issues converting KML to Shapefile
- KMLs with mixed geometry types (points + lines + polygons) can't go into a single shapefile. Split by geometry type in Google Earth (one folder per type) and convert each separately.
- KML <ExtendedData> names longer than 10 characters are truncated in the resulting DBF. Rename long fields before conversion if the exact names matter.
- KML styles (icons, colors, line widths) have no shapefile equivalent and are dropped. Shapefile carries no styling — symbology must be applied in ArcGIS/QGIS after import.
- NetworkLinks and GroundOverlays are dropped. Only vector <Placemark> features are converted.
Frequently asked questions
Can I convert a KML with points, lines, and polygons all together?
Not into a single shapefile — the format allows exactly one geometry type per file. Split the KML by geometry type first (folders in Google Earth are a natural way) and convert each.
Do ExtendedData fields become shapefile attributes?
Yes. Each <Data name='...'> child becomes a column in the .dbf file. Names are truncated to 10 characters per the DBF spec.
Is the .prj file included?
Yes. KML is always WGS 84, and the output pins the shapefile to EPSG:4326 so tools requiring explicit projection metadata load it without warnings.
Will my KML styling carry over?
No. Shapefile has no styling layer. Re-apply symbology in ArcGIS or QGIS after import.