- Enable Burn In on the intended subtitle track, not merely Default.
- Disable Forced Only when you need complete dialogue subtitles.
- Verify success by turning player subtitles off and checking captions remain.
- Confirm the Symptom With a Small Test Encode or Preview
- Check the HandBrake Settings Directly Related to This Problem
- Check the Source, Output, and Playback Factors That Apply
- Use the Activity Log to Separate Guesswork From Evidence
- Run a Clean Temporary Encode With Minimal Settings
- Quick Fix Checklist
- Frequently Asked Questions
You selected a subtitle track in HandBrake, completed the encode, and opened the finished video only to find that the subtitles are missing from the picture. This usually happens for one of four reasons: the subtitle was added as a selectable soft track instead of being burned in, Forced Only filtered out most or all captions, the chosen track or format was not handled as expected, or the player is hiding a soft subtitle track. The steps below isolate each possibility without requiring you to change unrelated video settings.
Burned-in subtitles become part of the video image and cannot be switched off. Soft subtitles remain separate tracks that a compatible player can enable or disable. Confirming which result you actually created is the key to fixing HandBrake subtitles not burned in.

Start with free Canva bundles
Browse the freebies page to claim ready-to-use Canva bundles, then get 25% off your first premium bundle after you sign up.
Free to claim. Canva-ready. Instant access.
1. Confirm the Symptom With a Small Test Encode or Preview
Before starting another full movie or long recording, test a short section containing dialogue that you know has subtitles. A controlled test tells you whether HandBrake is failing to render the selected track or whether you are simply viewing a section with no applicable captions.
1.1 Choose a section that definitely contains subtitles
Move to a chapter or time range where the desired subtitle track displays several complete lines in the original source. Avoid opening credits, silent scenes, and sections containing only signs or foreign-language dialogue unless those are specifically what you are testing.
If HandBrake offers a preview for your selected source and settings, generate a preview that crosses the known subtitle section. Make the preview long enough to include at least one expected caption. A preview from the wrong time range can incorrectly suggest that the burn-in setting is broken.
1.2 Know what a successful burn-in looks like
Open the preview or short encode in a video player and turn every subtitle track off in the player's subtitle menu. If the words remain visible, the subtitles were burned into the picture successfully. Stop changing subtitle settings at that point. Any remaining issue is likely related to style, placement, timing, or your choice of track rather than burn-in itself.
If the words disappear when subtitles are disabled in the player, HandBrake created a soft subtitle track. If no subtitle option appears and no text is visible, continue with the checks below.
1.3 Use a short range instead of repeatedly encoding the entire source
Select a short chapter or a limited range of seconds around the known dialogue. Keep the same source, subtitle track, and output format you intend to use later. This reduces troubleshooting time and prevents several simultaneous changes from obscuring the actual fix.
2. Check the HandBrake Settings Directly Related to This Problem
The most common HandBrake subtitles not burned in fix is found in the Subtitles tab. Adding a track is not the same as instructing HandBrake to render that track into every video frame.
2.1 Select the intended track in the Subtitles tab
Open the source, go to the Subtitles tab, and inspect the subtitle list. Remove tracks that you do not need during testing. Add one known subtitle track in the correct language and verify that it is the track you saw in the source.
Sources can contain several tracks with similar names. One might contain complete dialogue, another might contain captions for hearing-impaired viewers, and another might include only forced translations. Language labels can also be incomplete or inaccurate. Testing one track at a time makes the result unambiguous.
2.2 Enable the Burn In option
Find the row for the intended subtitle track and select its Burn In checkbox or burn behavior. The wording and layout can differ between HandBrake interfaces, but the required outcome is the same: the selected subtitle must be marked for rendering into the video rather than only being passed through as a separate track.
HandBrake can burn only one subtitle track into a given video image. If several tracks are listed, confirm that the correct row is marked for burn-in. Remove extra subtitle rows from the temporary test if you are uncertain which selection HandBrake will use.
After enabling Burn In, create another short preview or encode. Success means the text remains visible even after all subtitles are disabled in the player. Once that happens, stop changing subtitle options and apply the verified setup to the full encode.
2.3 Turn off Forced Only unless you specifically need it
Forced Only is a filter, not another term for permanent burn-in. It tells HandBrake to include only subtitle events marked as forced, such as translations for dialogue spoken in another language. It does not force ordinary subtitles onto the video.
If Forced Only is selected for a normal full-dialogue track, most captions may disappear. Some tracks contain no events marked as forced, producing a test with no visible text at all. Clear Forced Only, retain Burn In, and test the same known dialogue section again.
If captions now appear permanently, Forced Only was the cause. Leave it disabled unless your goal is specifically to show only forced events.
2.4 Do not confuse Default with Burn In
A Default flag generally asks a player to prefer a soft subtitle track. It does not make the captions part of the image, and players do not always honor default-track flags consistently. For subtitles that must appear on every television, phone, browser, or player, use Burn In rather than relying on Default.
3. Check the Source, Output, and Playback Factors That Apply
If the settings appear correct, determine whether the issue follows the source track, output container, encoder configuration, or playback environment. Not every factor in a HandBrake troubleshooting checklist is equally relevant to this symptom, so test them in a controlled order.
3.1 Identify whether the source subtitles are text or bitmap based
Subtitle tracks are commonly stored as text instructions or as bitmap images. SRT and some SSA or ASS content are text based. DVD VobSub and Blu-ray PGS subtitles are image based. HandBrake's available pass-through and burn-in behavior depends on the subtitle type and the selected output container.
A subtitle type that cannot be stored as a soft track in the chosen container may need to be burned in. Conversely, a compatible subtitle can be passed through successfully while remaining invisible until the player enables it. This is why seeing a subtitle row in HandBrake does not prove that it will be permanently rendered.
For an external subtitle file, confirm that you imported the intended file, selected the correct character encoding when applicable, and matched it to the correct video. A mismatched subtitle file may have timing so different that no captions appear in your test section.
3.2 Verify the actual output file and destination
Check the destination path and filename before encoding. Afterward, open that exact file rather than an older copy with the same name in a media library, downloads folder, or recently played list. Compare its modification time and duration with the job you just completed.
This simple check is especially important when multiple test encodes are being saved to different folders. If the freshly encoded file keeps its burned captions with player subtitles disabled, the HandBrake work is complete.
3.3 Inspect the player's subtitle menu
Open the player's subtitle or track menu. If the output contains a named subtitle track that can be toggled, you are looking at a soft subtitle. Enable it to confirm that the expected source track was included, then return to HandBrake and mark that track for burn-in if permanence is required.
Test the output in a second reputable player if the first player reports no tracks or displays them incorrectly. Player differences matter for soft subtitles, styling, and default flags. They should not affect correctly burned-in text because burned captions are ordinary pixels in the video.
3.4 Treat audio settings as unrelated unless the wrong source was selected
Audio track selection does not control subtitle burn-in. Changing codecs, channel layouts, or bitrates will not normally repair missing burned subtitles. Audio becomes relevant only when it reveals that you selected the wrong title, language edition, angle, or source file.
For example, if the audio and scene order differ from what you expected, return to source selection and identify the correct title before testing subtitles again.
3.5 Isolate hardware encoding and driver issues only after checking subtitles
Hardware video encoders normally receive frames after subtitle rendering has been prepared, so changing the encoder should not be the first fix. Still, a short software-encoder test can isolate an unusual pipeline, driver, or hardware compatibility problem.
Choose a standard software video encoder for one brief test while keeping the same subtitle row, Burn In setting, and range. If the software result contains permanent captions but an otherwise identical hardware encode does not, update the operating system and graphics driver through the hardware vendor's supported channels, then retest. If both results fail, return to the subtitle track, Forced Only setting, and source analysis rather than repeatedly changing drivers.

