How to Remove GPS Telemetry from GoPro and Drone Videos

What telemetry actually is

Telemetry is a stream of sensor readings stored inside the video file, each one stamped with the moment it was taken. GoPro cameras record it in a format called GPMF, which can carry GPS position, speed, altitude and motion data. Drones commonly record flight data as well, sometimes in a subtitle-style track inside the file, sometimes as a separate sidecar file, alongside the usual container tags naming the aircraft and camera.

Phones do the same thing in their own formats: Apple uses a timed track type called mebx, Google's is CAMM, and Sony writes RTMD. The names differ, but the structure is shared — a third track next to the video and audio tracks, quietly logging where the camera was, several times a second, from the moment recording started until it stopped.

A route, not a point

A photo with GPS gives away one location: the spot where you stood for a second. A video with telemetry gives away a journey. Played back on a map, the track draws the road you took, the trail you rode and the street where the clip began — which, for a video that starts in a driveway or outside a front door, is effectively a home address with a timetable attached.

The other readings add context a single coordinate cannot. Speed and altitude show how you travelled, pauses show where you stopped, and the timestamps show when. None of this is visible in the picture, and none of it is mentioned by most players, so people routinely publish it without realising it was ever recorded, let alone embedded in the file they shared.

The sharing routes make it worse. Clips posted to a streaming site are transcoded before anyone watches them, but action-camera and drone footage is constantly shared as files: sent to friends at original quality, dropped into cloud folders, attached to forum posts, even included with a second-hand camera or drone as sample footage. In every one of those cases the file travels intact, and whoever receives it receives the whole recorded journey with it, whether or not they go looking for it.

Why most cleaning tools leave the track behind

Most metadata tools were built to edit tags: titles, dates, device names and the other text fields in a container. A telemetry track is not a tag. It is a separate stream inside the file, so an instruction to clear the metadata simply never touches it. The tool reports the file clean because every field it knows how to read is empty, while the track it cannot read is still there.

Remuxing tools have the opposite problem. Their job is to copy every stream from the old container into a new one, and they do it faithfully — video, audio and the data track nobody asked about. So a clip can pass through two different kinds of cleaning and keep its GPS log both times. Removing telemetry requires a tool that recognises the track for what it is and deliberately leaves it out of the new file.

Editing does not save you either. Dropping a clip into an editor and exporting it produces a new file, but editors are built to preserve material, and depending on the tool and settings the data track or its contents can be carried into the export. A freshly exported file feels processed and therefore safe, which is exactly why it so often is not. Whatever route a clip has taken — straight from the camera or through an editor — the only reliable evidence is a scan of the final file itself.

The honest limit: what is baked into the picture

Some action-camera and drone apps offer the opposite of removal: data overlays. Editors such as camera makers' own apps can burn speed, altitude, a route map or a GPS gauge directly into the frames as visible graphics. Once telemetry is rendered into the picture like that, it is no longer metadata. It is part of the video itself, and no metadata cleaner can take it out.

The same applies to anything the camera could see: a house number, a street sign, a distinctive building at the start of a flight. Cleaning removes what is written in the file's hidden tracks and tags. Before sharing, watch the beginning and end of the clip with the same suspicion you apply to the file itself, because the first seconds of a journey are usually the most identifying.

A cleaning workflow that removes the track

Start with a copy, so the original stays untouched. Scan the copy first and read the report before removing anything: a telemetry or data track should be listed among the contents if one is present, alongside the container tags, device names and timestamps. If the scan of an action-camera clip shows no data track at all, the camera may have recorded with GPS switched off — worth knowing either way.

Then clean the copy with a tool that treats telemetry as metadata rather than content. MediaPure's video cleaner drops timed telemetry tracks — GPMF, mebx, CAMM and RTMD — instead of copying them across, while the video and audio streams are carried over without re-encoding. Download the result and keep it clearly separate from the original in your folders, so the cleaned file is the one that gets shared.

Verify the cleaned file

Cleaned is a claim; verify it. Scan the cleaned file again the same way you scanned the original. The report should now list no telemetry or data track and no location fields, while the video and audio remain. If a data track is still listed, the file has not been properly cleaned, whatever the tool that produced it said, and it should not be shared as though it had.

Also check the things cleaning must never change. Play the file from start to finish: the duration should match the original, the picture should be the right way up, and the sound should be present and in sync. A container rewrite copies the streams byte for byte, so any difference in playback means something other than metadata removal happened along the way.

Keep the original: it is your flight record

Telemetry is a liability in a shared file and an asset in your archive. For drone pilots especially, the original recording with its flight data can support insurance claims, warranty discussions, incident reports and your own records of where and how you flew. Deleting the original to be safe destroys that evidence along with the risk.

The workable routine is a strict separation. Originals stay in a private archive, under your control, for as long as they might be needed. Only copies are cleaned, and only cleaned copies leave your devices. That way the question for any file a stranger can download is never what it contains — you already know, because you checked.