IntactFile

Repair a corrupted DJI Air 3 video

When an Air 3's battery cuts out, it's forced into an auto-landing, or a card write stops mid-record, the last recording is almost never lost — it's just a clip the drone never got to finalize. The frames are still on the microSD, and they don't have to leave your device to recover them.

The DJI Air 3 is a dual-camera drone built for stable, line-of-sight aerial video — not the twitchy, crash-first flying of an FPV rig. It carries two primary cameras on matched 1/1.3-inch sensors — a 24 mm wide and a 70 mm 3× medium-tele — and records standard .MP4 files (H.264 or H.265/HEVC) straight to the microSD: 4K up to 60p, plus a 4K/100fps slow-motion mode, streamed back over DJI's O4 transmission. Because it is a steady camera platform rather than a racer, its files rarely die in a violent impact; the usual culprit is an interrupted write — an abrupt power loss, a forced auto-landing on a critical battery, or a card write cut short mid-record — that stops the recording before the drone can stamp the moov index the player needs. Drop the file above and the tool checks exactly that, in your browser, and rebuilds the container when the footage is recoverable.

Your file never leaves your device — repair runs in your browser. 0 bytes uploaded.

Your data is the big block — usually intact. What breaks is the small index. Repair rebuilds it.

Drop a file here or browseTap to choose a file

ZIP · Office · PDF · video · JPG · PNG · RAR/7z · SQLite — repaired right here in your browser. Nothing is uploaded

0 bytes uploadedFree: 3 repairs/day — up to 500 MB video, 100 MB docs & archives, 50 MB photos. Free download. Single repair €5.90. No account required.

Fix it now

  1. Drop the file
  2. Repair runs locally
  3. Download the result

Why an interrupted write — not a crash — strands the last clip

Because the Air 3 can record from both lenses, a single interrupted flight can leave a pair of unfinished MP4s from the very same moment — one from the 24 mm wide, one from the 70 mm 3× tele. And its fastest modes (the 4K/100fps slow-motion, plus 4K/60p) are H.265-only, so a broken Air 3 clip is frequently HEVC even when your everyday footage is H.264. Either way, each of these MP4s is written in two parts: the encoded picture (mdat) streams to the card frame by frame as you fly, and the index (moov) — the table that records where every frame sits and how the H.264/H.265 stream is configured — is written last, only when recording stops cleanly. Interrupt that final step and the footage is all there, but the map to it never gets stamped.

Power loss. A pack hitting its critical threshold, a battery jostled loose, or a cell simply run down mid-clip cuts the write the instant it happens. A forced landing. When the Air 3 auto-lands or returns to home on a low battery and the motors spin down, a file that was still recording can be left unfinalized. A card write cut short. A microSD ejected too soon, knocked loose, or too slow to keep pace can truncate the recording mid-stream. In every case the earlier clips from the same flight are fine — they were finalized before the next recording began — so it is only the file that was live at the moment of the interruption that ends up unplayable.

The giveaway is a file with a believable size — often hundreds of megabytes of real 4K — that a player still rejects as corrupt, reports as 0:00 long, or opens to a black frame. That size is the proof the footage was written; what is missing is only the index that points to it.

How the container is rebuilt — and why the second camera helps

With the moov gone, it can be reconstructed by scanning what survived in the mdat and regenerating the sample tables the drone would have written on a clean stop. A faithful rebuild needs the clip's exact stream configuration — codec (H.264 vs HEVC), resolution, frame rate and the parameter sets — and the ideal source is a healthy clip from the same Air 3 shot in the same mode. The dual-camera design works in your favour here: the wide and the tele record in matching settings, so one lens's good footage is a natural reference for the other, and an interrupted flight almost always leaves earlier clips on the card untouched. You'll only be asked for a reference if the file needs it.

Two honest limits. First, the ceiling on any interrupted write: whatever frames never reached the card before power was cut cannot be invented — the rebuild recovers everything up to the point the recording stopped, and not a frame past it. Second, if the aircraft came down hard in a forced landing or was recovered from water or a field, check the microSD itself before anything else: a physically damaged 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 when power was cut, a forced landing stopped the motors, or the card write was interrupted (unfinalized MP4, missing moov)
  • Either camera's file — the 24 mm wide or the 70 mm tele — that copied off the microSD but won't play in any player
  • H.265 (HEVC) clips from the 4K/60p or 4K/100fps slow-motion modes, and everyday H.264 files, left with a broken container
  • Container damage: missing index, wrong offsets, zero-length duration, when the video data itself survived

Can't fix

  • Footage never written because power was cut mid-record — the rebuild stops where the recording stopped (truncation past the cut can't be invented)
  • Data physically lost to a microSD damaged in a hard landing or water (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.

FAQ

My Air 3 lost power mid-flight and the last file won't open, but it's 900 MB. Is the footage there?

Almost certainly. A file that large is full of encoded frames; what it's missing is the moov index the drone writes only on a clean stop. Rebuilding the container re-maps those frames and the clip usually plays again.

Both the wide and the tele clip from that moment won't play. Can I fix both?

Yes. The Air 3 writes a separate MP4 for each camera, so a single interrupted flight can leave two unfinalized files. Rebuild each one the same way — and because both were recorded in matching settings, each makes a solid reference for the other.

Do I need another clip from the drone to fix it?

Sometimes. If the index can be rebuilt from the file alone, you won't be asked for anything. If not, a healthy clip from the same Air 3 in the same resolution and frame rate provides the exact codec settings for a faithful rebuild — and the drone's other lens usually supplies one.

Is my footage uploaded anywhere?

No. The file is read from your disk and rebuilt in your browser tab; nothing is sent. You can confirm 0 bytes leave your machine in the browser's Network tab.

Related: Repair any DJI video · Repair a DJI Mini 4 Pro video · "moov atom not found"