GeoJSON to KML Converter
Convert a GeoJSON FeatureCollection into KML that opens in Google Earth, Google My Maps, and most desktop GIS tools.
Paste a GeoJSON object or upload a .geojson file and download a KML version ready for Google Earth, Google My Maps, or any desktop GIS that consumes KML. Single Features and bare Geometries are wrapped into a FeatureCollection automatically so the converter accepts whatever shape your pipeline produces.
GeoJSON, defined in RFC 7946, is the format web mapping toolchains read and write by default. KML, standardised by the OGC, is what Google Earth, Google My Maps, and a long tail of desktop GIS tools still expect. Converting between the two is routine: a backend computes results in GeoJSON, an analyst wants to open them in Earth, and somebody has to bridge the formats.
The converter accepts a FeatureCollection, a single Feature, or a bare Geometry. Anything that is not already a FeatureCollection is wrapped into one before tokml emits the result. Each Feature becomes a KML Placemark, properties are written as ExtendedData, and Point, LineString, and Polygon geometries map to their KML counterparts. Multi-geometries are expanded into KML MultiGeometry blocks.
Nothing leaves the page. The conversion runs entirely in the browser, so the source data, which often contains addresses, asset IDs, or unreleased boundaries, never crosses the wire. The output is suitable for upload to Google My Maps, sharing as a .kml attachment, or pasting into a KML-aware viewer.
- 1
Provide GeoJSON
Upload a .geojson file or paste the JSON into the input. FeatureCollections, single Features, and bare Geometries all work.
- 2
Convert
The input is parsed, wrapped into a FeatureCollection if needed, then tokml converts each Feature into a KML Placemark with ExtendedData.
- 3
Save the KML
Copy the XML or download it as .kml. Open it in Google Earth, import it into My Maps, or share it with anyone running a KML-capable tool.
Share results with non-developers
Hand a teammate a .kml they can open in Google Earth instead of a JSON file they cannot read.
Publish to Google My Maps
Push a computed dataset into a personal or shared map for embedding in a site or sending to clients.
Desktop GIS round-trip
Many older GIS workflows read KML faster than GeoJSON. Convert when handing off to an analyst on a legacy stack.
Bookmark a point cluster
Turn a list of computed Points into a KML for offline use in mobile Earth or any viewer that supports KML.
Is my data uploaded anywhere?
No. JSON parsing and KML serialisation both happen in your browser. Nothing is sent to a server.
Are property fields preserved?
Yes. Each Feature's properties are written into a Placemark's ExtendedData block. The name property is also used for the Placemark name when present.
What if my input is a single Feature?
It is wrapped into a FeatureCollection automatically before conversion, so single-Feature inputs and bare Geometries both work.
Does the output open in Google Earth?
Yes. tokml emits KML 2.2-compatible XML, which Google Earth, Google My Maps, and most KML readers accept.
What coordinate system does the KML use?
WGS 84 longitude, latitude, and optional altitude. This matches both RFC 7946 and the KML specification.