CSV / Excel to KML Converter
Turn a spreadsheet of coordinates into KML or KMZ placemarks for Google Earth. Latitude and longitude columns are detected automatically. Free, no upload.
Accepted: .csv, .txt, .xlsx, .xls. Up to 20.0 MB, converted on your device.
Your file never leaves your device. Nothing is stored on any server.
Field surveys, GPS units and inventory systems usually produce a table: one row per location with latitude and longitude. To see those rows in Google Earth you need KML. Drop a CSV or an Excel workbook here; the converter finds the coordinate columns (latitude/longitude, lat/lon, y/x and similar names), turns each row into a placemark and keeps every other column as an attribute. Switch the output to KMZ if you want a compact file to share.
How to convert CSV to KML
Drop a .csv, .txt, .xlsx or .xls file. Coordinate columns are detected automatically; if they cannot be recognised you can pick the latitude and longitude columns (or a WKT column) yourself.
Choose which column should be the placemark name, and whether you want KML or KMZ output.
Click Convert and download the file. Open it in Google Earth or import it into Google My Maps.
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.
What is a KML file?
KML (Keyhole Markup Language) is an XML format for geographic data made popular by Google Earth and Google Maps. It stores points, lines and polygons in WGS84 latitude and longitude, groups them in folders, and can carry attributes in ExtendedData elements or in HTML descriptions.
Why use this converter
Excel and CSV supported
Both comma and semicolon separated CSV, including decimal commas, and .xlsx / .xls workbooks (first sheet) are accepted. No need to save as CSV first.
Coordinate columns detected
Columns named latitude, longitude, lat, lon, lng, x, y, northing, easting, lintang or bujur are recognised. Anything else can be selected manually in one click.
Every column becomes an attribute
All other columns are written as ExtendedData on the placemark, so Google Earth shows them in the balloon and GIS software can read them back as fields.
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
Are the other columns of my spreadsheet kept?
Yes. Apart from the coordinate columns, every column is written to the placemark as an ExtendedData field with its original header as the field name. Numbers stay numeric and dates from Excel are written as ISO dates.
What coordinate system should my CSV use?
KML requires WGS84 decimal degrees, so latitude should be between -90 and 90 and longitude between -180 and 180, for example -6.2088 and 106.8456 for Jakarta. Rows with empty or invalid coordinates are skipped and reported. If your data is in UTM metres, reproject it first (for example in QGIS) or convert the table to a shapefile with the correct .prj.
Can I create lines or polygons from a CSV?
Yes, if the table has a WKT column (LINESTRING, POLYGON, MULTIPOLYGON and so on). Choose it as the geometry column and each row becomes a path or polygon placemark. Building lines from ordered point rows is not supported yet.
Is the CSV to KML converter free, and is my spreadsheet uploaded?
It is free and the spreadsheet is never uploaded. The CSV or Excel file is parsed by your browser, so customer lists or survey data stay private.
Will the KML open in Google Earth, Google My Maps and QGIS?
Yes. The output is standard KML 2.2 (or a zipped KMZ), which opens in Google Earth Pro, Google Earth mobile, Google My Maps, QGIS and ArcGIS.
Which sheet of the Excel workbook is used?
The first sheet, with the first row as headers. Put the data you want to convert on the first sheet, or export that sheet to CSV.
My coordinates use commas as decimal separators. Does that work?
Yes. Semicolon-separated files with decimal commas (common in Indonesian, German or French Excel installations) are detected and parsed correctly.