Drone Footage Privacy: Remove GPS from DJI & GoPro Videos

Your Backyard Is Probably in That File

Drone pilots spend a lot of time thinking about airspace rules, battery life, and getting the perfect shot. Very few think about what happens to the GPS data riding along inside the video file they just uploaded to YouTube or sent to a client.

Here's the thing most pilots don't realize: the spot where you arm your drone and hit "fly" — your home point — is almost always your driveway, back patio, or front yard. And for DJI drones in particular, that launch coordinate gets baked into the SRT sidecar file that accompanies every video clip. Share the raw file and you're sharing your home address, precise enough to plot on a satellite map.

This isn't a fringe risk. For real estate photographers who film aerial walkthroughs, drone hobbyists who post footage to YouTube or Reddit, and commercial operators who send raw files to clients, the takeoff GPS record follows the footage wherever it goes. Understanding the dangers of geotagging matters just as much for aerial video as it does for phone photos — maybe more, because drone files carry far richer telemetry.

What DJI Drones Actually Embed

DJI's metadata footprint is split across two places, and understanding both matters.

Inside the MP4 file itself: DJI embeds camera and firmware information directly into the video container's metadata atoms. This includes the drone model (e.g., "DJI Mini 4 Pro"), firmware version, and — critically — the drone's serial number. That serial number is unique to your specific aircraft and registered to you in DJI's systems. A forensics analysis of any DJI MP4 can tie the footage back to a specific registered drone. For most sharing contexts, this is a minor concern. But for anyone posting footage anonymously or as part of investigative or activist work, it's a significant de-anonymization vector.

Inside the SRT sidecar file: When you record video on a DJI drone, the controller simultaneously generates a companion .SRT file with the same filename as the video clip. This file is a standard subtitle format that logs telemetry every second of the flight. Each entry contains the timestamp, latitude and longitude coordinates, altitude (both relative to the home point and absolute above sea level), ISO, shutter speed, aperture, and color mode. Open this file in VLC and you'll see your flight path plotted as on-screen subtitles.

The SRT file is where the real privacy exposure lives. Over a 10-minute flight, you're looking at 600 GPS coordinate entries — a complete spatial record of every second in the air, starting from takeoff. Anyone with that file and a free GPX converter can reconstruct your exact flight path and identify the launch location.

Some DJI models and firmware versions also embed a subset of this telemetry into the MP4 container atoms directly, particularly the ©xyz location atom. The specific behavior varies by model and firmware version, which is why checking the actual file with ExifTool is always more reliable than assuming. The SANS Internet Storm Center documented this in their DJI video metadata analysis, noting that the MP4 container carries camera/firmware metadata while the SRT carries the flight path record.

What GoPro Cameras Embed

GoPro takes a different technical approach — and in some ways a more thorough one. Rather than a sidecar file, GoPro stores all telemetry directly inside the MP4 video file using their own open standard called GPMF (GoPro Metadata Format, sometimes called General Purpose Metadata Format).

A GPMF-enabled GoPro video contains a minimum of four tracks: video, audio, timecode, and a dedicated telemetry track. That telemetry track stores GPS at up to 18Hz — meaning up to 18 GPS coordinate readings per second. Over a 5-minute action sequence, that's potentially 5,400 GPS data points, all embedded in the single MP4 file you share.

Beyond GPS, the GPMF track captures:

• GPS coordinates at up to 18Hz with latitude, longitude, and altitude
• Accelerometer data at 200Hz (tracks movement and vibration)
• Gyroscope data at 400Hz (orientation and rotation)
• Camera temperature sensor readings
• GPS fix quality and satellite count
• Highlight tags set during recording
• Field of view setting, color profile, and firmware version

What this means practically: a GoPro MP4 shared as a file contains everything needed to reconstruct not just where the camera went, but how it was moving and what orientation it was in at every moment. For drone-mounted GoPro setups (GoPro on a gimbal, or GoPro Karma), all of this is in one self-contained file — no SRT sidecar needed, because the telemetry rides inside.

