Convert GeoPackage to GPX
Free, in-browser conversion from GeoPackage (.gpkg) to GPX. Drop a file below — the converted output downloads automatically. No account, no software install, no upload retention for direct conversions.
About GeoPackage
GeoPackage (.gpkg) is an OGC standard that stores many layers — vector and raster — inside a single SQLite database with spatial indexes. It scales far beyond Shapefile and is the recommended format for GIS exchange today.
About GPX
GPX is an XML schema produced by virtually every GPS device and fitness app — Garmin, Wahoo, Strava, Komoot, Ride with GPS, Suunto, and Polar all read and write it. It carries tracks (recorded paths), routes (planned paths), and waypoints, optionally with elevation and timestamps.
How to convert GeoPackage to GPX
- Drop your GeoPackage file (.gpkg) on the area above, or click to browse.
- The file is parsed server-side — geometries are normalised to a GeoJSON FeatureCollection internally, then written out as GPX.
- The converted file downloads automatically. No retention; nothing is kept on the server.
Want to inspect the geometry before converting? Use the full 3D viewer instead — it renders the file on a MapLibre globe with toggleable layers, then lets you convert from the same toolbar.
Related conversions
FAQ
Is the GeoPackage to GPX converter free?
Yes. rooot viewer is free and requires no account. There are no per-conversion charges.
Do I need to install software?
No. The conversion runs server-side, the result is delivered as a download. Works in any modern browser.
Are my files kept after conversion?
Direct conversions through this page (the form above) do not persist files at all — the bytes are parsed in memory and the result returned. Persistence only happens when you use the main viewer's Open in roooute button, and persisted files are deleted within 24 hours.
What is the maximum GeoPackage file size?
50 MB per file.
Does the converter preserve attribute properties?
Yes — feature properties round-trip through the canonical GeoJSON intermediate. Schema differences between source and target formats may force lossy coercions (e.g. shapefile DBF column-name length limits), but rooot viewer applies sensible defaults.