GoPro Crash on the Slope — Rescuing Footage When the Camera Gives Up

Ski slope, bike trail, surf break — anyone who films with a GoPro knows the risk: a fall, a crash, a lost grip, and the camera cuts out. On the next power-up it flashes “RECOVERY,” tries to fix itself, and what you’re left with is an .MP4 that no player will open.

In most cases the footage is still recoverable. Here’s what to do on that first evening.

What happened during the crash

GoPros (especially the HERO11/12/13) write HEVC video to the microSD card continuously while recording. The index (the moov atom) only gets appended to the file when the recording ends cleanly. During a crash, several things happen at once:

1. The recording stops abruptly. moov is never written. You’re left with ftyp + mdat (holding all the raw frames) + a file with no index.
2. The card may hold an incomplete buffer. GoPros buffer internally and write in bursts — and the last burst is missing.
3. RECOVERY mode kicks in on the next boot. The GoPro tries to repair itself — it doesn’t always succeed, and it sometimes produces a “Recovery_GH010001.MP4” alongside the broken original.

First: back up the card, stop filming

Before you do anything else:

1. Turn the camera off (if it’s still on).
2. Take out the microSD card. On HEROx models, do it gently — the slot can be damaged from the impact.
3. Put the card in a card reader and mount it on your Mac/PC.
4. Copy the whole card as an image. On macOS: dd if=/dev/diskN of=~/gopro-crash.dmg bs=1m status=progress. From now on you work only on the image, never on the card.

Never work directly off the card — every read attempt risks flipping bits if the card picked up micro-damage during the fall. Image first, then work.

Finding the file: what’s actually on there?

Inside the image, in the DCIM folder, you’ll find the usual GoPro files:

• GH010001.MP4 — the main recording. If the clip ran longer than 4 GB, there are continuation files (GH020001.MP4, GH030001.MP4).
• GL010001.LRV — the low-resolution preview (a smaller file for playback in the GoPro app). This one is often intact!
• GH010001.THM — the thumbnail image.

If the .LRV file is intact (opens in QuickTime/VLC), that’s a good sign: it shows the recording actually happened and the card is working. The LRV is a separate file that the GoPro writes in parallel — it often survives when the main MP4 no longer plays.

But the LRV isn’t what you want to keep. It’s typically 1080p at low bitrate. You need the full 4K or 5K footage back.

Repair attempt 1: GoPro Quik / Player

GoPro has its own player (the Quik app on mobile, GoPro Player on desktop). When you open a broken .MP4, Quik sometimes attempts its own repair. For simple cases, that works.

Success rate: ~20%. GoPro Quik gives up quickly when the container is badly damaged.

Repair attempt 2: untrunc with a GoPro reference

If you have an intact GoPro recording from the same camera with the same settings (5K30, 4K60, 4K120, with or without HyperSmooth), use it as a reference.

brew install ffmpeg
git clone https://github.com/anthwlock/untrunc.git
cd untrunc && make FF_VER=4.1

# Referenz und kaputte Datei:
./untrunc -n -s referenz_intakt.MP4 GH010001.MP4
# Output: GH010001_fixed.MP4

Success rate: ~70% with H.264, ~40% with HEVC (see the note below).

Watch out for HEVC

The HERO11/12/13 write 4K60 and 5K in HEVC with hvcC headers that encode NAL units with a length prefix. Stock untrunc often reconstructs this incorrectly — the result is a file that “opens” but shows a blank picture. You’ll recognize it when the repaired file is playable but stays black.

In that case: try a different reference (ideally the exact same settings), or move up to attempt 3.

Repair attempt 3: Haven

Haven is built specifically for HEVC files from modern GoPros. You drag the broken .MP4 and the reference into the app. Haven:

1. Automatically detects a GoPro HERO as the source (from the ftyp brand and the mdat pattern)
2. Reads the hvcC header from the reference correctly
3. Reconstructs moov with the right NAL unit lengths
4. Corrects audio drift (HEROs often have 300–600 ms of drift after a repair)
5. Shows the result in the preview

Success rate for GoPro HEVC with a reference: ~92%.

Download Haven →

More detail on GoPro repair: Repair GoPro video

Special case: 360° footage (MAX, Fusion)

If your GoPro is a 360° cam (MAX, Fusion), you have two separate front- and back-lens streams inside the same MP4. Both have to stay in sync. During a crash, often only one of the two streams cuts out — the other stays intact.

Repair is more complex here. Haven supports 360° MAX files; with the Fusion the success rate is a bit lower, because the stitching format is more proprietary.

Special case: TimeLapse or NightLapse

GoPros capture TimeLapse either as a sequence of individual JPEGs (in the 100GBACK/ folder) or as a continuous MP4 (TimeWarp mode). If the TimeWarp stream is broken, the same repair strategy applies as with normal footage. With JPEG sequences, every file stands on its own — so a “broken TimeLapse” doesn’t really exist.

What should happen after the repair

Even after a successful repair:

1. Back up the original and the repaired file in two different places.
2. Format the card in your computer before using it again (not in the GoPro — that’s less thorough).
3. If the card keeps giving you trouble, replace it. SD cards have a finite number of write cycles. For a GoPro HERO13 at 5K60, a V90 card is the minimum — older V30-class cards usually can’t keep up.

Related guides

• Repair GoPro video — the complete guide — the full walkthrough covering every model and codec variant
• Repair HEVC — for when your GoPro writes HEVC
• The moov atom is missing — the underlying damage

Check your file locally → — browser-based diagnosis, no upload, 30 seconds.