GeoPackage to GPX Converter
Converts the point and line layers of a GeoPackage to GPX with GDAL's ogr2ogr.
Upload a .gpkg file. Points become waypoints, lines become routes and multilines tracks. The worker reprojects to WGS84 as GPX requires. Polygons cannot be stored in GPX; the report lists them.
Drag a file here to convert, or select file
Accepted: .gpkg · max. 50 MB
What the converter does
- GPX knows only waypoints, routes and tracks. Points become waypoints, lines become routes, multilines become tracks.
- Polygons cannot be stored in GPX and are not exported; the report names the layer and the number of polygons.
- GPX requires longitude/latitude: the worker reprojects to WGS84 (-t_srs EPSG:4326) if every layer has a coordinate system. If one does not, the coordinates are written unchanged and the report warns about it.
- Attributes that are not standard GPX fields are written as GPX extensions (<ogr:name> elements, option GPX_USE_EXTENSIONS=YES).
- Layers with mixed geometries are sorted by type through a temporary GeoPackage first, because a GPX file can only be written in one go.
- The report below the upload shows layers and features read and written, skipped layers with the reason, GDAL's warnings and the exact commands.
GDAL command the worker runs
For a GeoPackage with one point layer called points. Mixed layers go through gpx_staging.gpkg first (see the report for the exact commands).
Tested with
| Test file | Result |
|---|---|
| GeoPackage with 4 points and a mixed layer (2 points, 1 line, 1 polygon) | 6 waypoints and 1 route, 7 of 8 features; report: 1 polygon not exported, GPX cannot store areas |
Tested on 24 Sep 2026 with the worker code of this site and GDAL 3.10.3 (conda-forge build on Windows). The worker image runs the Debian build of the same GDAL version; the live worker was not part of these tests.
Limits
- Upload limit: 50 MB per file.
- Polygons are not exported (GPX has no areas).
- Each GDAL step may run for up to 240 seconds; a longer run is stopped with an error message.
Frequently Asked Questions
How do I know whether anything was lost?
After each conversion the page shows a report with the number of features read and written per layer, skipped layers with the reason, all GDAL warnings and the ogr2ogr commands that ran. If the counts differ, the report says how many features are missing.
What happens to my file?
Your browser uploads it directly to the GDAL worker on Fly.io (region Frankfurt). The worker converts it in a temporary folder and deletes the folder after sending the result, or immediately if the conversion fails. Files are not stored permanently.