Convert KML (Google Earth) straight to GPX for GPS devices locally - in one step. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
KML is the format of Google Earth and Google Maps, GPX that of GPS devices and outdoor apps (Garmin, Komoot, Wahoo). To get a route drawn in Google Earth onto a bike computer or hiking GPS you would otherwise have to chain two tools. This tool does it in one step: KML in, GPX out.
Placemarks (Point) become waypoints (wpt), lines (LineString) become tracks, compound lines (MultiGeometry) become multi-segment tracks. An area (Polygon) is output by GPX as a closed track, since it has no area format. Names are kept, elevation is carried over as ele. The coordinate order is correctly reordered from KML (longitude, latitude) to the GPX attributes lat/lon.
Everything runs entirely locally in the browser - your possibly sensitive route and location data never leaves your device. Honestly framed: geometry, name and elevation are transferred. KML-specific presentation (styles, icons, tours, overlays) has no counterpart in GPX and is not carried over. A KML file without placemarks, or an invalid file, is rejected with a clear message.
| Input formats | KML |
|---|---|
| Output format | GPX |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts KML straight to GPX 1.1 (internally via the GeoJSON model): Point to wpt, LineString/MultiGeometry to trk, Polygon as a closed track (GPX has no areas). Name and elevation are kept. KML styling, tours and overlays are not carried over. Coordinates WGS84, correctly reordered to lat/lon. KML without placemarks or invalid KML is rejected with an error.
This gets a route planned in Google Earth onto a GPS device or into an outdoor app in one step, without a detour via an intermediate format.
Lines become tracks. Since GPX has no areas, a polygon is output as a closed track (outer edge) instead of being discarded.
Yes, placemark names become name and elevation values become ele in the GPX file.
No, the conversion happens entirely locally in the browser; route data never leaves your device.