GeoJSON to KML converter

1. Pick or drop a .geojson or .json file: a FeatureCollection, a single Feature or a bare geometry.
2. Check the shapes on the map.
3. Download the KML and open it in Google Earth or any app that reads KML.

Runs in your browser. Files are never uploaded.

Input

A .geojson or .json file: a FeatureCollection, a single Feature or a bare geometry, in WGS84 longitude and latitude.

Output

A .kml file with every property written as text.

plot.geojson:
{"type":"Feature","properties":{"name":"Plot 1","commodity":"coffee","area_ha":1.3},"geometry":{"type":"Point","coordinates":[-84.520679,10.007963]}}

plot.kml, with this placemark:
<Placemark><name>Plot 1</name><ExtendedData><Data name="commodity"><value>coffee</value></Data><Data name="area_ha"><value>1.3</value></Data></ExtendedData><Point><coordinates>-84.520679,10.007963</coordinates></Point></Placemark>

• KML stores values as text, so numbers and true/false come back as text, empty values as blank text, and nested objects as JSON text. Invisible characters a KML file can't hold are removed.
• Style properties such as stroke and fill are kept as data fields, not applied as colours.
• Coordinates outside longitude and latitude ranges (for example a projected export from older QGIS) are refused. The tool can't confirm the datum is WGS84, so reproject other coordinate systems first.
• Features without a shape are left out, and the page says how many.

Drop the GeoJSON file on the GeoJSON to KML converter, check the shapes on the map and download the KML. It opens in Google Earth.

No. A property called name or description becomes the placemark name or description, and every other property is written to the placemark as extended data. KML stores values as text, so numbers and true/false come back as text, and empty values as blank text.

Not yet. Style properties such as stroke and fill are kept as data fields, but the KML uses Google Earth default colours.