DJI Mini 4 Pro Corrupted Video: How to Recover It

The Mini 4 Pro is built around one number, 249 grams, and everything else follows from that. A small battery with tight power margins, and a single microSD card in the belly of the aircraft holding every frame you shot. When a recording ends the way it should, the drone closes the file and you never think about any of this. When it ends any other way, what is left on the card is a dead file where your flight should be.

Crashes are the obvious way that happens, but far from the only one. A battery hitting empty sooner than the app promised will do it, and so will a card that stops responding mid-write. Whatever was recording at that moment becomes the casualty, and it is usually the one clip you launched for.

How the file gets written, and why it breaks

During recording the drone appends compressed video to the MP4 on the card as fast as it comes, up to 150 Mbps in the heaviest modes. What it cannot write until the very end is the index. An MP4's index (the moov atom) lists where every frame sits in the file and when it should play, and since the drone has no idea how long you will keep rolling, that table is only assembled when recording stops. Power dies first and the card holds megabytes of intact frames with no map to them. Players refuse the file not because the footage is gone but because they cannot find it.

Which codec is inside depends on the mode. 4K100 slow motion and the 10-bit profiles (D-Log M and HLG) are always H.265, while standard modes may be H.264. For a broken file the distinction barely matters, since the break is in the container, not in the frames.

Signal loss, for the record, breaks nothing. If the video feed to your controller drops out, recording carries on aboard the aircraft. It takes a real power cut or a card fault to leave a damaged file behind.

Before you try recovery

First move, before any tool touches anything, is to copy the whole card to a computer and work only on the copies. Some repair attempts modify files in place.

Then, roughly in order of effort:

1. Suspect the reader before the file. microSD cards get read through SD adapters and cheap USB readers, and those fail more often than the cards do. A copy that stalls, or a card that keeps remounting, can look exactly like corruption. Try a second reader, or plug the drone itself in over USB-C, before writing the footage off.
2. Let the firmware have a go. With the card back in the drone, power it on. DJI's built-in repair kicks in when it finds a recording that never closed, and for simple cases it is all you need. It does not have to be your airframe either; any Mini 4 Pro can run the repair, because everything it works from is on the card.
3. VLC. It tolerates damage the stock players will not, and it settles a different question too. A clip that plays in VLC but not in QuickTime or Photos usually means your computer lacks H.265 support, and the file was never damaged at all.
4. untrunc, a free command-line tool, if the file was cut short rather than left unindexed. It rebuilds from a donor, an intact recording made with the same settings, so it only helps if you kept one.

Real corruption looks like this

The file size is plausible, hundreds of megabytes or more. The duration shows 0:00 or nothing at all. VLC fails too. ffprobe reports "moov atom not found" or "invalid data". Other files from the same card play fine. That is a missing index, and it is fixable without any reference file.

How our recovery handles Mini 4 Pro footage

Almost everything the recovery needs survived on your card. The frames are intact; what was lost with the power was the bookkeeping around them. The engine scans the raw bytes for frame boundaries and rebuilds the container around what it finds. The stream itself carries its own description, resolution and frame timing included, which is why no reference clip is asked of you.

Nothing gets re-encoded along the way, so 10-bit D-Log M comes back exactly as flat and gradeable as the drone wrote it. Recordings past 4 GB get 64-bit offsets in the new index (without them, a long flight would cut off partway), and the AAC audio track is reconstructed in sync with the picture.

Proof comes before payment. Uploading is free, the 5-second preview of the recovered result is free, and the full file starts at $5 only if that preview shows your flight. No working preview, no charge.

What you do

1. Upload the MP4. Free, up to 50 GB.
2. Watch the free preview about a minute later.
3. Pay if it is your footage, playing correctly. Otherwise you owe nothing.

FAQ

The drone went into water but the card still reads. Any hope? If the computer can copy the file off the card, yes. Treat it as a normal recovery case and upload the copy. If the card itself is dead, a data recovery lab has to extract the data first; upload whatever they hand back. Failing everything, the DJI Fly app on your phone caches a low-resolution copy of the transmitted feed, which is at least something.

Is the 4K100 slow-motion file different? Only in codec (always H.265) and size. The recovery path is the same, and the slow-motion timing is preserved because it is baked into the recording.

Why does my footage look flat and gray? That is D-Log M doing its job, not damage. It is meant to be color graded. If the file plays, it does not need recovery.

Does this cover the Mini 3 Pro, Mini 5 Pro, and other DJI drones? Yes. DJI's MP4 structure is consistent across the range. See also the Mavic 3 guide and the Osmo Action 4 guide.

What if the last file from the flight is missing from the card entirely? If the card shows no file at all, the drone never created one, and there is nothing to repair. A 0-byte file is the same story.

Is my footage safe? EU servers, HTTPS upload, auto-deleted after 48 hours. Privacy policy.

Related

• DJI Mavic 3 corrupted MP4
• Moov atom not found
• Recover HEVC / H.265 files
• How our recovery engine works

Upload your Mini 4 Pro file →