GoPro HERO Recovery: Every Generation, Every File Type

Updated by XAppSet Team

GoPro HERO recovery depends on which generation wrote the card, and the differences are not cosmetic: a HERO3 names its clips GOPR0001.MP4 while a HERO13 writes GX010038.MP4, and the files that disappear most often are not the same on both. The single most useful thing to know before scanning is what a healthy card from your model looks like, because recovery software is far better at finding files when you can tell it what it is looking for.

Start by copying the whole card to a folder on a computer, not just the clips you can see. GoPro cards carry companion files — thumbnails, low-resolution proxies, telemetry, and on newer models cloud-sync state — and several of those help rebuild the clips you actually lost.

What Changed Across Generations, and What Did Not

Three things have stayed constant since the HERO3 era, and they explain most recovery behavior on GoPro media.

First, every clip is written as a standard MP4 with a moov index at the end of the file, which means an interrupted recording has all the video data and no usable index. Second, long recordings are split into chapters of roughly 4 GB, because FAT32 compatibility shaped the original design and the division remains useful for camera stability. Third, GoPro writes small companion files beside the clips — .THM thumbnails on every generation, and .LRV low-resolution proxies on many older and mid-generation models.

What changed is the codec, the naming scheme, and the storage model:

  • HERO3 (2012) through HERO4 (2014) record H.264 and name clips sequentially: GOPR0001.MP4, GOPR0002.MP4, and so on, with matching .THM thumbnails. The HERO4 introduced GPR RAW stills on higher-end bodies, which put two very different file types on the same card.
  • HERO5 (2016) and HERO6 (2017) moved to a naming pattern that encodes the codec and the chapter: GH01 for AVC and GX01 for HEVC, followed by a two-digit chapter number and a four-digit file number. HERO6 made HEVC common at 4K.
  • HERO7 (2018) and HERO8 (2019) refined the same scheme. HERO8 added cloud auto-upload, which is the first generation where the card’s state can be modified by something other than a recording.
  • HERO9 (2020) through HERO13 (2024) write very large 5.3K and 8K files at high bitrates, and the entry-level HERO released in 2024 uses the same naming convention. GoPro MAX and 360 mods write .360 files with a GS01 prefix instead of an MP4.

Recovery tools that only search for .MP4 signatures will miss .360 files, GPR stills, and every fragmented HEVC clip whose chapter order matters. That is the practical difference between a tool built for GoPro media and a generic photo carver.

File Naming by Generation

The filename is a map of how the clip was written. Read it before you scan, and the recovery plan becomes much more specific.

GenerationClip namingCodecCompanion filesMost often lost
HERO3 and HERO3+GOPR0001.MP4H.264.THMFinal chapter after battery death
HERO4GOPR0001.MP4 plus GOPR0001.GPRH.264.THM, .LRVGPR stills after a card pull
HERO5, HERO6GH01####.MP4, GX01####.MP4H.264 and HEVC.THM, .LRVMiddle chapters, proxy deletion
HERO7, HERO8GH01/GX01 chaptersHEVC.THM, .LRVInterrupted cloud upload
HERO9, HERO10GX01 chaptersHEVC.THM5.3K clips with heavy fragmentation
HERO11, HERO12, HERO13GX01 chapters, GS01 for 360HEVC.THM, GPMF telemetryThermal-stopped long takes

The chapter digits matter more than they look. In GX020038.MP4, the 02 is the chapter and 0038 is the take, so GX010038.MP4 and GX020038.MP4 are the first and second parts of the same recording. When a scan returns chapter 2 of a take without chapter 1, you have a fragment of a longer clip rather than a complete file, and playing it will show the middle of an action with no beginning. Reassembly, not recovery, is what is missing.

If your model is old enough to produce .LRV files, do not dismiss them. They are low-resolution copies with the same structural markers as the full clip, and they are frequently used to rebuild a damaged index. Our guide to salvaging THM and LRV files explains what each of them can and cannot contribute.

Chaptering: One Take, Many Files

One continuous take becoming many chapter files worth the same as the whole

This is the part most GoPro users learn the hard way. GoPro does not record a new file because you stopped; it starts a new chapter because the current file reached a size threshold. A three-minute downhill run at 5.3K can therefore exist as three or four chapters, and the card’s file system treats them as unrelated files.

The consequences for recovery are specific:

  • A single recovered chapter is not the take. It plays, and it may look correct, but it is a fragment. Count the chapters against the duration you remember before concluding that a clip is fully recovered.
  • Chapter numbering survives deletion better than the content does. The file system entries are gone after a delete or quick format, but the internal metadata and the companion thumbnails often still carry the take number, which is how tools reconstruct the order.
  • Gaps are the giveaway. If a scan returns GX010038 and GX030038 but not GX020038, chapter 2 was either overwritten or written to a bad block, and the missing part is probably gone rather than merely hidden.
  • Playback order is not automatic. Even when every chapter is recovered, most players will not chain them. Concatenating them in the right order is a separate step; the process is covered in our page on GoPro chaptered video.

Chapters are also the reason a GoPro card can look healthy while holding incomplete takes. The camera writes the index of each chapter only when that chapter closes, so a power loss mid-take leaves the last chapter index-less while the earlier chapters stay perfectly playable. That asymmetry is why people report “the first half is fine and the last minute is broken.”

GPR, MP4, and Mixed Storage on One Card

Three file types sharing one memory card space

