Does a GPX file say what app recorded it?

The short answer

Open the very first line of a GPX 1.1 file and, alongside the version number, there is almost always a creator attribute — a short string naming the app, website, or device that generated the file. It sits in plain text, unencrypted, as part of the file's opening tag, not buried in some optional extension. Any program built to read GPX files can see it without doing anything special, because reading that opening tag is one of the first things a GPX parser does.

Where this comes from in the format itself

GPX is an XML-based format, and the root element of every valid GPX 1.1 file — the outermost tag that everything else sits inside — carries two required attributes: version, which says which revision of the format the file follows, and creator, which names whatever produced it. Underneath that root tag, a file can also carry an optional metadata block with fields like name, description, time, and author, though those are filled in at the discretion of whichever app wrote the file and are often left mostly empty.

The creator attribute is the one piece of self-identification the format actually requires, which is why it shows up far more consistently across GPX files than any of the optional metadata fields do.

Why the format asks for this at all

GPX was built to move trail data between many different tools made by many different companies, not to keep a single company's app self-contained. A format meant for that kind of exchange benefits from knowing, at a glance, where a given file came from — the same reason a document format, an image file, or a piece of exported software might quietly note which program built it. It is a debugging and compatibility convenience more than anything else: if a file behaves oddly on import, knowing which app produced it narrows down where to look.

What it does and does not tell anyone

The creator field tells you, or whatever software opens the file, which app or service generated it. That is close to the limit of what it says. It does not name your phone model, it does not say which settings you had turned on, and it says nothing about who you are unless you separately filled in an author or contact field yourself, which most people never do and most apps never require. It is a label on the file, not a profile of the person who recorded it.

That is a very different kind of information from what a track can reveal about where you actually walked — the points inside the file, including where a recording started, are the part worth thinking about if privacy is the concern, not the name of the app sitting on the opening tag. That side of things is covered on its own in the guide to what a GPX file can reveal about where you live.

Where you would actually notice it

Most map apps and route platforms never surface this field in their normal interface — you upload a file, it shows a track on a map, and that is the whole experience. It becomes visible in two situations: opening the raw file in a text editor, where it sits right there on the first line, or using an import tool that happens to display a "source" or "created by" label as part of its upload confirmation. Neither situation is common day to day, which is part of why the field feels like a hidden detail even though it has never actually been hidden.

Things that trip people up

• Assuming the creator field is a privacy risk on the level of a name or a location — it names software, not a person, and carries no personal detail on its own.
• Assuming a GPX file with no visible app name anywhere is somehow more anonymous — the creator attribute is required by the format, so it is almost always present even when nothing in a normal map view ever shows it to you.
• Treating the creator field as proof of which physical device recorded a hike — it names the software, and software can run on many different devices, so it says nothing about the phone itself.
• Expecting every GPX file to carry a filled-in author, description, or contact field the way it carries a creator attribute — those extra metadata fields are optional, and most apps leave most of them blank.

Where TrailCam fits in

TrailCam exports routes as GPX 1.1, the same widely supported version of the format that Strava, Garmin Connect and Komoot read, so an exported file follows these same standard rules rather than a private variant of its own. TrailCam is free to download.