Home server for Plex and Jellyfin: hardware transcoding, storage and the apps around it

A good home server for Plex in 2026 is a small Intel machine with Quick Sync, an SSD for the system and apps, and large hard drives for media. Quick Sync, the video engine built into Intel CPUs, lets one low-power box transcode several streams at once, which is the job that decides whether a media server feels smooth. An Intel N100/N150 mini PC or a used ThinkCentre Tiny is enough for most households, whether you run Plex or Jellyfin. Around it, a handful of open-source apps (Sonarr, Radarr, Prowlarr and Seerr) organise the library and handle requests from the rest of the family.

Plex or Jellyfin first

The hardware is the same for both, but the costs are not. On Plex, hardware transcoding and remote streaming require a Plex Pass ($6.99 a month, $69.99 a year or $749.99 lifetime for new buyers, as of October 2026). Jellyfin is free and open source (GPL-2.0) and includes hardware transcoding and remote access at no cost. Our Jellyfin vs Plex comparison covers the trade-offs in depth; the rest of this guide applies to either.

Why hardware transcoding decides your CPU

Transcoding converts a video on the fly when a device cannot play the original file, or when the connection is too slow for the original bitrate. Doing it in software takes most of a CPU's power for a single 4K stream. Doing it with a dedicated video engine costs a few watts.

Hardware	Jellyfin	Plex	Notes
Intel Quick Sync (iGPU)	Free	Plex Pass	Best choice for most servers; low power
NVIDIA NVENC (discrete GPU)	Free	Plex Pass	Strong, but adds a card and its idle power
AMD (VA-API on Linux)	Free	Plex Pass	Works, generally less mature than Intel for this job
Apple VideoToolbox	Free	Plex Pass	Only on macOS hosts
Raspberry Pi 5	Deprecated	Not available	No hardware encoder on the Pi 5

Which Intel generation? Newer is better, because each generation adds codecs. The N100 and N150 use the same graphics generation as 12th-gen Core chips, which decode HEVC 10-bit and AV1 in hardware and handle HDR-to-SDR tone mapping on the GPU in Jellyfin. Older 8th to 10th-generation chips in used office PCs still handle H.264 and HEVC well, but they lack AV1 decoding. Jellyfin's documentation notes that older Jasper Lake and Elkhart Lake Celerons have no AV1 support and advises buying newer hardware when shopping.

The best transcode is no transcode. If your TVs and streaming sticks can direct-play your files, the server only reads from disk. Transcoding mostly happens for remote viewers, browsers, subtitles that need burning in, and 4K HDR files on non-HDR screens.

Passing the GPU into a container

In Docker, give the container access to the Intel GPU device. A minimal Jellyfin service looks like this:

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    restart: unless-stopped
    ports:
      - "8096:8096"
    devices:
      - /dev/dri:/dev/dri
    volumes:
      - ./config:/config
      - ./cache:/cache
      - /srv/data/media:/data/media:ro

Then enable Intel QSV (or VA-API) in Jellyfin's playback settings. The Jellyfin deploy guide covers permissions and the render group. If Compose is new to you, read our Docker Compose tutorial first.

Storage: plan it before you buy drives

Media libraries grow faster than anything else on a home server. A sensible layout:

• SSD for the operating system, Docker and app data. Media server metadata, thumbnails and databases are many small files and are much faster on flash.
• Hard drives for media. Large CMR drives give the best cost per terabyte. Two or more drives can be pooled with a tool like mergerfs, protected with SnapRAID or ZFS, or handed to a NAS.
• One /data folder for downloads and media. Put downloads and the finished library on the same file system, and mount that single parent folder into every container. That lets the *arr apps use hardlinks and instant moves instead of copying files.

Remember that RAID or parity is not a backup. At minimum, back up each app's configuration folder; re-downloading a film is annoying, rebuilding years of watch history and metadata is worse.

A small mini PC has room for one or two drives, so bulk storage usually lives in a USB enclosure or a NAS. For the mini PC itself, see our best mini PC for a home server comparison.

The apps around the media server

The "*arr stack" is a family of open-source apps that watch for new releases, fetch them through your download client, rename them and place them in your library. Use them with content you have the right to download.

App	What it does	GitHub stars	Licence
Sonarr	TV series management	16,826	GPL-3.0
Radarr	Film management	14,506	GPL-3.0
Prowlarr	Indexer manager that feeds Sonarr, Radarr and Lidarr	7,330	GPL-3.0
Lidarr	Music management	5,712	GPL-3.0
Seerr	Request portal for family and friends	12,815	MIT
qBittorrent	Download client with a web UI	40,592	GPL-2.0

Star counts are from the appsgit catalog on October 6, 2026.

Seerr deserves a note. Jellyseerr and Overseerr, the two popular request apps, merged into a single project called Seerr. It works with Jellyfin, Plex and Emby, imports your media server users, and lets them request a film or series that Sonarr or Radarr then fetch. If you previously ran Jellyseerr, Seerr is where development continues.

The whole category is listed under media management, and media servers themselves under media servers.

Beyond films and TV

The same box can serve music and books with almost no extra load. Navidrome streams your music collection to Subsonic-compatible apps; our Navidrome guide sets it up. Audiobookshelf handles audiobooks and podcasts with progress sync across devices. If you are weighing Navidrome against Jellyfin's built-in music support, see Navidrome vs Jellyfin.

Remote access without opening everything

Remote viewing is where most media servers get exposed carelessly. Put Jellyfin behind a reverse proxy with HTTPS, such as Caddy or Nginx Proxy Manager, and keep the *arr apps, the download client and Seerr's admin pages on your LAN or a VPN. The *arr apps were not designed to face the open internet.

Power, noise and uptime

A media server is on all day, so idle power matters more than peak speed. Intel mini PCs idle at a few watts plus whatever your hard drives draw; spinning disks add noise and power, so let the system and apps live on the SSD and allow the media drives to spin down when nobody is watching. If power cuts are common where you live, a small UPS protects the drives and the database files of your *arr apps from corruption.

A sample build

• CPU and box: Intel N150 mini PC or a used ThinkCentre Tiny with an 8th-gen or newer Core i5.
• RAM: 16 GB.
• System drive: 1 TB NVMe SSD.
• Media: two large hard drives in a USB-C or network enclosure, or a NAS.
• Software: Ubuntu Server or Debian, Docker Compose, Jellyfin or Plex, Sonarr, Radarr, Prowlarr, Seerr and a download client.

For everything else a first server should run, read homelab for beginners.