You added a subtitle track in HandBrake, the job finished without an error, and the finished file has no subtitles in it. Nothing failed loudly, so there is nothing to search for — which is why this one wastes so much time.
The good news is that HandBrake's subtitle documentation names one cause outright, and spells out the consequence in the same sentence. It is a dropdown most people never touch.
What "subtitles not showing" actually means
Before you change anything, work out which of two different problems you have. HandBrake describes two ways of putting subtitles into an output file:
"Hard Burn: This means the subtitles are written on top of the image permanently. They cannot be turned on or off like on the DVD."
"Soft Subtitles: This means the subtitles will appear as separate selectable tracks in your output file. With the correct playback software, you'll be able to enable / disable these subtitles as required."
Those two fail in completely different ways.
- Burned subtitles are pixels. If they are missing, they were never drawn — the problem happened at encode time, in HandBrake.
- Soft subtitles are a track. They can be perfectly present in the file and still not appear, because a soft track is something your player has to select. HandBrake's own wording is conditional: with the correct playback software.
So the first diagnostic is a question, not a setting: did you pick Burn In, or leave the track soft? If it was soft, check your player's subtitle menu before blaming the encode — if the track is listed there, HandBrake did its job. Everything below assumes the track genuinely is not in the output.
The fastest fix: the Char Code dropdown
If you imported an SRT file on the Subtitles tab, this is the first thing to check, because HandBrake's documentation writes the cause and effect out in one line:
"You should make sure the correct character code is selected from the "Char Code" dropdown. Selecting the wrong code, will result in your output file having no subtitle track, and can cause the player to crash when playing that track."
That is the exact symptom that brought you here: a mismatched character code produces an output file with no subtitle track at all.
The second half of the sentence matters just as much: it can also crash the player on that track. If your experience is "the video plays until the subtitles are due, then the player dies," you are looking at the same dropdown, not at a corrupt video.
The fix is to reopen the Subtitles tab, select your imported SRT, and set Char Code to the encoding the file was actually saved in. For which codes that dropdown offers and how to identify your file's encoding, check the official documentation rather than guessing from a blog post.
If you would rather not gamble on a dropdown at all, burn the text into the frames instead.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
Because the output is burned in, there is no soft track for a player to ignore, and no dropdown standing between your file and the finished frames.
Other documented causes
You exported to WebM
Symptom: every setting looks right, but a soft subtitle track never appears in the output.
HandBrake's subtitle documentation states it flatly:
"Soft subtitles are currently unsupported in the WebM container."
The container page agrees from the other direction: WebM "can include "hard" burned in subtitles" and soft subtitles are "currently unsupported." HandBrake marks that container page as a draft, but the subtitles page carries the identical restriction.
Fix: either burn the subtitles in, or output MP4 or MKV instead. HandBrake's documentation says MP4 "can also include "soft" text subtitles that can be turned on or off," and MKV can carry soft subtitles as either text or bitmap images.
You tried to burn more than one track
Symptom: you selected two subtitle tracks, and one of them is simply absent.
HandBrake documents a hard ceiling of one burned track. For Blu-ray PGS subtitles it says "With MP4, you can burn ONLY 1 subtitle track into the video," and for MKV, "you can only burn 1 subtitle track into the file. The rest must be passed through." The DVD VOBSUB section states the same one-track burn limit for both containers.
Fix: burn one and pass the others through as soft tracks — which needs a container that supports them, so not WebM.
You passed PGS through into MP4
Symptom: a Blu-ray subtitle track disappears from an MP4 output specifically.
The documentation is explicit: "You can not pass-through PGS into MP4 as this file format does not support it." MKV can pass through multiple PGS tracks; MP4 cannot take any.
Fix: output MKV to keep the track selectable, or burn the one track you need into an MP4.
Foreign Audio Search did not find the track
Symptom: you enabled Foreign Audio Search for a partially subtitled source, and the output has nothing.
HandBrake scans "for subtitles that appear only 10% (or less) of the time in addition to scanning for the presence of any forced subtitles." The documentation then covers the case where that scan does not produce the track: "If you do not get a foreign section only subtitle track in your output file, then you may have to manually find and select the correct subtitle track from the "Track" dropdown menu."
Fix: stop relying on the search and choose the track by hand.
Your subtitle file is a .vtt
Symptom: the import does not behave like the walkthrough you followed.
HandBrake's list of subtitle sources it can read covers DVD VOBSUB and CC tracks, Blu-ray PGS, "User supplied SRT files," and SSA/SRT/CC embedded in files such as MKV or MP4. WebVTT is not on that list, and the documentation does not address .vtt import in either direction.
Fix: feed it the format that is documented. Converting first with VTT to SRT removes the ambiguity — see SRT vs VTT for what that conversion actually changes.
The file came out as .m4v
Symptom: the encode succeeded but you cannot find the .mp4, or something downstream refuses the file.
Using SRT subtitles is one of three documented triggers for this. HandBrake automatically switches the extension to M4V "when you pass-through audio (AC3), use SRT subtitles or have chapter markers enabled." The documentation is emphatic that nothing else changed: "They are the exact same file, the only difference is the extension."
Fix: nothing, usually — rename it back if a tool insists on .mp4. HandBrake also notes that QuickTime 7 and QuickTime 7-based applications cannot play an MP4 with those features enabled unless it carries the .m4v extension, a limitation that does not apply to QuickTime X or iOS.
How to tell it worked
Play the output and check the subtitle menu, not just the picture. Burned subtitles "cannot be turned on or off"; a soft encode should give you a separate selectable track you can enable and disable. Test on a single chapter rather than the whole film — HandBrake recommends short test encodes when dialling in subtitle offsets, and the same habit saves an hour of character-code guesswork.
Before you go looking on HandBrake's troubleshooting page, note what is actually on it: launching the interface on Linux, the Gatekeeper prompt on Mac, the .NET Desktop Runtime on Windows, and deleting your configuration data and presets. For anything outside that, check the official documentation.
FAQ
Why does HandBrake say the subtitles were added but the video has none? One documented cause is the Char Code setting on an imported SRT. HandBrake states that selecting the wrong code "will result in your output file having no subtitle track."
Why did my player crash when I turned subtitles on? The same setting. HandBrake's documentation notes that a wrong character code "can cause the player to crash when playing that track," so treat a crash on the subtitle track as the same problem rather than a broken video file.
Can HandBrake burn two subtitle tracks into one video? No. The documentation states you can burn only one subtitle track, for both MP4 and MKV output. Additional tracks have to be passed through as soft subtitles.
Why do my subtitles disappear when I output WebM? Because soft subtitles are "currently unsupported in the WebM container." Burn them in, or use MP4 or MKV if you need a track viewers can switch off. Our browser-based subtitle burner handles the burn-in case without a reinstall.
Does HandBrake accept .vtt subtitle files? HandBrake's documented list of readable subtitle sources includes user-supplied SRT files and does not mention WebVTT, and the docs do not say either way whether .vtt works. Convert to SRT first if you want a documented path.
My subtitles show up but the karaoke effects are gone. Is that a bug? No. For SSA subtitles, HandBrake says animated effects such as fade in/out and karaoke "are not currently supported. (Only the middle frame of the animation will be used.)" Burned SSA keeps fonts and colours; passed-through SSA text keeps only bold, italic and underline.
Behaviour cited from HandBrake's official documentation on subtitles and containers, checked 20 September 2026. More encoding fixes are collected in the fix guides, and every browser-based tool we run is listed on the tools page.
