Why Quick Sync decides this purchase
When a phone, browser or old TV can't play a file directly, the server transcodes it on the fly. Done in software, that keeps several CPU cores busy for every stream. Done on Intel Quick Sync, the iGPU's fixed-function media engine handles decoding and encoding while the CPU cores stay mostly idle. Plex says its hardware acceleration works on Intel Core processors with Quick Sync and recommends 5th-gen Broadwell or newer for the best experience. Jellyfin's Intel guide goes further and maps each codec to the generation that supports it.
Quick Sync by generation
- 6th gen (Skylake, HD 5xx): HEVC 8-bit decode and encode, but no HEVC 10-bit. Jellyfin's docs say to choose 7th gen or newer instead.
- 7th gen (Kaby Lake, HD/UHD 6xx): HEVC 10-bit decode and encode, which covers most 4K HDR files. This is also Plex's floor for HEVC encoding.
- 8th–10th gen (Coffee Lake, Comet Lake, mostly UHD 630): the same media features as 7th gen in the 1-liter business minis. Jellyfin puts UHD 620/630 in its mainstream tier.
- 11th gen and newer (Tiger Lake, Alder Lake, Raptor Lake: UHD 7xx and Iris Xe): adds AV1 decode. Jellyfin notes that UHD 770 and Iris Xe have a second video engine for more concurrent transcodes.
- Core Ultra Series 1 (Meteor Lake): adds AV1 encode.
- N-series: Alder Lake-N chips such as the N100 belong to the same media-driver platform family as Tiger Lake and Alder Lake, which supports AV1 decode. The older Jasper Lake and Elkhart Lake Pentium/Celeron chips have no AV1 acceleration.
The Quick Sync transcoding by generation guide goes deeper on each step, and N100 vs N150 vs N305 covers the low-power chips.
Tone mapping HDR to SDR
When a 4K HDR file plays on an SDR screen, the server has to tone map it or the picture looks washed out. Jellyfin supports hardware tone mapping on every Intel GPU that can decode HEVC 10-bit, which in practice means 7th gen and newer. It offers two methods: OpenCL, which supports Dolby Vision profile 5 and is widely supported, and QSV VPP, which uses less power but only works on Linux. On N95 and N100 machines, Jellyfin's docs say you need Intel's OpenCL runtime at version 23.xx or newer. Plex notes that HEVC transcodes to its web client come out as 8-bit, which triggers tone mapping when the source is 10-bit.
Plex: hardware transcoding needs Plex Pass
This catches people out. Plex's support article says hardware-accelerated streaming "is a premium feature and requires an active Plex Pass subscription", held by the server owner. Without it, Plex still direct-plays compatible files but transcodes in software. Other Plex details worth knowing: HEVC encoding needs a 7th-gen Core and Plex Media Server 1.41.3 or later; Linux support for 9th-gen Core and later needs Plex Media Server 1.17.0 or later; and in Docker you have to pass the iGPU device into the container. Jellyfin is free, open-source software, so its hardware acceleration has no subscription gate.
AMD mini PCs: fine for Jellyfin, a gamble on Plex
Plex says its AMD GPU support is provided "as is" and recommends Intel Quick Sync or a dedicated NVIDIA GPU. Jellyfin supports AMD Ryzen APUs through AMF on Windows and VA-API on Linux: Ryzen 4000 (Renoir) and newer encode HEVC 10-bit, Ryzen 6000 and newer decode AV1, and Ryzen 7000/8000 encode AV1. Jellyfin's AMD page is candid that AMD's HEVC and AV1 encoders "are currently no match for Intel QSV and NVIDIA NVENC" on quality, though newer generations have improved. So a Ryzen mini PC is a reasonable Jellyfin box, but for Plex buy Intel.
Storage: USB DAS or a NAS share
A 1-liter box typically holds one NVMe drive and, on business models such as the EliteDesk 800 G4 and the taller NUC 13 Pro, one 2.5-inch drive. That's room for the OS, the metadata database and a modest library at most. For anything bigger you have two common options. A USB direct-attached storage enclosure keeps everything in one place and is simple to set up. A NAS share (SMB or NFS) keeps the library on a separate box and lets the mini PC concentrate on serving and transcoding; this is where a 2.5 GbE port starts to earn its keep. Either way, keep the server's database and transcode temp folder on the local NVMe.
Sharing the box with other services
A media server rarely lives alone. The same Intel iGPU that transcodes can decode camera streams for Frigate, and a Proxmox host can run Jellyfin next to Home Assistant and network services, provided you pass the iGPU into the right container. If you also want workflow automation, an AI agent server or a local LLM on the same hardware, size RAM and storage for all of them. Before buying, work through the used mini PC buying checklist.