HandBrake Chapters Missing After Encode: How to Fix It

You finish an encode, open the output, and discover that the chapter menu is empty, chapter titles are wrong, or next-chapter navigation does nothing. When HandBrake chapters are missing after an encode, the cause usually falls into one of four categories: the source contained no detectable chapters, chapter marker creation was disabled, the selected container did not preserve the expected chapter structure, or the playback application is hiding or ignoring valid markers.

The fastest solution is to test each stage separately. Confirm that HandBrake detects chapters before encoding, verify the relevant setting, create a short output, and inspect it in more than one capable player. This approach avoids repeatedly changing video, audio, and hardware encoding options that normally have no effect on chapter markers.

1. Confirm the Symptom With a Small Test Encode or Preview

Before changing a full conversion job, determine whether the output truly lacks chapters or whether one player simply does not display them. Chapter markers are navigation points stored in the media container. They are separate from subtitles, audio tracks, and visible text burned into the picture.

1.1 Check whether HandBrake detects source chapters

Open the source in HandBrake and allow the scan to finish. Look for the chapter range controls and the chapter list associated with the selected title. The exact position can vary by operating system and interface layout, but HandBrake should expose chapter information when the selected source title contains detectable markers.

Confirm all of the following before encoding:

• The correct source title is selected.
• The range is not restricted to seconds or frames when you expect source chapter boundaries.
• More than one chapter appears when the source is supposed to have several.
• The chapter names or numbered entries correspond reasonably to the source.

If HandBrake shows only one chapter, or no meaningful chapter list, there may be nothing for it to preserve. This is common with screen recordings, phone videos, camera footage, downloaded clips, and many previously converted files. Such sources often contain a continuous video timeline without authored chapter navigation.

Success looks like this: HandBrake displays the expected source chapters before the job starts. Once that happens, stop investigating source detection and move to the marker and playback checks.

1.2 Create a short, controlled test

A preview is useful for checking picture quality, but a very short preview may not cross a chapter boundary. For chapter troubleshooting, make a temporary encode that includes at least two known chapter points. If practical, select a short chapter range rather than encoding the entire title.

1. Choose the correct source title.
2. Select a range that includes two or three chapters.
3. Use a standard MP4 or MKV preset.
4. Enable chapter markers.
5. Save the output to a local folder with a simple filename.
6. Open the result in at least two players that support chapter navigation.

Success looks like this: the player can jump to the expected boundaries, even if its interface does not show a permanent chapter list. If one player works and another does not, stop changing HandBrake settings. The remaining issue is player support or interface behavior.

2. Check the HandBrake Settings Directly Related to This Problem

2.1 Enable the chapter marker option

HandBrake must be instructed to write chapter markers into the destination container. Find the chapter marker control in the current job and make sure it is enabled before adding the job to the queue. Depending on the interface, it may be labeled Chapter Markers, Create Chapter Markers, or similarly.

If a job was already added to the queue before you changed the setting, remove it and add it again. Queued jobs retain the settings captured when they were created. Changing the visible job afterward may not update an older queue entry.

Success looks like this: a new encode created after enabling markers contains navigable chapter points. You do not need to alter the video codec, quality value, frame rate, or audio bitrate once the markers work.

2.2 Verify the selected title and chapter range

Disc structures and multi-title files can contain several titles. A main feature, bonus item, menu, and short clip may each expose different chapter layouts. HandBrake can preserve chapters only from the title being encoded.

Check the title duration and chapter count. If the duration is unexpectedly short or the chapter count differs from what you see during normal playback, select the intended title and rescan if necessary. Also confirm that the range includes the chapters you expect. Encoding one chapter will naturally produce fewer navigation points than encoding the full title.

Success looks like this: the selected title has the expected duration, and its listed chapter count matches the content you intend to convert.

2.3 Review renamed chapter titles

HandBrake may allow you to rename chapter entries before encoding. Renaming changes labels, not chapter timing. Blank or unusual names can make a player menu look incomplete even when the navigation points remain intact.

For testing, use simple names such as Chapter 1, Chapter 2, and Chapter 3. Avoid relying on decorative characters until basic navigation works. Some playback applications display only chapter numbers, some display custom names, and others provide next and previous controls without showing titles.

