KML to GPX Converter
Get a route designed in Google Earth onto a GPS device or fitness platform.
Common issues converting KML to GPX
- KML Polygons have no GPX equivalent. Their outer rings are converted to tracks; holes (inner rings) are dropped.
- KML ExtendedData fields don't map cleanly to GPX — the most useful ones (name, description, time) are preserved; others are dropped.
- If the KML uses <TimeStamp> or <TimeSpan> elements, the timestamps flow into GPX <time> tags.
- Styling is lost in both directions — both formats express it differently. Configure appearance on-device or in your app after import.
Frequently asked questions
Which Garmin devices read the output?
All modern Garmin devices and apps (BaseCamp, Connect, Edge series, fēnix, Forerunner) read GPX 1.1 natively.
Do KML LineStrings become tracks or routes?
Tracks by default. Add a gpxType=route indicator in your KML's ExtendedData if you need <rte> elements instead.
What happens to polygons?
Their outer ring is emitted as a track (useful for loops or property boundaries). Inner rings (holes) are dropped — GPX has no polygon concept.
Are Google Earth timestamps preserved?
Yes. <TimeStamp> and <TimeSpan> elements become <time> tags on the corresponding GPX elements.