The Real-World Risk Scenarios

Knowing what's in the file matters less than understanding when it causes a real problem. A few scenarios worth thinking through:

Real estate and aerial photography: A real estate agent or property photographer hires a drone operator, receives the raw footage, and uploads it directly to a property listing platform or sends it to the homeowner. If the SRT file is attached or the MP4 contains embedded GPS, the precise property coordinates (and the flight path around the property) travel with every download. That's usually fine for a listed property — but not fine if the footage includes GPS data from the operator's home where they test-flew the drone that morning.

Hobbyists sharing to YouTube or social media: YouTube and most social media platforms re-encode uploaded video, stripping container metadata as a side effect of their processing pipeline. The GPS risk on YouTube is relatively low for the public-facing video. But the risk is real for anyone who also shares the original file via Google Drive, Dropbox, WeTransfer, or Discord file upload — all of which preserve files as-is. Our complete video metadata removal guide covers exactly which platforms strip metadata and which don't.

Investigative footage and anonymous submissions: A journalist or activist using a drone to document a news event needs to be especially careful. The serial number embedded in DJI MP4 files is tied to the registered operator. Even without GPS, that serial number can identify the drone's owner through DJI's registration database if law enforcement requests it. For sensitive contexts, pre-share metadata stripping isn't optional.

OSINT and open-source intelligence: Anyone can download drone footage from public sources and run ExifTool or MediaInfo against the file. OSINT practitioners regularly use video metadata to geolocate footage — it's one of the core techniques. For an understanding of what analysts can reconstruct from metadata alone, our article on what OSINT experts can find gives a clear picture of the scope.

How to Remove GPS from Drone Footage

There are a few approaches depending on your tools and workflow. Here's what actually works.

Step 1 — Delete or omit the SRT file: For DJI footage, this is the highest-priority step. The SRT sidecar is a plain text file containing the full GPS flight log. Simply deleting it (or not including it when you share files) removes the most detailed location record. This doesn't touch the MP4 itself, so it needs to be paired with Step 2.

Step 2 — Strip the MP4 container metadata: MetaClean's video metadata tool processes MP4 and MOV files entirely in your browser — nothing leaves your device. Drop in the drone footage, click Remove Metadata, and download the cleaned version. MetaClean strips the GPS atom, device/serial information, recording application metadata, timestamps, and other container fields without re-encoding the video stream. That means no quality loss and no long encoding wait, even for large 4K files.

For GoPro files with GPMF tracks, the process works the same way. MetaClean removes the telemetry track from the MP4 container while preserving the video and audio streams intact.

Alternative — FFmpeg (command line): If you're comfortable in a terminal, FFmpeg can strip container metadata without re-encoding: ffmpeg -i input.mp4 -map_metadata -1 -codec copy output.mp4. This is fast and lossless but leaves GoPro's embedded GPMF telemetry track intact in some configurations, so verify with ExifTool afterwards.

Alternative — ExifTool: exiftool -all= drone.mp4 removes container metadata fields. For batch processing a folder of DJI clips: exiftool -all= -overwrite_original *.mp4. ExifTool is comprehensive for MP4 container atoms but may not fully address GPMF telemetry tracks in GoPro files — again, verify the output.

After processing by any method, verify by running exiftool output.mp4 and checking that GPS-related fields no longer appear in the output. For GoPro files, also check that the telemetry track size has been reduced significantly.

How Platforms Handle Drone Video Metadata

