To extract DJI flight logs, you work through four separate storage locations in order of how likely each one is to still exist. The copy on the phone that flew the mission is usually the fastest to reach and the most valuable after an incident, the remote controller holds a second copy, the aircraft holds the most detailed record if it still boots, and the account cloud holds whatever synchronized. The single most common mistake is clearing the flight app’s data to free up space, which destroys the best copy of the only record of a mission.
Logs contain no footage and cannot reconstruct it. What they establish is facts: where the aircraft was, how high it flew, when the camera was recording, and precisely when that recording stopped. That is enough to direct a recovery attempt at the right file and, in many disputes, to settle whether the footage ever existed.
Prepare before you export anything
Three precautions apply regardless of source.
Check the footage first. If the aircraft survived and still holds media, copy the footage before connecting devices to export data. Logs are read-only in normal operation, but every operation on a damaged aircraft risks the storage it holds; where it has internal storage, start with the guide to extracting footage from drone internal storage.
Record provenance as you go. Note the date, app version, device model, and aircraft serial number alongside each export. If the log will support a warranty claim or a client conversation, provenance matters as much as content.
Do not clear app data or reinstall the app. A reinstall typically wipes local records, and a partial cloud sync means some were never uploaded. Export first, tidy later.
Exporting from the flight app
The app on the phone or tablet that flew the aircraft is the first place to look, and the only source certain to survive the loss of the aircraft. The procedure is consistent across recent versions:
- Open the flight app and sign in with the account used on the day of the flight.
- Open the profile or account screen and select Flight Records.
- Locate the flight by date and time, and confirm it by duration and map trace.
- Use the record’s share or export option and choose the format the app offers, commonly a text record.
- Save the export to two locations and note the file name in your provenance record.
Mobile records are stored per device rather than per aircraft, so a pilot flying with two phones has records split across both. Collect from every device that flew the mission before assuming you have the full set.
One limitation is easy to overlook: records only reach the cloud when the device has network access and the app is signed in. Flights in remote areas can sit unsynced for days.
Exporting from the remote controller
Controllers with built-in screens run the flight app themselves and keep their own copies of the records. After a flyaway or a crash, a recovered controller is often the only intact piece of equipment.
The export path mirrors the app: open the records screen, select the flight by date, and use the share option to write the record to a card. Controllers without a screen hold far less, usually only the most recent session data used for diagnostics.
Two details matter. On a controller used with more than one aircraft the records are interleaved, so filter by date. And controller records can be truncated relative to the aircraft’s own log, because the controller only sees what the radio link carried; a dropout leaves a gap that does not exist onboard.
Exporting from the aircraft
The aircraft holds the most detailed record, sampled at the highest rate, and it is the only copy that continues through a complete loss of the control link. It also requires the aircraft to boot.
DJI exposes the onboard record through the desktop assistant application for the matching aircraft series. Connect the aircraft by USB, open the assistant, select the flight data or black box section, and export. Onboard logs use a different format from app exports and need the manufacturer’s viewer or a compatible analysis tool.
Three constraints apply:
- The record is a ring buffer. Onboard storage is finite, so older flights are overwritten. If several flights have happened since the one you need, the log may already be gone.
- Booting can be the last thing a damaged aircraft does. Copy the footage before exporting the log, and stop if the aircraft shows any sign of instability.
- The aircraft clock may be unsynchronized. It sets itself from satellite time, so a flight that never acquired a fix carries timestamps offset from wall-clock time.
Pulling the synchronized copy from the cloud
If the app was signed in and the device had connectivity, the records were uploaded to the account and can be retrieved from any device signed into it. This is the copy that survives a lost phone or a wiped device.
Sign in elsewhere with the same account, open the flight records screen, and look for records uploaded rather than recorded locally. Records synced from other devices are usually marked as such, and export works the same way.
Cloud retention follows the account’s normal rules and depends on the sync having completed, so treat it as a backup rather than the primary source.
Reading the log to find the interruption
An exported flight record is a time series — one row of telemetry per sample interval. Five fields carry most of the recovery value.
| Field | What it tells you | Why it matters |
|---|---|---|
| Timestamp per sample | The exact time of every recorded event | Brackets an interruption to within one sample interval |
| Camera state flag | Whether the camera was recording at that moment | Proves footage was captured even if the file is missing |
| GPS position and altitude | The aircraft’s track | Locates a missing aircraft and reconstructs a flight path |
| Battery voltage and current | The pack’s condition under load | Distinguishes a power event from a manual stop |
| Warning and event flags | Storage errors, signal loss, mode changes | Identifies whether the media was already failing |
The interruption timestamp drives the recovery work. Find the last sample in which the camera state flag was active and the first in which it was not: the gap between them is the moment recording stopped, accurate to within the sampling interval, and it maps onto one file on the card.
From there the media-side work is the interrupted recording recovery procedure: identify that file, keep the intact chapters beside it as a structural reference, and rebuild the index. A recording that stopped with nominal voltage is a manual stop or a storage error; one that stopped as voltage collapsed is the battery voltage sag failure.
Two timing caveats matter. The aircraft clock and the phone clock are separate, so log timestamps will not match the modified times of video files on the card; measure the offset from the first synchronized sample and apply it across the record. And logs from different sources can disagree about the same instant, because the controller records what the link delivered while the aircraft records what happened.
Using a log as proof that footage existed
The most valuable thing a flight log does is independent of recovery: it establishes that the camera was recording at a specific time.
That matters in three situations. A commercial client who believes a segment was never filmed can be shown a timestamped record of the camera’s state at that moment. An insurer or manufacturer handling a malfunction claim expects the flight record as part of the evidence package, and a complete export supports the claim while a partial one weakens it. And in your own assessment, a log showing recording active at the last telemetry sample tells you the data is on the media and justifies a deeper scan.
Two limits apply. A log cannot reconstruct footage that was overwritten — it proves the flight happened and the camera ran, but returns no images, and the criteria are set out in the guide to when data is unrecoverable. And a log cannot describe what the camera saw: it can place the aircraft sixty meters above a building and pointed at it, but it cannot show the building.
The underlying mechanics of where these records come from and how they are structured are covered in the flight log recovery overview. If the airframe itself is still missing, the last logged position is the starting point for the field search for a lost drone.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive. Data that has not been overwritten comes back in full; data that has been overwritten cannot be recovered by any tool.
Frequently Asked Questions
Where do I find DJI flight logs?
In four places: the flight app on the phone or tablet that flew the mission, the remote controller if it has a screen, the aircraft’s onboard storage through the desktop assistant tool, and the account cloud if sync completed. Export from the app first, because it is the copy most likely to survive losing the aircraft.
What file format are DJI flight records?
Records shared from the app are commonly exported as text files that a viewer can read. Raw onboard logs are a different, binary format needing the manufacturer’s viewer or a compatible analysis tool. Both describe the same flight at different sample rates.
Can a flight log recover deleted drone video?
No. Logs contain flight data, not image data, and no telemetry record can reproduce a frame. What a log does is prove the camera was recording at a given time, which tells you the footage exists on the storage medium and justifies a deeper scan for the unfinished file.
Why do my log timestamps not match my video file times?
Because the aircraft clock and the phone clock are set separately, and the aircraft only synchronizes from satellite time when it acquires a fix. A flight that never locked on carries a fixed offset from wall-clock time. Measure that offset from the first synchronized sample and apply it to the whole record.