Linux Tutorials

Best Mini PC for Plex and Jellyfin Transcoding

This post contains affiliate links. If you buy through them, we may earn a small commission at no extra cost to you. Learn more.

A handful of Intel chips cover almost every mini PC worth buying for a Plex or Jellyfin server, and the one that matters is the integrated GPU, not the CPU cores. Quick Sync, the media block baked into Intel graphics, is what turns a 4K HDR movie into a stream your phone can play. It does the job on 10 watts while the CPU sits idle. Pick the wrong box and you either stall on the second stream or pay for an AMD iGPU that Jellyfin itself tells you to avoid.

Original content from computingforgeeks.com - post 174221

This guide ranks mini PCs by the one number that decides whether your library plays smoothly: how many simultaneous transcodes the iGPU sustains. We measured that on two real Intel iGPUs in the lab, a Skylake HD 530 and a Tiger Lake Iris Xe, with the exact ffmpeg command Jellyfin runs. Then we matched the result to the chips shipping in mini PCs today. You will see where an N150 lands, why the HD 530 can’t touch 4K HDR, and which single box we would buy for a household that actually hits the server at the same time. If you would rather drop in a graphics card than rely on an iGPU, that is a separate buyer guide on transcoding GPUs.

Current as of October 2026.

Quick picks

Every box here runs Intel Quick Sync except the last one, which is the popular AMD mini PC we’re telling you to skip for this job. Prices are what the listings showed when we wrote this, so check the live price before you buy.

AwardMini PCiGPUAV1 encodePrice
Best overallBeelink Mini S13 (N150)Intel Graphics, 24 EUNo~$329
Best budgetGMKtec G3S (N95)Intel UHD, 16 EUNo~$250
Best for a busy houseASUS NUC 13 Pro (i5-13420H)Intel UHD, 48 EU, dual channelNo~$769
Most streams and newest codecsMINISFORUM M1 Pro-125HIntel Arc, 7 Xe-coresYes~$895
Popular, but skip it hereBeelink SER5 (Ryzen 5 5500U)Radeon Vega 7No~$389
Ranked by how the iGPU handles concurrent transcodes, not by CPU speed. Only the Core Ultra box can encode AV1.

The picks

1. Beelink Mini S13 (N150): the one most people should buy

Beelink Mini S13 N150 mini PC for Plex and Jellyfin
Beelink Mini S13, Intel N150. The Mini S chassis. Image: Beelink.

The N150 is the current floor for a media server you buy new, and it’s the floor you want. Its Gen12 graphics carry 24 execution units, the same count as the Skylake HD 530 we measured, but with the two things that old chip could not do: a working 4K HDR tone-map and AV1 decode. That gap is the whole reason to spend 329 dollars on a current box instead of 60 on a used Skylake that stalls the moment a phone asks for HDR.

Who it’s for: a one or two TV household on Jellyfin or Plex. Expect a couple of simultaneous 4K HDR transcodes and a stack of lighter 1080p ones, which covers almost every home. That estimate brackets off our measured Gen9 and Tiger Lake boxes rather than this exact unit, because the N150 sits between them on throughput. For how the N150 compares to its siblings on raw compute, we put the N150 up against the N355 separately.

Skip it if your library is mostly 4K HDR remuxes and three people watch at once. The N150 ships single-channel memory, and Jellyfin’s own docs say dual-channel roughly doubles the bandwidth that HDR tone-mapping leans on, so this is the box that tops out first on heavy content. For that load, buy up the list.

2. GMKtec G3S (N95): the cheapest way in that still works

GMKtec G3S N95 mini PC media server
GMKtec G3S, Intel N95. Image: GMKtec.

The N95 is the same Alder Lake-N family as the N150 with a smaller graphics block, 16 execution units against 24, so it keeps the modern Quick Sync feature set: HEVC and H.264 encode, AV1 decode, and a tone-map that actually runs. At around 250 dollars it’s the cheapest box we would put a media server on, and the 1,400-plus reviews on the listing tell you plenty of people already have.

Buy it for one stream at a time, or a couple of light 1080p ones, on a tight budget. It handles a single 4K HDR transcode, which is all a one-TV setup ever asks for. The base listing ships 8GB and a SATA-class slot, so budget a RAM and NVMe upgrade if you run the full Jellyfin or *arr stack. For a dedicated low-power box, we also walked through a Jellyfin and *arr media build on similar hardware.

Look higher if you expect two heavy streams at once. With the smallest iGPU here and single-channel memory, the N95 is the first to drop below realtime on HDR, and the 80 dollars up to an N150 buys real headroom. Treat it as a single-viewer server, not a family one.

3. ASUS NUC 13 Pro (i5-13420H): dual channel for a busy house

