Running Plex Media Server on a NAS puts very different demands on the hardware than file storage or backups. The CPU has to do the heavy lifting when a client cannot play a file natively, decoding and re-encoding video in real time at whatever quality the client requests. Get the CPU wrong and streams buffer, stutter, or simply fail to start under load.
The single biggest factor in 2026 is whether a NAS CPU includes Intel Quick Sync — Intel's dedicated hardware video encoding block. A NAS with Quick Sync and an active Plex Pass license can transcode 10 or more 1080p streams simultaneously on a chip that would buckle under even two streams in software mode. If you plan to run more than one or two concurrent streams, Quick Sync is the feature to prioritize.
Top Picks at a Glance
| Pick | CPU | HW Transcoding | Max Simultaneous 4K | RAM (base) | Price |
|---|---|---|---|---|---|
| Synology DS923+ | AMD Ryzen R1600 dual-core | No Intel QSV | 1–2 (SW only) | 4 GB | ~$600 |
| QNAP TS-464 | Intel Celeron N5105 | Yes (Intel Quick Sync) | 3–4 with Plex Pass | 8 GB | ~$500 |
| Synology DS1522+ | AMD Ryzen R1600 dual-core | No Intel QSV | 1–2 (SW only) | 8 GB | ~$700 |
| TerraMaster F4-424 | Intel N95 | Yes (Intel Quick Sync) | 3–4 with Plex Pass | 8 GB | ~$450 |
| QNAP TS-264 | Intel Celeron N5105 | Yes (Intel Quick Sync) | 3–4 with Plex Pass | 8 GB | ~$350 |
Our Picks in Detail
- AMD Ryzen R1600 dual-core with strong software transcoding performance and a large app ecosystem for
- Intel Celeron N5105 with Intel Quick Sync hardware transcoding support — handles multiple simultaneo
- AMD Ryzen R1600 in a five-bay enclosure for large media libraries requiring both transcoding headroo
- Intel N95 with hardware transcoding at a strong value price point — an excellent option for budget-c
- Intel Celeron N5105 in a compact two-bay package with hardware transcoding — the most affordable pat
Prices shown are for the diskless enclosure. Add NAS-rated drives (typically $60–$120 each) to your budget.
Hardware Transcoding vs Software Transcoding: Why It Matters for Plex
Software transcoding uses the NAS's main CPU cores to decode and re-encode video. It is flexible and supports virtually every codec, but it is extremely CPU-intensive. A dual-core AMD Ryzen R1600 in the Synology DS923+ scores around 3,500 PassMark — enough for perhaps two simultaneous 1080p software transcode streams before the CPU hits its limits. 4K software transcoding on the same chip is marginal at best.
Hardware transcoding offloads video encode and decode work to Intel's Quick Sync Video engine, a dedicated silicon block on Intel's integrated graphics. Quick Sync can handle H.264 and H.265 (HEVC) encode and decode simultaneously, and the CPU load for each stream drops dramatically. A QNAP TS-264 with an N5105 can handle 10 or more concurrent 1080p H.264 transcode sessions with Quick Sync active.
The catch: hardware transcoding requires an active Plex Pass subscription. Without Plex Pass, Plex Media Server ignores the Quick Sync hardware entirely and falls back to software transcoding. If you choose a NAS specifically for its Quick Sync support, budget the Plex Pass annual fee (roughly $40–$50/year) into your total cost of ownership. Jellyfin — the free, open-source Plex alternative — includes hardware transcoding support at no cost.
How Many Simultaneous Streams Can Your NAS Handle?
The answer depends heavily on whether you are using software or hardware transcoding, and what resolution and codec your content is encoded in.
For software transcoding, a rough rule is 2,000 PassMark score per simultaneous 1080p stream. The AMD Ryzen R1600 in the DS923+ scores around 3,500 total, giving you roughly one comfortable 1080p software transcode stream, maybe two if conditions are favorable. 4K software transcoding demands 12,000+ PassMark per stream — effectively impossible on NAS-class hardware.
For hardware transcoding with Intel Quick Sync, the constraint shifts from CPU cores to the Quick Sync engine's concurrent session limits. Modern Intel Celeron and Pentium Quick Sync implementations handle 10+ simultaneous 1080p H.264 transcode sessions, and 4–6 simultaneous 4K HEVC sessions, with the CPU barely breaking a sweat. Network bandwidth and drive throughput become the real limits long before the Quick Sync engine is saturated.
Direct play — where the client plays the file natively without any transcoding — has essentially zero NAS CPU cost. Optimizing your library and client setup for direct play is always the most efficient path.
Direct Play vs Transcoding: Optimize Your Library to Reduce NAS Load
Every stream that direct plays instead of transcoding is free in terms of NAS CPU load. The NAS just reads the file from disk and pushes bytes to the client — no encoding, no decoding, no Quick Sync required. This is why the Plex client device matters as much as the NAS hardware.
Modern smart TVs, Apple TV 4K, NVIDIA Shield, and Roku Ultra all support H.264 and H.265 direct play at 1080p and 4K, including common audio formats like AAC and AC3 (Dolby Digital). If your library is encoded in H.264 with AAC audio, and your clients support it, the NAS CPU load for playback is negligible regardless of how many streams are running.
Problems arise when clients encounter subtitles in image-based formats (PGS, VOBSUB), audio in DTS-HD or Atmos formats the client cannot pass through, or video encoded in HEVC with HDR tone mapping required. Each of these triggers a transcode. Keeping your library in broadly compatible formats — H.264 video, AAC or AC3 audio, SRT subtitles — eliminates most transcoding on supported clients.
Storage Planning for Plex: How Much Drive Space Do You Need?
Library size is the other major planning question. Content encoded for home libraries varies enormously in file size depending on resolution, codec, and bitrate.
As rough estimates: 4K HDR Blu-ray remuxes run 50–80 GB per movie. 4K encodes at moderate bitrates run 20–40 GB. 1080p Blu-ray remuxes are 15–25 GB each. 1080p encodes at 8–15 GB each are common. 1080p at more aggressive compression can get down to 4–6 GB per movie. TV episodes at 1080p typically run 1–4 GB per episode.
A library of 200 movies at mixed quality might run anywhere from 1 TB to 15 TB depending on your quality preferences. Plan for growth — a 4-bay NAS lets you start with two drives and add more as your library expands. With a two-bay NAS in RAID 1, your usable capacity is capped at the size of a single drive, so a 2 x 8 TB configuration gives 8 TB usable.
NAS-rated drives (WD Red, Seagate IronWolf) are optimized for always-on operation and perform better in multi-drive NAS environments than desktop drives. They are worth the modest price premium for a Plex server that runs continuously.
Network Speed Requirements for Plex on a NAS
Plex streams over your local network (or the internet for remote access) at bitrates that depend on the resolution and quality setting. For local playback, a gigabit wired connection is more than sufficient — even 4K Blu-ray remuxes at 80 Mbps are well within gigabit's 940 Mbps practical bandwidth. Wi-Fi adds potential for interference and latency, but modern Wi-Fi 6 connections typically handle even high-bitrate 4K content without issues.
For remote access over the internet, the bottleneck is your upload speed. A 4K direct play stream at 40–80 Mbps requires that much upload bandwidth at the NAS end, plus the download bandwidth on the remote client's connection. In practice, Plex usually transcodes remote streams to a lower bitrate to fit available bandwidth — a 25 Mbps upload connection will handle a few simultaneous remote 1080p streams comfortably. For a rough guide: allow 25 Mbps of upload for each 4K remote stream, 8 Mbps per 1080p remote stream, and 4 Mbps per 720p remote stream.
Local 2.5G Ethernet is not necessary for Plex playback but does help with library management, large file copies to the NAS, and metadata downloads. If your NAS and switch support 2.5G, it is a worthwhile upgrade for overall responsiveness.
Frequently Asked Questions
Does Plex hardware transcoding require a Plex Pass?
Yes. Hardware transcoding (Intel Quick Sync, NVENC, etc.) is a Plex Pass feature. Without an active Plex Pass subscription, the Plex Media Server will fall back to software transcoding regardless of the NAS hardware.
Can a 2-bay NAS run Plex?
Yes. A 2-bay NAS like the QNAP TS-264 runs Plex well, especially if your clients support direct play. With hardware transcoding enabled, a 2-bay NAS with an Intel Quick Sync CPU can handle multiple simultaneous 1080p streams without issue.
What is the minimum CPU for smooth Plex transcoding?
For software transcoding of 1080p content, you need roughly 2,000 PassMark score per simultaneous stream. For 4K software transcoding, that rises to 12,000+ PassMark per stream — beyond most NAS CPUs. Intel Quick Sync hardware transcoding changes this entirely: even modest Intel Celeron CPUs handle 10+ simultaneous 1080p streams with hardware transcoding active.
Should I use Plex or Jellyfin on my NAS?
Jellyfin is free and open-source — hardware transcoding, mobile apps, and all features are included at no cost. Plex has a more polished mobile experience, better remote access setup, and a larger community. If you want the easiest setup and best apps and don't mind the Plex Pass subscription, choose Plex. If you want zero recurring costs and are comfortable with a slightly rougher setup, Jellyfin is excellent.