What does the converter do with KML Points?

Each Point inside a Placemark becomes a GPX waypoint (wpt) with the latitude and longitude split out of the KML coordinate tuple, plus the Placemark name and description if present.

How are lines and polygons handled?

A LineString becomes a GPX track (trk) with one track segment of trkpt points. A Polygon's outer boundary is also exported as a track so the shape is preserved, since GPX has no native polygon type.

Does it understand the lon,lat ordering difference?

Yes. KML stores coordinates as lon,lat,ele while GPX uses separate lat and lon attributes. The converter swaps the order so your points land in the right place rather than mirrored across the globe.

Will nested folders and MultiGeometry work?

Yes. The parser walks all Placemarks regardless of how deeply they are nested in Folders, and it iterates every geometry inside a MultiGeometry so multi-part features are not dropped.

Is my KML uploaded anywhere?

No. The conversion runs locally in your browser with DOMParser and string building. Your location data is never sent to a server, logged or stored.

KML to GPX Converter

KML (Keyhole Markup Language) is Google Earth’s format, while GPX (GPS Exchange Format) is what Garmin devices, Strava, Komoot and most GPS apps import. This free converter remaps one to the other entirely in your browser, so you can move a route out of Google Earth and onto your watch without uploading your private tracks anywhere.

How it works

The converter walks the KML document and rebuilds it as GPX:

DOMParser reads the KML and collects every Placemark, no matter how deeply nested inside Folder elements.
For each Placemark it inspects the geometry, including each child of a MultiGeometry:
- a Point becomes a GPX waypoint (wpt),
- a LineString becomes a track (trk → trkseg → trkpt),
- a Polygon outer ring is exported as a track too, since GPX has no polygon type.
KML coordinate tuples are lon,lat,ele; the tool splits them and writes GPX’s separate lat and lon attributes plus an ele child — handling the order swap for you.
Everything is wrapped in a GPX 1.1 root with the correct namespace.

Tips and example

A KML Placemark like:

<Placemark><name>Summit</name>
  <Point><coordinates>16.3738,48.2082,171</coordinates></Point>
</Placemark>

becomes a GPX waypoint with lat="48.2082" lon="16.3738" and <ele>171</ele> — note that KML’s first number is longitude. If an imported route appears mirrored or in the wrong hemisphere, a lon/lat swap is almost always the cause, and this tool gets the order right.

All processing is local; your KML never leaves your browser.