BYTETOOLS

GeoJSON to GPX Converter

Convert a GeoJSON FeatureCollection into valid GPX 1.1: Points become waypoints, LineStrings become tracks, and elevations are preserved.

Drop a .geojson or .json file here, or click to browseConverted locally — the file is never uploaded

Paste or drop a GeoJSON file to convert it into a GPX track you can load onto a GPS.

What is the GeoJSON to GPX Converter?

GPS units, Garmin BaseCamp, Strava, Komoot and OsmAnd all speak GPX, while web mapping tools and open data portals hand you GeoJSON.

  • Points and MultiPoints become waypoints; LineStrings and MultiLineStrings become tracks
  • Third coordinate written as an elevation, and properties mapped to name, desc and time
  • Namespaced GPX 1.1 output with the topografix schema location and full XML escaping
  • Optional conversion of polygon rings into closed track segments
  • Adjustable coordinate precision and a live count of waypoints, tracks and track points
  • Everything happens in your browser — files are never uploaded

How to use the GeoJSON to GPX Converter

  1. 1

    Drop a .geojson or .json file, or paste the GeoJSON into the box.

  2. 2

    Set the GPX file name and creator attribute that will appear in the metadata.

  3. 3

    Choose the coordinate precision, and whether to write elevations and convert polygon rings to tracks.

  4. 4

    Check the waypoint and track counts, plus any warning about geometries that were skipped.

  5. 5

    Copy the GPX or download it as a .gpx file ready for your device.

About the GeoJSON to GPX Converter

GPS units, Garmin BaseCamp, Strava, Komoot and OsmAnd all speak GPX, while web mapping tools and open data portals hand you GeoJSON. This converter bridges the two: Point and MultiPoint features become waypoints, LineStrings and MultiLineStrings become tracks with proper track segments, and a third coordinate value is written out as an elevation.

Feature properties are mapped onto the GPX fields people actually look at — name, description and time — and any timestamp is normalised to ISO-8601 so devices accept it. The output is namespaced GPX 1.1 with the topografix schema location, with every name and description XML-escaped, so it imports cleanly rather than failing a schema check halfway through.

The file you drop is read and converted by your browser. Nothing is uploaded to a server, which means your routes, hunting spots and survey tracks never leave the device, and the converter works with no connection at all.

Frequently asked questions

What is the difference between GeoJSON and GPX?

GeoJSON is a general-purpose JSON format for any geographic feature, with arbitrary properties. GPX is an XML format built specifically for GPS devices, with just three concepts: waypoints, routes and tracks. Converting means fitting the richer format into those three boxes.

Will my elevation data survive the conversion?

Yes, as long as your GeoJSON positions include a third number. GeoJSON stores positions as longitude, latitude and elevation, and that third value is written straight into the GPX elevation element. Leave the elevation checkbox on to keep it.

What happens to polygons?

GPX has no polygon type, so a polygon's rings are written as closed track segments if you leave that option enabled. The shape is preserved and will draw correctly, but your device will treat it as a track to follow rather than an area.

Why does my converted file have no timestamps?

GPX timestamps come from your data, not from the clock. If your GeoJSON features carry a time, timestamp or date property, it is parsed and written as ISO-8601; if they do not, the track points are written without times, which every GPS reader accepts.

Can I load the result into Garmin or Strava?

Yes. The output is GPX 1.1 with the standard topografix namespace and schema location, which is what BaseCamp, Garmin Connect, Strava, Komoot, OsmAnd and Gaia GPS all expect. Download the .gpx file and import it the usual way.

Related tools