HERO4 and later bodies with RAW photo modes write GPR files alongside video, and the mix changes the recovery problem in two ways.

GPR is a container-based RAW format, not a plain image. It holds the sensor data plus an embedded preview image and metadata, so a damaged GPR is not necessarily a lost photo: the embedded JPEG preview can often be extracted and used even when the RAW data is unrecoverable. The workflow for that is described in our guide to extracting the embedded JPEG from a RAW file.

Mixed cards also fragment faster. A card that alternates between multi-gigabyte video files and smaller RAW bursts produces exactly the interleaved, scattered allocation that makes naive recovery tools return unplayable files. This is one practical argument for using separate cards for stills and video on a job where both matter.

A third file type appears on newer bodies: GPMF telemetry tracks that store gyro, GPS, and speed data alongside the video. Losing them does not lose the picture, but it does lose stabilization data and speed overlays, and some editors rely on them for post-processing. Their recovery is a distinct problem from video recovery.

Cloud Sync From HERO8 Onward Changes Recovery

HERO8 and later can upload clips to a GoPro subscription automatically while the camera charges, and this has a side effect worth understanding: the camera writes to the card during upload. Files are tagged as uploaded, and in some firmware the camera performs maintenance on the card at the same time.

Three practical consequences follow:

  • The cloud copy may be the good copy. If a clip uploaded successfully, download it rather than trying to recover it from a failing card. It costs nothing and is faster.
  • A partial upload leaves a partial file in the cloud and a local card that has been written to. If the upload was interrupted, the cloud version is a truncated clip and the local card may have lost reliability. Compare durations between the two before deciding which to repair.
  • Upload state can confuse a recovery scan. Files already uploaded may behave differently in the file system, and a card pulled during an upload session is the classic case that produces a card the camera later refuses to read. That scenario is covered in our page on GoPro cloud upload failures.

One generation-specific caution applies to the HERO9 and later bodies: 5.3K and 8K clips at high bitrates push the card hard for extended periods, and thermal throttling can stop a recording mid-take. A card that failed there is not necessarily a bad card, but it is a card that should be tested after the footage is off it.

Which Files Fail, and Which Recovery Route They Need

Most GoPro losses fall into five patterns, and each has a different answer.

Clips deleted in the camera, or the card quick-formatted. The standard case. Nothing has overwritten the blocks, so a signature-based deep scan recovers the video; the work is proportional to card size, and a 128 GB scan typically runs 15 to 45 minutes.

The last chapter is missing or will not play. A power loss or a card removal mid-take. The data is usually present and the index is not; the camera’s own repair prompt, GoPro’s desktop app, or a reference-file repair fixes most of these. Our guide to repairing HEVC footage covers the codec-specific cases.

Chapters recovered but the take is out of order. Chapter 2 plays, chapter 1 plays, and the sequence is wrong. Reassemble by take number rather than by file date.

The card is no longer recognized. Do not format when the camera or the computer offers to. The data is usually intact behind a damaged index, and the correct next step is to image the card and work from the image.

GPR stills recovered as unreadable files. Try extracting the embedded preview, and check whether the files are complete by size against a known-good GPR from the same camera.

When the problem is deleted material rather than a broken index, and you are on Windows with a card the computer can still detect, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive. Recovered-but-unplayable files are a separate problem with a separate fix: the data is there and the container needs rebuilding.

The Order of Operations on a GoPro Card

  1. Take the microSD card out of the camera and set the camera aside. Do not connect the GoPro over USB; the firmware can write to the card on connection.
  2. Copy anything that still plays to a computer, including .THM and .LRV companions and any .GPR stills, so the scan does not have to re-read them.
  3. Note the take numbers you care about from the files you do have. That list is what turns a scan result into a decision.
  4. Scan with a card reader using a deep, signature-based pass, and let it finish; large GoPro clips surface late because their fragments span the card.
  5. Save the results to a different drive, then check chapter counts, durations, and playback on a machine with HEVC support before you trust the set. Our page on verifying recovered drone footage sets out a verification routine that applies to action cameras equally.
  6. Delete nothing from the card until the recovery is verified and the footage exists in two places.

For a wider look at how GoPro files behave inside the container, our GoPro video recovery walkthrough covers the HEVC fragment problem in more depth, and recovering deleted GoPro videos covers the deletion case start to finish.

Frequently Asked Questions

Why are my GoPro clips split into several files?

GoPro splits long recordings into roughly 4 GB chapters for file-system compatibility and camera stability. The chapters are parts of one continuous take, not separate recordings. They must be reassembled in chapter order to play as the original clip.

Can I recover a GoPro clip with no chapter 1?

You can recover the chapters that remain, but the missing part is only recoverable if nothing has overwritten it. A take whose first chapter was overwritten will always begin mid-action. Scan the card fully before assuming the chapter is gone, and check .LRV proxies for a low-resolution copy.

Do the LRV and THM files matter for GoPro HERO recovery?

Yes, particularly on older generations. .THM thumbnails confirm what a clip contains, and .LRV proxies carry structural markers that help rebuild a damaged index. Back them up along with the clips, and do not delete them during cleanup.

Does GoPro cloud upload remove footage from my card?

No. Auto-upload copies clips to the cloud and marks them as uploaded, but the card keeps the originals until it is formatted. If a clip uploaded successfully, the cloud copy is a faster route than recovering from a failing card, though an interrupted upload leaves a truncated cloud file.

Privacy Overview
XAppSet

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful. Learn more

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.