Add your GEOJSON file
Drop one or more .geojson files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
GEOJSON to GPX
Converting a .geojson font to .gpx repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop GEOJSON files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting GeoJSON to GPS Exchange Format
Converting a .geojson font to .gpx repackages the same glyphs and metrics for a different delivery target. A .geojson file encodes geographic features as JSON: geometries such as Point, LineString and Polygon, each optionally carrying a free-form properties object, usually collected in a FeatureCollection. It is the format web mapping actually runs on.
A .gpx file is the GPS Exchange Format: an XML schema for waypoints, routes and recorded tracks, where every point carries a latitude and longitude and may carry elevation and a timestamp. It is what a GPS watch or handheld exports. For this route the practical draw is universally supported across GPS devices and fitness platforms and distinguishes planned routes from recorded tracks, which matters in practice — balanced against verbose XML — large for the number of points it carries, which is worth knowing before you commit a large batch.
Why convert GEOJSON to GPX?
The practical trigger for this conversion is usually a mismatch: with .geojson, verbose and large for dense geometry, with no built-in compression. Switching to .gpx buys you universally supported across GPS devices and fitness platforms, which is why it is the better fit for exporting a recorded run, ride or hike from a watch or phone. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
GEOJSON vs GPX at a glance
| Aspect | GeoJSON (.geojson) | GPS Exchange Format (.gpx) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | coordinate order is longitude, latitude — the reverse of how people say it, and the single most common source of bugs | three distinct concepts: wpt waypoints, rte planned routes, and trk recorded tracks made of trkseg segments |
| Strongest at | rendering geographic data in Leaflet, Mapbox or OpenLayers | exporting a recorded run, ride or hike from a watch or phone |
| Weak spot | verbose and large for dense geometry, with no built-in compression | verbose XML — large for the number of points it carries |
| Metadata | geometry and the properties object are preserved. Styling is not part of the format, so a conversion from KML loses that presentation information rather than GeoJSON dropping it | coordinates, elevation, timestamps and point names are preserved. Vendor extension data such as heart rate is not carried into targets with no equivalent field |
Pick GPX as the output
Select .gpx in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if GPX is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid GPX file. Outputs keep the original filename with the .gpx extension.
GEOJSON to GPX questions, answered
Will converting GEOJSON to GPX lose quality?
There is no visual quality to lose — geojson is text-oriented and gpx is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert GEOJSON files here?
Yes — the .geojson file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the GPX file work?
Read by Garmin, Strava, Komoot, QGIS, Google Earth and the whole OpenStreetMap ecosystem. Novus Convert parses waypoints and track segments locally and converts to GeoJSON and KML.
Will the GPX file be bigger or smaller than my GEOJSON?
It depends on the content: three distinct concepts: wpt waypoints, rte planned routes, and trk recorded tracks made of trkseg segments. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my GEOJSON file?
In .geojson, geometry and the properties object are preserved. Styling is not part of the format, so a conversion from KML loses that presentation information rather than GeoJSON dropping it. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert GPX back to GEOJSON?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .geojson → .gpx → .geojson is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.