Understanding what platforms do (and don't do) when you upload drone footage helps you decide when pre-upload stripping is essential versus advisory.

YouTube: Re-encodes all uploaded video into multiple delivery formats. This processing strips most container metadata, including GPS atoms. For standard YouTube uploads, your GPS data isn't in the public-facing stream. But YouTube retains the original uploaded file internally — and if you also share the original file via Google Drive or another channel, that file remains intact.

Vimeo: Similar to YouTube — re-encoding strips metadata from the public-facing video. Original files uploaded to Vimeo's "original quality" preservation option may be stored with metadata intact server-side.

Direct file sharing (Dropbox, Google Drive, WeTransfer, email): No processing occurs. The file is stored and transmitted exactly as you uploaded it, metadata included. This is the highest-risk sharing scenario and where pre-share cleaning matters most.

WhatsApp and Telegram (Document mode): Transmit files as-is. Full container metadata preserved, SRT files transmitted if included. If you're sending drone footage to a client or colleague via messaging apps and attaching the actual video file, they receive all embedded data.

For a comprehensive look at how different platforms handle video metadata across all use cases, the video metadata privacy complete guide covers the full platform landscape with specific guidance for drone operators.

Building a Clean-Before-Share Workflow

The most effective protection isn't remembering to clean files after something goes wrong — it's building the strip step into your workflow so it happens automatically before anything leaves your device.

A practical post-flight checklist for drone operators:

1. Copy footage from SD card to working folder
2. Edit your video as normal — most editors don't expose or strip container metadata, so editing doesn't solve the problem
3. Before any export or sharing step, process the final MP4 through MetaClean or your preferred command-line tool
4. Separately, decide what to do with SRT files — if they're not needed by the recipient, don't include them
5. Share the cleaned file

For real estate photographers and commercial operators who deliver footage to clients, consider making metadata-clean delivery part of your standard workflow. It's a professional detail that matters — clients who later share the footage further don't need to think about metadata at all.

MetaClean processes files in your browser with no server uploads, which fits naturally into this kind of workflow. There's no account required, and the processing happens locally regardless of file size (up to 500MB supported). It's the same approach used for cleaning photos and PDFs — batch processing means you can run multiple video clips in one session rather than handling them one at a time.

Frequently Asked Questions

Does DJI store my home point GPS in the video file?

DJI stores the flight path GPS log in a companion .SRT sidecar file — not directly in the MP4 video file. However, the SRT file's first entry is typically recorded right after arming at the launch location, which is almost always your home, driveway, or yard. The MP4 file itself contains device and serial number metadata but typically not the full GPS track. Both files need to be handled separately before sharing.

Does GoPro embed GPS in the video file itself?

Yes. GoPro cameras with GPS capability store telemetry — including GPS coordinates at up to 18 readings per second — in a dedicated GPMF track inside the MP4 file. Unlike DJI, there's no separate sidecar file; all location data rides inside the single video file you share. This means sharing a raw GoPro MP4 is equivalent to sharing a GPS track log of wherever you filmed.

Does YouTube remove GPS data when I upload drone footage?

YouTube re-encodes uploaded videos and strips most container metadata as a side effect, including GPS atoms. For standard public uploads, the GPS data is not present in the video viewers can download. However, YouTube retains your original uploaded file internally, and if you also share the raw file via Google Drive or other direct-file channels, that version remains fully intact with all metadata.

What is the DJI serial number privacy risk?

DJI embeds your drone's serial number directly in every MP4 video file as part of the container metadata. That serial number is unique to your specific aircraft and tied to your registered identity in DJI's database. Anyone analyzing the video file with ExifTool can extract it. For anonymous sharing or sensitive filming contexts, removing container metadata before sharing is important even if GPS tracking isn't the primary concern.

Can I just delete the SRT file instead of stripping the MP4?

Deleting the SRT file removes the most detailed GPS record — the complete flight path log — but the MP4 still contains device model, firmware version, and serial number metadata. For most casual sharing, deleting the SRT is the most important step. For situations requiring full anonymization (investigative work, anonymous posting), both the SRT file and the MP4 container metadata need to be cleaned.

Does video editing software remove drone metadata automatically?

Most video editing software — including DaVinci Resolve, Premiere Pro, and Final Cut Pro — does not automatically strip metadata from exported files. Editors typically carry over or rewrite container metadata during export, and the output file may still contain GPS atoms or device information. Always verify with ExifTool after export, or clean the final output file before sharing regardless of which editor you used.