How to upload a GPX file to OpenStreetMap
Every other guide here about getting a GPX file somewhere else is about the same kind of destination â an app that already has a map, reading your file back in to show you your own hike again. OpenStreetMap is a different kind of trip. The file is not going in to be replayed; it is going in as raw material that other people might use to make the map itself a little more accurate. Once that difference is clear, the actual steps are the easy part.
The short answer
openstreetmap.org has its own GPS Traces section, reachable once you are signed in with a free OpenStreetMap account. Choose a .gpx file, add a short description and a tag or two, decide how visible the trace should be, and upload it. What comes out the other end is a trace sitting alongside everyone else's â a scatter of points other mappers can look at, not a path that has been added to the map on its own. Uploading a trace does not edit the map by itself; nobody's route just appears as a trail because the file went up.
Why this upload works differently from every other one
Every app covered elsewhere in these guides treats an imported GPX file as something to hand back to you â a line on your own map, a distance and elevation total, a route you can replay. OpenStreetMap has none of that built around an uploaded trace, because giving something back to you is not what the upload is for. OpenStreetMap is not an app that reads your hike; it is the shared map underneath a long list of other apps, built and edited by people working from a common dataset rather than each keeping their own copy. A GPS trace uploaded there is not a hike being logged for you to look back on â it is reference material, the sort of thing a mapper opens as a faint line in the background while deciding whether a junction, a rerouted section after a washout, or a social trail that has appeared on the ground actually belongs on the map yet.
What actually happens to the file after it uploads
The points in your file land on OpenStreetMap much as they were recorded, rendered as a track other mappers can browse alongside the traces everyone else has contributed near that same spot. What does not happen automatically is any of that becoming an actual way on the map â the line you walked and the path a hiker following OpenStreetMap later sees are two separate things, connected only once a person opens an editor, pulls up your trace as a background layer, and draws the trail over it by hand, checking it against whatever else is already mapped nearby. A trace can sit there for a long time as pure reference before anyone gets around to that step, and some traces are only ever used to double-check a trail that is already drawn rather than to add a new one.
The description and tags matter more than the file itself
A .gpx file on its own is just a line with no context, and a mapper deciding whether to trust it wants to know what it is a record of before drawing anything from it. A short description â a trail name, or a note that this is the rerouted section around a washed-out switchback rather than the old line still shown on the map â is what turns an anonymous scatter of points into something another mapper can act on with confidence. A trace with no description at all still helps, but it sits in a queue behind ones that explain themselves, simply because nobody browsing traces can tell at a glance what an unlabelled one is worth.
Visibility is worth a pause before you upload
The upload form lets you choose how visible a trace is, and it is worth actually deciding rather than accepting whatever is selected by default. A GPS trace is, among other things, a timestamped record of exactly where you were, and the start and end of a hike recorded from your own front door carries that same information about home along with the trail. None of that is unique to OpenStreetMap â it is the same consideration that comes up with any GPX file leaving your phone, covered on its own elsewhere in these guides â but it is worth thinking through here specifically, since a trace made public is, by design, something other people can look at rather than something staying on one device.
Where TrailCam fits in
TrailCam records a route with GPS on an iPhone and exports it as a standard GPX 1.1 file, which is exactly the kind of file OpenStreetMap's upload page is built to accept. If a trail near you has changed â rerouted, newly worn in, or missing from the map altogether â exporting that specific route and handing the file to OpenStreetMap is a way to put an accurate, recent trace in front of the people who maintain that map. GPX export is part of the optional TrailCam Pro upgrade; the app itself is free to download.
Questions
- Does uploading a GPS trace to OpenStreetMap put the trail on the map right away?
- No. The trace lands as reference material â a background line other mappers can see â and it only becomes an actual mapped path once someone opens an editor and draws the trail over it by hand. Uploading and mapping are two separate steps.
- Do you need an OpenStreetMap account to upload a GPS trace?
- Yes. Viewing the map does not require signing in, but uploading a trace does, and creating an account is free.
- Is an uploaded GPS trace public by default?
- Visibility is a choice you make on the upload form, not something fixed. Because a trace records exactly where and when you were somewhere, including the start and end of the hike, it is worth deciding on visibility deliberately rather than uploading on autopilot.
Recording your own routes
TrailCam is an iPhone app that records your route with GPS, keeps video clips, photos and voice notes pinned to the spot where you took them, and exports the result as GPX 1.1 or CSV. It is free to download.