4. Use the Activity Log to Separate Guesswork From Evidence
HandBrake's Activity Log records what the application scanned, selected, and processed. It is more useful than changing presets randomly because it can reveal whether a subtitle track was detected and whether it participated in the encode.
4.1 Review the log immediately after the failed test
Open the Activity Log associated with the short encode. Search for terms such as subtitle, sub, burn, SRT, SSA, PGS, or VobSub. Exact wording varies with the source and application build, so focus on the meaning of the lines rather than expecting one specific message.
Look for evidence that:
- The source scan detected subtitle tracks
- The selected track number matches the intended language or type
- A subtitle track was included in the encode configuration
- The selected subtitle was marked for burn-in rather than only pass-through
- The job completed without a subtitle decoding or reading error
If the log shows no selected subtitle, return to the Subtitles tab and add one known track. If it shows a different track number, remove all rows and add only the correct one. If it indicates Forced Only behavior, clear that option for the full-dialogue test.
4.2 Compare one failed log with one successful test
After changing a single setting, run the same short range again and compare the relevant subtitle lines. A meaningful comparison is more reliable than interpreting an isolated technical message.
Once the log shows the intended track being burned and the output retains captions with player subtitles disabled, stop troubleshooting. Warnings unrelated to subtitles do not need to be solved merely because they appear in the log.
5. Run a Clean Temporary Encode With Minimal Settings
If the existing queue item or custom preset has accumulated several subtitle selections, create a clean temporary job. The goal is not to find the best quality settings. It is to prove that one known subtitle track can be rendered correctly.
5.1 Build the controlled test
- Reopen the source and select the correct title or file
- Choose a short range containing known subtitle dialogue
- Select a standard built-in preset suitable for your device
- Open the Subtitles tab and remove every automatically added track
- Add one known full-dialogue subtitle track
- Enable Burn In for that track
- Disable Forced Only
- Save to a new filename in an easy-to-find local folder
- Encode and open the exact new file
- Disable subtitles in the player and check whether the text remains
If this clean encode works, the source subtitle is usable and HandBrake can burn it. Compare the clean job with your original configuration, especially automatic subtitle selection rules, extra tracks, Forced Only, container choice, and custom preset behavior.
If the clean encode still fails, try a different known subtitle track from the same source. This separates a damaged, empty, mislabeled, or incompatible track from a broader processing problem. Do not test five tracks simultaneously because that makes the result difficult to interpret.
6. Quick Fix Checklist
- Test a short section where captions definitely appear
- Add one known subtitle track in the Subtitles tab
- Select Burn In on that exact track
- Turn off Forced Only for normal full-dialogue subtitles
- Do not rely on Default to make subtitles permanent
- Open the newly created destination file, not an older copy
- Disable player subtitles to verify that the text is part of the picture
- Check the Activity Log for the selected track and burn behavior
- Try a clean built-in preset before modifying unrelated settings
- Use a software encoder test only if simpler subtitle checks fail
The decisive success test is simple: burned-in captions remain visible when the player's subtitle menu is set to off. Once that condition is met, there is no reason to keep changing encoders, containers, drivers, or subtitle flags.
7. Frequently Asked Questions
7.1 Why did HandBrake include subtitles that are not visible?
HandBrake may have included them as a soft subtitle track. Open the player's subtitle menu and enable the track. If it appears, return to HandBrake and select Burn In when you need the captions permanently embedded in the picture.
7.2 Can I burn in more than one subtitle track?
Only one subtitle track can normally be rendered into the video image during a HandBrake encode. You can choose one track for burn-in and, where the container and formats allow it, include other tracks as selectable soft subtitles. For a bilingual permanent display, you generally need a single prepared subtitle track containing both languages.
7.3 Why does Forced Only produce no subtitles?
The selected track may contain no events flagged as forced. Forced Only filters the track to those events rather than making all captions mandatory. Disable Forced Only and repeat the same short test. If normal captions appear, the source track was valid but did not contain the forced flags you expected.
7.4 Why do subtitles appear in one player but not another?
That usually indicates soft subtitles. Players differ in container support, subtitle rendering, default-track handling, and menu behavior. Burned-in subtitles should appear in every player because they are part of the video frames. Confirm by switching subtitle playback off.
7.5 Will changing the MP4 or MKV container fix burn-in?
Container choice strongly affects which subtitle formats can be stored as selectable tracks, but a correctly burned subtitle becomes part of the video and no longer depends on subtitle-track support. Changing containers may help a soft-subtitle compatibility problem, but it is not a substitute for selecting Burn In.
7.6 What if HandBrake detects no subtitle track?
Confirm that the selected source title actually contains subtitles. For an external text subtitle, import the correct file and verify its timing against the video. For disc-derived sources, work only with media you are legally entitled to process. If HandBrake's scan and Activity Log show no subtitle data, there is no detected track available to burn until the source or external subtitle is corrected.