1. Home
  2. Files & Archives
  3. GPX / KML Converter

GPX / KML Converter

Convert hiking and running tracks between GPX, KML, GeoJSON and CSV.

Runs in your browser · No upload

How to use

  1. Drop or choose GPX, KML, KMZ or GeoJSON files. If you pick several, they are merged into one.
  2. Under Convert to, choose GPX, KML, GeoJSON or CSV.
  3. If needed, turn on Remove timestamps, set a thin-out tolerance, or change the coordinate decimals. The output and the route preview update right away.
  4. Click Download, or copy the result.

Supported formats

Format Typically used by Read Write
GPX 1.0 / 1.1 Garmin and Strava style devices and services, hiking apps tracks, segments, routes, waypoints tracks, routes, waypoints
KML 2.2 Google Earth, Google My Maps points, lines, polygons (with holes), multi-geometry, gx:Track points, lines, polygons, gx:Track
KMZ KML packed in a ZIP the doc.kml inside (read only)
GeoJSON web mapping code Feature, FeatureCollection, Multi* all
CSV spreadsheets (not read) lat, lon, ele, time, name

The format is detected from the content, not the extension, so a .json file that holds GeoJSON still opens.

Mind the coordinate order

GPX writes latitude and longitude as separate attributes, but KML and GeoJSON put longitude first. A point near Seoul City Hall is lat="37.5663" lon="126.9779" in GPX and 126.9779,37.5663,38 (lon, lat, elevation) in KML. This tool writes and reads each format in its own order. If you edit files by hand and swap them, the point lands somewhere else entirely, often in the middle of an ocean.

What gets calculated

  • Total distance: points are joined with the haversine formula (the Earth treated as a sphere) and summed. Seoul City Hall (37.5663, 126.9779) to Busan City Hall (35.1798, 129.0750) comes out at about 325.05 km. This is the sum of straight great-circle legs, not road distance.
  • Elevation gain and loss: a change only counts once it moves more than 3 m away from the reference elevation. GPS elevation jitters, and summing every wiggle overstates the climb. Going 100, 102, 101, 103, 101, 102 m gives 0 m gain and 0 m loss, while 100 → 110 → 104 → 120 m gives 26 m gain and 6 m loss.
  • Start and end time, duration, average speed: shown only when the points carry times. Times are shown as written in the file (usually UTC). Average speed uses the full duration, rests included.
  • Bounding box: the minimum and maximum latitude and longitude around every point.

Why remove timestamps

A recorded activity with times and coordinates reveals when you were where. A track that starts at the same place at the same hour every day points to a home or workplace. If you only want to share the route, turn on Remove timestamps: every point’s time and every KML when entry is dropped. If the start or end itself is near your home, cutting those points out of the track is safer.

Thinning points and decimals

  • Thin-out (Douglas–Peucker): removes points on nearly straight stretches while staying within the tolerance. The first and last points are always kept. Eleven points on a straight line become 2 at a 5 m tolerance. On winding paths, points that bend more than the tolerance stay.
  • Decimals: 0.000001 degree of latitude is about 0.11 m (longitude is about 0.09 m near 37 degrees latitude). Six decimals are plenty for walking records; four decimals is about 11 m steps, which makes smaller but coarser files.

What is lost when converting

  • GPX routes (rte) and tracks (trk) are not distinguished in KML or GeoJSON, so reading the result back gives tracks only.
  • Styles (line colors, icons) and extension data such as heart rate, cadence or temperature are not carried over.
  • GPX has no polygons, so KML polygons are written as closed tracks.
  • KML keeps times only through gx:Track. The KML this tool writes uses gx:Track for tracks that have times.
  • CSV holds a point list only. A name starting with =, +, - or @ gets a leading ' so spreadsheets do not read it as a formula.

Why the preview has no map

The preview is a line drawn from your coordinates using the Mercator projection, scaled to fit. Background map tiles have to be fetched from a map server, which would tell that server where your route is. Route files often contain home and work locations, so the tool makes no outside requests at all. Orange lines are tracks, dashed lines are routes, green is the start and red is the end. If elevation is present, an elevation profile over distance is drawn too.

Your files are processed in your browser only and are never sent to a server.

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.