4K Transcoding on a Seedbox: GPU vs CPU

What Is Transcoding?

Transcoding is converting a video from one format to another in real-time. It happens when your Plex or Jellyfin client can't play the original file directly.

For example: you have a 4K HEVC file, but your Roku only supports 1080p H.264. The server transcodes it on the fly — decoding the HEVC stream and re-encoding it as H.264 at 1080p.

When Does Transcoding Happen?

• Different codec: Client doesn't support HEVC/H.265 (common on older devices)
• Resolution mismatch: 4K file, 1080p screen (or remote streaming quality set lower)
• Subtitle burn-in: Image-based subtitles (PGS, VOBSUB) require transcoding to overlay
• Bandwidth limit: Remote streaming quality set below the original bitrate

When Does It NOT Happen?

Direct Play means the client plays the file as-is. No server processing needed. This happens when:

• Client supports the codec (most modern devices handle H.264)
• Resolution matches or client handles downscaling itself
• Text-based subtitles (SRT, ASS) used instead of image-based
• No bandwidth restrictions set

If your clients can direct-play your files, you don't need GPU transcoding at all. A standard AppBox is perfectly fine.

CPU Transcoding

Every seedbox can transcode using the CPU. The question is how many simultaneous streams it can handle.

A single 1080p transcode needs roughly 2,000 PassMark CPU score. A 4K transcode needs 12,000-17,000 depending on the codec.

On a shared AppBox, you get 3-5 CPU transcodes depending on your plan. This is enough for most users — especially if some streams are direct-playing.

GPU (Hardware) Transcoding

GPU transcoding offloads the work to dedicated video encoding hardware. It's dramatically faster and handles more streams simultaneously.

Intel QuickSync (used in Bytesized GPU AppBoxes):

• No session limits (unlike NVIDIA which caps at 3-5)
• Handles 10+ simultaneous 1080p transcodes easily
• 4K HEVC → 1080p without breaking a sweat
• Lower power usage than CPU transcoding
• Supports HDR to SDR tone mapping

When you need GPU transcoding:

• Multiple users streaming simultaneously (family/friends)
• 4K library with viewers on slower connections
• Image-based subtitles (PGS) that require burn-in
• HDR content viewed on SDR displays

The Decision Framework

Plex vs Jellyfin for Transcoding

Plex requires Plex Pass (€5/month) to enable hardware transcoding. Without it, Plex falls back to CPU.

Jellyfin includes hardware transcoding for free. No paywall.

On a Bytesized GPU AppBox, both Plex and Jellyfin can use the GPU. If you're cost-conscious, Jellyfin gives you GPU transcoding without the Plex Pass surcharge.

Tips to Reduce Transcoding

1. Use direct-play clients: Apple TV 4K, NVIDIA Shield, and modern smart TVs direct-play almost everything
2. Use text subtitles: SRT/ASS subtitles don't trigger transcoding (PGS/VOBSUB do)
3. Set remote quality to Original/Maximum: In Plex client settings, set remote streaming to maximum quality
4. Optimize your library: Use Radarr/Sonarr quality profiles to download formats your clients support natively

Bytesized Plans

• AppBox — 3-5 CPU transcodes, 10 Gbit, from €11/month. Perfect for direct play and light transcoding.
• GPU AppBox — Dedicated GPU, 6+ hardware transcodes, smooth 4K. For power users and multi-viewer setups.

Bytesized has been offering GPU-accelerated seedbox hosting since the early days of 4K streaming. With 15+ years of media server hosting experience and a 4.8/5 Trustpilot rating, you're in good hands.

What's Next?

• Set up Plex on your seedbox
• Compare Plex vs Jellyfin
• Browse GPU AppBox plans