Success looks like this: chapter navigation lands at the correct times. If timing works but names are hidden, the encode is structurally successful and the remaining limitation belongs to the player.

3. Check the Source, Container, Destination, and Playback Environment

3.1 Understand when the source has no chapters to preserve

HandBrake does not automatically invent meaningful scene boundaries for a source with no chapters. A single video file from a phone, camera, screen recorder, or editing export commonly has no authored chapter table. In that situation, enabling chapter markers cannot create a useful multi-chapter result from nothing.

If the source should contain chapters, inspect the original in a chapter-aware media information tool or another capable player. If no application finds chapters, return to the software that authored or exported the source. Add chapters there, or use a dedicated container editing tool after encoding if your workflow requires custom navigation points.

Success looks like this: an independent application confirms that the source contains multiple chapter timestamps. If it does not, stop changing HandBrake settings because preservation is impossible without source markers.

3.2 Compare MP4 and MKV behavior

Both MP4 and MKV can store chapter information, but playback support varies. A television, phone gallery, browser-based player, editing application, or operating system media app may recognize chapters in one container and ignore them in another. This does not necessarily mean HandBrake failed.

MP4 is often chosen for broad device compatibility, while MKV can accommodate a wide range of streams and container features. Neither choice guarantees that every player will expose a chapter menu. If the target device matters most, encode a small MP4 and MKV test with identical chapter settings, then test both directly on that device.

Do not assume that changing the filename extension converts the container. Renaming .m4v to .mp4, for example, only changes the name. Use the desired container setting in HandBrake and create a new output.

Success looks like this: one tested container provides reliable chapter navigation on the intended playback device. Keep that container and stop changing unrelated settings.

3.3 Test players that expose chapter navigation

Some players hide chapters inside a Playback, Navigation, or Chapter menu. Others enable next-chapter commands only while the file is playing. Minimal phone, browser, and television interfaces may ignore chapter data completely.

Test the output in at least two desktop players known to handle common media containers. Look for a chapter menu and try keyboard or menu commands for next and previous chapter. If one application detects all markers at the correct times, the output contains chapters.

Also test the file locally rather than through a media server. A server may transcode, remux, or present a different interface that omits chapter controls. Local playback separates the encoded file from server-side behavior.

3.4 Rule out destination and file-transfer problems

Chapter loss is rarely caused by the destination folder itself, but an incomplete file, stale copy, or incorrectly selected output can create the same symptom. Confirm that you are opening the newly encoded file rather than an older file with a similar name.

• Save the test to a local, writable folder.
• Use a new filename for every test.
• Wait for the job to report completion before opening or copying it.
• Avoid testing from a partially synchronized cloud folder.
• Copy the completed file to the device again if an older version may be cached.

Success looks like this: the exact newly completed local file contains chapters in a capable player.

3.5 Know which settings usually do not cause missing chapters

Video hardware encoders, graphics drivers, audio tracks, and subtitle selections do not normally create or remove container chapter markers. An encoder or driver failure can stop a job, corrupt an output, or produce playback problems, but it is not the first place to look when video and audio play correctly and only chapter navigation is absent.

Audio and subtitle settings matter only indirectly. For example, a complicated job may fail or a target device may reject the resulting combination of streams. To isolate that possibility, use one ordinary audio track and no subtitles in a temporary test. Do not spend time updating drivers or changing hardware encoders unless the Activity Log reports an encoding failure or the output itself is damaged.

4. Use the Activity Log to Separate Guesswork From Evidence

The HandBrake Activity Log records source scanning, selected titles, output settings, and job completion details. It is the best place to determine whether HandBrake found a chapter structure and whether the expected job actually ran.

4.1 What to look for in the log

Open the Activity Log after scanning the source and again after the test encode. Search for references to the selected title, duration, chapter count or chapter boundaries, destination container, and job completion status. Wording can differ across platforms and releases, so focus on the recorded facts rather than one exact phrase.

• Does the scan show the expected title and duration?
• Does the source information indicate multiple chapters?
• Does the encode use the intended MP4 or MKV container?
• Did the correct queue job run?
• Did the process finish successfully?
• Are there read errors, source scan failures, muxing errors, or an interrupted job?

