Convert GeoJSON to GPX locally - for GPS devices, outdoor and navigation apps. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Sometimes a route exists as GeoJSON - from a map tool, a planner or a programming interface - but the target device only speaks GPX: a bike computer, a hiking GPS, a navigation or outdoor app. This tool takes your GeoJSON and writes a GPX file you can load onto the device or import into the app.
Points (Point) become waypoints (wpt), lines (LineString) become tracks (trk) with one segment, multi-part lines (MultiLineString) become a track with several segments. Elevation values from the third coordinate are written as ele, a geometry name as name. Since GPX has no area format, an area (Polygon) is output as a closed track (the outer edge) - honest and practical instead of discarding it. The coordinates are correctly reordered from GeoJSON (longitude, latitude) to the GPX attributes lat/lon.
Everything runs entirely locally in the browser - your location and route data never leaves your device. Honestly framed: clean GPX 1.1 with waypoints and tracks including names and elevation is written. GeoJSON properties beyond name and elevation (arbitrary properties) have no fixed place in GPX and are not written out. An invalid GeoJSON file is rejected with a clear message.
| Input formats | GEOJSON, JSON |
|---|---|
| Output format | GPX |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts GeoJSON to GPX 1.1: Point to wpt, LineString to trk (one segment), MultiLineString to trk (several segments); Polygon/MultiPolygon as a closed track (outer edge, since GPX has no areas). Elevation from the third coordinate to ele, name to name. Arbitrary other properties are not carried over (no GPX counterpart). Coordinates WGS84, correctly reordered to lat/lon. Invalid GeoJSON is rejected with an error.
GPX is the standard format for GPS devices and outdoor apps (Garmin, Komoot, Wahoo). This lets you load a planned route onto your device.
LineString becomes a track with one segment, MultiLineString a track with several segments.
GPX has no areas; a polygon is output as a closed track (outer edge) instead of being discarded.
Yes, a third coordinate in the GeoJSON is written as ele in GPX.
No, the conversion happens entirely locally in the browser; route data never leaves your device.