KML and KMZ to CSV: Tested Point Samples and Field Checks
Use these fictional files to check what a point-table conversion keeps, changes and leaves out. Download the complete KML/CSV reference pack, or inspect the files separately below. Its two expected CSVs were specified from the source data and compared byte-for-byte with the current KML & KMZ to CSV converter. The locations are teaching examples, not survey or navigation data.
Try it free: KML & KMZ to CSV Converter Free to use, no account needed.
| Input | Expected CSV | Question it answers |
|---|---|---|
| Two simple points (.kml) | Two point rows | Are coordinate order, missing altitude, text codes and spreadsheet protection retained correctly? |
| Points with a LineString (.kml) | Two point rows after acknowledging the exclusion | What happens when one placemark contains two Points and another contains a line? |
| Two-document KMZ exercise | The two CSVs above, one selected document at a time | Does the tool ask which KML document to read instead of silently choosing one? |
The pack README gives the exact expected values and reuse permission. The archive includes both source KML files, the two CSVs, the KMZ exercise and that README. It requires no account or personal location data.
Run the comparison
- Open the converter, select an individual KML sample, and choose Read map. The filename and selected state should appear before processing. Keep Protect formula-like text in spreadsheets enabled for an exact CSV comparison.
- Review the point rows, then choose Download CSV. The downloaded name is
map-points.csv. Compare its bytes with the corresponding expected file. The expected CSV uses UTF-8 with a byte-order mark, quoted fields and CRLF record separators; the first sample also contains an internal line break in one description. - For the KMZ exercise, choose a KML document when prompted and read it again. Each document has its own result. Switching documents invalidates the previous preview and download.
The multi-document KMZ is only a converter-selection exercise. For ordinary Google Earth distribution, use one KML per KMZ. Google's KMZ packaging guidance says Earth reads the first KML it finds in a multi-KML archive and ignores the rest. Our converter deliberately asks you to select one of the two documents.
Check the simple-points output
| Source detail | Expected CSV result | Why check it |
|---|---|---|
KML <coordinates> | Separate Longitude, Latitude, Altitude columns | The tuple order is longitude, latitude, optional altitude; it must not be swapped. The source decimal strings are not rounded. |
Folder Training / Sites | Folder column on both rows | Nested context is retained; the KML document title is not added to the path. |
Café, "North" | A quoted Name cell | An accent, comma and quotation marks remain valid CSV text. |
First point 12.50; second point no altitude | 12.50 then an empty Altitude cell | Missing altitude is not invented as zero. The second point uses clampToGround as its altitude mode. |
Site codes 001 and 002 | Same text bytes in the Site code column | CSV has no type schema: import that column as Text in Excel to prevent leading zeros disappearing. |
Note =1+1 | '=1+1 with the default protection option | The apostrophe is intentional spreadsheet-formula protection; switching the option off changes this output. |
The first description spans two lines in the KML and remains one quoted CSV cell. A text editor or CSV Viewer is useful for inspecting it before spreadsheet software interprets values. Google's KML Point reference defines the coordinate order; the table above describes this converter's exported subset.
Check the mixed-geometry output
The second KML contains one placemark with two Points inside MultiGeometry and a separate placemark with one LineString. The preview should show two rows for the two Points, with Point number 1 and 2 and the same placemark ID pair-003. The first point's altitude is 0 with relativeToGround; the second has an empty altitude with clampToGround. Site code 003 repeats on both rows.
The LineString is reported as one excluded feature, not turned into vertices, a midpoint or an empty row. The converter requires you to acknowledge this partial export before enabling the CSV download. After acknowledgement, the downloaded CSV should match the mixed-geometry expected file. Keep the original KML if you need the line. Google's KML MultiGeometry reference describes the container; this page tests our point-only extraction rather than a complete GIS export.
Field and loss boundary
The CSV contains placemark name, folder path, source placemark ID, point number, longitude, latitude, optional source altitude, altitude mode, description and supported ExtendedData fields. A placemark with several Points becomes several rows. An absent field stays empty. Descriptions are exported as literal text; HTML or CDATA markup is not rendered into a map balloon. Google documents Data and SimpleData under ExtendedData.
The CSV is not a reversible copy of the map. This converter does not export routes, polygon boundaries, tracks, overlays, linked-map contents, icon styles, timestamps, media or map appearance. It does not calculate terrain height, change coordinate systems or fetch remote resources. A table that looks correct can still be incomplete for a GIS task: compare the reported exclusions with the source before using it.
For a step-by-step guide to selecting your own file, handling invalid coordinates and importing into Excel, read How to convert KMZ to CSV. The current tool accepts UTF-8 KML 2.2 up to 10 MiB and at most 10,000 point rows; KMZ also has archive and document limits described in that guide. Selected files are processed in a browser worker, while ads and site services can make separate network requests.
About this reference
Version 1, 15 October 2026. TimeToTime Tools created the fictional locations and independently specified the expected CSVs. Automated tests compare the current converter output with those files and check document selection and the partial-export gate. You may copy, adapt and share the original examples without a required backlink, as described in the README. The cover is an AI-assisted conceptual illustration, not a map of the sample coordinates or a product screenshot. This page is a tested fixture explanation, not a claim that the tool preserves every KML feature or that these coordinates describe real places.
Try it free: KML & KMZ to CSV Converter Free to use, no account needed.