Hardcode subtitles when they must stay visible as part of the picture in every compatible playback situation. In HandBrake, choose the intended subtitle track, enable Burn In, preview it, then encode and check the exported file.
Burning is different from adding a selectable subtitle track: a burned subtitle cannot be switched off, while a soft track can be toggled in a compatible player. Before you begin, confirm which outcome your viewers need and whether HandBrake can use the subtitle source you have.
Hard-Burned or Selectable: Choose the Right Result
A hard-burned subtitle is drawn over the video image during encoding. The text becomes part of the picture; it is not an independent track that a viewer can hide. That makes it useful when you need captions to appear consistently in a player or workflow that may not expose subtitle controls. It also means a typo, bad line break or wrong language is baked into the result and requires a new encode to correct.
A selectable, or soft, subtitle remains a separate track in the file. Viewers may be able to turn it on or off, and a file can carry more than one such track depending on the format and playback support. This gives viewers more control, but you must check that the destination container and player recognise the track. A subtitle file sitting beside a video is not automatically embedded or displayed everywhere.
| Consideration | Hard-burned subtitles | Selectable subtitle track |
|---|---|---|
| Viewer control | Always visible; cannot be toggled off | Can be enabled or disabled where supported |
| Appearance | Part of the video image | Player renders the separate track |
| Portability | Travels with the picture | Depends on container and player support |
| Corrections | Usually means editing and encoding again | May be possible to replace or choose another track |
| Track choice | HandBrake burns one track per encode | Number and type depend on container and source |
Choose burned captions when visibility is the priority and you have checked the text carefully. For example, a short public information clip shared in players with inconsistent subtitle controls may be easier to follow with captions in the image. For a lecture where viewers may want a different language, or prefer no text over the picture, a selectable track is usually the more flexible choice.
Burning subtitles does not automatically make a video accessible. Readability, accurate wording, timing, language choice and the needs of your audience still matter. If viewers need control, a burned version alone is not a substitute for a selectable track.
Check Your Subtitle Source Before Opening HandBrake
First determine where the subtitles are. They may be embedded in the original video as one or more tracks, or supplied separately as a file such as SRT. If embedded, identify the language and track you intend to use. Names and ordering are not always obvious, so check the source in a player that lets you inspect or switch subtitle tracks before encoding.
HandBrake documents support for common subtitle sources, including user-supplied SRT, embedded text subtitles such as SRT or ASS, closed captions, and bitmap subtitles from DVD or Blu-ray sources. This is not a promise that every subtitle format, file or disc source will work. If a track does not appear in HandBrake, confirm its format and whether it needs to be imported separately rather than assuming the software has found it.
For an external subtitle file, keep the video and subtitle file accessible and note the exact language version. Similar filenames can make it easy to import the wrong translation or a subtitle intended for a different edit. If you are preparing a long loop for a YouTube channel, a clean source file is worth checking before you build the stream around it; the guide to adding hymn lyrics to a recorded church stream also illustrates why text and picture need to be planned together.
Timing is a separate question from format. An SRT may load successfully but appear ahead of or behind speech because it was made for another cut, frame rate or opening sequence. Check an early line, a section around the middle and a later line against speech or on-screen action. HandBrake allows an SRT offset adjustment in milliseconds; use a measured adjustment only after confirming the direction and approximate difference.
Character encoding matters too. Incorrect encoding can lead to missing subtitle tracks or playback problems, and accented or non-Latin text may display incorrectly. Inspect the subtitle file in a text editor that can identify or set encoding, and use a short test encode to check the actual characters. Do not rely solely on the track appearing in the selection list.
Add or Select the Track in HandBrake
Open the video in HandBrake and wait for the source scan to finish. Select the Subtitles tab. Depending on your source, use the control to add an external subtitle file or select an existing track from the source. Verify the language and track identity before changing settings. If the source has multiple tracks, selecting the first listed one by habit can put the wrong language permanently into the picture.
For an imported SRT, inspect any available encoding and offset settings. If the words are consistently early or late, adjust the offset in the appropriate direction, then preview the affected lines. Avoid trying to fix a timing problem by changing the video’s frame rate or other unrelated encode settings; first establish whether the subtitle file matches this specific edit.
HandBrake’s documentation describes burning one subtitle track into an encoded file. If you need captions in two languages, make separate encodes or retain separate selectable tracks where the chosen container and player support them. A single burned image cannot offer a viewer a choice between two subtitle languages.
For a command-line workflow, HandBrakeCLI provides burn-related options, including --subtitle-burned for a selected track and --srt-burn for an imported SRT. Track indexes depend on the source and supplied tracks, so do not paste a guessed index into a command. Check the current HandBrakeCLI command-line reference, inspect the tracks available to your input and test a short section before encoding the full video.
Enable Burn In and Check the Format
In the Subtitles tab, select the intended subtitle and enable its Burn In option. Confirm that it is applied to the track you actually want, not simply that a subtitle is present in the queue. Then review the output container and delivery requirements before encoding.
Containers differ in what they can carry as selectable tracks and what HandBrake can pass through. HandBrake documents that MP4 can burn one subtitle but does not pass through PGS subtitles. MKV can pass through multiple PGS tracks and burn one. In the cited HandBrake documentation, WebM supports hard subtitles but not soft subtitles. These are format and workflow constraints, not a guarantee that every player handles every file identically. Consult the current HandBrake subtitle guide and container support notes for the source and output you are using.
If your goal is an MP4 with a PGS track, for instance, do not expect that track simply to pass through as a selectable subtitle. Burning the chosen track may be possible, but first confirm that the source is recognised and the preview displays it correctly. If the goal is to preserve several selectable PGS tracks, MKV may suit the file better, subject to the destination player accepting it.
The delivery platform matters as much as the file extension. A hard-burned caption is part of the encoded picture, whereas a soft track relies on support along the playback route. For a recorded programme intended for an always-on YouTube channel, settle the caption version and review the source file before preparing a long-running broadcast. The practical guide to running a recorded forest-sounds stream from a laptop in India is a reminder that source preparation is one part of a larger continuous-stream workflow.
Preview Placement and Timing
Use HandBrake’s preview to inspect representative moments before committing to the full encode. Look at a frame with a short line, one with a longer line, a scene with important detail near the bottom edge, and any section where the subtitle changes quickly. The preview can reveal whether the text is inside the frame, whether line breaks are awkward and whether a face, sign or other essential detail is covered.
Check legibility against both bright and dark scenes. A subtitle that reads over a dim background may disappear over a pale wall or sky. If the source subtitle styling is preserved, judge the actual rendering rather than assuming its original appearance will survive unchanged. HandBrake documents that ASS/SSA styling can be preserved when burned; passed-through text in MP4 may retain fewer styling attributes. The result can therefore look different across burn-in and soft-track approaches.
Watch for subtitle timing against speech and meaningful on-screen events. A line that starts before a speaker begins or lingers after the next shot can distract even if the file is technically synchronised at another point. If using SRT, correct an offset only after comparing several places; timing drift that grows across the video is different from one fixed offset and may point to a mismatched subtitle version.
Preview is a check, not proof of the final file. A short representative encode lets you test the rendered output and the chosen player without waiting for the complete video. Keep the test long enough to include the kinds of scenes and subtitle changes that exposed problems in the preview.
Encode and Review the Exported Video
When the track, burn-in setting, container and preview all look right, start the encode and save to a clearly named output file. Keep the original video and subtitle source unchanged until you have reviewed the result. This makes it easier to correct an encoding mistake without searching for the source again.
After encoding, open the exported file in the player or playback environment you expect to use. Check the opening, a section around the middle and the ending; for a long programme, sample additional scene changes and any point where the subtitle file changes language or style. Confirm that the words are present, correctly spelt, timed sensibly and not clipped by the frame. Also check that the video itself still plays as expected.
If the captions are burned in, try to remember that there is no subtitle control to turn them off: the text belongs to the image. That makes review especially important before a file is reused in a continuous playlist. A wrong title card, spelling error or late line may repeat for hours once the same file becomes the source for a channel. For other continuous-stream preparation decisions, see the software guide for a continuous YouTube stream on a low-cost PC.
If the output is wrong, identify whether the fault is in the subtitle source, track selection, encoding, timing or container before changing settings. A missing character points towards encoding or a source-file problem; the wrong language points towards track selection; consistent early or late text may call for an SRT offset adjustment. Re-encode a brief section after a targeted change, then review the full exported file when ready.
When a Soft Subtitle Track Is Better
Use a soft track when viewers should be able to switch captions off, select among languages or use player controls that suit their needs. This is also a better fit when you expect the wording to change and want to avoid making a new picture encode for each correction. Preserve the original subtitle file and keep language labels clear so you can tell tracks apart later.
The trade-off is compatibility. A separate track may be ignored by a container, playback app or destination platform, and styling can vary. Confirm the specific file and player combination rather than assuming that an embedded track will be shown. HandBrake’s documented container notes are a useful starting point, but the behaviour of the final destination still needs a real playback check.
You can also keep two deliverables where the audience and workflow justify it: one with subtitles burned in for predictable visibility, another with a selectable track for viewer choice. They are different files with different consequences, not a single version that can provide both behaviours. Label them plainly and test each one before publishing.
For a 24/7 YouTube channel, captions should be considered alongside the source, playlist and broadcast plan rather than as an afterthought. A correctly encoded video can still be the wrong asset if it contains the wrong language or cannot be changed when the programme changes. When the file is ready, a cloud-run broadcast can remove the separate burden of keeping your own computer on overnight; StreamNeo is built for that specific operational pain, but it does not choose or correct subtitles for you.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can I turn off subtitles after burning them into a video?
No. Burn-in writes the subtitles into the picture, so a viewer cannot toggle them off as a separate track. If viewer control matters, use a selectable subtitle track in a compatible container and player.
Can HandBrake burn every subtitle format?
No. HandBrake supports common sources, but format and container support differ, and not every track can be passed through or burned in the same way. Check the current HandBrake documentation and test your particular source before encoding the full video.
Why are my SRT subtitles out of sync?
The file may have been made for a different cut or timing, or it may need a measured offset adjustment. Compare several points in the video: a consistent shift may be corrected with HandBrake’s millisecond offset, while timing that drifts over time may indicate a mismatched source.
Should I choose MP4 or MKV?
Choose based on the subtitle type and the destination player, not just the extension. HandBrake documents different pass-through support for MP4 and MKV, particularly for PGS tracks; consult its current container guidance and play a test export in the intended environment.