How to convert Shapefile to GPX
- Drop a zip containing the shapefile's parts, with the .prj included.
- Check the preview; point layers become waypoints, lines become tracks, and polygon boundaries are traced as tracks.
- Choose GPX and convert, then copy the file to your device.
What changes when you convert Shapefile to GPX
| What | Shapefile → GPX | |
|---|---|---|
| Geometry | Changes | Points and lines transfer directly. GPX has no polygon type, so polygons are converted to their boundary as line tracks rather than being dropped. |
| Attributes | Changes | GPX has a fixed schema, so only its native fields (name, description, elevation, time) are filled. Extra columns are not written. |
| Styling & labels | Kept | Neither Shapefile nor GPX stores visual styling, so there is nothing to lose. Geometry and data carry straight over. |
| Coordinate system | Changes | GPX only accepts WGS84 (EPSG:4326), so data stored in another system is reprojected to longitude/latitude on the way out. |
| Elevation (Z) | Kept | 3D Z values carry from Shapefile into GPX wherever the source records them. |
| File structure | Kept | A single, self-contained .gpx file you can move around on its own. |
Why convert Shapefile to GPX?
A Shapefile is desktop GIS currency, which means survey points, trail centerlines and boundaries drawn in ArcGIS or QGIS, while GPX is what the hardware out on the trail actually reads. The conversion maps one world onto the other: a point layer becomes waypoints, a line layer becomes tracks, a polygon layer becomes tracks traced along each boundary, and elevation is kept wherever the shapefile records Z. Projected coordinates are reprojected to WGS84 from the .prj on the way out, so a route planned on a UTM grid still lands in the right valley.
Coordinate system handling
Shapefiles arrive in every coordinate system that surveying and government work produce, State Plane feet, UTM meters and national grids among them, and the .prj in the zip names which one applies. The converter reads that sidecar and reprojects everything to WGS84 automatically, because the GPX specification admits no other datum.
No .prj accompanies the output, and the absence is correct rather than an oversight: a GPX carries its datum by definition, so no sidecar is defined for it. Converting is where projection management ends for this data, and every device and app downstream reads the coordinates as WGS84 without asking.
What to check when converting Shapefile to GPX
Choose a name column before you convert, because most .dbf columns have nowhere to land in a GPX. The name field is the one that matters: it becomes the label beside each waypoint or track on a Garmin or in Strava, while the rest of the attribute table stays behind in the .dbf.
Troubleshooting Shapefile to GPX
- Waypoints surface thousands of kilometers from the study area. The zip went in without its .prj, so projected meters were read as if they were degrees. Recover the .prj from the original data delivery and rezip it with the other parts, or assign the correct CRS in QGIS and export a fresh shapefile to convert.
- Accented names arrive garbled on the device. A .dbf stores text in a code page that a .cpg sidecar is supposed to announce, and without that file characters beyond plain ASCII come out wrong. Add the .cpg to the zip when one exists, or re-export the shapefile from QGIS with UTF-8 encoding and convert the new copy.
- Extra loops appear inside a converted boundary. A polygon with holes, a reserve with an excluded parcel for example, writes every ring as its own boundary track, inner rings included. Delete the hole geometry in a GIS first when only the outer edge matters on the ground.
- A long line shows up cut short on the handheld. Many units cap a single track around 10,000 points and silently drop the remainder, a limit no conversion setting can lift. Simplify the geometry in QGIS to cut the vertex count before converting, or split the feature into stages and convert each stage.
About the formats
A Shapefile usually holds finished desktop GIS work: survey points, trail centerlines, or boundaries drawn in ArcGIS or QGIS. GPX is what a Garmin unit or phone app actually reads out in the field. Converting bridges the two by turning your shapefile geometry into waypoints and tracks that a handheld device can navigate. This is how an office-planned route reaches the trailhead. Keep the whole set together, because the shapefile arrives as several parts.
Frequently asked questions
My shapefile is in a UTM zone, so do I need to reproject it first?
No. The converter reads the .prj and reprojects to longitude and latitude on the way out, so keep the .prj in the zip.
How do I keep the full attribute table from the .dbf?
Keep the shapefile itself, or export a CSV or GeoJSON copy alongside the GPX; only the fixed GPX fields travel to the device.
Why will the layer not load after I drop it?
The parts have to be together, so zip the .shp with its .dbf, .shx and .prj and drop the whole zip.
What happens to polygon shapefiles when I convert to GPX?
GPX stores only waypoints, routes and tracks, so a polygon is written as track paths tracing each boundary while a point layer becomes waypoints. The filled-area meaning is not preserved; expect outlines rather than shapes.
Can I load the GPX straight onto a Garmin?
Yes. GPX is the common language for handheld GPS units, so Garmin devices, Strava, Komoot and GPSBabel all read the output directly.
Related converters
Ready to convert?
Drop a file and download the result in seconds. Nothing is uploaded, nothing is stored.