ASUS NUC 13 Pro i5-13420H mini PC for Jellyfin transcoding
ASUS NUC 13 Pro, Core i5-13420H. Image: ASUS.

This is the step up that matters for a household that actually loads the server. The i5-13420H carries Intel UHD graphics with 48 execution units, twice the N150’s count, and the NUC runs dual-channel DDR4, so it clears the memory-bandwidth wall that caps the single-channel N-boxes on tone-mapping. Its eight cores also leave room for Plex, the *arr apps and a few containers without starving the transcode, the kind of load we sized in how many VMs a mini PC really handles.

This is the box for three or four concurrent streams with some 4K HDR in the mix. Reading off our measured Iris Xe box, which has 96 execution units, this 48-unit chip with dual-channel memory should land around half of it, which is comfortably a busy family’s load. The media feature set matches the N-series: HEVC and H.264 encode, AV1 decode, no AV1 encode.

Pass on it if you only ever serve one or two streams, because an N150 does that for a third of the price. One listing note: this ASIN ships the i5-13420H and Intel UHD graphics, not the Iris Xe version of the NUC 13 Pro, so confirm the processor line in the title before you buy. It’s still the right media class, just UHD rather than Iris Xe.

4. MINISFORUM M1 Pro-125H: the most streams and the only AV1 encoder

MINISFORUM M1 Pro Core Ultra 5 125H mini PC with Intel Arc for AV1 transcoding
MINISFORUM M1 Pro-125H, Core Ultra 5 125H with Intel Arc graphics. Image: MINISFORUM.

The Core Ultra 5 125H is the only box here with a full Intel Arc iGPU, seven Xe-cores at 2.2 GHz, and it’s the only one that can encode AV1 in hardware. That matters two ways: it serves more simultaneous HDR streams than anything below it, and it can transcode into AV1, the codec that saves the most bandwidth for remote streaming. It also ships dual-channel DDR5-5600, which feeds the tone-mapper the bandwidth Jellyfin says it wants.

Who it’s for: the heavy home server, five or more streams with 4K HDR, or anyone who wants to re-encode a library to AV1. Its Arc graphics sit above our measured Tiger Lake box, which already held four to five heavy HDR streams, so this is the ceiling of the mini-PC field short of adding a discrete transcoding card.

Skip it if you serve one or two streams, because you are paying for an iGPU and a stream count you will never use. At around 895 dollars it’s the most expensive pick by a wide margin. If you want the same AV1 media block for less, the GMKtec K15 with the Core Ultra 5 125U runs cheaper, though its cut-down iGPU gives up some tone-map headroom.

5. Beelink SER5 (Ryzen 5 5500U): the popular box to skip

Beelink SER5 Ryzen 5 5500U mini PC
Beelink SER5, AMD Ryzen 5 5500U. The SER chassis. Image: Beelink.

The SER5 is a fine little computer and the wrong one for a media server, and it’s on this list because so many people buy it for one anyway. The Ryzen 5 5500U is a Zen 2 Lucienne part with Radeon Vega 7 graphics, which carries AMD’s older VCN 2 video block: no AV1 at all, not even decode, and an H.264 encoder that Jellyfin rates well below Intel’s. Jellyfin’s hardware page is blunt about it, saying AMD “is NOT recommended if you intend to use integrated graphics.”

The practical cost is quality, not just speed. Because most clients fall back to H.264, you transcode to H.264 most of the time, and that is exactly where AMD’s encoder is weakest. For the same money as this box you can buy the N150 and get a better encoder, AV1 decode and lower idle power.

Buy the SER5 if you want a general desktop with more CPU than an N-series chip and transcoding isn’t the point. For Plex or Jellyfin, pick any Intel box above it instead.

How we counted streams per iGPU

A transcode counts as “real” only if it runs faster than the video plays. A 1080p movie at 24 frames per second needs the iGPU to hold at least 24 fps per stream. The number of streams a box handles is the point where the slowest stream still clears realtime. We ran Jellyfin’s own ffmpeg command (QSV with VA-API, jellyfin-ffmpeg 8.1, low-power encode) in N parallel copies and recorded the slowest stream’s fps at each step.

Two Intel iGPUs in the lab bracket the field. The HD Graphics 530 is Skylake, the Gen9 graphics still sold in cheap used SFF boxes. The Iris Xe is Tiger Lake, the strongest iGPU before Intel split graphics into the Arc line. Every N95, N100 and N150 mini PC on sale today sits between these two on raw throughput, so the measured numbers below are the floor and ceiling you are buying into.

