Repair a corrupted Nikon Z8 video

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.

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.

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.