To merge GoPro chapter files, you have to know which of the two chaptering architectures you are dealing with, because they fail differently. Self-contained chapters, which is what a modern GoPro writes as GH01, GH02, GH03 and so on, are each a complete MP4 that plays on its own; joining them is a lossless table rewrite. Index-dependent chaptering, used by some camcorders and drones, keeps the sequence definition in one place, and losing that one place makes every remaining file unplayable even though all of them are intact.
So the first action after a loss on a chaptered recording is not to merge anything. It is to confirm that every chapter is still present and that the lowest-numbered chapter survived, since that file is the one most likely to hold the index for the whole take.
Why a Camera Splits One Take Into Chapters
Chaptering is not a leftover from the FAT32 era, even though that is where it started. FAT32 capped a single file at 4 GB, which at high bitrates is under fifteen minutes of 4K footage, so cameras had no choice but to start a new file. Modern action cameras format cards as exFAT, which supports files measured in terabytes, and they still chapter recordings at roughly the same size. The reason is risk: a single 90-minute file that loses its index is a total loss, while a chaptered take loses only the chapter that was being written.
| Behavior | What you see on the card | What it means for recovery |
|---|---|---|
| Chapters written every 4 GB | GH01xxxx.MP4, GH02xxxx.MP4, GH03xxxx.MP4 | The four-digit group after GH is the chapter number |
| Chapter size after a settings change | Same numbering, new clip number | Never mix two different recordings in one merge |
| Telemetry stream | GPMF data inside each MP4 | Resets at every chapter boundary |
| Camera shut down mid-chapter | Final chapter has no closing index | Full file size, will not play, repairable |
| Card formatted then reused | First chapters overwritten before later ones | Recovery must begin at chapter one |
The naming convention carries more information than most people read. In GH010123.MP4, the GH prefix means a standard chapter, 01 is the chapter number, and 0123 is the clip identifier. A 4K recording might also produce LRV proxies and THM thumbnails with matching numbers. When you sort recovered files, sort by extension first and then by the full filename, because sorting by size will interleave proxies with real footage.
The Two Chaptering Architectures
Self-contained chapters. Every GoPro MP4 chapter contains its own movie atom, its own track tables, and its own codec initialization data. Chapter 2 does not need chapter 1 to open. This is the architecture the format has used since the HERO3 era, and it has one large advantage: a corrupted or missing middle chapter costs you that chapter’s content and nothing else. The rest of the take still plays.
Index-dependent chapters. Some camcorders and several drones write segment files that are meaningless without a playlist or an index stored elsewhere — in the first file of the sequence, in a sidecar file, or in a directory the camera maintains. The segment files hold compressed video payload but no self-contained description of how to decode them in sequence. When the index is gone, every file in the sequence becomes a stream of bytes that no player can interpret, even though each file is byte-for-byte intact.
The distinction explains an outcome that looks impossible: a card that scans cleanly and yields twenty files of correct size, none of which will play. The files are fine. The interpreter is missing. This is also why the recovery order matters. When a scan returns files from a chaptered take, start with the lowest chapter number and work upward, because if an index exists anywhere on the card it is most likely inside the first file, and its presence or absence determines whether the remaining files are usable as-is or need reconstruction.
Lost Chapter One Is Worse Than It Looks
Losing chapter one is the most damaging single loss in a chaptered recording, and the reason is not that the first four gigabytes are the most valuable.
If the chaptering architecture is self-contained, losing chapter one costs you the opening section of the take and nothing else. If it is index-dependent, losing chapter one removes the decoder’s roadmap for the entire sequence. The remaining chapters still contain every frame they recorded, but the metadata that describes their track structure, their time base, and their frame ordering lived in the file that no longer exists.
Recovery software handles the two cases differently. For a self-contained sequence, recovery is complete: scan, collect, merge. For an index-dependent sequence with a missing first file, the remaining chapters have to be treated as raw video data and rebuilt from the bitstream — a resynchronization job rather than a file-listing job. That is slower and less certain, and it is why a scan that appears to return everything can still produce an unusable take.
There is a related trap in the recovery sequence itself. If the card was formatted and then reused, the oldest files are the ones most likely to have been overwritten, which means chapter one is usually the first casualty. A scan that reports a complete set of twenty chapters should be checked against the camera’s own record of the recording length before you trust it. For the wider version of this vertical, see our guide to stitching chaptered footage from GoPro cards, which covers the GoPro-specific tools and naming rules in detail.
Joining Chapters Without Re-encoding
When every chapter is present and playable, a merge is a container operation, not a rendering operation. Nothing is decoded and nothing is recompressed, so the join takes seconds rather than minutes and the output is bit-identical to the source frames.
Two conditions have to hold. All chapters must share the same codec, resolution, frame rate, and audio configuration, which is true within a single recording and false across two recordings made with different settings. And the merge has to rewrite the track tables rather than concatenate bytes.
The byte-level approach is the most common mistake. Copying chapters into one file with a shell command produces something that plays in some players and stops at the first splice in others, because a player reads the first movie atom, then follows offsets that pointed into the original file and now point into the wrong place. The result looks like a corrupted file, and people often conclude the footage is damaged when the data is untouched.
| Method | Decodes video? | Preserves quality | Handles mismatched parameters | Notes |
|---|---|---|---|---|
| Byte-level copy | No | Yes | No | Breaks offset tables, unreliable playback |
| Concat demuxer | No | Yes | No | The correct lossless path |
| Editing timeline export | Yes | No, unless set to pass-through | Yes | Re-encodes by default |
| Recorder or camera-generated index | No | Yes | Handles only its own format | Not available after the fact |
Frame alignment at the splice is the subtle part. A chapter boundary can fall between frames that were captured at the same instant, and a camera that dropped a frame while closing one chapter and opening the next leaves a one-frame gap that no merge tool can invent. The visible result is a single-frame flash or a barely perceptible audio skip at each boundary. Nothing is wrong with the merge; the gap was recorded that way.
Telemetry has the same problem in a different form. GoPro writes GPMF sensor data into every chapter, and that stream restarts at each new file. If you plan to run stabilization or overlay speed and altitude, do the merge first and apply the telemetry afterward, or the sensor stream will reset in the middle of the processed clip. The general mechanics of how these files are structured are covered in our page on how GoPro splits a recording.
Repairing a Chapter That Will Not Play
A chapter that shows the correct file size and refuses to open is missing its index, not its video data. That is the signature of a recording that was interrupted by a battery pull, a card removal, or a shutdown while the buffer was still flushing.
The frames are present in the file. What is absent is the table that tells a player how many frames there are, where each sample starts, and how the audio and video tracks interleave. Repair means rebuilding that table from the elementary stream, which is why a repaired file usually plays perfectly and sometimes loses the final second or two.
Three practical rules apply. First, work on a copy and keep the original, because a repair attempt that writes over the source can destroy the only copy of the index fragments. Second, repair before merging: a chapter with no index should be rebuilt first and then joined, since most merge tools simply skip a file they cannot parse. Third, verify the repaired chapter on its own before adding it to a sequence. The checks worth running are described in our guide to verifying recovered video files.
If several chapters are damaged at the end of the take — the expected pattern when power was lost during a long recording — treat them as a group. The last chapter is almost always the worst affected, and the second-to-last often only needs its trailing index rebuilt. Where an MP4 is missing its index atom entirely, the dedicated walkthrough in our article on repairing a missing moov atom covers reconstruction and the tools involved.
If you are on Windows and the card is still detected by a computer, 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. A chapter set that was overwritten by later recording is not recoverable by any tool, and a card that no longer enumerates belongs to a laboratory; the boundary is the same one described in our overview of recovering interrupted recordings.
Frequently Asked Questions
Why are my GoPro videos split into GH01 and GH02 files?
Because the camera closes the current file and opens a new one at a fixed size, around 4 GB, rather than writing one long file. On exFAT cards this is a deliberate design choice, not a file system limit: it caps the loss from a single failed write and keeps files manageable for editing software.
Can I merge GoPro chapters without re-encoding?
Yes, as long as every chapter came from the same recording and holds the same codec, resolution, frame rate, and audio layout. Use a concat demuxer, which rewrites the track tables and copies the compressed frames unchanged. Byte-level copying breaks the internal offset tables and produces playback that stops at the splice.
What happens if one chapter in the middle is missing?
With self-contained chapters, you lose that chapter’s content and the rest still plays. With index-dependent chapters, a missing middle file can interrupt the sequence. In both cases, check whether the missing chapter was overwritten rather than merely deleted, since overwritten blocks cannot be recovered.
Does a chapter file that will not open mean the footage is gone?
Usually not. A file with the correct size that refuses to play is normally missing its index, which happens when recording was interrupted. The frames remain in the file and can be rebuilt, though a repaired clip may lose the last second or two at the end.