DiskScout
Media Server · 6 min read

Best Storage Setup for a Plex or Jellyfin Server

Capacity math for real media libraries, where SSDs actually help, and how to build cheap without gambling your library.

Updated July 2026

1. Size the Library First

Media libraries have predictable appetites. Remuxed Blu-rays run 20–40GB per movie and 4K remuxes 50–80GB; quality 1080p encodes land around 8–15GB, and TV runs 1–3GB per episode at good 1080p quality. Translate your habits: a 500-movie 1080p library with a dozen TV series fits comfortably in 8–10TB; a 4K remux collector crosses 30TB shockingly fast. Then apply the two growth rules — libraries only grow, and usable space is less than raw space once redundancy and file-system overhead take their share. Sizing for 2–3× your current library is the difference between a build that lasts years and one you rebuild next spring.

2. HDDs Hold the Library; SSDs Have Two Small Jobs

Streaming video is a sequential-read workload at 5–100 Mbps per stream — a single hard drive sustains well over 1,000 Mbps sequentially, so even several simultaneous streams barely wake it up. Big cheap HDDs are unambiguously the right home for the media files. SSDs earn their keep in two specific roles: the OS/application drive, and Plex's metadata + transcode directory — library browsing snappiness lives there, since metadata access is random I/O where HDDs feel slow. A modest 250–500GB SSD covers both jobs. Spending SSD money per-TB on media files themselves buys nothing you can perceive during playback.

Media files → cheapest CMR HDDs per TB
OS + Plex metadata → small SSD
Movies on NVMe → wasted money

3. How Much Protection Does a Media Library Need?

Be honest about replaceability. If your library can be re-acquired with effort, full backups may be overkill — but a drive failure still means days of re-downloading and re-organizing, which is why parity redundancy hits the sweet spot for media: one or two parity drives protect the collection without doubling costs. This is also where media servers differ from general NAS advice: SnapRAID and unRAID-style setups are beloved for media precisely because they allow mixed drive sizes, grow one drive at a time, and spin down idle disks — and a parity failure loses only the files on the dead drive, not the whole pool. Whatever you choose, the metadata SSD and any irreplaceable personal media still deserve real backups.

4. Buying the Drives: Where the Money Goes

Media storage is the most price-per-TB-driven purchase in this hobby, and the market rewards patience. The recurring winners: high-capacity externals to shuck during sales (see our shucking guide), recertified enterprise drives for parity-protected pools, and whichever large CMR capacity currently sits at the per-TB floor — historically the 12–16TB band, but it moves, which is what our live tracker is for. Avoid SMR for anything in a parity pool. Buy the fewest, largest drives that fit your budget: fewer spindles means lower power draw, fewer failure points, and free bays for the growth that is definitely coming.

5. Three Reference Builds

Starter (≤10TB library): two large CMR drives mirrored, or one data + one SnapRAID parity, plus a 500GB SSD for OS and metadata — simple, quiet, expandable. Enthusiast (10–40TB): four to six bays, RAIDZ2 or dual-parity SnapRAID across 12–16TB drives bought at per-TB lows, SSD for metadata, and a cold spare on the shelf. Hoarder (40TB+): 8+ bays or a disk shelf, drives sourced almost entirely from shucking and recertified channels, dual parity minimum, and scheduled scrubs — at this scale a drive is always near failure somewhere, and the build must treat that as routine maintenance rather than crisis.

Quick Decision Guide

Library size Drives Protection SSD role
Under 10TB 2 large CMR Mirror or 1 parity 500GB OS + metadata
10–40TB 4–6 × 12–16TB RAIDZ2 / dual parity 500GB OS + metadata
40TB+ 8+ mixed/shucked Dual parity + scrubs 1TB metadata + transcode

Frequently Asked Questions

Do I need an SSD for 4K streaming?
No — 4K remuxes stream at up to ~100 Mbps, a trivial sequential load for any hard drive. If 4K playback stutters, the bottleneck is transcoding CPU/GPU or the network, never the disk.
How many streams can one hard drive serve?
Sequential throughput supports 10+ simultaneous 1080p streams in theory; in practice a handful of mixed streams with seeking is completely comfortable. Multiple drives in a pool spread the load further.
Should the transcode directory be on SSD or RAM?
If you have RAM to spare, a tmpfs/RAM transcode directory is free and eliminates SSD wear from transcoding. Otherwise the metadata SSD handles it fine — transcode writes are modest against modern TBW ratings.
Is a NAS appliance or a DIY server better for Plex?
Appliances (Synology/QNAP) win on simplicity; DIY wins on transcoding power and cost per bay — an inexpensive Intel CPU with Quick Sync handles many transcodes that entry NAS appliances cannot. Storage advice in this guide applies identically to both.

Ready to find the best deal?

Compare prices across Amazon regions — sorted by price per TB.

Find the cheapest large drives per TB

Related Guides