Remove Metadata From Drone Video Before Sharing

A drone still is one shutter press: one EXIF block, often one GPS pair plus altitude and gimbal tags. A drone video is a time series. Many consumer and prosumer aircraft write a telemetry track alongside the picture — coordinates sampled through the flight, not a single pin for “where this file was saved.” Share the MP4 to a client, a listing site, or YouTube without stripping that track and you can publish a map of the flight, including where you stood when you took off.

Stills from the same session are a different file and a different job: strip metadata from a drone photo. The structural contrast between movie containers and JPEG EXIF is how video metadata differs from photo metadata. This page is the application those two set up but do not cover: drone-specific video telemetry before you share the clip.

What is actually embedded in drone video

What follows is a general picture, not a spec sheet for every airframe and firmware. DJI, Autel, Skydio, FPV stacks, and older Phantom-era apps do not all write the same atoms. Firmware updates add and remove fields. Companion apps sometimes keep a richer log in the cloud or in a .srt / flight-record file beside the movie. Treat this as the class of data to look for, not a guarantee that your particular clip contains every item on the list.

A GPS path, not a single capture point. A photo says “this still was taken here.” Drone video can say “the aircraft was here, then here, then here,” for the length of the clip. That path can reconstruct the property line you flew, the backyard you crossed, and the street you used as a corridor — even if the camera was pointed at a roof and never showed the sidewalk.

Home-point or takeoff coordinates. Many systems record where the aircraft considered home: often the pilot's exact launch spot, which may be a driveway, a parking stall, or a backyard, not the building in the thumbnail. That single point is frequently more sensitive than the subject location. A listing video of a client's house that also tags your home pad is a two-address leak.

Altitude and speed over time. Useful for accident review and mapping. On a public clip, altitude plus a recognizable skyline can still place the flight even when you thought you had “only shared the pretty parts.” Speed profiles are less identifying than GPS, but they ride in the same telemetry bundle.

Timestamps throughout the clip. Video already has a duration. Telemetry often stamps samples so a viewer with the right tool can align “this second of the movie” with “this coordinate.” That is a log, not a single DateTimeOriginal.

Those fields may live in the MP4/MOV container (user-data atoms, timed metadata tracks, XMP packets, ISO6709 location strings) or in a sidecar the flight app wrote next to the file. Some apps mux an SRT subtitle track that is literally GPS-and-altitude text on a timeline. Turning off on-screen HUD in the editor does not remove a subtitle or metadata track you never opened. Inspect the file, not only the picture.

Why this is different from drone photos

A drone JPEG's EXIF/XMP is a block attached once. You wipe that block (or rewrite a clean still) and the locating tags for that image are gone. The site's drone photo page is that job: GPS, altitude, gimbal, aircraft tags on a still. It does not walk a timed track. It cannot, because a still has no timed track.

Drone video metadata can be a continuous data track running the length of the clip. Stripping it is a container job: drop or rewrite the telemetry samples, location atoms, and any muxed SRT without relying on “I exported a new H.264 so it must be clean.” Re-encoding can leave user-data atoms alone if the exporter copies metadata. A photo EXIF remover will not open the movie and will not see those samples. That is why video metadata is a different structure from photo metadata, and why a flight's JPEG and MP4 each need their own pass.

Poster frames and gallery thumbnails are a third object. An MP4 can carry a JPEG cover image with its own EXIF. You can strip the movie's GPS track and still ship a thumbnail that pins the pad. Treat the still and the movie as two files even when they came from one flight.

How to strip it — keep the clip on this device

The trust rule is the same as the rest of this site: the file should not be sent to a remote “video cleaner.” Choose the drone video from local storage (the flight-app export folder, an SD card, Files). Process it on this device so the original never leaves the machine for someone else's disk. Download or export a cleaned result. The source file stays where it was until you delete or archive it on purpose.

MetadataWipe's browser panel rewrites JPEG and PNG in this tab — the right tool for stills, listing heroes, YouTube custom thumbnails, and poster frames pulled from the same flight. Open those rasters here, confirm GPS/altitude in the panel, strip, and re-open the download. That is the still half of a drone share, documented on the drone photo guide.

The video half is the container. In a local editor or a local metadata strip, drop the telemetry track, location atoms, and any GPS-bearing subtitle file that travels with the MP4. A remux that copies “all metadata” is not a strip. Prefer an export setting that does not copy locating tags, then verify with a tool that reads video atoms — not with Photos' info pane, which is EXIF-oriented and can look “empty” while the timed track is still in the movie.

1. Export the actual movie you will share from the flight app (MP4/MOV), plus any SRT or flight-log sidecar you might otherwise zip by habit.
2. Strip the video locally so GPS path, home-point, and altitude samples are not in the file that will travel. Keep a tagged archive elsewhere if you still need mapping or incident review.
3. Handle stills and thumbnails separately. Any JPEG from that flight — including a frame grab — goes through MetadataWipe in the browser. A cleaned movie does not clean those stills.
4. Verify both artifacts before the listing site, the client Dropbox, or YouTube Studio sees them. If only the thumbnail is public, wipe the thumbnail. If the movie is public, strip the movie. If both, both.
5. Watch the flight app's own cloud. Some companion apps sync flight logs to the pilot's account independently of the video file. Cleaning the MP4 does not unsync a log that already left the phone. That account is outside this tool; it is still part of the share decision.

Quality: a metadata-only rewrite does not re-encode the picture. Bitrate and sharpness stay. If you also re-encode for YouTube's recommended settings, that is a separate quality choice, not a requirement of stripping telemetry.

Common mistakes

Assuming a photo metadata remover automatically handles video the same way. It does not. EXIF tools look for JPEG/TIFF segments. A drone MP4's telemetry is a different structure. Run the stills here; strip the movie as a video file.

Only checking the thumbnail or first frame for GPS. A cover JPEG can be clean while a timed track still logs the whole flight. Conversely, a stripped movie can sit next to a geotagged poster frame. Inspect both.

Forgetting the flight app's own cloud log. Several vendors store flights against the pilot account. That log is not inside the MP4 this page is about. Revoke or avoid that sync if the takeoff point should not live in a dashboard you do not control. MetadataWipe cannot reach a separate cloud account.

Zipping “the flight folder” for a client after cleaning one hero still. The folder still has the MOV, the SRT, and fifty tagged JPEGs. Share only the inspected deliverables.

Turning off the HUD overlay and calling the file clean. On-screen gauges are pixels. Telemetry in the container is invisible in the player. Different layer.

When the home-point is the leak

Real-estate walkthroughs, roof inspections, and “view of the neighborhood” hobby clips are the everyday cases. The subject in frame is a client's house or a public park. The home-point is where you launched — often your vehicle or your own property. Viewers of the pretty video do not need that pin. Mapping originals can keep it. Public copies should not.

YouTube and social recompression may drop some atoms and keep others. Do not use a platform as the stripper. Hand them a file that already lacks the track. The same discipline as stills: clean first, then publish.

Related guides

See also:

• Strip metadata from a drone photo
• How video metadata differs from photo metadata