The Hardware a Plex Server Genuinely Needs
The spec floor per scenario, and why the iGPU decides it
As an Amazon Associate we earn from qualifying purchases. Prices and availability come from Amazon.com as of the last update and may change.
A Plex server's requirements scale with transcoding, not library size: for direct play almost any device works, for one or two 1080p transcodes you need an Intel chip with Quick Sync (or a Plex Pass plus a modern iGPU), for 4K HDR transcoding you need an 11th-gen or newer Intel iGPU (UHD 730/770), and for many users you add cores and RAM on top. The single spec that matters most is the iGPU generation, not the core count or the CPU brand. Below is the floor per scenario, and the four builds are the just-buy-this answer.
What actually matters (and what does not)
The instinct is to buy a fast CPU, but Plex barely uses CPU cores for transcoding when hardware acceleration is on. What matters is the integrated GPU and its generation, because Quick Sync does the transcode in fixed-function silicon. A humble Intel N100 with a modern iGPU out-transcodes a much larger AMD CPU that has no iGPU at all. So read the iGPU first, then cores, then RAM.
Everything else is secondary. Storage capacity determines how much you can hold, not how well it streams. RAM is light for Plex itself. Network rarely limits a single client. Get the transcoding tier right and the rest is easy to size, which is why this whole cluster leads with the iGPU decision.
Spec floor by scenario
| Scenario | What you need | |
|---|---|---|
| Direct play only | Any client that plays your files | Even an ARM NAS or a Raspberry Pi; no transcoding, so the iGPU is idle |
| 1-2 1080p transcodes | Intel Quick Sync + Plex Pass | An N100 or an Intel-Celeron NAS; 8-16 GB RAM |
| 4K HDR to 1080p transcode | 11th-gen+ Intel iGPU (UHD 730/770) | A 12th/13th-gen Core i5; 16-32 GB RAM |
| Many concurrent users | More cores + RAM + fast network | A Core i5/i7 or Xeon, 32 GB+, 2.5/10GbE; iGPU still transcodes |
The Plex Pass line
Hardware transcoding is a Plex Pass feature on every scenario above except pure direct play. Without a Plex Pass, Plex software-transcodes on the CPU, which raises the bar dramatically: a job an N100 iGPU shrugs off would tax a far bigger processor in software. So for any server that will transcode, budget a Plex Pass (subscription or lifetime) as a requirement, not an extra.
Direct play is the exception. If every client plays your files natively, no transcoding happens, the iGPU stays idle, and even a cheap ARM box streams 4K remux limited only by the network and drives. Many people over-buy hardware for transcoding they never actually trigger, so check whether your clients direct-play before sizing up.
The just-buy-this answer
If you would rather not spec it yourself, the four builds on this site map straight onto these scenarios: the Budget N100 for direct play and light 1080p transcoding, the Family N305 for three to five concurrent 1080p streams, the 4K Core i5 for 4K HDR transcoding, and the high-end tower for 4K remux at scale with many users. Each lists every part with a live price, so the requirement becomes a shopping list.
Whichever route you take, size the storage separately with the calculator and fit NAS-rated CMR drives by live price per terabyte. Compute for the transcoding you do, storage for the library you keep, and the two are independent.
Frequently asked questions
What are the minimum requirements for a Plex server?
For direct play, almost anything: even a low-power ARM box streams files a client can play natively. For transcoding you need an Intel CPU with Quick Sync and a Plex Pass, plus 8-16 GB of RAM. The requirement scales with transcoding, and the iGPU generation matters more than the CPU speed.
What CPU do I need for a Plex server?
An Intel CPU with a Quick Sync iGPU, chosen by generation for your target: an N100 for 1080p and light 4K, a 12th/13th-gen Core i5 (UHD 730/770) for 4K HDR tone-mapping. Core count matters only for serving many concurrent streams; the iGPU does the transcoding work.
How much RAM does a Plex server need?
Plex itself is light; 8 GB works and 16 GB is a comfortable baseline for most servers. Go to 32 GB or more only for a ZFS pool that wants a large ARC cache, for running containers and apps, or for RAM-disk transcoding. Buying extra RAM does not add transcode capacity.
Do I need Plex Pass to run a Plex server?
You can run Plex free for direct play and software transcoding. But hardware transcoding, the thing that makes an efficient server possible, requires a Plex Pass (subscription or lifetime). For any server that will transcode, treat Plex Pass as a requirement rather than an optional extra.
Does library size affect Plex server requirements?
Not really for streaming. Library size sets how much storage you need, not how well the server transcodes or direct-plays. A 100 TB library streams no differently from a 5 TB one; you just need the drives to hold it. Size storage with the calculator and the transcoding tier with the iGPU.
Can a Raspberry Pi run a Plex server?
Only for direct play or a very small library. A Raspberry Pi has no Quick Sync, so it cannot hardware-transcode and software-transcodes poorly. It works if all your clients play files natively, but for any real transcoding an Intel Quick Sync box is the right minimum.