PGS vs SRT Subtitles: Why PGS Buffers and How to Convert
EqualangIn brief
Learn why Blu-ray PGS image subtitles force Plex and Jellyfin to transcode 4K video, how they differ from SRT text, and how to OCR PGS into UTF-8 SRT.
Keywords: pgs vs srt subtitles; pgs or srt subtitles; convert pgs to srt subtitles; pgs subtitles meaning; blu-ray pgs transcoding plex jellyfin
PGS (Presentation Graphic Stream, .sup) subtitles are pre-rendered transparent bitmap images ripped from Blu-ray discs, whereas SRT (SubRip, .srt) subtitles are plain UTF-8 text files containing timestamps and character strings. Because Smart TVs, web browsers, and streaming sticks rarely support rendering raw Blu-ray PGS bitmaps over video streams, selecting a PGS track forces media servers like Plex, Jellyfin, and Emby to decode your video, burn the subtitle images onto every frame, and re-encode on the fly. Switching to or converting PGS into a plain-text .srt file stops video transcoding immediately, restores Direct Play, and lets you resize or translate your subtitles freely.
What Are PGS Subtitles (and Why Do They Exist)?
When people search for PGS subtitles meaning, they are usually staring at a track labeled English (PGS) or HDMV PGS inside a Blu-ray Remux .mkv file.
On physical Blu-ray and 4K UHD Blu-ray discs, studios do not store subtitle dialogue as selectable text fonts. Instead, the authoring house renders every line of dialogue into a transparent bitmap graphic (S_HDMV/PGS in Matroska containers, or .sup when extracted to a standalone file)—just as DVD discs used VobSub (.idx/.sub) image tracks.
Storing subtitles as pictures guaranteed that every hardware Blu-ray player in 2006 displayed the exact font, drop shadow, and screen coordinates chosen by the studio without needing font files licensed or installed on the player. However, outside of dedicated Blu-ray players, bitmap subtitles create two major headaches:
- No text strings exist inside the file: A 25 MB
.supfile holds thousands of compressed pictures of words, not characters. A video player cannot change the font family, scale the text size cleanly without pixelation, or copy-paste a word. - Severe hardware compatibility limits: While desktop players like MPV, VLC, or Kodi can overlay PGS bitmaps locally, most Smart TV native apps, web browsers (which expect WebVTT via HTML5
<track>elements), Roku devices, and budget streaming sticks cannot decode PGS streams during Direct Play.
PGS vs SRT Subtitles at a Glance
If you are deciding between PGS or SRT subtitles for a home media library, here is how the two formats compare across storage, playback, and customization:
To see why media servers treat them so differently, compare what is actually stored inside each file.
An SRT file is human-readable plain text:
142 00:14:22,150 --> 00:14:25,400 The reactor coolant valve is locked.
A PGS track inside an .mkv container is a binary stream of Presentation Composition Segments (PCS), Window Definition Segments (WDS), Palette Definition Segments (PDS), and Object Definition Segments (ODS). If you inspect an .mkv file with mkvmerge -i, you can spot the difference by codec ID:
$ mkvmerge -i movie.mkv File 'movie.mkv': container: Matroska Track ID 0: video (V_MPEGH/ISO/HEVC) Track ID 1: audio (A_TRUEHD) Track ID 2: subtitles (S_HDMV/PGS) Track ID 3: subtitles (S_TEXT/UTF8)
Here, Track 2 (S_HDMV/PGS) is a Blu-ray bitmap stream, while Track 3 (S_TEXT/UTF8) is an embedded SRT text stream.
Why PGS Subtitles Force Plex and Jellyfin to Transcode and Buffer
A common frustration in home theater setups goes like this: a 60 Mbps 4K HDR Blu-ray Remux plays smoothly with zero CPU usage on your NAS—until you turn on the English (PGS) subtitle track on your living room TV. Suddenly playback stalls, buffers every five seconds, and your server CPU hits 100%.
Here is what happens behind the scenes, as documented in the official Jellyfin and Matroska specifications:
- Client capability check: When you start playback, the client app (your TV, Roku, or browser) tells the media server which video, audio, and subtitle codecs it can render natively.
- Bitmap burn-in fallback: If the client cannot render
S_HDMV/PGSbitmaps directly over the video plane, the media server must burn in (hardcode) the subtitles. To do that, the server decodes every single 4K video frame, composites the PGS bitmap image onto the raw video pixels, and re-encodes the entire video stream into H.264 in real time. - HDR tone-mapping overhead: If the source video is 4K HDR10 or Dolby Vision and the server has to transcode the video to burn in a PGS image, it often has to run HDR-to-SDR tone mapping at the same time. Without a dedicated hardware GPU transcoder, software 4K tone mapping + subtitle burn-in will overwhelm most NAS processors, resulting in constant buffering or washed-out colors.
- The audio cascade problem: If your audio track is also transcoding (for example, TrueHD 7.1 downmixing to stereo for a TV speaker), keeping video and burned-in PGS timestamps synchronized adds even more transcoding overhead.
When you switch the subtitle track from PGS to SRT, the server simply sends the 50 KB .srt text stream alongside the untouched 4K video stream. The TV renders the text locally using its own built-in font engine, and video transcoding drops to zero.
When Is PGS Still Useful?
Despite its streaming drawbacks, PGS is not a broken format—it simply serves a different purpose:
- Exact spatial placement for signs and forced subtitles: When an alien speaks in a sci-fi film or a foreign newspaper headline appears at the top-left corner of the frame, PGS places the translated graphic right underneath or over that exact screen region.
- Custom studio typography: Stylized callouts, vertical Japanese text, or custom franchise fonts are preserved pixel-for-pixel in PGS, whereas standard
.srtrelies on whatever sans-serif font your player uses. - Direct Play on high-end local clients: If you play files over SMB/NFS using an Nvidia Shield Pro (via Kodi or Plex with direct PGS rendering support), Apple TV 4K (via Infuse), or a desktop PC running MPV, the client device overlays PGS graphics natively without waking up your server's transcoder.
How to Convert PGS to SRT Subtitles (Step-by-Step OCR Workflow)
Because a PGS track contains images rather than text letters, you cannot convert .sup to .srt with a simple file-format wrapper or a basic ffmpeg -c:s srt copy command. To convert PGS to SRT subtitles, you must run OCR (Optical Character Recognition) to read the pixels in each bitmap and write out matching UTF-8 text characters.
The cleanest cross-platform tool for this is the free, open-source editor Subtitle Edit.
Step 1: Extract the .sup Track (Optional if Opening .mkv Directly)
Subtitle Edit can open .mkv files directly and read embedded PGS tracks. However, if you work on a headless Linux server or prefer extracting the raw .sup file first using MKVToolNix, inspect the track IDs and run mkvextract:
# 1. List all tracks and find the S_HDMV/PGS track ID mkvmerge -i movie.mkv # 2. Extract Track ID 2 to a standalone .sup file mkvextract tracks movie.mkv 2:english_pgs.sup
Step 2: Run OCR in Subtitle Edit
- Open Subtitle Edit and drag your
english_pgs.supfile (or the originalmovie.mkv) into the main window. - If you loaded an
.mkvwith multiple subtitle tracks, select thePGStrack you want to convert from the prompt. - The Import/OCR Blu-ray (.sup) subtitle file window will open automatically, displaying every timestamp alongside its raw bitmap image.
- Under OCR method, select either:
- Tesseract 5 (works across dozens of languages; select your matching dictionary under Language), or
- nOCR (fast vector-line matching built into Subtitle Edit, great for clean Latin-alphabet Blu-ray fonts).
- Ensure Fix common OCR errors and Prompt for unknown words are checked, then click Start OCR.
Step 3: Fix Common Blu-ray OCR Glitches
Even on crisp 1080p Blu-ray bitmaps, serif and italic fonts can trick OCR engines in a few predictable ways. Before saving, scan the review pane for:
- Lowercase
lvs. UppercaseI: Words likeI'llorIllyriaare frequently misread asl'llorIIIyria. Subtitle Edit's built-in dictionary check (Tools -> Fix common errors) catches most of these automatically. - Italic tags (
<i>...</i>): Blu-ray subtitles often italicize off-screen voices or radio transmissions. Verify that italicized lines close cleanly with</i>so raw tags do not show up on your TV. - Music notes (
♪): Song lyrics on Blu-ray discs often start and end with bitmap eighth-note symbols. Make sure your OCR engine maps them to standard UTF-8♪characters rather than random punctuation like#or~.
Step 4: Save as UTF-8 .srt for Plex or Jellyfin
- Click OK to send the recognized text lines to Subtitle Edit's main editor.
- At the top toolbar, confirm Format is set to
SubRip (.srt)and Encoding is set toUTF-8 with BOM(orUTF-8). - Go to
File -> Save as...and save the file in the exact same folder as your movie using your media server's language naming convention:
/Movies/Arrival (2016)/ ├── Arrival (2016).mkv └── Arrival (2016).en.srt
Refresh your metadata in Plex or Jellyfin, select the newly added English (SRT External) track, and your 4K stream will immediately switch from CPU-heavy transcoding to Direct Play.
Once you have converted a PGS bitmap track into a clean .srt text file, you can also follow our guides to translate MKV subtitles, translate an SRT subtitle file with Equalang, or combine two languages into a single track for Plex dual subtitles.
Frequently Asked Questions
Why can't I just rename .sup to .srt or run a fast FFmpeg stream copy?
Because a .sup file contains compressed bitmap pictures and zero text characters. Running ffmpeg -i movie.mkv -c:s srt out.srt fails with a codec mismatch error (Subtitle encoding currently only possible from text to text or bitmap to bitmap) because FFmpeg does not guess letters from pixel graphics without an OCR engine.
Are ASS/SSA subtitles text or images like PGS?
ASS/SSA (SubStation Alpha, .ass) subtitles are text-based, not bitmap images. However, .ass files include complex vector positioning, custom embedded fonts, and karaoke animations. Because many Smart TV players cannot render complex .ass styling natively, Plex and Jellyfin will sometimes still burn .ass subtitles into the video just like PGS unless you set your player's subtitle burn-in setting to Only image formats.
Should I delete the PGS track from my .mkv after creating an .srt?
You do not need to delete it. Leaving the original PGS track inside the .mkv takes only 20–40 MB and preserves the original Blu-ray typesetting for desktop players like MPV or Kodi. Just place your external movie.en.srt next to the .mkv (or mux it in as the default subtitle track with mkvmerge) so TV clients pick the .srt track first.