Convert GeoJSON to GPX Online — Free GIS Converter

GeoJSON is a flexible format for storing all kinds of geographic features, but GPS devices, fitness trackers, and trail navigation apps like Garmin, Strava, and AllTrails expect GPX — convert your .geojson file to .gpx instantly with geodata.plus.

Why convert GeoJSON to GPX?

GPX (GPS Exchange Format) is the universal language of consumer GPS hardware and outdoor recreation apps. When you have route or track data stored in GeoJSON — perhaps exported from a web mapping tool, a GIS analysis, or an open-data portal — you often need to get it onto a Garmin device, upload it to Strava, or share it with hikers using AllTrails. None of those platforms accept GeoJSON. GPX is the format they all speak natively, and converting is the only path to loading your data onto a device or into a fitness platform.

This conversion is also common in trail-building and land management workflows, where planners draw proposed routes in QGIS or Mapbox (exporting GeoJSON) and then need to share the track with field crews using handheld GPS receivers.

Why use geodata.plus

• Free tier — convert up to 3 files per month at no cost, no credit card required
• Automatic CRS detection — GeoJSON is always WGS 84, which GPX also requires; geodata.plus validates the coordinate system automatically
• Optional reprojection — if your GeoJSON source deviates from RFC 7946 conventions, geodata.plus can normalize it to WGS 84 before writing GPX
• Browser-based — no Garmin BaseCamp, GPSBabel, or QGIS install needed; works on any modern browser
• Encrypted transfer — all uploads use TLS; files are stored temporarily in Cloudflare R2 and automatically deleted on schedule
• Auto-deleted output — output files are automatically deleted after 2 days (free tier) and 7 days (Pro); no manual cleanup needed

How it works

1. Upload your GeoJSON file (.geojson or .json) using the widget above
2. geodata.plus detects the format and confirms the coordinate reference system (WGS 84 / EPSG:4326)
3. Select GPX as the output format
4. Download your .gpx file, ready to load onto a GPS device or upload to Strava, AllTrails, or Garmin Connect

GeoJSON format

GeoJSON encodes geographic features — points, lines, polygons — as JSON objects with a properties dictionary. Its open, text-based structure makes it the standard output format for web mapping APIs, open-data portals, and GIS exports intended for browser consumption. All coordinates are in WGS 84 longitude/latitude per the RFC 7946 specification.

| Property | Value | |---|---| | Extension | .geojson, .json | | Type | Vector, single file | | Coordinate system | Always WGS 84 (EPSG:4326) | | Geometry types | Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon | | Common software | Leaflet, Mapbox, OpenLayers, QGIS, ArcGIS, GitHub |

GPX format

GPX (GPS Exchange Format) is an XML schema designed specifically for GPS data interchange. It defines three core element types: <wpt> for individual waypoints, <rte> for planned routes made up of route points, and <trk> for recorded tracks made up of track segments and points. GPX files always use WGS 84 coordinates, and each point can carry an elevation (<ele>) and a timestamp (<time>). The format is intentionally simple — it does not support polygons or complex attribute tables.

| Property | Value | |---|---| | Extension | .gpx | | Type | Vector, single file XML | | Coordinate system | Always WGS 84 (EPSG:4326) | | Geometry types | Waypoints, Routes, Tracks (no polygon support) | | Common software | Garmin, Strava, AllTrails, Komoot, Google Earth, BaseCamp |

Frequently asked questions

What happens to GeoJSON polygon features when converting to GPX?

GPX does not support polygon geometry. If your GeoJSON contains polygons, geodata.plus converts their exterior ring boundaries to closed track segments (<trk>), which approximates the polygon outline as a GPS track. Interior rings (holes) are not preserved. You will see a warning in the conversion summary noting any geometry type changes.

Will my GeoJSON properties be preserved in the GPX file?

GPX supports a small set of named metadata fields on each element (<name>, <desc>, <cmt>, <sym>, <type>). geodata.plus maps the GeoJSON name property to <name> and serializes remaining properties into the <desc> element as a readable key-value list. Arbitrary structured data cannot be stored in standard GPX, but the information is not lost.

Can I include elevation data from my GeoJSON in the GPX output?

Yes. If your GeoJSON coordinates include a third value (the Z/altitude component, e.g., [lon, lat, elev]), geodata.plus writes that value to the GPX <ele> element on each point. If your GeoJSON also carries an ele or elevation property on each feature, that value is used as a fallback when the coordinate Z value is absent.