Does Jellyfin need the same formats as Plex?

Yes — the same universal recipe applies: MP4, H.264, AAC audio, SRT subtitles. Jellyfin transcodes with the same triggers (unsupported codec, PGS subs, HDR tone-mapping). Jellyfin has no paid hardware-transcoding tier advantage to lean on, so direct-play-friendly files matter even more.

Do subtitles force Plex to transcode?

Text subtitles (SRT) almost never do — they direct-play or direct-stream. Image subtitles (PGS from Blu-rays, VOBSUB from DVDs) force video transcoding on most clients because the server must burn them in. Converting PGS to SRT (via OCR) is the highest-value single fix for subtitle buffering.

Should I keep MKV or convert to MP4 for Plex?

Keep MKV masters (all tracks, chapters, quality), and generate MP4 H.264 + AAC + SRT versions for anything that buffers. Remuxing H.264 MKVs to MP4 takes seconds with zero quality loss — only re-encode files whose codec or audio actually triggers transcoding.

How do I batch convert my whole Plex library?

Convert overnight in bulk: point a batch tool at the library, output MP4 with H.264 video, AAC audio, and SRT subtitles, and keep originals until you've spot-checked playback. Tools built for this (Tdarr, Unmanic, FileFlows) automate it server-side; a desktop batch converter like Formatif Pro does it with per-file status and no container setup.

← Back to Complete Guide

Best Video Format for Plex & Jellyfin (Stop the Buffering)

Q: What is the best video format for Plex?

MP4 with H.264 video, AAC audio, and SRT subtitles. This combination direct-plays on virtually every Plex client — smart TVs, sticks, consoles, phones — with no server transcoding. MKV works too on modern clients, but exotic audio (TrueHD, DTS-HD) and image subtitles (PGS) force transcoding.

Q: Why does Plex keep buffering on some files?

Because the server is transcoding: the client can't play the file as-is, so Plex converts it live. Common triggers are H.265 on old clients, TrueHD/DTS audio, PGS subtitles, and 4K HDR tone-mapping on weak servers. Pre-transcoding those files to MP4 H.264 + AAC + SRT eliminates the buffering.

Q: Can Plex play 4K HDR without transcoding?

Only if client, file, and display all agree: an HDR-capable client and TV playing H.265 HDR10 will direct-play. The moment tone-mapping kicks in (HDR→SDR for an SDR screen), even strong servers sweat — software tone-mapping a 4K stream can saturate a CPU. Keep a 1080p SDR copy alongside 4K HDR for remote and mobile viewing.

One movie plays instantly, the next buffers every ten seconds — same server, same TV. The difference is never luck. It's whether your file direct-plays or forces a transcode. Here's the universal recipe, the per-client traps, and how to fix a whole library overnight.

By Hadi Karaki, maker of FormatifSeptember 4, 202611 min read

The only concept that matters: direct play vs transcode

Direct play = the server sends the file as-is; even a Raspberry Pi can serve 4K this way. Transcode= the server re-encodes live because the client can't handle something in the file; a single 4K transcode can saturate a desktop CPU. Buffering is almost always a transcode your server can't sustain — not a network problem. Every recommendation below exists to keep you in direct play.

The universal recipe (memorize this)

MP4 · H.264 video · AAC audio · SRT subtitles

This combination direct-plays on virtually every Plex and Jellyfin client ever made. Deviate from any of the four only for a reason — and know the cost below.

The three traps that force transcoding

Trap 1: image subtitles (PGS / VOBSUB)

Text subtitles (SRT) direct-play or direct-stream almost everywhere. Image subtitles — PGS from Blu-rays, VOBSUB from DVDs — are pictures, so most clients can't overlay them; the server burns them into the video, forcing a full video transcode. Converting PGS→SRT with OCR is the single highest-value buffering fix in most libraries.

Trap 2: premium audio (TrueHD, DTS-HD MA)

Beautiful on a home theater, poison for sticks and phones. Most clients can't decode TrueHD/DTS-HD, triggering at least an audio transcode (cheap) — but combined with subtitles it often cascades into video transcoding (expensive). Keep the HD track for the theater and an AAC stereo track for everything else; MKV holds both happily.