WorkloadHD 530 (Skylake Gen9)Iris Xe (Tiger Lake)
1080p H.264 to 720p, slowest stream4 streams at 113 fps each10 streams at 65 fps each
4K HEVC 10-bit HDR to 1080p, with tone-mapFailed (no working path)4 to 5 streams at 44 fps each
AV1 4K to 1080p H.264No AV1 decode4 streams at 58 fps each
Measured 2026-10 on the lab boxes with Jellyfin’s ffmpeg. A 1080p stream needs about 24 fps, so every number above realtime is a stream the box can serve.

The light row flatters every chip, and we stopped testing it at four streams on the HD 530 because 113 fps each left so much headroom. Almost nobody transcodes 1080p H.264 anyway, because that codec plays directly on every client made in the last decade. The row that decides a media server is the middle one: a 4K HDR movie going to a phone that needs 1080p SDR. The HD 530 never finished it. Its VA-API HEVC decode returned hwaccel initialisation returned error and the OpenCL tone-map fallback crawled below realtime, so a Gen9 box is a one-stream SDR server in practice. Tiger Lake held four to five of those heavy streams at once, and that gap is the whole reason to buy a current chip.

Where do today’s mini-PC chips land between these two? The N-series graphics (Gen12) sit closer to Tiger Lake than to Skylake on the heavy row, and they add the two things the HD 530 lacks: a working HDR tone-map and AV1 decode. That is why an N100 built in 2023 outruns a Skylake i7 from 2015 at the only job that matters here. Intel’s own guidance backs the floor: Jellyfin lists the N100 as a minimum recommended CPU for a hardware-accelerated server and says plainly that “AMD is NOT recommended if you intend to use integrated graphics for Jellyfin.”

Plex Pass or not: what changes the math

Hardware transcoding is free on Jellyfin and paid on Plex, and that single fact moves the budget more than the choice of mini PC. Jellyfin turns on Quick Sync with no licence and imposes no limit on concurrent encode sessions on an Intel iGPU. Plex gates the same feature behind an active Plex Pass, and a new Lifetime pass now costs 749.99 dollars after the July 2026 increase, with a 5-year pass at 249.99.

The practical read: if you run Plex and don’t already own a Lifetime pass, the licence costs more than any mini PC in this guide, and the hardware you buy should assume you will pay it. If you run Jellyfin, every stream count above comes free with the box. Either way the iGPU does the work, so the buying decision is the same. The licence only changes what you spend around it. If you would rather keep the media on a dedicated appliance, a NAS built for self-hosting Plex is the other route.

ItemJellyfinPlex
Hardware transcode costFreePlex Pass required
Intel iGPU session limitNoneNone (Intel)
Current encoder stackjellyfin-ffmpeg 8.1Bundled transcoder
Lifetime licencen/a749.99 dollars
Both servers use the same Quick Sync hardware; only Plex charges for access to it.

The 4K HDR test the HD 530 failed

If you are tempted by a used Skylake or Kaby Lake SFF box because it’s 60 dollars on marketplace, run one test before you commit: a 4K HDR HEVC file to a 1080p SDR client. That is the transcode an older iGPU chokes on, and it’s exactly what a phone or a TV app requests when it can’t play HDR directly. On the HD 530 the Jellyfin command never produced a frame.

