KML to CSV Converter
When a stakeholder has dropped pins in Google Earth and the team needs that list in a spreadsheet or a database.
Common issues converting KML to CSV
- Lines and polygons contribute their centroid to the lat/lng columns. If you need the full geometry preserved per row, convert to WKT instead.
- Folder hierarchy inside the KML is flattened — every Placemark becomes a row regardless of nesting. A 'folder' column records the immediate parent folder name.
- Placemark styling is not exported. Only vector data and ExtendedData fields are preserved in the CSV.
- <Description> fields sometimes contain embedded HTML. Those HTML strings pass through as-is into the description column; strip or sanitize downstream if needed.
Frequently asked questions
What columns are in the output?
'name' and 'description' from the Placemark, 'latitude' and 'longitude' from the geometry, plus one column per ExtendedData <Data> element found across the file.
How are lines and polygons represented?
As their centroid in the lat/lng columns. For full geometry preservation convert to WKT instead.
What about nested folders in the KML?
Folder structure is flattened — every Placemark becomes a row regardless of how deeply it's nested. An optional 'folder' column records the parent folder name.
Is the output UTF-8?
Yes, UTF-8 with a BOM so Excel on Windows renders accented characters correctly on double-click.