CSV to KML Converter
Fastest path from a spreadsheet of locations to something you can visualize in Google Earth or share with non-GIS stakeholders.
Common issues converting CSV to KML
- Coordinate columns must be identified — use the mapper to confirm. Files where coordinates are combined in one cell (e.g. '48.1351, 11.5820') can be split automatically.
- Row counts above ~100,000 start to slow Google Earth rendering. Cluster, split, or simplify before converting for large datasets.
- Pin styling defaults to Google Earth's yellow pushpin. Add <Style> blocks to the KML afterwards if you need color-coding by attribute.
- This isn't a geocoder. If your CSV has addresses but no coordinates, geocode first with a service like Google or Nominatim.
Frequently asked questions
Which column becomes the pin label in Google Earth?
A column named 'name' if one exists. Otherwise the first non-coordinate text column is used. Rename the desired column to 'name' in your CSV to control this.
What happens to non-coordinate columns?
They become <ExtendedData> fields on each Placemark, visible in Google Earth's info popup when a user clicks a pin.
Can I style the pins?
Not automatically from CSV data — the output uses Google Earth's default pushpin. Add <Style> blocks manually afterwards or use a styling tool.
Does the converter handle European decimal commas?
Yes. Numeric values using a comma as the decimal separator are normalized. Semicolon-delimited CSVs still need to be converted to comma-delimited first.