Trap 3: 4K HDR tone-mapping

H.265 HDR10 direct-plays on HDR clients — until someone watches on an SDR screen and the server must tone-map HDR→SDR live. Software tone-mapping a 4K stream is brutally CPU-heavy. Rule: keep a 1080p SDR copy next to every 4K HDR file for remote, mobile, and bedroom-TV viewing.

Per-client cheat sheet

Client	Plays natively	Watch out for
Fire Stick / Chromecast	H.264 MP4/MKV, AAC	H.265 on old sticks; PGS subs; TrueHD
Apple TV / iPhone / iPad	H.264/H.265 MP4, AAC (Infuse plays everything)	MKV in native apps; use Infuse for exotic files
Smart TVs (Tizen/webOS)	H.264 MP4; H.265 on 4K sets	Codec roulette by model year; ASS/PGS subs
PS5 / Xbox	H.264 MP4, AAC	Limited subtitle support; no TrueHD/DTS-HD
NVIDIA Shield	Nearly everything incl. TrueHD/DTS-HD	Almost nothing — the reference client
Web browser	H.264 + AAC only, effectively	H.265, MKV quirks, all HD audio

Jellyfin clients behave the same way — the recipe and traps are identical; only the server software differs.

Fix it once, overnight

Pre-transcode the library instead of firefighting files.

The workflow: keep MKV masters with every track, and generate direct-play MP4s (H.264 + AAC + SRT) for anything that buffers. H.264 MKVs remux in seconds with zero loss; only true problem files need re-encoding. Server-side automators (Tdarr, Unmanic, FileFlows) do this hands-free — or point Formatif Pro ($8.95 one-time) at the library for a desktop batch with per-file status, no container setup, and no uploads.

Batch whole libraries, subfolders included

Remux where possible, re-encode where needed

Keep masters; generate direct-play copies

One-time purchase of $8.95 — no subscription

Plex & Jellyfin questions, answered

What is the best video format for Plex?

MP4 with H.264 video, AAC audio, and SRT subtitles — direct-plays on virtually every client with no transcoding.

Why does Plex keep buffering?

The server is transcoding something the client can't play — usually H.265 on old clients, TrueHD/DTS audio, PGS subtitles, or 4K HDR tone-mapping. Pre-transcode to the universal recipe.

Does Jellyfin need different formats?

No — same recipe, same traps. Direct-play-friendly files matter even more on Jellyfin.

Do subtitles force transcoding?

SRT almost never; PGS/VOBSUB usually do (burn-in). OCR image subs to SRT for the biggest single buffering fix.

Can Plex play 4K HDR without transcoding?

Yes if client, file, and display all agree. Keep a 1080p SDR copy for remote/mobile/SDR screens — tone-mapping 4K live melts CPUs.

Keep MKV or convert to MP4?

Keep MKV masters; generate MP4 direct-play copies for problem files. Remux H.264 MKVs in seconds, zero loss.

How do I convert the whole library?

Overnight batch: MP4 + H.264 + AAC + SRT, keep originals until spot-checked. Tdarr/Unmanic server-side, or a desktop batch tool with per-file status.

Keep learning

MKV vs MP4 explained

Containers, remuxing, and why your library is MKV in the first place.

Convert MKV to MP4

5 tested methods with exact commands — remux in seconds, zero loss.

H.264 vs H.265

The codecs behind direct play — why H.264 still rules the living room.

A library that never buffers.

Formatif Pro ($8.95 one-time) and Formatif AI ($12.95 one-time) handle video, image, and audio conversion offline — with batch workflows, no file size limits, and a 3-day free trial.

Download free trial Read: MKV vs MP4 guide

Server-side automators work too — this page exists so you pick the workflow that fits, with direct-play files either way.

Written by

Hadi KarakiLinkedIn

Founder of Formatif, a local-first offline media processing suite for Windows and Linux. Hadi writes about video, image, and audio formats, compression, and privacy-first desktop workflows.