Transcoding occurs when your Plex server converts a video file in realtime so a client device can play it. This conversion happens whenever the client cannot decode the video codec such as HEVC on older devices, when the client internet bandwidth is too low for the original file bitrate, when the audio codec is not supported by the client, or when image-based subtitles need to be burned into the video stream.
During transcoding, the server decodes the original file completely and then re-encodes it in a format and bitrate the client can handle. For a 4K HEVC file, this means decoding roughly 50 to 80 Mbps of video and re-encoding it as H.264 at perhaps 8 to 20 Mbps. This process is computationally intensive and is the primary reason Plex servers struggle under load.
HEVC is designed to compress video efficiently, but that compression efficiency comes at a cost: it is extremely expensive to decode and re-encode in software. A single 4K HEVC transcode on CPU alone requires a processor with a PassMark score of roughly 17,000 or higher to maintain realtime playback speed. Most NAS devices score between 2,000 and 4,000 on the same benchmark, meaning they can barely handle even a single 1080p transcode let alone 4K content.
A typical four-core desktop processor scores between 7,000 and 10,000, which means one 4K transcode maxes it out completely and leaves no headroom for other tasks or additional streams.
By contrast, a dedicated GPU with hardware encoding handles that same 4K transcode using a tiny fraction of its processing capacity. A single modern GPU can perform twenty or more simultaneous 4K transcodes while the rest of the chip sits idle and the CPU does nothing encoding-related.
There are three distinct playback modes that determine how much work your server performs.
| Mode | What happens | Server CPU load |
|---|---|---|
| Direct Play | File sent as-is with no conversion at all | Approximately zero percent |
| Direct Stream | Container format changed but video and audio untouched | Approximately one percent |
| Transcode | Video decoded and re-encoded completely | 80 to 100 percent per stream |
Direct play is always the goal because it requires no server processing beyond reading the file from disk and sending it over the network. The file arrives at the client exactly as it was stored. Direct stream occurs when the video and audio codecs are compatible but the container format is not, such as an MKV file playing on an Apple TV that only accepts MP4. Plex rewraps the streams without re-encoding, which is nearly as lightweight as direct play.
A full transcode is where the problems start. The server must decode every frame of video, optionally apply tone mapping for HDR content, and encode it into a different codec, resolution, or bitrate. This is where CPU usage spikes and buffering begins if the hardware cannot keep up with realtime speed.
Understanding why Plex transcodes helps you reduce or eliminate unnecessary transcoding.
Hardware transcoding using a GPU dedicated video encoder is the standard solution to the transcoding performance problem. Plex supports Intel Quick Sync, NVIDIA NVENC, and AMD VCE for GPU-accelerated encoding. With hardware transcoding enabled, the GPU handles the decode and encode pipeline while the CPU stays nearly idle.
The practical challenge is that most Plex servers lack a capable GPU because they run on a NAS, a Raspberry Pi, or a compact headless system where adding dedicated graphics hardware is not possible or practical. Even when a GPU is available locally, Plex Pass is required to access hardware transcoding. Without the subscription, Plex uses CPU-only transcoding regardless of what GPU hardware is installed.
Even without a GPU, you can minimize transcoding through several strategies. Pre-convert your library to H.264 with AAC audio in MP4 or MKV containers, which direct plays on virtually every Plex client. Use text-based SRT subtitles instead of image-based formats. Add secondary audio tracks in compatible formats like AAC stereo alongside surround tracks so clients with limited audio support can direct play the fallback track.
Set remote streaming quality to Original or Maximum in every Plex client app. The default quality cap is the most common cause of unnecessary remote transcoding. When bandwidth allows, streaming the original file is always preferable to forcing the server to re-encode it.
Monitor which clients and files trigger the most transcodes using the Plex dashboard or Tautulli. Target the most frequent offenders with format conversions or client setting changes. Every transcode you eliminate frees server resources and improves the experience for all users.
N100 mini PCs, NAS boxes, or GPU offloading — which fits your library?
GPU support, codec handling, and the real differences for 4K streaming.
Technical deep-dive: cartridge, HTTP pipes, and GPU workers — no SSH needed.
Join the pre-beta waitlist and lock in 50% off for life.
Claim My Early-Adopter Spot →