Does a video clip from a hike have GPS data embedded in the file itself?

The short answer

Whether a video file carries its own embedded GPS coordinate depends on whatever recorded it and whether Location Services was available at the time — the same condition that decides whether a photo gets one. That is a property of the file itself, sitting in its metadata alongside things like the recording length and the device model. A route-tracking app pinning a clip to a point on a map is a different mechanism entirely: it is the app's own record, tying a clip to a spot on the route it was already tracking, and it works whether or not the clip's own file happens to carry a coordinate of its own.

In other words, a clip can be pinned correctly on a replayed hike with nothing written into the file itself, because the pin was never coming from the file in the first place.

Two different places a location can live

A video file is built the same way a photo file is: the actual footage, plus a block of metadata sitting alongside it — recording length, frame rate, device, and sometimes a GPS coordinate, written automatically if the recording app had Location Services access and a fix was available the moment recording started. That field, when it exists, belongs to the file. Copy the file anywhere and whatever is in that field travels with it, the same way a photo's embedded coordinate does.

A route point, by contrast, belongs to the app that is tracking the hike, not to the clip. The app already knows where you are for the entire walk, because it is recording a continuous line of coordinates the whole time regardless of whether anyone taps to capture anything. Pinning a clip to that route is a matter of noting which one of those already-recorded points the clip belongs to — an entry in the app's own record of the hike, sitting next to the clip rather than inside it.

Why a clip does not need its own coordinate to land in the right place

Replaying a route works from the app's own record of the walk, not by opening each clip and reading a field out of it. The route already has a coordinate for every moment of the hike; pinning a clip is just marking one of those existing moments as the one the clip belongs to. Nothing about that process depends on the clip's file carrying its own embedded location, because the location was never going to be read from the file at all — it was already sitting in the route before the clip was even captured.

That also means the two can genuinely disagree without either one being wrong. A clip's own embedded coordinate, if it has one, was written by whatever software handled the recording, under whatever rules that software follows for when to write it. The route's pin was written by a different piece of software, at a different moment, for a different reason. Treating them as if they must always match is the part that trips people up, not either coordinate being unreliable on its own.

Checking whether a specific clip has one

The way to find out is the same as for a photo: look at the file's own info on the device that has it, rather than guessing from how it behaves inside a route. Not every video app writes this field even when it could, and a clip that has travelled through messaging apps, cloud transfers, or format conversion on the way to wherever you are checking it can easily have lost a field it once had, the same way a shared photo can lose its own coordinate along the way. A missing field there says nothing about whether the clip is correctly placed on the route it came from — that placement lives somewhere else entirely.

What this means for exporting a hike

A GPX file is a coordinate format with a place for a route and a place for named waypoints, and no field built for an attached video, so a clip's pin does not travel into a GPX export at all — only the route itself does. Whatever a clip's own file carries or does not carry is a separate matter again from that, and neither one substitutes for the other: a route exported without its pinned clips is missing something a GPX file was never going to hold anyway, and a clip with no embedded coordinate of its own is missing something the route replay never needed it to have.

Where TrailCam fits in

TrailCam pins a video clip of up to two minutes, a photo, or a spoken voice note to the point on the route recorded at the moment you started capturing it — an entry in the route itself, not something that depends on what the clip's own file happens to carry. Replaying a saved route later shows each clip at that point regardless, with the elevation profile running underneath. Exporting a hike as GPX 1.1 or CSV, part of the optional TrailCam Pro upgrade, carries the route only; the clips stay in the app, where replaying the route is what puts everything back together. TrailCam itself is free to download.