AnyFormat

00 GeoJSON → KML

GeoJSON to KML

Properties become ExtendedData, so nothing is dropped.

01GEOJSON in
02KML out
03Options 2

0 keeps full precision. Six places is about 10 cm — beyond that is noise from consumer GPS.

  • No upload The conversion runs in this tab. Your file never travels — not to us, and not to the advertising.
  • No sign-up, no email, no daily cap There is no account system to sign up to.
  • No size limit we invented Only your device's memory — about ~2 GB on a desktop browser, ~400 MB on a phone.
  • Turn your Wi-Fi off and convert anyway The conversion needs nothing but this page. Ads will not load without a connection; your file will still convert. That is the whole claim, and it takes five seconds to check.

Converts GeoJSON to KML so Google Earth can open it. Feature properties are written as ExtendedData rather than being crushed into the description, which is what keeps them usable after import.

Properties survive as real data

A feature's name and description become the Placemark's name and description. Everything else in properties becomes an <ExtendedData> entry — a named field with a value — rather than being concatenated into a description string.

That distinction matters after import: Google Earth shows ExtendedData as a proper table in the balloon, and My Maps exposes it as columns you can style and filter by. Text jammed into a description is just text.

Geometry mapping

Points, LineStrings and Polygons map directly. MultiPoint and MultiLineString become MultiGeometry. MultiPolygon and GeometryCollection are split into separate placemarks first, so every part is addressable.

Polygon holes become <innerBoundaryIs> rings, which Google Earth renders correctly.

Escaping, and why it is worth mentioning

KML is XML, so any ampersand or angle bracket in your property values has to be escaped or the file will not parse. A place called "Marks & Spencer" breaks a naive converter outright. All values are escaped here, so text with markup in it produces a valid document rather than a corrupted one.

Styling is the thing KML has and GeoJSON does not

GeoJSON deliberately describes geometry and properties and says nothing about how any of it should look — colour, line weight and icons are the renderer's business. KML has opinions about all three, plus extrusion, altitude modes and time spans. So converting upward leaves you with unstyled placemarks that Google Earth draws in its defaults. The properties all survive and appear in the description balloon, which is usually what people actually wanted; adding a style block afterwards is a text edit rather than a re-export.

Other names for this

Also searched as “geojson to google earth”, “json to kml”.

Questions

Will my properties show in Google Earth?
Yes — they become ExtendedData, which Earth displays as a table in the placemark balloon.
Can I set the colours?
Not from GeoJSON, which has no styling. Style the layers in Google Earth or My Maps after import.
My Maps says the file is too large.
It caps a layer at 2,000 features and a file at 5 MB. Split the collection, or reduce coordinate precision to shrink the file.
Is my file uploaded?
No. Everything runs in this tab. That matters more here than almost anywhere else on the site — a calendar is your movements, an address book is other people’s personal data, and a GPS track is where you live and where you run. None of it is sent anywhere.