KML to GeoJSON Converter
Typical when you've designed features in Google Earth and need them in a format a web map or GIS pipeline can consume.
Common issues converting KML to GeoJSON
- KML supports embedded HTML in <description> tags — this survives as a string property in GeoJSON but you should sanitize it before rendering in a browser.
- Inline KML styles (icons, line colors, polygon fills) have no GeoJSON equivalent and are dropped. Render styling in your map library using the preserved feature properties instead.
- KMZ files are zipped KML bundles with embedded images — unzip first and convert the contained .kml file. Linked images and overlays cannot be transferred to GeoJSON regardless.
- MultiGeometry containers in KML expand to the equivalent Multi* GeoJSON types — but if the container mixes geometry types, those can't be collapsed to a single GeometryCollection-free output.
Frequently asked questions
Does KML support multiple geometry types in one file?
Yes. KML files can contain Points, LineStrings, and Polygons in the same document. Each becomes a separate Feature in the output FeatureCollection with its own geometry type. If your downstream tool requires a homogeneous type, filter after conversion.
Do feature properties carry over from <ExtendedData>?
Yes. Each <Data name='...'> element becomes a key on the resulting feature's properties object. <SimpleData> under a <SchemaData> is handled the same way.
What coordinate system does the output use?
WGS 84 (EPSG:4326). KML is always in WGS 84, and RFC 7946 also mandates WGS 84, so coordinates pass through unchanged.
Can I convert a KMZ file directly?
Not in one step — KMZ is a zip container. Extract the doc.kml inside the archive and upload that file. Images and overlays packaged in the KMZ can't be represented in GeoJSON.