By Lucas, founder of FixMyVideos · Updated
GoPro Hero 12 or Hero 13 truncated file: what is left on the card and how to recover it
The battery died halfway down the trail, or the card came out while the camera was still writing, and now there is a GX…MP4 on the card that is clearly hundreds of megabytes long and will not open anywhere. We have tested this recovery on recordings from the Hero 10, Hero 11 and Hero 12. The Hero 13 Black writes the same kind of MP4 and should behave the same way, but we have not had one to test yet.
What the camera leaves behind when it stops mid-clip
A GoPro MP4 is a chain of boxes. The big one, mdat, holds the coded pictures and the audio frames written one after another as you film. A second box, moov, is the index: where each picture starts, how long it is, when it plays, and the decoder configuration needed to read any of it. The camera can only write moov after you press stop, because the sizes it lists are unknown until then. Lose power first and the card holds mdat with no index in front of it. Players find no moov and give up. Some report "moov atom not found", QuickTime says the file is not compatible, Windows shows error 0xc00d36c4, and the file browser lists a long clip as 0:00.
A GoPro adds a second problem. For HEVC and H.264 the decoder needs parameter sets (VPS, SPS and PPS for HEVC) that describe how the picture was encoded. Some encoders repeat them inside the video stream. When we measured the action cameras and phones in our test corpus, GoPro included, none of them did: they store those parameter sets only inside the moov box. So the file has lost the index and the decoder settings together, while the pictures are still on the card.
Between the pictures, a GoPro wraps each audio frame behind a 16-byte header of its own that starts with the letters GP, and drops chunks of telemetry in between (gyro, accelerometer and GPS readings, which GoPro calls GPMF).
Check these first, for free
Copy everything off the card before you experiment. Copy the whole DCIM folder to a computer, broken file included, and work on the copies. Do not format the card and do not keep filming on it.
Let the camera try its own repair. GoPro cameras look for an unfinished file when they power up and try to close it. Put the card back in the same camera with a charged battery, switch it on and wait until it settles. Older models showed an SOS icon for this. If the file still does not play afterwards, the pictures are usually still in it.
Find the right chapter. The camera splits long recordings into chapters of roughly 4 GB. The file name tells you which is which: GX means HEVC and GH means H.264, the next two digits are the chapter, the last four the recording. GX010123.MP4, GX020123.MP4 and GX030123.MP4 are one take. Only the chapter that was open when the power went is damaged, and that is always the last one. The earlier chapters play on their own, so that last file is the only one to recover.
The .LRV next to it may play. The .LRV file with the same number is the low-resolution proxy the camera records at the same time for the phone app, and .THM is a thumbnail. The proxy was interrupted at the same moment, so it is often broken too, but it is small and sometimes plays.
Keep a healthy clip from the same camera. Any clip that plays, filmed on the same camera at the same resolution, frame rate and codec setting, holds the exact parameter sets your broken file is missing. The open-source tool untrunc needs exactly that and is built for exactly this case. We may ask for the same thing (more on that below).
What our engine does with a GoPro file that has no index
First it walks the mdat and finds each picture from its own internal length fields and slice headers. The telemetry chunks in the gaps between pictures contain byte runs that look like the start of a picture, and an early version of our walker anchored on a few of them and skipped two or three real pictures each time. On a 180 MB Hero 12 4K30 HEVC test recording, where we keep the original index to check against, that walk found 3304 of the 3310 pictures. Each missing picture is a reference for the ones predicted from it, so the rebuilt file decoded with 14 errors and showed short glitches at those spots. We changed the walker to arbitrate between competing sync points, and in June 2026, on that same recording, it carved all 3310 pictures, byte for byte the same as the camera's own index, in 43 seconds for the whole analyze, rebuild and validate run.
Then it needs the parameter sets the file no longer contains. We keep a store of encoder profiles, keyed by codec, resolution and frame rate, and every candidate has to decode the recording cleanly before it is used. Matching resolution and frame rate is not enough. A GoPro Hero 12 and a DJI Osmo Action 4 both shoot HEVC 4K at 30 fps, and the DJI profile, borrowed for a Hero 12 clip, fails that decode test because the encoder settings differ. Our store keeps several profiles per resolution for that reason. The June run rebuilt the Hero 12 test recording with no reference clip, but the profile that decoded it had been taken from the original of that very recording, so it shows the store doing its job rather than proving that every Hero 12 file will match. Moov-stripped copies of a Hero 10 clip (5.3K at 29.97 fps) and two Hero 11 clips also rebuilt from stored profiles alone with no decode errors, and the two Hero 11 clips got their AAC sound back within 11 ms of the picture. For H.264 files (the GH names) the engine also tries to rebuild the missing settings from the stream itself, and keeps them only if the file then decodes cleanly. When nothing works, the page asks you for one healthy clip from the same camera in the same mode, the one mentioned in the checklist above.
Most HEVC files in our test corpus (34 of 56) carry no frame rate inside the stream at all. GoPro does, but only in the VPS parameter set. Once our parser read it there, all 12 GoPro files in our test set gave their exact frame rate.
Audio is the last piece. Because every AAC frame sits behind one of those GP headers, no gap in the file begins with anything that looks like audio. The engine walks the headers, pulls out the AAC frame behind each one, and keeps the audio only if it decodes with no errors at all. On our Hero 12 test clip the rebuilt sound came back at 48 kHz stereo, landing 45 ms from the picture when we measured it.
When the index is there and the file still misbehaves
A GoPro file can also go wrong in our hands. One reached us in perfect health: a 5.3K HEVC recording of 846 MB with its index intact, decoding with zero errors. Our pipeline still routed it into a rebuild, and the delivered file had no sound and was turned 90 degrees, both because of bugs on our side. The rebuild had trusted the bytes it found between pictures over the camera's own audio table, which listed 3628 real AAC frames, and it had written a fresh track header without the camera's rotation, which is how GoPro records "shot in portrait". We fixed both, and the same file then came out with audio byte for byte identical to the camera's, 0.0 ms of offset at three points we checked, and all 2320 pictures decoding. If your recovered GoPro file comes back silent or sideways, tell us: those were our bugs and we fix them.
A rebuild keeps the video and the audio and drops the other tracks, so the GPMF telemetry and the timecode are not in the recovered file.
We have not validated recovery of the two-lens .360 files from the GoPro MAX, so this page does not promise it.
When the footage is gone
Some files have nothing left to rebuild, and the diagnosis says so instead of selling you a preview.
- 0 bytes. A 0-byte upload gives us nothing to work on. After a power cut the card's file table can still say 0 while the recorded data sits elsewhere on the card, so stop using the card and try a tool that recovers from the whole card (or a lab) before you format it.
- Every byte is zero. We have opened a 30 MB camera file in which every single byte was
0x00. The name and size were there, the content was not. - A header and nothing else. A 24-byte upload held only the first box that says "this is an MP4", with no recording behind it.
- One block repeated. A copy made from a failing card can come back as the same few sectors over and over. One 20 MB file held 12 KB of distinct data. Copying it again through a different reader is the only move that can still work.
If the card itself shows "SD ERR" and the computer can barely read it, that is a hardware problem. A data recovery lab has to make a full copy of the card first, and only then can software get a usable file out of it.
Getting a preview of your file
Upload the broken chapter, up to 150 GB. The engine analyzes it and, within a few minutes, shows you a free 5-second preview so you can see whether it is your footage. You pay only if you want the full file: €6 under 2 GB, €18 from 2 to 20 GB, €35 from 20 to 50 GB and €59 above that, VAT included. Uploads are deleted automatically after 48 hours.
FAQ
Do I need a healthy clip from the same camera? Often not. If our profile store holds a profile that decodes your recording cleanly, the rebuild runs without one. If none does, the page asks for a clip from the same camera at the same resolution, frame rate and codec, and uses its parameter sets.
The camera tried its own repair when I switched it on, but the file still does not play. Is it lost? Not necessarily. If the file still does not play after the camera's repair, the pictures are usually still in it, and the analysis tells you what it found before you pay anything.
My recording was split into several files. Which one should I upload?
The last chapter, the one that was being written when the camera stopped. The earlier chapters (GX01, GX02 and so on with the same four-digit number) were closed normally and play on their own.
Will the recovered file keep my GPS and gyro data? No. The rebuild keeps picture and sound only. The GPMF telemetry track is left out, so tools that draw speed or route overlays will not find it.
Does this work on the Hero 13, Hero 11 and older models? We have tested recordings from the Hero 10, 11 and 12. The Hero 13 writes the same MP4 structure and we expect it to behave the same, but we have not tested one. Whether a given file rebuilds without a reference clip depends on whether a stored profile from the same encoder decodes it, and the analysis tells you before you pay anything.
Is my footage safe? It is uploaded over HTTPS to servers in the EU, deleted automatically after 48 hours, and never shared or used for training. See the privacy policy.
Related
- "moov atom not found": what is missing from your MP4
- GoPro SD card error
- Video plays but has no audio
- Recover HEVC / H.265 files
- DJI Osmo Action 4 corrupted video
- DJI Mavic 3 corrupted MP4
Free preview · No commitment
Ready to recover your video?
Upload your file and get a free 5-second preview in about a minute. Pay only if the preview looks right.
Upload your file →