[hevc @ 0x...] Failed setup for format vaapi: hwaccel initialisation returned error.
[vf#0:0 @ 0x...] Error reinitializing filters!
[vf#0:0 @ 0x...] Task finished with error code: -38 (Function not implemented)

Gen9 graphics decode HEVC 8-bit but not the 10-bit Main10 profile every 4K HDR release uses, so the hardware decode never initialises and the tone-map filter has nothing to run on. Forcing the software path works but defeats the point: it pins the CPU and runs below realtime. A Gen12 N100 or newer does the same file in hardware because 10-bit HEVC decode and HDR tone-mapping both moved into the fixed-function block. This is the clearest line in the whole category. Buy Gen12 or newer, and skip anything older than an N-series chip for a server that will ever touch HDR.

Count streams on your own box

You don’t have to trust a spec sheet. Once Jellyfin is installed with hardware acceleration enabled, start one transcode from a 4K HDR title, watch the dashboard, and add clients until any stream drops below 1x. That number is your box’s real ceiling for that kind of file.

To script it, the table above came from a small harness that runs N copies of the transcode, times each one and prints the slowest stream’s fps:

CMD=$(cat "$1"); N=$2; T=$(mktemp -d)
for i in $(seq "$N"); do
  ( s=$(date +%s.%N); eval "$CMD" -f null - >/dev/null 2>"$T/$i.err"; e=$(date +%s.%N); echo "$s $e" > "$T/$i.t" ) &
done
wait
min=99999
for i in $(seq "$N"); do
  fr=$(grep -ao 'frame= *[0-9]*' "$T/$i.err" | tail -1 | grep -o '[0-9]*$')
  [ -z "$fr" ] && { echo "stream $i failed to transcode"; continue; }
  read s e < "$T/$i.t"; fps=$(python3 -c "print(round($fr/($e-$s),1))")
  min=$(python3 -c "print(min($min,$fps))")
done
echo "N=$N min_fps=$min"; rm -rf "$T"

Save it as streams.sh and feed it a file holding the exact command Jellyfin generates. The harness appends the output argument, so the command file stops at the encoder. This is the heavy case, a 4K HDR HEVC file tone-mapped down to 1080p H.264, which is the row that decides a media server:

/usr/lib/jellyfin-ffmpeg/ffmpeg -init_hw_device vaapi=va:/dev/dri/renderD128,driver=iHD -init_hw_device qsv=qs@va -init_hw_device opencl=ocl@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -i file:/media/test/hevc4k-hdr.mp4 -vf "setparams=color_primaries=bt2020:color_trc=smpte2084:colorspace=bt2020nc,scale_vaapi=w=1920:h=1080:extra_hw_frames=24,hwmap=derive_device=opencl:mode=read,tonemap_opencl=format=nv12:p=bt709:t=bt709:m=bt709:tonemap=bt2390:peak=100:desat=0,hwmap=derive_device=qsv:mode=write:reverse=1:extra_hw_frames=16,format=qsv" -c:v h264_qsv -low_power 1 -preset veryfast -b:v 8M

Run bash streams.sh cmd.txt 4 for four parallel streams, then raise the last number until min_fps drops below the video’s frame rate, usually 24. That last N that still clears realtime is how many of those streams the iGPU serves at once. Run it with the real titles your family watches, because a light 1080p H.264 file and a heavy 4K HDR remux land on opposite ends of the table. The heavy one is the honest test.

What actually decides a Plex or Jellyfin mini PC

Four specs decide whether a box serves your library, and none of them is the CPU benchmark the listing leads with. Check these before you look at anything else:

  • Graphics generation, Gen12 or newer: this is the line between a box that tone-maps 4K HDR and one that fails it. An N-series chip or any Core Ultra clears it; anything older than an N100, including used Skylake and Kaby Lake SFF boxes, doesn’t.
  • Memory channels: dual-channel roughly doubles the bandwidth HDR tone-mapping uses, so it’s the cleanest reason one box serves more heavy streams than another. The N95 and N150 are single-channel; the NUC and the Core Ultra boxes are dual.
  • AV1 encode versus decode: every Intel pick here decodes AV1, but only the Core Ultra encodes it. You need encode only if you plan to re-compress a library to AV1 or stream it out at low bitrate. For normal playback, decode is enough.
  • Quick Sync, not an AMD iGPU: Intel’s encoder is better and easier to set up, and Jellyfin recommends against AMD integrated graphics outright. If a mini PC’s only GPU is Radeon Vega, it’s the wrong tool for this job.

Notice what is missing from that list: core count, clock speed, and RAM capacity. They matter for the apps around the server, the *arr stack, downloads, a database. But the transcode itself runs on the fixed-function media block, which is why a 6-watt N150 out-serves a much faster CPU with no Quick Sync.

Which one to buy for your library

Match the box to how many people hit the server and how much of your library is 4K HDR, not to a spec-sheet score:

  • One or two viewers, any budget: the Beelink Mini S13 (N150). It’s the floor that still does everything a small household needs, HDR included.
  • One viewer, lowest price: the GMKtec G3S (N95). A single stream at a time, with a RAM and SSD upgrade budgeted in.
  • A busy family, some 4K HDR: the ASUS NUC 13 Pro. Dual-channel memory and eight cores carry three or four streams and the apps around them.
  • The heavy server, or you want AV1: the MINISFORUM M1 Pro-125H. The full Arc iGPU serves the most streams and is the only pick that encodes AV1.

If you remember one thing, make it the generation line. A current N150 at 329 dollars will out-transcode a used Skylake i7 that looks like a bargain. The media block, not the CPU, is what turns your library into something every screen can play. Buy Gen12 or newer, size up for the number of simultaneous viewers, and the rest of the spec sheet barely matters.

Keep reading

Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) Ubuntu Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 Security UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 PHP2Shell (CVE-2026-109618, CVE-2026-109619): Check and Patch PHP Php PHP2Shell (CVE-2026-109618, CVE-2026-109619): Check and Patch PHP Fedora 45 kmscon Console: Fonts, Keymaps and Reverting to fbcon Fedora Fedora 45 kmscon Console: Fonts, Keymaps and Reverting to fbcon nvidia-smi Command on Linux: Monitor GPU Usage, Memory, Processes AI nvidia-smi Command on Linux: Monitor GPU Usage, Memory, Processes What are CentOS 8 New features? CentOS What are CentOS 8 New features?

Leave a Comment

Press ESC to close