Building or upgrading a Plex or Jellyfin server? The two things that decide the hardware are how many streams need transcoding at once and how much upload speed your remote viewers use. Enter your expected streams and file bitrates to see what CPU or iGPU class you need, how much upload bandwidth to plan for, and how much storage your library takes.
Bitrates vary a lot by source: a 4K disc remux is often 50 to 80 Mbps, a 4K web file far less. Check a few of your own files (Plex and Jellyfin both show the bitrate in the media info) and use those figures. The transcoded bitrate is the remote quality setting you choose in the app.
| Simultaneous streams | At home | Remote |
|---|---|---|
| 4K HDR, transcodede.g. to a 1080p phone or TV that cannot play the file | ||
| 4K SDR, transcoded | ||
| 1080p, transcodedto a lower bitrate | ||
| 4K, direct playdevice plays the original file | ||
| 1080p, direct play |
A typical movie is about 2 hours; a TV season of 10 one-hour episodes is about 8 to 10 hours without ads.
- CPU / iGPU needed–
- Total streams–
- CPU-only PassMark estimate–
- Suggested internet upload–
- Local network traffic from the server–
- Storage, 4K–
- Storage, 1080p–
How this is calculated
- CPU-only transcoding uses Plex’s published PassMark guidance per transcode: about 17,000 for a 4K HDR (50 Mbps, 10-bit HEVC) file, 12,000 for 4K SDR, and 2,000 for a 1080p (10 Mbps H.264) file, each converted to 1080p. The calculator adds these up for streams running at once. Plex notes that real requirements vary a lot between files, and burned-in subtitles or audio conversion add load.
- Hardware transcoding moves the video work to the iGPU, so the CPU score matters much less. Neither Plex nor Jellyfin publishes a per-chip stream count, so the calculator recommends a chip class rather than a number of streams. Plex’s hardware transcoding needs a Plex Pass; Jellyfin’s is free. Jellyfin does not recommend AMD integrated graphics for transcoding.
- Upload = remote transcoded streams × the transcoded bitrate + remote direct-play streams × the file bitrate. The suggested upload follows Jellyfin’s guidance of at least 20 Mbps for remote access and keeping server use to about 70% of your upload.
- Storage per hour = bitrate in Mbps × 3,600 seconds ÷ 8 ÷ 1,000, which is about 0.45 GB per hour for every 1 Mbps.
Sources
Checked November 20, 2026: Plex, What kind of CPU do I need for my server?, Using hardware-accelerated streaming and HDR to SDR tone mapping; Jellyfin, Hardware selection.
Tips
- Direct play wherever you can. A device that plays the original file puts almost no load on the server. Most transcoding happens because of unsupported codecs, image-based subtitles or a remote quality limit.
- 4K remote streaming is mostly an upload problem. Direct-playing a 4K remux outside the home needs far more upload than most cable plans provide, so remote viewers usually get a transcoded stream.
- Keep the transcode folder on an SSD. Jellyfin suggests sizing it at roughly your largest file times the number of streams running at once.
Related: Best mini PC for Plex and Jellyfin transcoding · Best N150 and N100 mini PCs for a home server · NAS RAID capacity calculator · Best NAS hard drives