🧭 GeoJSON to GPX Converter
Paste GeoJSON and get a GPX 1.1 file, LineStrings become tracks and Points become waypoints, ready to load onto a GPS device.
GeoJSON → GPX 1.1
How the geojson to gpx converter works
The converter reads GeoJSON geometries and writes valid GPX 1.1: LineString (and MultiLineString) features become track segments of <trkpt> points, and Point features become <wpt> waypoints, carrying a name from the feature's properties.name. It converts GeoJSON's [longitude, latitude] coordinate order back to GPX's lat/lon attributes and preserves elevation as <ele> where present.
This is the inverse of the GPX-to-GeoJSON converter, useful when a route was designed in a web-mapping tool (which speaks GeoJSON) and needs to go onto a Garmin, Wahoo or phone app (which speak GPX). As with the forward direction, the lon/lat vs lat/lon swap is handled for you. Polygon geometries have no natural GPX equivalent and are skipped. Everything runs in your browser.
Frequently asked questions
How do I convert GeoJSON to GPX?
Paste or open your GeoJSON and the tool outputs a GPX 1.1 file, LineStrings become tracks and Points become waypoints. Download the .gpx and load it onto your device or app.
Does it fix the coordinate order?
Yes, GeoJSON stores [longitude, latitude] while GPX uses separate lat and lon attributes. The converter swaps them so the GPX is correct, avoiding the classic wrong-location bug.
What GeoJSON geometries are supported?
Point (→ waypoint), LineString and MultiLineString (→ track segments). Polygons don't map cleanly to a GPS route and are skipped; a feature's properties.name is used to label waypoints.
Can I load the result onto a Garmin or Strava?
Yes, the output is standard GPX 1.1, which Garmin Connect, Strava, Komoot, Wahoo and most GPS apps and devices import directly.
Is my data uploaded?
No, the conversion runs entirely in your browser and works offline, so your route data never leaves your device.