Converting GPX to Shapefile brings GPS waypoints, routes, and tracks into the Esri multi-file set for desktop GIS.
What is GPX?
GPX (GPS Exchange Format) is an open, XML-based schema for exchanging GPS data such as waypoints, routes, and tracks between devices and applications.
GPX models data through three primary elements: waypoints (individual named points of interest), routes (an ordered list of routepoints describing a planned path), and tracks (recorded paths made of one or more segments of trackpoints, often carrying timestamps and elevation). It is the common tongue of handheld GPS units, fitness watches, and outdoor apps like Garmin, Strava, and Komoot. It is a point- and line-oriented format built around navigation, not a general-purpose polygon or attribute-table format.
What is Shapefile?
The Shapefile is a widely used vector data format developed and published by Esri, stored as a set of sibling files that share a common base name.
A single "shapefile" is really a bundle: the mandatory .shp (feature geometry), .shx (a shape index for fast seeking), and .dbf (a dBASE table of attributes), usually alongside a .prj (coordinate system) and sometimes a .cpg (attribute encoding). It is the lingua franca of desktop GIS and is read by virtually every tool, from ArcGIS and QGIS to GDAL/OGR. Its age shows in several hard limits: DBF attribute field names are truncated to 10 characters, each file component is capped at 2 GB, every file holds a single geometry type, and attribute types are constrained to what DBF supports (limited-width text, numbers, dates, and booleans).
Why convert GPX to Shapefile?
Shapefile is the format desktop GIS and many analysis workflows expect, so converting lets you analyze recorded tracks and field points in ArcGIS or QGIS. It produces an indexed, attribute-tabled dataset ready for spatial queries and geoprocessing. This is the standard step for turning GPS logs into analyzable GIS layers.
Coordinate systems
The GPX specification fixes all coordinates to WGS84 latitude/longitude with elevation in meters, so like KML it carries no projection information and any exported data is expressed in EPSG:4326.
The coordinate reference system lives in the optional .prj sidecar as a WKT (well-known text) string. When the .prj is absent the CRS is genuinely unknown and consumers typically fall back to assuming WGS84, which can silently misplace data that was in another projection.
What to watch out for
- Shapefile holds one geometry type per file, so GPX points and line features (tracks/routes) typically become separate output files.
- Attribute names longer than 10 characters are truncated to satisfy the DBF specification.
- GPX is WGS84, and a .prj declaring EPSG:4326 is written; the output is delivered as a .zip.
- GPX <extensions> and long text may not fit cleanly into DBF fields and can be clipped or dropped.
How to convert GPX to Shapefile
- Drag your GPX file (.gpx) into the converter above, or click to browse.
- Confirm the source is GPX and choose Shapefile as the output format.
- Optionally pick a target coordinate system (EPSG) to reproject.
- Click Convert and download your Shapefile file. Everything runs in your browser.
Frequently asked questions
- Will I get one Shapefile or several?
- Often several. Shapefile allows one geometry type per file, so waypoints (points) and tracks/routes (lines) are usually separated.
- What coordinate system will the output have?
- WGS84 (EPSG:4326), since GPX is always WGS84; a matching .prj is included.
- Are GPX extension fields preserved?
- They are mapped to DBF attributes where possible, but the 10-character name limit and DBF field widths may truncate or drop some values.