Convert GeoJSON to KML so web-map data opens cleanly in Google Earth. The translation runs on your device via WebAssembly; the JSON never touches a server.
Drop a file here, or click to browse
KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more
No GeoJSON file to hand? Download a sample GeoJSON file (100 points) and drop it above to see the conversion.
Every format stores different things, so a conversion is never perfectly loss-free. Here is exactly what carries over when you convert GeoJSON to KML, and what to watch for.
| What | GeoJSON → KML | |
|---|---|---|
| Geometry | Kept | Points, lines and polygons are preserved exactly, including multi-part shapes. |
| Attributes | Kept | Every column and full field name moves from GeoJSON into KML untouched. |
| Styling & labels | Changes | KML supports styling; features are written with clean default styling and a name label you can restyle in Google Earth. |
| Coordinate system | Changes | KML is defined in WGS84 (EPSG:4326), so data is reprojected to lon/lat on the way out. |
| Elevation (Z) | Kept | 3D Z values carry from GeoJSON into KML wherever the source records them. |
| File structure | Kept | A single, self-contained .kml file you can move around on its own. |
GeoJSON is the working language of web maps. It powers Leaflet, Mapbox GL and OpenLayers, and moves features through APIs as plain JSON text. However, most non-developers cannot open a raw GeoJSON file. KML is what they can open. It is the format Google Earth and Google Maps read, so it displays points, lines and polygons with labels and styling straight away. So people convert GeoJSON to KML to turn API or web-map output into something a colleague can double-click. For example, you can hand off boundaries or field points as a Google Earth layer without any coding.
GeoJSON is already defined in WGS84 longitude/latitude (EPSG:4326), so no guessing is needed on the way in.
KML is defined in WGS84 (EPSG:4326), so the output is reprojected to longitude/latitude, exactly what Google Earth and web maps expect. A quick CRS check before you download saves the classic "my GeoJSON data is in the wrong place" surprise; the guide on coordinate systems and EPSG codes goes deeper.
Both formats use WGS84 lon/lat, so coordinates line up cleanly here. However, watch your attributes. GeoJSON often carries nested properties or many fields, but KML shows attributes inside placemark descriptions, not a tidy table. So rich or nested values can flatten or read awkwardly in Google Earth. Also check that each GeoJSON feature has a sensible name property, since that becomes the KML placemark label.
GeoJSON files typically come out of Leaflet, Mapbox GL, OpenLayers, QGIS, GDAL. Once you convert to KML, the file opens in Google Earth Pro on the desktop, Google Earth for web, and Google Maps (via My Maps), as well as QGIS and ArcGIS Pro. The KML output follows the standard specification exactly, so those programs read it without any special import settings.
GeoJSON is where web maps keep their data. A Leaflet or Mapbox GL layer, an API response, or a feature you edited in the browser all arrive as GeoJSON. KML is where that same data goes to be seen in Google Earth. This conversion takes features built for a slippy web map and rewrites them as placemarks, paths and polygons that Earth can draw over imagery. In practice it is the handoff from a developer's dataset to a viewer anyone can open.
Yes, feature properties are carried into each placemark and appear in its description bubble when you click it in Google Earth. However, they show as description text rather than a structured attribute table.
Yes. KML is exactly the format Google Earth and Google Maps read, so you can double-click the file and your points, lines and polygons appear right away.
Each feature's properties become KML ExtendedData attached to its placemark. In Google Earth you see those key/value pairs when you click the placemark and its balloon opens. Values stay as text, so numbers are written out rather than kept as typed fields.
Yes. Points, LineStrings and Polygons in the same GeoJSON each map to the matching KML geometry, and MultiPolygon or MultiLineString become MultiGeometry placemarks. Unlike a shapefile, KML does not force one geometry type per file, so a varied collection stays together in a single document.
A KML file opens in Google Earth (desktop and web), QGIS and ArcGIS. Because the output follows the standard specification, any tool that supports KML will read it without special settings.
No conversion is perfectly loss-free because each format stores different things, but geometry and attributes are preserved; only presentation-level styling (which KML does not store) is left behind.
