Before you rip Blu-ray with subtitles, write down the tracks you need and verify a short output sample. A file that plays its first scene can still be missing a second language or the subtitles for a later foreign-language exchange. Keep your readable source until those checks pass.
Use this workflow with self-authored or authorized media that your tools can already read. For software selection, start with the Blu-ray ripper comparison; this guide focuses on preserving and checking tracks.
1. Make a track inventory before choosing a preset
Create one row for each track you might need. Do not discard a track simply because another one has the same language label: listen to or view a representative section before deciding its purpose.
| Record | What to check | Your intended result |
|---|---|---|
| Audio track number and language | Spoken language, track title, commentary or audio description | Keep, omit, or retain until identified |
| Audio codec and channel layout | Source values and proposed output settings | Preserve the source encoding, or create a separately identified compatibility track |
| Subtitle track and language | Dialogue, foreign-language passages, or accessibility information | Selectable full subtitles, scene-only subtitles, or a fixed burned-in version |
| Default and forced flags, when available | Metadata reported by the tool, separately from what the track actually contains | Expected initial selection in the player |
| Scene timestamps | One dialogue scene and a known subtitle event | Repeatable points for checking the output |
SDH and closed captions can include sound cues as well as speech; keep that accessibility requirement in your checklist. A language tag alone is not enough to distinguish the version you need. Jellyfin explains subtitle types.
2. Choose a container and an audio plan
MKV can hold multiple audio and subtitle streams. That makes it a useful starting point when track choice matters, but the container does not select the right tracks for you. MakeMKV describes these container capabilities.
For each selected audio track, decide whether the goal is to retain its encoding or produce another version for a specific device. Record both outputs separately if you need both. Do not interpret a matching language label as proof that the channel layout or encoding stayed unchanged.
HandBrake presets store selection rules, not a fixed source-track list; missing language labels and a passthrough fallback can change the result. Inspect the populated audio and subtitle lists for every title. Audio and subtitle defaults.
3. Decide whether subtitles must remain selectable
In HandBrake, MKV can pass through multiple PGS tracks; MP4 cannot pass through PGS. Burning one subtitle track makes it permanent in the picture. HandBrake subtitle documentation.
| Your requirement | Decision before processing |
|---|---|
| Switch subtitle languages or turn them off | Keep selectable tracks in an output your player supports; test each required language |
| Always show one chosen subtitle version | Consider a burned-in playback copy after checking the exact track and scenes; retain a source without the burn-in |
| Deliver an MP4 file | Resolve the subtitle workflow before encoding; changing the filename does not solve track compatibility |
| Keep options open for future devices | Retain the readable source and a record of the selected tracks, even after a playback copy passes |
The linked HandBrake pages are marked as drafts in its documentation navigation. Match their guidance to your installed version and inspect its actual output. For the broader container decision, see the MP4 compatibility workflow.
4. Check forced subtitles at a known scene
Treat these as three separate questions: does the needed text exist, did the output keep it, and will the player select it? A forced flag does not answer all three. Identify a scene where you expect translated dialogue or on-screen text, then record exactly what should appear.
HandBrake’s foreign-audio scan is an aid, not a guarantee; its documentation says manual track selection may be necessary. Do not assume an empty scan result means no subtitles are needed. Avoid applying a forced-only filter to your only retained full-subtitle version without checking what it removes.
In Plex, language metadata and subtitle mode affect automatic selection; an unknown language does not match a preferred language. Check those settings as well as the embedded forced flag. Plex subtitle configuration.
5. Verify the output, then the actual client
First process a short section containing your recorded events. If one section cannot include them all, use several samples. In a media-information viewer, compare the output with your inventory:
- Are all intended audio and subtitle tracks present? Compare purposes, not just total counts.
- Are languages, codec names and audio channel layouts what you selected?
- Are track names and default/forced flags present where expected?
- Does the output contain selectable subtitles when that was your requirement?
Next open the sample in the exact app and device you plan to use. Switch through the retained audio tracks, enable each required subtitle, and revisit the known scene. Check both initial automatic selection and manual selection; reopen the file to see whether the starting behavior matches your plan.
For Plex or Jellyfin, also inspect the server’s playback status with subtitles off and on. Jellyfin documents that subtitles can cause remuxing or video transcoding, depending on compatibility. A successful desktop preview does not establish another client’s behavior. Jellyfin compatibility guidance.
If the check fails
| Observation | Next step |
|---|---|
| Required track is absent from the file | Revisit source selection and output settings: missing subtitles or audio |
| Track exists but the wrong one starts | Check its language and flags, the player’s preferences, and whether manual selection works |
| Subtitle appears but playback starts transcoding | Compare playback with that subtitle disabled: unexpected Plex/Jellyfin transcode |
| Expected text never appears in the sample | Confirm the scene and source track before spending time on a full encode |
Only start the full job after the samples meet your checklist, then recheck those events in the final file. This is a documented verification method. We have not tested physical discs, commercial software retention, subtitle rendering, or your playback hardware for this guide; our existing synthetic metadata checks cannot establish those outcomes.