Which GeoJSON geometries are supported?

Point becomes a GPX waypoint. LineString becomes a track with one segment. MultiLineString becomes a track with one segment per line. A Polygon's outer ring is exported as a track, since GPX has no polygon type.

How does coordinate order work?

GeoJSON stores coordinates as [longitude, latitude, optional elevation]. GPX uses separate lat and lon attributes, so the converter reads index 0 as longitude and index 1 as latitude and writes them in the right GPX slots.

Are feature properties kept?

A feature's properties.name is used as the waypoint or track name, and properties.desc or properties.description becomes the GPX desc. Other arbitrary properties are not part of the GPX schema and are not emitted.

What if I paste a single Feature instead of a FeatureCollection?

Both work. The converter accepts a bare Feature, a FeatureCollection, or even a raw geometry object, normalising each into a list of features before building the GPX.

Is my GeoJSON uploaded anywhere?

No. Parsing and conversion run entirely in your browser. Your geographic data never reaches a server, is never logged, and never leaves your device.

GeoJSON to GPX Converter

GeoJSON (RFC 7946) is the standard format for web maps and GIS, while GPX is what Garmin devices, Strava, Komoot and most GPS hardware import. This free converter remaps GeoJSON features to GPX in your browser, so you can take a route designed in a web tool and load it onto a device without uploading your private geographic data anywhere.

How it works

The converter normalises the input and rebuilds it as GPX 1.1:

The JSON is parsed and reduced to a list of features, whether you paste a FeatureCollection, a single Feature, or a raw geometry.
Each geometry is mapped:
- Point → a waypoint (wpt),
- LineString → a track with one segment,
- MultiLineString → a track with one segment per line,
- Polygon → a track built from its outer ring (GPX has no polygon type).
Coordinates are read as [lon, lat, ele] — longitude first per RFC 7946 — and written into GPX’s separate lat/lon attributes with an ele child when a third value is present.
properties.name and properties.desc carry over as the GPX name and description.

Tips and example

A GeoJSON point feature with "coordinates": [16.3738, 48.2082] becomes:

<wpt lat="48.2082" lon="16.3738"></wpt>

The first array element is longitude, not latitude — a frequent source of mirrored maps. This tool always reads index 0 as longitude. If a converted track appears in the wrong place, check that your source GeoJSON itself used the correct [lon, lat] order.

All processing is local; your GeoJSON never leaves your browser.