GeoJSON to GPX

updated 28 April 2026

Before you start

You need a GeoJSON FeatureCollection, a single Feature, or a raw geometry. The converter only really makes sense for these geometry types:

• Point & MultiPoint  →  GPX waypoints (<wpt>).
• LineString & MultiLineString  →  GPX tracks (<trk> with one <trkseg> per line).
• Polygon / MultiPolygon  →  track of the outer ring(s). This is lossy — interior holes are dropped because GPX has no concept of polygons.

The conversion is fundamentally lossy in another way too: GPX has a fixed schema (name, desc, ele, time, etc.) and can't carry arbitrary feature properties. I serialize the rest into the <desc> tag as key: value lines so the data is at least visible inside Garmin / Strava popups.

Everything happens locally. No upload, no size limit beyond what your tab can hold in memory.

How to use it

1. Paste your GeoJSON into the left pane, or drop a .geojson file.
2. Click Convert.
3. Check the status bar — it reports waypoint, track, and dropped-feature counts.
4. Click Download .gpx and load the file into Garmin Connect, Strava, Komoot, AllTrails, BaseCamp, OsmAnd, or any other GPS tool that speaks GPX 1.1.

Example

Input (GeoJSON Feature with elevation):

{
  "type": "Feature",
  "properties": { "name": "Summit" },
  "geometry": { "type": "Point", "coordinates": [-122.0, 37.5, 1430] }
}

Output (GPX 1.1):

<wpt lat="37.5" lon="-122">
  <ele>1430</ele>
  <name>Summit</name>
</wpt>

Notice the coordinate flip: GeoJSON is [lon, lat, ele] but GPX uses lat="…" lon="…" attributes. I handle the swap automatically and pull the third coordinate into <ele>.

Tips & common pitfalls

• Naming matters. Garmin Connect and most consumer apps display the <name> tag prominently. Set properties.name on each feature so your tracks aren't a wall of "Untitled".
• Elevation needs a third coordinate. If your GeoJSON points are [lng, lat] only, the <ele> tag is omitted. Some devices then show altitude as zero — paste through a tool like gdal first if you need elevation from a DEM.
• Timestamps come from coordTimes. If your input has a properties.coordTimes array (one ISO-8601 string per vertex, the convention used by togeojson), I emit a <time> tag inside each <trkpt>. Per-feature properties.time works for waypoints.
• Polygons are flattened. GPX has no polygon type. I write a track for the outer ring and silently drop interior holes — fine for things like park boundaries, wrong for things like hydrology with islands.
• Properties land in <desc>. Anything not in the GPX vocabulary becomes a key: value line inside <desc>. Most apps render this on tap; some show only the first line.

Troubleshooting

Related tools

• GPX to GeoJSONThe reverse direction — pull tracks out of GPX into modern JSON.
• GeoJSON ViewerSanity-check your tracks on a map before exporting.
• Simplify GeoJSONTrim huge tracks before converting so the GPX stays under device limits.
• GeoJSON to KMLHeading to Google Earth instead of a GPS device? Use this.

See also: if you need to do something adjacent on this site, try GPX to GeoJSON to turn GPX tracks into GeoJSON, Simplify GeoJSON to thin a dense track, or GeoJSON to KML to convert GeoJSON to KML for Google Earth.

Frequently asked questions