IntactFile

Repair a corrupted Nikon Z8 video

When a Z8 recording dies mid-take, the footage is almost always still on the CFexpress card — what's missing is the index the camera writes only when the clip ends cleanly. That index can be rebuilt without the file ever leaving your device.

The Nikon Z8 records internally into two container families: standard QuickTime .MOV files for H.265 (HEVC 10-bit / 8-bit), H.264, ProRes 422 HQ and ProRes RAW HQ; and Nikon's proprietary .NEV wrapper for 12-bit N-RAW, up to 8.3K 60p. 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 get a file full of real HEVC or ProRes data with 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 a Z8 clip ends up unplayable

A QuickTime .MOV is written in two parts: the picture data streams to the card frame by frame as you record (the mdat), and the moov atom — the sample tables that say where every frame lives, plus the codec configuration a decoder needs — is stamped last, when recording stops normally. Deny the Z8 that clean stop and the container is left headless: gigabytes of valid H.265 or ProRes, with nothing indexing it. Players respond with "moov atom not found," a codec error, or a black frame that shows no duration.

On the Z8 the interruption tends to arrive in specific ways:

  • Thermal shutdown. The Z8 packs the Z9's stacked sensor into a much smaller body with far less thermal mass, and extended 8.3K or 4K high-frame-rate takes can push it to auto-power-off before you press stop — leaving the current clip unfinalized. Early firmware was especially prone to this; later updates raised the ceiling but did not remove it.
  • The card was pulled or power was cut. Removing the CFexpress Type B card while the access lamp is still lit, or an EN-EL15c that dies mid-take, ends the write before the index is committed.
  • The card could not sustain the write. N-RAW and ProRes need a fast CFexpress Type B card; a slower or failing card can stall the stream and truncate the file.

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

.MOV, N-RAW and what the rebuild targets

It helps to know which file you have. If you shot H.265, H.264, ProRes 422 HQ or ProRes RAW HQ, your clip is a standard QuickTime .MOV and its index is a moov atom — exactly the structure a container rebuild reconstructs. If you shot N-RAW, the clip is a .NEV file, Nikon's own 12-bit raw-video wrapper; N-RAW is frequently paired with an H.264 .MOV proxy recorded at the same time, and that proxy is itself a normal MOV you can lean on.

When the moov is missing from a .MOV, it can be rebuilt by scanning the surviving stream and reconstructing the sample tables the camera would have written on a clean stop. That job is far more faithful when it has the exact stream configuration — the HEVC parameter sets (VPS/SPS/PPS) or the ProRes frame geometry — and the most reliable source of those is a healthy clip from the same Z8 shot in the same mode: same codec, resolution, frame rate and bit depth. 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.

Why Z8 footage shouldn't be uploaded

Z8 files are large — a few minutes of ProRes 422 HQ or N-RAW runs to many gigabytes — and it's usually footage you can't reshoot: a paid shoot, a wedding, wildlife you waited hours for. Upload-based repair sites take a full copy of that onto servers you can't inspect, over a slow round-trip, under terms you didn't write.

Here the repair runs entirely in your browser. The file is read straight from your disk, rebuilt in the tab, and saved back — nothing is transmitted. You can verify it: open your browser's Network tab and watch 0 bytes of the clip leave your machine. That's not a privacy promise, it's the mechanism, and it means even a multi-gigabyte Z8 clip never has to wait on an upload bar.

What this can and can't fix

Can fix

  • The last clip when the Z8 overheated, lost power, or the card was pulled before finalizing (unfinalized MOV, missing moov)
  • H.265 (HEVC), H.264, ProRes 422 HQ and ProRes RAW HQ .MOV files that copied off the card but won't play
  • H.264 .MOV proxies recorded alongside an N-RAW 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 counterfeit CFexpress card — recover the card first, then repair
  • N-RAW .NEV clips whose proprietary raw stream was truncated before any frames reached the card
  • A file that reads as 0 bytes or is mostly zeros (nothing to rebuild from)
  • Missing HEVC/ProRes decoder support on your own computer — that's a playback problem, not a corrupt file

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

FAQ

The Z8 overheated and stopped, and now the last clip won't open. Can it be fixed?

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

Is my file a .MOV or a .NEV, and does it matter?

H.265, H.264 and ProRes takes are QuickTime .MOV files with a standard moov index — that's what the container rebuild targets. N-RAW takes are .NEV files in Nikon's proprietary raw wrapper; if you recorded a proxy alongside, that proxy is a normal .MOV you can repair.

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 Z8 at the same codec, resolution and frame rate so the rebuild inherits the exact stream configuration (VPS/SPS/PPS for HEVC).

Do I need NX Studio or a Windows PC to repair it?

No. NX Studio is for viewing and converting, not for rebuilding a container whose index was never written. This repair runs in any modern browser on Mac, Windows or Linux, with nothing to install, and the file never leaves your device.

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