Convert GPX to KML

Your file never leaves your device — conversion happens here in your browser.

Google Earth and most map viewers don't read GPX natively as a styled path — KML is the format they expect, and this tool builds one from your track in a single pass. What KML gains in universal map-viewer support, it loses in data: it's a geometry spec built for Google Earth, not a fitness format, so it was never designed to carry heart rate, cadence, power, speed, distance, or lap information — none of those fields exist in the KML schema, full stop, not because this converter drops them but because there's nowhere to put them. What does survive exactly is the geometry itself: every trackpoint's timestamp, latitude, longitude, and elevation, rendered as a path you can open, zoom, and fly through in Google Earth. One quirk worth knowing before you inspect the output file: KML orders its coordinate triples as longitude, latitude, elevation — the reverse of GPX, TCX, and nearly every other format, including this site's own CSV export. It trips people up when they open the raw XML expecting lat-first ordering, so if you're hand-checking the file, that's not a bug, that's the KML spec. If you need the sensor data preserved alongside a route you can still open in a map, GeoJSON keeps everything through a coordinateProperties block and works in modern web-mapping tools; KML is the better choice specifically when Google Earth compatibility is what you're after. As with every tool here, the conversion runs entirely client-side, in your browser, with no upload — even a long route with a huge point count converts locally without ever leaving your device.

Questions

Will my heart rate or pace data show up in Google Earth after converting?

No. KML has no fields for heart rate, cadence, power, speed, or distance — it's a geometry format, not a fitness format, so that data was never something KML could hold, regardless of converter.

Why are the coordinates in the KML file in a different order than my GPX?

KML writes coordinates as longitude, latitude, elevation, while GPX and most other formats write latitude first. That's the KML specification, not an error in the conversion.

Does GPX to KML preserve lap markers?

There's nothing to preserve — GPX has no lap concept, and KML has none either, so this conversion was never going to carry lap data in either direction.

Is there a version of this that keeps my sensor data?

Yes — convert GPX to GeoJSON instead. It preserves heart rate, cadence, and power in a coordinateProperties block while still working in modern map tools.