BLU-RAY PGS SUBTITLES
Keep Blu-ray PGS subtitles in MKV, burn one into MP4, or OCR them to text.
PGS subtitles are image-based, so the right path depends on the destination. MKV can retain multiple selectable PGS tracks when the player supports them. HandBrake cannot pass PGS through to MP4; one subtitle track can instead be burned into the video. If you need editable, searchable, or broadly reusable text, OCR the images to SRT and manually correct names, punctuation, timing, and forced-only choices before relying on the file.
This guide begins with a Blu-ray, BDMV folder, MKV, or standalone .sup subtitle file that your tools can already read lawfully. It does not explain decryption, keys, firmware changes, or any method for bypassing protected-disc access controls.
PGS stores subtitle pictures rather than ordinary text. Keeping PGS preserves the original rendered captions, while converting to SRT requires optical character recognition and creates text that must be reviewed.
The container changes the decision. HandBrake documents PGS passthrough for MKV, but not for MP4. In MP4 output, PGS must be burned into the video; HandBrake can burn only one subtitle track into a file.
Forced flags and automatic selection are useful routing signals, not a substitute for inspection. Preview representative dialogue, forced signs or foreign-language lines, subtitle timing, and playback on the actual target device before processing a library.
GOOD FIT
This page is for you if...
- Users with a lawfully readable Blu-ray, BDMV folder, MKV, or standalone .sup file who need to preserve or convert PGS subtitles.
- Media-library owners choosing between selectable MKV subtitles and a device-compatible MP4.
- People who need OCR-produced SRT for editing, searching, accessibility workflows, or players that do not render PGS.
- Users deciding how to handle full subtitle tracks and forced-only lines.
CHOOSE ANOTHER PATH
It is not the right starting point if...
- A physical disc whose subtitles do not appear during direct playback; that is a playback-control troubleshooting problem, not this file-workflow guide.
- Instructions for decrypting a protected disc, using keys, modifying drive firmware, or bypassing access controls.
- A promise that automatic OCR is accurate enough to publish without human review.
- Assuming a subtitle marked forced will be selected and rendered correctly by every application and device.
BEFORE CHOOSING SOFTWARE
Confirm the prerequisites first.
A software match is useful only when the source, hardware, operating system, and destination also match.
- 01
A lawfully readable source
Start from a Blu-ray, BDMV folder, MKV, or standalone .sup file your selected tool can already open. HandBrake states that it does not defeat copy protection.
- 02
A destination container
Choose MKV when selectable PGS tracks matter, or MP4 when device compatibility matters enough to accept burning one subtitle track or using text subtitles.
- 03
Language and track inventory
Identify full, forced, commentary, hearing-impaired, and duplicate tracks by language and content instead of trusting track numbers alone.
- 04
A target-player check
Confirm that the actual TV, phone, browser, media server, or editing app can render the selected subtitle format and honor the intended default or forced behavior.
DECISION TABLE
Match the tool to the job.
Start with the row that describes the desired result, then complete the verification step before paying.
| Your priority | Start with | Why | Verify before choosing |
|---|---|---|---|
| Preserve multiple selectable Blu-ray subtitle tracks | MKV with PGS passthrough | HandBrake documents PGS passthrough in MKV, allowing the original image subtitles to remain separate from the video. | All intended languages are present, track names and flags are correct, and the target player renders PGS without transcoding or omission. |
| Create an MP4 with guaranteed visible subtitles | Burn one selected PGS track into the video | HandBrake does not support PGS passthrough in MP4, while burned subtitles become part of the encoded picture. | The correct full or forced track is selected, cropping does not cut captions, preview lines are readable, and permanent subtitles are acceptable. |
| Need editable or searchable subtitles | In Subtitle Edit, import the image-based subtitle for OCR | Use File → Import → Image-based subtitle for OCR with a Blu-ray .sup file or Matroska PGS track, then save reviewed text as SRT. Recognition still requires dictionary or manual fixes; it is not guaranteed transcription. | Names, punctuation, italics, line breaks, hearing-impaired cues, timing, overlapping entries, and encoding on representative scenes. |
| Keep only forced dialogue or signs | Inspect the forced flag and preview the actual events | Selection rules can scan or prefer forced tracks, but metadata and authoring choices vary across sources and players. | Foreign-language dialogue, signs, track-level versus event-level forced behavior, default settings, and the output on the destination device. |
| Preserve an archive and make a convenient playback copy | Keep a source-oriented MKV, then create a separate MP4 | One file does not have to satisfy both preservation and broad-device playback. The archive can retain PGS tracks while the derivative uses burned or reviewed text subtitles. | Storage, track inventory, filenames, language tags, and a reproducible record of which track was burned or OCR-converted. |
CATALOG MATCHES
No product ranking without PGS-level evidence
This page intentionally leaves the catalog list empty. A generic ripping label does not prove PGS passthrough, OCR, forced-track handling, or burn-in behavior for the exact edition.
Evidence boundary: Use the documented HandBrake and Subtitle Edit paths above, or verify equivalent PGS behavior on a vendor's current first-party page before treating any product as a match.
Use the decision checks above and verify candidates against official vendor documentation.
FINAL CHECK
Before you download or pay.
Use this short list to catch edition, platform, and marketing-label mismatches.
- The source is already lawfully readable by the selected tool.
- I identified full, forced, commentary, and accessibility tracks instead of selecting by language alone.
- For MKV, the target player can render selectable PGS tracks.
- For MP4, I accept that PGS passthrough is unavailable and only one subtitle track can be burned.
- For SRT, I budgeted time to proofread OCR text and inspect timing.
- I previewed representative dialogue, forced lines, signs, punctuation, and caption placement on the target device.
- I kept the preservation file separate when a compatibility-oriented derivative would discard subtitle information.
FAQ
Questions to settle before choosing.
What are PGS subtitles on a Blu-ray?
PGS subtitles are image-based captions used in Blu-ray workflows. They preserve the authored appearance but are not ordinary editable text, so searching or producing SRT requires OCR and review.
Can MKV keep multiple PGS subtitle tracks?
Yes. HandBrake documents PGS passthrough for MKV. Keep the needed languages and full or forced variants, label them clearly, and test that the destination player actually renders and selects them as intended.
Can HandBrake pass PGS subtitles through to MP4?
No. HandBrake's current subtitle documentation lists PGS passthrough for MKV but requires PGS to be burned for MP4. Because only one subtitle track can be burned into a file, choose and preview that track carefully.
How do I convert PGS subtitles to SRT?
In Subtitle Edit, use File → Import → Image-based subtitle for OCR with a Blu-ray .sup file or a Matroska PGS track. Run recognition for the correct language, save to SRT, then manually review names, punctuation, styles, line breaks, timing, and any text the OCR could not confidently recognize.
Does a forced flag guarantee the right subtitle appears?
No. HandBrake can use language, default, and forced selection rules, but source flags and player behavior vary. Preview forced dialogue and signs in the output and test the exact target player.
Does this guide fix subtitles missing during physical Blu-ray playback?
No. This page is about PGS tracks in an already readable Blu-ray, BDMV, or MKV file workflow. Missing subtitles while directly controlling physical-disc playback are a separate player, menu, track-selection, or compatibility problem.
REFERENCESEvidence and official sources5 guide references
Guide-level technical claims use the first-party references below. Product matches use catalog evidence from official product pages. These are editorial source checks, not hands-on performance testing. A checked date is a snapshot, not a promise that the source has not changed.
Guide references
- HandBrake: Subtitles ↗HandBrake documents PGS as a bitmap subtitle, PGS passthrough for MKV, required burn-in for MP4, and the limit of one burned subtitle track per output file.Checked Oct 16, 2026
- HandBrake: Audio and subtitle defaults ↗HandBrake documents language selection, first or all matching tracks, foreign-audio search, burn behavior, and default-track options used to route full and forced subtitles.Checked Oct 16, 2026
- HandBrake: About HandBrake ↗HandBrake describes its supported output containers and states that it does not defeat or circumvent copy protection, establishing the readable-source boundary for this guide.Checked Oct 16, 2026
- Subtitle Edit: OCR documentation ↗Subtitle Edit's official repository documents OCR workflows for image-based subtitles, including recognition engines, dictionaries, manual correction, and review of unrecognized text.Checked Oct 16, 2026
- Subtitle Edit: FAQ ↗Subtitle Edit's official FAQ documents subtitle conversion and correction considerations that support proofreading rather than treating OCR output as automatically accurate.Checked Oct 16, 2026