How to convert GPX to Shapefile
- Drop your .gpx file into the box at the top of the page.
- Check the preview; waypoints convert as points, while tracks and routes convert as lines.
- Choose Shapefile and convert, then unzip all the parts into one folder and add the .shp to QGIS or ArcGIS.
What changes when you convert GPX to Shapefile
| What | GPX → Shapefile | |
|---|---|---|
| Geometry | Changes | Points, lines and polygons are all carried over, but a Shapefile holds a single geometry type per file. A layer that mixes types is written one type at a time. |
| Attributes | Changes | Every column is kept, but the Shapefile .dbf caps field names at 10 characters, so long names are shortened (values are untouched). |
| Styling & labels | Kept | Neither GPX nor Shapefile stores visual styling, so there is nothing to lose. Geometry and data carry straight over. |
| Coordinate system | Kept | GPX is always WGS84, and that is what the output records in its .prj file unless you choose another EPSG code. |
| Elevation (Z) | Kept | 3D Z values carry from GPX into Shapefile wherever the source records them. |
| File structure | Changes | A working Shapefile is several files, so you download one .zip holding .shp, .shx, .dbf, .prj and .cpg. Keep them together. |
Why convert GPX to Shapefile?
GPX captures fieldwork: hikes, rides and waypoints logged on a Garmin or a phone, and all of it tends to live only in outdoor apps. Shapefile is the working format of desktop GIS, so the conversion turns those recordings into layers ArcGIS or QGIS can query, style and join. A trail becomes a line you can buffer, survey waypoints become points you can measure against parcels, and the result publishes through GeoServer or opens in MapInfo when colleagues need it.
Coordinate system handling
The input side carries no surprises, because a GPX can only hold WGS84, so every waypoint and trackpoint reaches the converter as longitude and latitude on that datum. The default output keeps those values and writes EPSG:4326 into the .prj, which is why QGIS and ArcGIS place the layer correctly without asking a single question.
That .prj is the shapefile's entire memory of its coordinate system, so guard it: separated from the sidecar, the layer loads with an unknown CRS and invites the guessing games GIS users dread. Entering a different EPSG code at conversion time reprojects the coordinates on the way out and records the chosen system in the .prj in place of WGS84.
What to check when converting GPX to Shapefile
The download is one zip, and it can hold more than one shapefile. A shapefile stores a single geometry type, while a GPX can mix point waypoints with line tracks and routes, so mixed content yields a point shapefile and a line shapefile side by side. Nothing was dropped; load each as its own layer. Keep the unzipped parts together, because the .shp needs its .dbf, .shx and .prj, and expect attribute names longer than 10 characters to be truncated in the .dbf.
Troubleshooting GPX to Shapefile
- The planned route and the recorded track merged into one layer. Routes and tracks are both line geometries, and the output groups features by geometry type, so the pair lands as separate records inside the same line shapefile. Open the attribute table, tell them apart by the name field, and export either selection to its own file in QGIS when the two must stay separate.
- The shapefile stopped loading after its table was opened in Excel. Saving a .dbf from Excel rewrites the table in a form the .shp can no longer pair with, which breaks the whole layer. Convert again for a clean copy, and make attribute edits inside QGIS or ArcGIS, where the .dbf is updated without damage.
- Waypoint icons from the handheld are missing in the GIS. The little flag or tent a Garmin draws beside a waypoint travels as plain text in the sym field rather than as styling, and desktop GIS opens every new layer with default symbology. Apply categorized symbology on the sym column and each symbol value gets its own marker back.
- QGIS reports the track as a multipart feature. Pauses in the recording split a track into segments, and the segments stay bundled as one multipart line. Run Multiparts to Singleparts in QGIS when each stretch needs to stand alone, or leave the feature whole for buffering and length work, where the parts make no difference.
About the formats
A GPX file is what your GPS unit, watch or trail app hands you: waypoints, routes and recorded tracks. A Shapefile is what desktop GIS expects when you want to measure, buffer or join that data against other layers, and converting bridges the two. You record a route in the field and then turn it into a shapefile so ArcGIS or QGIS can treat those tracks as proper vector features for analysis and mapping.
Frequently asked questions
Should I reproject before computing length and area statistics?
Yes, when you want results in meters: enter the EPSG code of a projected system, such as your UTM zone, before converting.
Where can I publish or open the converted shapefile?
The shapefile loads into ArcGIS, QGIS, GeoServer and MapInfo, so one conversion covers desktop analysis and web publishing.
Can I convert the shapefile back to GPX later on?
Yes. The Shapefile to GPX converter turns the layers back into waypoints and tracks a handheld can navigate.
What happens to per-point elevation and timestamps from a track?
A track that becomes a single line feature keeps one attribute record, so point-by-point elevation and time values do not survive as columns. Convert the same file to CSV or Excel when you need per-point rows, and keep the original GPX as the full record.
Related converters
Ready to convert?
Drop a file and download the result in seconds. Nothing is uploaded, nothing is stored.