Repair a Corrupted Panasonic Lumix GH6 Video

Repair a corrupted Panasonic Lumix GH6 video

When a GH6 recording won't open, it's rarely lost footage — it's a high-bitrate clip the camera never got to finalize. The frames are usually still on the card, and they don't have to leave your device to recover them.

The Panasonic Lumix GH6 (DC-GH6) records up to 5.7K (5728×3024) at 60p, C4K 120p and anamorphic modes, writing internally to CFexpress Type B and SD UHS-II. Its heaviest formats — Apple ProRes 422 HQ and ProRes 422 — land in QuickTime .MOV files, as do the 10-bit 4:2:2 Long-GOP HEVC (H.265) modes; lighter H.264 modes can land in .MP4. Every one of those becomes playable only when the camera writes its index (the moov atom for MOV) at the end of the take. If that final write never happens, you get a file full of real ProRes or 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.

Fix it now

Drop the file
Repair runs locally
Download the result

Why the GH6's failures are about the card, not heat

The GH6 is unusual among mirrorless bodies: it has an active cooling fan, so Panasonic rates it for unlimited recording and it rarely, if ever, thermally shuts down. That removes the most common cause of a truncated clip — and points the finger squarely at storage and power instead.

The GH6's top modes are brutally demanding. ProRes 422 HQ at 5.7K runs at roughly 1.9 Gb/s, which is why ProRes 5.7K is CFexpress-Type-B only; the SD slot simply can't sustain it. When a card can't keep up, or begins to fail, the camera stalls the write and the current file is left unfinalized. The other classic culprits are mechanical:

The card was pulled too soon — removed while the access lamp was still writing, so the tail of the file, where the index lives, was never committed.
Power was cut. A depleted DMW-BLK22 battery or a yanked DC coupler during a long take ends the write instantly.
A card at its limit. Feed a high-bitrate HEVC or ProRes mode a card slower than it needs and the recording can drop or truncate.

The reassuring part is that these are the recoverable cases: the take you shot up to the moment of failure is sitting in the file as valid ProRes or HEVC — only the small trailing map is missing.

How the container is rebuilt — and why a good take helps

When the moov is gone, it can be reconstructed by scanning the surviving data and rebuilding the sample tables the GH6 would have written on a clean stop. For a faithful result the rebuild needs the exact stream configuration — whether the clip is ProRes or HEVC, the resolution and frame rate, the 10-bit 4:2:2 layout, and (for HEVC) the parameter sets — and the most reliable source of those is a healthy clip from the same GH6 shot in the same mode. Because a card or power fault usually only strands the last file, the earlier takes on that card are typically intact and make a perfect reference. Keep one handy; you'll only be asked for it if the broken file needs it.

One honest note on formats: match the reference to the broken clip. A ProRes 5.7K sample won't stand in for a broken HEVC clip, and vice versa, because the two carry entirely different codec configuration. And if the CFexpress card itself is failing — returning zeros for parts of the file — that's lost data, not a container problem; copy the whole card to your computer first, and if the bytes are there, the rebuild does the rest.

What this can and can't fix

Can fix

The last clip when a card stalled, the card was pulled, or power was cut before finalizing (unfinalized MOV, missing moov)
ProRes 422 HQ / ProRes 422 and 10-bit 4:2:2 HEVC .MOV files that copied off the card but won't play
H.264 .MP4 clips left unfinalized by the same interruptions
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 CFexpress or SD card — recover the card first, then repair
A clip whose reference you can't match — e.g. no healthy ProRes sample for a broken ProRes file
Files that read as 0 bytes or mostly zeros after a card failure
Missing ProRes/HEVC decoder support on your own computer — that's a playback issue, not corruption

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

FAQ

The GH6 has a fan and never overheats — so why did my clip break?

Exactly because heat isn't the issue, the cause is almost always storage or power: a card that couldn't sustain the write, a card pulled too soon, or a dead battery. Any of those cuts the recording before the camera writes the moov index, leaving a valid clip with no map.

My clip was ProRes 5.7K on a CFexpress card. Recoverable?

Usually yes, if the data reached the card. ProRes 5.7K runs near 1.9 Gb/s, so a card that stalled mid-write can truncate the file rather than erase it. Rebuilding the moov re-maps the frames that were written; only footage from after the stall is genuinely gone.

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 GH6 in the same format (ProRes or HEVC), 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 — which also means a multi-gigabyte 5.7K clip never waits on an upload.