Fix it now
- Drop the file
- Repair runs locally
- Download the result
The DJI Air 3 is a dual-camera drone — a 24 mm wide and a 70 mm 3x medium-tele, both on 1/1.3-inch sensors — that records into standard MP4 files using H.264 or H.265 (HEVC), up to 4K at 100 fps. When a clip won't open after a hard landing, the encoded video is normally intact on the microSD; what's missing is the moov index the player needs to read it. Drop the file above and the tool checks exactly that, in your browser, and rebuilds the container when the footage is recoverable.
Why a crash breaks the last clip specifically
An MP4 is written in two parts: the media payload (mdat) streams to the card frame by frame as you fly, and the index (moov) — the table that says where every frame lives and how the H.264/H.265 stream is configured — is written last, when recording stops cleanly. A drone almost never stops cleanly when something goes wrong:
Power loss. A depleted battery, a battery ejected on impact, or a flyaway that ends in a crash all cut power the instant they happen — mid-write, before the moov is stamped. Physical impact. The camera and its storage take the hit; if the write is interrupted, the final file is left headless. The earlier clips from the same flight are fine because they were finalized; it is only the recording that was live at the moment of failure that ends up unplayable.
The symptom is consistent: a file with a realistic size (often hundreds of megabytes) that a player rejects as corrupt, shows as 0:00 long, or opens to nothing. That size is the tell — the footage is there; only its map is missing.
How the rebuild works — and why a good flight helps
When the moov is missing, it can be reconstructed by scanning the surviving mdat and rebuilding the sample tables the drone would have written on a clean stop. For a faithful result the rebuild needs the exact stream configuration — codec (H.264 vs HEVC), resolution, frame rate and the parameter sets — and the most reliable source of those is a healthy clip from the same Air 3 recorded in the same mode. Because a crash usually leaves earlier clips from that very card intact, you typically have a perfect reference already. You'll only be asked for one if the file needs it.
One honest caveat specific to drones: if the aircraft was recovered from water, a field, or a long drop, check whether the microSD itself survived. A physically damaged or corrupted card can return zeros for parts of the file — and no software can rebuild footage that was never actually saved. Copy the card to your computer first; if the bytes are there, the container rebuild does the rest.
What this can and can't fix
Can fix
- The clip that was recording at the moment of the crash or power loss (unfinalized MP4, missing moov)
- H.264 or H.265 files that copied off the card but won't play in any player
- Container damage: missing index, wrong offsets, zero-length duration
- Files a recovery tool returned in an unplayable state, when the video data itself survived
Can't fix
- Footage never written because power was cut before those frames reached the card
- Data physically lost to a microSD damaged in the crash (recover the card first, then repair)
- Clips overwritten after the card was reused or reformatted
- Files that read as 0 bytes or mostly zeros
If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.