If the log detects only one chapter, revisit the source and selected title. If it detects multiple chapters and the job completes, test the output in another player. If the log reports muxing or write errors, solve those errors before evaluating chapter support.

4.2 Protect private information when sharing a log

The log may contain filenames, folder paths, device details, and source labels. Review and redact sensitive information before posting it publicly. Preserve the technical lines around source detection, chapter information, container selection, and errors so other users can diagnose the issue.

Success looks like this: the log confirms multiple source chapters, the intended destination container, and successful completion. At that point, player compatibility is the most likely remaining cause.

5. Run a Clean Temporary Encode With Minimal Settings

If earlier checks are inconclusive, create a clean job instead of repeatedly modifying the original queue entry. The goal is not to produce the final quality setting. It is to determine whether the chapter path works from source scan to player.

1. Restart HandBrake and open the source again.
2. Select the correct title and confirm its chapter count.
3. Choose a standard built-in preset suitable for the source.
4. Select MP4 or MKV.
5. Enable chapter markers.
6. Keep one normal audio track.
7. Disable subtitles for this diagnostic test.
8. Select a short range containing multiple source chapters.
9. Save to a local folder with a unique filename.
10. Add the fresh job to an empty queue and start it.
11. Check the Activity Log for successful completion.
12. Test the file in two chapter-capable players.

If this clean test works, the original source and HandBrake installation can preserve chapters. Rebuild the final job gradually, keeping the working container and chapter setting. Add desired audio and subtitle tracks, then retest before committing to a long encode.

If the clean test fails but the log confirms source chapters, repeat it once with the other container. If one container works on the target device, use it. If neither works in any capable player, save the log and seek support with the source type, operating system, container, and exact test results.

6. Quick Fix Checklist

• Confirm that HandBrake detects multiple chapters in the selected source title.
• Enable the chapter marker option before adding the job to the queue.
• Remove and recreate queue entries made with old settings.
• Make sure the selected range contains more than one source chapter.
• Use simple chapter names while testing renamed titles.
• Create a short local MP4 or MKV test.
• Open the exact new output in at least two capable players.
• Check hidden Playback, Navigation, or Chapter menus.
• Try next-chapter controls even when no chapter list is visible.
• Review the Activity Log for source chapters, the selected container, and completion.
• Do not change codecs, drivers, audio, or subtitles without evidence they caused a failure.
• Stop changing HandBrake settings when another player successfully finds the chapters.

7. Frequently Asked Questions

7.1 Why does HandBrake show no source chapters?

The selected title may not contain authored chapter markers, or you may have selected the wrong title. This is normal for many camera files, phone videos, screen recordings, and earlier exports. Check the title duration and inspect the original with another chapter-aware application. If no tool detects chapters, HandBrake has no chapter table to preserve.

7.2 Why are chapters present in VLC or another desktop player but missing on my TV?

The television's player may not expose chapters for that container or playback path. Test both MP4 and MKV samples directly on the TV. If a desktop player finds the chapters, HandBrake wrote usable markers and the TV's interface or format support is the limiting factor.

7.3 Does changing from a hardware encoder to a software encoder restore chapters?

Usually not. Hardware and software video encoders compress the picture, while chapters are written as container navigation data. Change the encoder only if the Activity Log shows an encoding error, the job does not finish, or the video output is otherwise defective.

7.4 Can HandBrake automatically create chapters for a video that has none?

HandBrake primarily preserves chapter information detected in the source. Enabling chapter markers does not perform scene detection or create meaningful navigation points in an unchaptered video. Add markers in an authoring workflow or use an appropriate container editing tool if custom chapters are required.

7.5 Why did my renamed chapter titles disappear?

The markers may still exist even when the player does not display custom names. Try next and previous chapter navigation and inspect the file in another player. If navigation works at the right timestamps, the issue is title display support rather than missing chapter data.

7.6 Should I reinstall HandBrake when chapters are missing?

Not as a first step. First confirm source chapter detection, enable chapter markers, recreate the queue entry, inspect the Activity Log, and test another player and container. Reinstallation is reasonable only when settings cannot be saved, scans consistently malfunction, or other program features are also broken.