You added a 4K HDR movie to your Plex library. It looks incredible on your OLED. Then someone tries to watch it on their phone over LTE, and your server’s CPU hits 100%. Welcome to transcoding.
What Is Transcoding?
Transcoding is when your Plex (or Jellyfin) server converts a video file on-the-fly so a client device can play it. This happens when:
- The client can’t decode the codec (HEVC/H.265 on older devices)
- The client’s internet bandwidth is too low for the original bitrate
- The audio codec isn’t supported (TrueHD, DTS-HD)
- Subtitles need to be burned in (PGS/ASS image-based subtitles)
The server decodes the original file, then re-encodes it in a format and bitrate the client can handle. For a 4K HEVC file, this means decoding ~50-80 Mbps of video and re-encoding it as H.264 at maybe 8-20 Mbps. That’s computationally brutal on a CPU.
Why 4K HEVC Is the Worst Case
HEVC (H.265) is designed to be efficient at compressing video — but that efficiency comes at a cost: it’s extremely expensive to decode and re-encode. A 4K HEVC transcode requires roughly:
- 17,000+ PassMark score for a single 4K transcode on CPU
- Most NAS devices: 2,000-4,000 PassMark — they can barely handle 1080p
- A 4-core i5: maybe 7,000-10,000 PassMark — one 4K transcode maxes it out
Meanwhile, an NVIDIA GPU with NVENC can handle that same 4K transcode using less than 5% of its power while the rest of the chip sits idle. A single RTX 4090 can do 20+ simultaneous 4K transcodes.
Direct Play vs Direct Stream vs Transcode
There are actually three playback modes:
| Mode | What Happens | CPU Load |
|---|---|---|
| Direct Play | File sent as-is. No conversion. | ~0% |
| Direct Stream | Container changed, video untouched. | ~1% |
| Transcode | Video decoded + re-encoded. | 80-100% |
Direct Play is always the goal. But you can’t control what devices your family and friends use, and you can’t control their bandwidth. Transcoding is inevitable for any Plex server shared with more than one or two people.
The GPU Solution
Hardware transcoding — using a GPU’s dedicated video encoder — is the standard solution. Plex supports Intel Quick Sync (QSV), NVIDIA NVENC, and AMD VCE. The problem: most Plex servers don’t have a capable GPU, or they’re running on a NAS or a headless box in a closet where adding a GPU isn’t practical.
That’s the gap PlexBeam fills. Instead of upgrading your hardware, you offload the transcode to a remote GPU worker. Your NAS stays cool, your CPU stays idle, and 4K transcodes finish at 11× realtime (267 FPS) instead of stuttering at 0.3×.
What About Plex Pass Hardware Transcoding?
Plex Pass unlocks hardware transcoding — but only for GPUs installed on the same machine as your Plex server. If your server is a Raspberry Pi, a Synology NAS, or a low-power mini PC, there’s no GPU slot, or the built-in Quick Sync is too weak for 4K.
PlexBeam works with Plex Pass. It’s not a replacement — it’s what you use when your local hardware transcoding isn’t enough.