Skip to content
Spatly

Convert Shapefile to GPX

1

Add your Shapefile

Drop a shapefile anywhere on this page

.zip · it never leaves the browser

2

Options

Only needed when the archive has no .cpg and text looks wrong.
≈ 11 cm on the ground
Keep every vertex
00verticesunchanged
Points → waypoints, lines → tracks
3

Your GPX

Add a shapefile and the GPX appears here, with its feature counts and anything this pair cannot carry.

Converted in this tab. Your Shapefile is never uploaded — reading, converting and writing all run in the browser, so this works offline once the page has loaded.
— , —
FidelityShapefile → GPX

What comes across, and what cannot

Preserved

  • Geometry — points and lines come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
  • Names come across as the waypoint or track name; elevation is kept where a Z ordinate exists.
  • Elevation (the Z ordinate) is preserved where the source has one.

Dropped

  • Areas. GPX has no polygon type, so each ring is written as a closed track: the shape survives, the fact that it encloses an area does not.
  • Most attributes. GPX defines a fixed vocabulary per point — name, description, elevation, time — and anything outside it has no home, so only the name field is carried across.
  • One thing that is not this tool's doing: a .dbf caps field names at ten characters, so truncated names such as POPULATIO arrive that way in the source and cannot be recovered.

Esri Shapefile (zipped)

Not one file but a set — .shp geometry, .dbf attributes, .prj projection, .cpg text encoding — which is why you upload the whole thing as a .zip. Field names are capped at ten characters and the .dbf has no Unicode of its own.

.zip · application/zip

GPS Exchange Format (GPX)

What GPS units and fitness apps speak. It has exactly three containers — waypoints, routes and tracks — so it holds points and lines but has no concept of an area, and only a fixed set of fields per point.

.gpx · application/gpx+xml

AlsoKML to GPXKMZ to GPXShapefile to GeoJSONShapefile to KMLAll conversions
HowHow it works

Convert Shapefile to GPX, step by step

  1. Step 1

    Add your Shapefile

    Drop a shapefile anywhere on the page, paste it, point at a URL, or press Sample to start from real data. Several files at once are fine.

  2. Step 2

    Set what matters

    Coordinate precision and simplification on every pair, plus the handful of settings this one needs — the .dbf text encoding, and waypoints or tracks.

  3. Step 3

    Take the GPX

    Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.

PrivateRuns in your browser

Your data never leaves the page

Every conversion, measurement and export happens client-side. Nothing is uploaded, logged or stored — you can even use this offline once the page has loaded. Only “Open in Studio” sends data, and only after you sign in.

Go furtherTurn a GeoJSON into an interactive mapRead the guide
FAQQuestions

Good to know

What is preserved when converting Shapefile to GPX?
Geometry — points and lines come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude. Names come across as the waypoint or track name; elevation is kept where a Z ordinate exists. Elevation (the Z ordinate) is preserved where the source has one.
What is lost converting Shapefile to GPX?
Areas. GPX has no polygon type, so each ring is written as a closed track: the shape survives, the fact that it encloses an area does not. Most attributes. GPX defines a fixed vocabulary per point — name, description, elevation, time — and anything outside it has no home, so only the name field is carried across. One thing that is not this tool's doing: a .dbf caps field names at ten characters, so truncated names such as POPULATIO arrive that way in the source and cannot be recovered.
Do I upload the .shp on its own?
No — zip the whole set and drop the .zip. A shapefile is at least a .shp, a .shx and a .dbf; without the .dbf you get geometry with no attributes, and without the .prj the coordinates are assumed to be WGS84 already.
My Turkish, Greek or Cyrillic field values come out as mojibake.
That is the .dbf's text encoding. If the zip has no .cpg file the reader cannot know it, so set the encoding hint in step 2 — windows-1254, ISO-8859-9, windows-1251 and UTF-8 are all offered — and the attribute table is re-read with it.
Is the shapefile reprojected?
Yes, when a .prj is present: coordinates are transformed to WGS84 longitude/latitude, which is what GPX expects. A shapefile with no .prj is taken as already being in WGS84.
Waypoints or tracks?
Both, and you decide. Left on automatic, points become <wpt> waypoints and lines become <trk> tracks. Force waypoints and every vertex of every line is written as a separate waypoint; force tracks and your points are threaded, in order, into a single track — which is how you turn a list of stops into a route a GPS unit will follow.
Will it load on my Garmin or in Strava?
The output is GPX 1.1 with the standard namespace and no extensions, which is the dialect Garmin, Wahoo, Strava, Komoot and OsmAnd all accept. Elevation is written as <ele> when the source has a Z ordinate.
Is my file uploaded anywhere?
No. The Shapefile is read, converted and written entirely inside this page — there is no upload, no queue, no server-side copy and no size limit imposed by a plan. Large files are parsed in a background worker so the page stays responsive. The only action that transmits anything is Open in Studio, and that happens after you sign in and press it.
Is there a limit on file size or number of files?
There is no imposed limit; the practical ceiling is your browser's memory. Files over about 5 MB are handed to a web worker so the interface keeps responding, and you can drop several files at once — each is converted separately and the set can be downloaded as one zip.