KML / KMZ to GeoJSON Converter

About this tool

KML is what Google Earth, My Maps and most survey apps hand you. GeoJSON is what Leaflet, Mapbox, OpenLayers, QGIS and every modern web map want to read. This converter moves map data between the two in either direction, in the browser — your file is never uploaded, and there is no account or size-gated tier.

Going KML → GeoJSON, each Placemark becomes a GeoJSON Feature:

• Point, LineString and Polygon become the matching geometry, with a polygon's inner rings kept as holes; MultiGeometry becomes a GeometryCollection.
• name and description become properties, and everything in ExtendedData/SimpleData becomes a property of the same name.
• TimeStamp becomes a time property; TimeSpan becomes begin and end.
• Inline and shared styles (Style, styleUrl, StyleMap) are resolved and folded into simplestyle-spec properties — stroke, stroke-width, stroke-opacity, fill, fill-opacity, marker-color — so a styled route still looks like a route when a web map draws it.
• The Folder hierarchy becomes a slash-separated folder property, so a layer tree survives the trip instead of collapsing into one flat list.

Going GeoJSON → KML, all of that runs backwards: properties become <name>, <description> and <ExtendedData>, simplestyle properties become an inline <Style>, the folder property rebuilds the <Folder> tree, and you choose the <Document> name plus the <altitudeMode> Google Earth should use.

Worked example

Input (KML):

<kml xmlns="http://www.opengis.net/kml/2.2"><Document>
<Folder><name>Trails</name>
<Placemark><name>Trailhead</name><description>Parking lot</description>
<Point><coordinates>-122.0841234,37.4212345,15</coordinates></Point>
</Placemark>
</Folder>
</Document></kml>

Output (GeoJSON, at the default 6 decimal places):

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-122.084123, 37.421235, 15.0]
      },
      "properties": {
        "name": "Trailhead",
        "description": "Parking lot",
        "folder": "Trails"
      }
    }
  ]
}

Switch Convert to to KML and paste that GeoJSON back to get a KML document with a Trails folder and the same placemark inside it.

Limits and what is not carried over

• Input is capped at 2 MB, and a KML entry inside a KMZ at 8 MB. Larger exports should be split by layer first.
• KMZ arrives base64-encoded. A KMZ is a zip archive and this page takes text, so paste the base64 form — it is detected automatically by its UEsD prefix. On macOS or Linux: base64 -w0 map.kmz (drop -w0 on macOS).
• Both formats are WGS84, so nothing is reprojected. Coordinates in another system must be reprojected before conversion.
• Not carried over: NetworkLink and other external references (fetching them would need network access), screen overlays, tours, and image or model files bundled inside a KMZ — a custom icon's URL survives as a property, the icon file itself does not.
• KMZ output is not produced. Take the KML result and zip it with any archiver to get a KMZ.

FAQ