Free sample GPX files

Picking the right sample for your test

For different testing goals, different samples are the sharpest tool:

• Verifying basic GPX 1.1 parsing. Start with short-hike-5km. Small, simple, single track, single segment, named waypoints. If your parser doesn't produce the expected distance, gain, and trackpoint count for this file, don't bother with the larger samples until you fix the basics.
• Testing wide pace and elevation ranges. mountain-hike or mountain-biking. Both have meaningful elevation gain, varied pace, and data shaped like a real recording. mountain-hike has sustained climbs and descents; mountain-biking has alternating up-and-down for a different stress profile.
• Testing sensor-data display. The extensions-test file is the only one with Garmin TrackPointExtension v1 data (heart rate, cadence, temperature on every trackpoint). Use it to verify your app reads the gpxtpx namespace correctly and renders the sensor values on charts.
• Testing multi-track / multi-day apps. multi-day-hike has 4 tracks (one per day) inside a single file with overnight waypoints between them. road-trip is another 4-track variant for driving. These exercise the wall-clock-time vs moving-time distinction that single-track parsers don't need to handle.
• Testing waypoint-only parsing. The geocaching-pocket-query file has 15 waypoints and no track. Parsers that assume every GPX has at least one track will fail; correct parsers should produce zero distance, zero duration, and 15 waypoints with sym/type metadata.
• Testing zero-elevation edge cases. The sailing-route file has zero elevation throughout (sea level). Apps that compute elevation gain should produce zero; apps that try to draw an elevation profile should either render a flat line or skip the chart entirely.
• Testing long-file performance. The road-trip file is ~700 KB with 4,200 trackpoints — the largest in the corpus. Use it to spot performance issues with parsers that store every trackpoint in memory or that re-render polylines on every interaction.

What can I use these for?

Test a GPX parser. The files cover the common variations a real parser sees: single-segment tracks, multi-segment recordings (pause/resume), multi-track files (multi-day trips), routes with named waypoints, pure-waypoint geocaching exports, and trackpoints with Garmin extensions. If your parser handles all 12, it'll handle 95%+ of real-world files.

Demo content. Use the files in product walkthroughs, tutorials, screenshots, or videos. They don't belong to any user, don't depict any private location, and are released under CC0 — no permission, no attribution.

Test integrations. Upload to Strava, Garmin Connect, Komoot, AllTrails, or any other GPX consumer to verify your import flow end-to-end. The files are clean GPX 1.1 with proper namespace declarations and parse on every platform we've checked.

Learn the format. Crack open any of the files (most are plain XML you can read in a text editor) to see how GPX 1.1 elements compose: metadata, waypoints, routes, tracks, segments, trackpoints, and the gpxtpx extension namespace. The GPX format pillar walks through the structure in detail.

License

All sample files on this page are released under Creative Commons Zero (CC0) — public domain. Use them for any purpose, commercial or otherwise, with no attribution required. The files include no real user data: coordinates are plausible for the named region but the routes are synthetic.