IntactFile

Repair a corrupted Fujifilm X-T5 video

When an X-T5 clip stops opening, it's almost never lost footage — it's a 10-bit HEVC recording the camera never got to finalize. The frames are still in the file; what's missing is the index that points to them, and it never has to leave your machine to get back.

The Fujifilm X-T5 records up to 6.2K 30p (from its full 40MP sensor), 4K 60p and 1080 240p, using 10-bit 4:2:2 HEVC (H.265) or H.264 with F-Log/F-Log2 profiles. Its 10-bit modes are written into QuickTime .MOV files (H.264 modes can use .MP4), and a .MOV becomes playable only once the camera writes its moov atom — the index that maps every frame — at the end of the take. Interrupt the recording before that and you're left with a file full of valid HEVC data and no map to it. Drop the clip 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 50 MB video, 10 MB docs & archives, 10 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

How an X-T5 clip ends up unplayable

A QuickTime .MOV stores its frames as they're captured (the mdat) and writes the index (the moov atom — the sample tables plus the HEVC configuration a decoder needs) only when recording stops normally. Deny the X-T5 that clean stop and the container is left headless: a large .MOV of perfectly valid 10-bit HEVC with nothing indexing it. Players report "moov atom not found," a codec error, or a black frame with no duration.

The X-T5 is a photo-first, IBIS-equipped body with no cooling fan, and its video interruptions cluster around a few causes:

  • Thermal shutdown. Extended 6.2K or 4K/60p takes generate real heat in a compact body; if the camera hits its limit and cuts out before you press stop, the current clip is left unfinalized. (Fujifilm's "Auto Power Off Temp: High" setting buys more time but doesn't remove the limit.)
  • The card was pulled or power was cut. Popping the SD card while the access lamp is lit, or an NP-W235 that dies mid-take, truncates the file before the index is committed.
  • The card couldn't sustain the write. 10-bit 4:2:2 HEVC at high bitrates wants a fast V60/V90 UHS-II card; a slower or failing card can stall the stream and drop the recording.

In each case the footage you shot up to the moment of failure is sitting in the file — only the small trailing map is missing.

How the container is rebuilt — and why HEVC needs a match

When the moov is missing, it can be reconstructed by scanning the surviving stream and rebuilding the sample tables the X-T5 would have written on a clean stop. For a faithful result the rebuild needs the exact stream configuration — for 10-bit HEVC that means the parameter sets (VPS/SPS/PPS) that describe the 4:2:2 layout, resolution and frame rate — and the most reliable source of those is a healthy clip from the same X-T5 shot in the same mode. If the camera overheated on the last take, the earlier takes on that card are usually intact and make a perfect reference. Keep one handy; you'll only be asked for it if the broken file needs it.

One caveat specific to Fujifilm's HEVC: if you switched between the 10-bit 4:2:2 HEVC modes and 8-bit H.264, make sure the reference matches the codec of the broken clip — an H.264 sample can't supply the configuration a broken HEVC file needs. And a physically failing SD card that returns zeros for parts of the file is lost data, not a container problem; copy the whole card off first, then repair what comes off it.

What this can and can't fix

Can fix

  • The last clip when the X-T5 overheated, lost power, or the card was pulled before finalizing (unfinalized MOV, missing moov)
  • 10-bit 4:2:2 HEVC (H.265) .MOV files, and H.264 clips, that copied off the card but won't play
  • F-Log / F-Log2 recordings left headless by an interrupted take
  • Container damage: broken index, wrong sample offsets, zero-length duration, when the video data itself survived

Can't fix

  • Footage physically lost to a failing or worn SD card — recover the card first, then repair
  • A broken HEVC clip with no matching HEVC reference (an H.264 sample can't stand in)
  • Files that read as 0 bytes or mostly zeros after a card failure
  • Missing HEVC decoder support on your own PC — that's a playback issue; install HEVC extensions

If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.

FAQ

The X-T5 overheated and stopped, and now the clip won't open. Fixable?

Usually yes. A thermal shutdown cuts the recording before the camera writes the moov index, leaving a large .MOV full of valid 10-bit HEVC with no map. Rebuilding the container re-maps those frames and the clip typically plays again.

My clip was 10-bit 4:2:2 HEVC — does that change the repair?

Only the reference. The rebuild works the same way, but if a reference clip is needed it must also be HEVC from the same X-T5, because HEVC carries a different configuration (VPS/SPS/PPS) than the H.264 used in the 8-bit modes. Match the codec and you're fine.

Do I need another clip from the same camera to fix it?

Only if the index can't be rebuilt from the file alone. If prompted, use a healthy clip from the same X-T5 at the same resolution and frame rate so the rebuild inherits the exact stream configuration.

Is my footage uploaded to fix it?

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

Related: Repair MOV (any source) · "moov atom not found" · Repair video (all formats) · Verify the zero-upload claim