Skip to content
Spatly

Convert GeoJSON to GPX

1

Add your GeoJSON

Drop a GeoJSON file anywhere on this page

.geojson · .json · it never leaves the browser

2

Options

≈ 11 cm on the ground
Keep every vertex
00verticesunchanged
Points → waypoints, lines → tracks
3

Your GPX

Add a GeoJSON file and the GPX appears here, with its feature counts and anything this pair cannot carry.

Converted in this tab. Your GeoJSON is never uploaded — reading, converting and writing all run in the browser, so this works offline once the page has loaded.
— , —
FidelityGeoJSON → GPX

What comes across, and what cannot

Preserved

  • Geometry — points and lines come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
  • Names come across as the waypoint or track name; elevation is kept where a Z ordinate exists.
  • Elevation (the Z ordinate) is preserved where the source has one.

Dropped

  • Areas. GPX has no polygon type, so each ring is written as a closed track: the shape survives, the fact that it encloses an area does not.
  • Most attributes. GPX defines a fixed vocabulary per point — name, description, elevation, time — and anything outside it has no home, so only the name field is carried across.

GeoJSON (RFC 7946)

The web's lingua franca for vector data: plain JSON, WGS84 longitude/latitude, every geometry type, and an untyped property bag per feature. It carries no styling — colour and symbology belong to the map, not the file.

.geojson · .json · application/geo+json

GPS Exchange Format (GPX)

What GPS units and fitness apps speak. It has exactly three containers — waypoints, routes and tracks — so it holds points and lines but has no concept of an area, and only a fixed set of fields per point.

.gpx · application/gpx+xml

AlsoGPX to GeoJSONShapefile to GPXKML to GPXGeoJSON to KMLAll conversions
HowHow it works

Convert GeoJSON to GPX, step by step

  1. Step 1

    Add your GeoJSON

    Drop a GeoJSON file anywhere on the page, paste it, point at a URL, or press Sample to start from real data. Several files at once are fine.

  2. Step 2

    Set what matters

    Coordinate precision and simplification on every pair, plus the handful of settings this one needs — waypoints or tracks.

  3. Step 3

    Take the GPX

    Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.

PrivateRuns in your browser

Your data never leaves the page

Every conversion, measurement and export happens client-side. Nothing is uploaded, logged or stored — you can even use this offline once the page has loaded. Only “Open in Studio” sends data, and only after you sign in.

Go furtherTurn a GeoJSON into an interactive mapRead the guide
FAQQuestions

Good to know

What is preserved when converting GeoJSON to GPX?
Geometry — points and lines come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude. Names come across as the waypoint or track name; elevation is kept where a Z ordinate exists. Elevation (the Z ordinate) is preserved where the source has one.
What is lost converting GeoJSON to GPX?
Areas. GPX has no polygon type, so each ring is written as a closed track: the shape survives, the fact that it encloses an area does not. Most attributes. GPX defines a fixed vocabulary per point — name, description, elevation, time — and anything outside it has no home, so only the name field is carried across.
Does the file have to be a FeatureCollection?
No. A bare geometry, a single Feature, an array of geometries or a FeatureCollection are all accepted, and a common API envelope such as { data: … } is unwrapped for you.
Waypoints or tracks?
Both, and you decide. Left on automatic, points become <wpt> waypoints and lines become <trk> tracks. Force waypoints and every vertex of every line is written as a separate waypoint; force tracks and your points are threaded, in order, into a single track — which is how you turn a list of stops into a route a GPS unit will follow.
Will it load on my Garmin or in Strava?
The output is GPX 1.1 with the standard namespace and no extensions, which is the dialect Garmin, Wahoo, Strava, Komoot and OsmAnd all accept. Elevation is written as <ele> when the source has a Z ordinate.
Is my file uploaded anywhere?
No. The GeoJSON is read, converted and written entirely inside this page — there is no upload, no queue, no server-side copy and no size limit imposed by a plan. Large files are parsed in a background worker so the page stays responsive. The only action that transmits anything is Open in Studio, and that happens after you sign in and press it.
Is there a limit on file size or number of files?
There is no imposed limit; the practical ceiling is your browser's memory. Files over about 5 MB are handed to a web worker so the interface keeps responding, and you can drop several files at once — each is converted separately and the set can be downloaded as one zip.