Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
The best mini PC for a Jellyfin server is the one whose media engine matches the streams you actually serve, not the one with the most cores. For a normal household, an Intel N-series box does the job, and the same client-first logic behind our Plex minimum requirements breakdown applies here. Jellyfin's own hardware guidance names recent Intel integrated graphics for low-power servers, and points specifically at the N100 class.
Two things separate a media server from a general-purpose mini PC. The first is the codec engine: Intel Quick Sync and AMD's VCN block process far more video in hardware than the CPU cores next to them, and which formats they touch changes by generation, most visibly with AV1. The second is everything around the chip, meaning drive positions, NIC speed, memory channels, and the Linux kernel floor a newer Intel generation needs before its graphics will accelerate anything at all.
Get the engine right and a low-power N-series part outperforms a much faster CPU at the same job. Get it wrong and a far quicker machine still pegs its processor on a single stream. The eight picks below are ordered by how well their media path, storage and networking fit a Jellyfin deployment.
Quick picks
- Best overall on a budget: Beelink MINI S12 Pro (N100)
- Best current low-power pick with 2.5GbE: GMKtec NucBox G3 Plus (N150)
- Best when Jellyfin shares the box with containers: Beelink EQ12 Pro (Core i3-N305)
- Best premium Intel with AV1 encode: ASUS NUC 14 Pro (Core Ultra 5 125H)
- Best mature business-grade Intel: ASUS NUC 13 Pro
- Best converged homelab host: Minisforum MS-01
- Best AMD mixed-use picks: Beelink SER8 and Minisforum UM890 Pro
What Makes a Great Jellyfin Mini PC?
Jellyfin supports Intel Quick Sync, Intel and AMD VA-API, NVIDIA NVENC and AMD AMF hardware acceleration. On Linux, Quick Sync is the smoother path, and Jellyfin's own hardware guide still prefers Intel for a newly bought integrated-GPU server, citing AMD's H.264 encoder quality and driver situation. Modern AMD is fully supported through VA-API, so the distinction is friction rather than capability.
Codec generation decides what a machine can do in hardware:
| Platform | H.264 encode/decode | HEVC 10-bit | AV1 decode | AV1 encode |
|---|---|---|---|---|
| Intel N100 / N150 / N305 / N355 | Yes | Yes | Yes | No |
| Intel 12th / 13th Gen Core | Yes | Yes | Yes | No |
| Intel Core Ultra (Arc / Xe-LPG) | Yes | Yes | Yes | Yes |
| Ryzen 6000 / Radeon 680M | Yes | Yes | Yes | No |
| Ryzen 7040 / 8040 / Radeon 780M (VCN 4) | Yes | Yes | Yes | Yes |
| Ryzen 5000 / Vega | Yes | Yes | No | No |
The workload you actually have matters as much as the chip. Direct Play costs almost nothing, because the client handles the original file. Transcoding begins when the client cannot play it, and HDR tone mapping, image-based subtitle burn-in and audio conversion all shift work back toward the CPU. That is what decides whether CPU headroom or the fixed-function engine is the binding constraint.
Memory is next. If you are new to the low-power tier, the N100 buying guide covers the memory-channel trap in detail: N100 and N150 are single-channel processors, so you cannot make them dual-channel with a matched kit. Dual channel matters mainly on machines doing iGPU-heavy work such as tone mapping. As a planning rule, 8 GB is workable for Jellyfin alone, 16 GB is a sensible default once an *arr stack joins it, and 32 GB or more is really about ZFS, many VMs or a large container fleet.
Storage splits into two roles. Keep the operating system, Jellyfin database, metadata and transcode cache on an SSD or NVMe drive, because that is where the small random writes land. Bulk media can live on hard drives or a NAS, and mainly needs sequential throughput above the media bitrate. If capacity is the priority rather than the server itself, our NAS picks work through bays and controllers.
Network is the last input. 1GbE is enough for ordinary household playback and several high-bitrate streams. 2.5GbE helps when the server reads from a NAS or serves multiple remux streams. 10GbE is a homelab and storage feature, and it does not increase Quick Sync's codec throughput. Use wired Ethernet for the server itself.
One caveat that bites people on newer hardware: Intel Twin Lake graphics (N150, N250, N350) need a recent kernel, with Linux 6.9 or newer identified in Jellyfin's known-issues guidance, and Meteor Lake Core Ultra needs a modern kernel as well. An old distribution is a common reason acceleration appears not to work when it is really just missing driver support.
#1 Beelink MINI S12 Pro: The Budget Default
The MINI S12 Pro is the simplest way to buy a working Jellyfin server. The N100 is on Jellyfin's recommended integrated-GPU list, its Quick Sync engine handles H.264 and HEVC in both directions plus AV1 decode, and it ships as a complete system rather than a barebone, so there is no memory or drive to source. Where it gives ground is expansion: one 1GbE port, one M.2 slot and one 2.5-inch SATA bay.
| Spec | Detail |
|---|---|
| CPU | Intel Processor N100 (Alder Lake-N), 4 cores / 4 threads, up to 3.4 GHz, 6 W processor base power |
| iGPU | Intel UHD Graphics, 24 EUs, Quick Sync |
| Hardware codecs | H.264 encode/decode, HEVC encode/decode, VP9 and AV1 decode; no AV1 encode |
| Memory | 1 × DDR4-3200 SO-DIMM, 16 GB officially listed |
| Storage | M.2 2280 NVMe/SATA plus a 2.5-inch SATA bay |
| Network | 1GbE (controller varies by listing) |
| Ports | Dual HDMI, USB-A, audio |
Pros
- Ships preconfigured, so there is nothing to source
- N100 Quick Sync covers the common codecs in hardware
- The 2.5-inch SATA bay adds a drive without an external enclosure
Cons
- Single memory channel and a 16 GB official ceiling
- One 1GbE port limits NAS transfers
- A 2023 platform now sold mainly through third-party stock
Verdict: The default first Jellyfin server. It handles the common library codecs and a household of clients without asking you to plan anything.
Perfect for: a dedicated household Jellyfin box on a small budget.
Check the Beelink MINI S12 Pro on Amazon
#2 GMKtec NucBox G3 Plus: Current Low-Power Pick With 2.5GbE
The G3 Plus is the current-silicon version of the budget recipe. The N150 sits in the same low-power media class as the N100 with slightly higher clocks, and GMKtec pairs it with a 2.5GbE Intel I226-V controller, which removes the networking ceiling most entry machines place on NAS pulls and backups. Storage is split across a primary M.2 2280 PCIe 3.0 slot and a secondary M.2 2242 slot that can take a SATA drive.
| Spec | Detail |
|---|---|
| CPU | Intel Processor N150 (Twin Lake), 4 cores / 4 threads, up to 3.6 GHz, 6 W processor base power |
| iGPU | Intel Graphics, 24 EUs; Quick Sync |
| Hardware codecs | H.264/HEVC encode/decode, VP9 and AV1 decode; no AV1 encode |
| Memory | 1 × DDR4-3200 SO-DIMM, up to 32 GB |
| Storage | M.2 2280 PCIe 3.0 NVMe plus M.2 2242 SATA |
| Network | 2.5GbE (Intel I226-V) |
| Wireless | Wi-Fi 6, Bluetooth 5.2 |
| Size | Approximately 114 × 106 × 42.5 mm |
Pros
- 2.5GbE from an Intel controller
- Higher memory ceiling than the S12 Pro, at 32 GB
- Two M.2 positions in a very small chassis
Cons
- Twin Lake graphics want Linux 6.9 or newer
- No AV1 hardware encode
- Single memory channel
- The I226-V is worth validating in both directions on Linux before you commit
Verdict: The pick when a budget box also has to talk to a NAS. The 2.5GbE port is the reason to choose it over an N100 machine.
Perfect for: a low-power server that pulls media from networked storage.
Check the GMKtec NucBox G3 Plus on Amazon
#3 Beelink EQ12 Pro: Jellyfin Plus Containers
The EQ12 Pro is the pick when Jellyfin shares the box with an *arr stack or a couple of virtual machines. The Core i3-N305 has eight cores instead of four, and that extra CPU matters less for the video engine, which stays in the same Gen12 low-power class, than for metadata scans, audio transcodes, subtitle burn-in and virtualization headroom. It also brings dual 2.5GbE and an internal 2.5-inch bay. If the plan is Jellyfin inside Proxmox rather than bare metal, the Proxmox host picks cover the same tradeoffs.
| Spec | Detail |
|---|---|
| CPU | Intel Core i3-N305 (Alder Lake-N), 8 cores / 8 threads, up to 3.8 GHz, 15 W processor base power |
| iGPU | Intel UHD Graphics, 32 EUs |
| Hardware codecs | H.264/HEVC encode/decode, AV1 decode; no AV1 encode |
| Memory | DDR5, 16 GB in the official configuration |
| Storage | M.2 PCIe SSD plus a 2.5-inch SATA bay |
| Network | Dual 2.5GbE |
| Wireless | Wi-Fi 6, Bluetooth 5.2 |
| Displays | Triple 4K60 outputs |
Pros
- Eight CPU cores for the side services, not just transcoding
- Dual 2.5GbE suits a router lab or heavy NAS traffic
- Internal 2.5-inch bay keeps a library drive inside the chassis
Cons
- Same low-power media engine as the N100, no AV1 encode
- Legacy family that is now hard to source new
- Owners report EQ12-family BIOS quirks under Proxmox, so test the recovery workflow before going headless
Verdict: Still the value sweet spot for a machine that hosts Jellyfin and everything around it. The eight cores buy scheduling room, not transcoding throughput.
Perfect for: a home server running Jellyfin alongside containers or light VMs.
Check the Beelink EQ12 Pro on Amazon
#4 ASUS NUC 14 Pro: Premium Intel With AV1 Encode
The NUC 14 Pro is where the media engine changes generation. The Core Ultra 5 125H carries Arc/Xe-LPG graphics that encode and decode AV1 as well as H.264 and HEVC, which the N-series and 12th/13th-gen Core parts cannot encode. It brings two memory channels, Thunderbolt 4 and 2.5GbE, and it is available as a barebone kit or a configured system. Two caveats matter: Meteor Lake graphics need a modern kernel, with support incomplete below Linux 6.7, and the Arc-branded graphics path wants both DIMM slots populated.
| Spec | Detail |
|---|---|
| CPU | Intel Core Ultra 5 125H (Meteor Lake), 14 cores / 18 threads |
| iGPU | Intel Arc / Xe-LPG |
| Hardware codecs | H.264, HEVC and AV1 hardware encode/decode |
| Memory | 2 × DDR5-5600 SO-DIMM |
| Storage | M.2 2280 PCIe 4.0 plus M.2 2242 PCIe 4.0 |
| Network | 2.5GbE |
| Ports | 2 × Thunderbolt 4, HDMI 2.1, USB-C and USB-A |
| Wireless | Wi-Fi 6E |
Pros
- AV1 hardware encode and decode, the biggest media-feature jump here
- Dual-channel DDR5 and two Thunderbolt 4 ports
- Barebone option lets you choose known-good DIMMs and an SSD
- ASUS rates this chassis for round-the-clock operation
Cons
- Needs a current Linux kernel before its media engine accelerates anything
- Runs louder than the low-power picks under sustained load
- Premium tier for a job the N-series chips largely cover
Verdict: The pick when you want AV1 output or when the server also does heavier work. For straight Jellyfin, its codec advantage is the only part that matters.
Perfect for: a server that encodes AV1 or does more than stream.
Check the ASUS NUC 14 Pro on Amazon
#5 ASUS NUC 13 Pro: Mature Business-Grade Intel
The NUC 13 Pro is the conservative choice. The 13th-generation Core P-series parts, the Core i5-1340P and Core i7-1360P, use Iris Xe graphics with a mature Quick Sync path that older kernels already handle well. They decode AV1 without encoding it, and they use DDR4 rather than DDR5, which barely matters at this level. What you get over a budget box is headroom: dual Thunderbolt 4, 2.5GbE, and a chassis built for business deployment.
| Spec | Detail |
|---|---|
| CPU | Intel Core i5-1340P or Core i7-1360P (13th Gen) |
| iGPU | Intel Iris Xe |
| Hardware codecs | H.264/HEVC encode/decode, AV1 decode; no AV1 encode |
| Memory | 2 × DDR4-3200 SO-DIMM |
| Storage | M.2 2280 PCIe 4.0 plus M.2 2242 SATA |
| Network | 2.5GbE (Intel I226-class), Wi-Fi 6E |
| Ports | 2 × Thunderbolt 4, dual HDMI |
Pros
- Quick Sync path mature on both older and newer kernels
- Two Thunderbolt 4 ports and 2.5GbE
- Barebone and configured options across several CPUs
Cons
- No AV1 hardware encode
- Previous generation, and DDR4 rather than DDR5
- More CPU than a Jellyfin-only box needs
Verdict: The safest Intel purchase if you want a platform that will not fight your kernel. You pay for maturity and ports, not for extra transcode throughput.
Perfect for: an always-on server where kernel support should be boring.
Check the ASUS NUC 13 Pro on Amazon
#6 Minisforum MS-01: Jellyfin Inside a Homelab
The MS-01 solves a different problem. It is a converged server: an Intel H-series CPU with Quick Sync, three M.2 storage positions with U.2 support through an adapter, a PCIe 4.0 x16 physical slot that runs at x8, and two 10GbE SFP+ ports plus two 2.5GbE. That networking and storage is what you pay for, not transcode throughput, which 10GbE does not increase. It makes sense when Jellyfin lives inside a Proxmox environment reading from a fast NAS or feeding other VMs, the kind of setup covered in the homelab starter guide.
| Spec | Detail |
|---|---|
| CPU | Intel Core i5-12600H, Core i9-12900H or Core i9-13900H |
| iGPU | Intel Iris Xe, Quick Sync |
| Hardware codecs | H.264/HEVC encode/decode, AV1 decode; no AV1 encode |
| Memory | 2 × DDR5-5200 SO-DIMM (capacity varies by revision) |
| Storage | 3 × M.2 (PCIe 4.0 x4, PCIe 3.0 x4, PCIe 3.0 x2), U.2 via adapter |
| Expansion | PCIe 4.0 x16 physical slot, up to x8 electrical |
| Network | 2 × 10GbE SFP+ plus 2 × 2.5GbE RJ45 |
| Ports | 2 × USB4, HDMI 2.0, USB-A |
| Size | 196 × 189 × 48 mm |
Pros
- Dual 10GbE SFP+ plus dual 2.5GbE
- Three storage positions and a real PCIe expansion slot
- QSV acceleration works inside Proxmox with the right device mapping
Cons
- No AV1 hardware encode on this generation
- Needs a shelf or tray in a rack, since it is not a native 1U
- Overkill if the only job is serving a few streams
Verdict: A fast NAS link and a virtualization host in one box. Buying it purely for Jellyfin wastes most of what it offers.
Perfect for: a converged server where Jellyfin is one workload among several.
Check the Minisforum MS-01 on Amazon
#7 Beelink SER8: AMD Mixed-Use
The SER8 is the AMD answer, and a capable one. The Ryzen 7 8845HS with Radeon 780M uses VCN 4 hardware that encodes and decodes H.264, HEVC and AV1, which is broader on paper than the N-series Intel parts. The catch is software. On Linux, AMD uses VA-API, and Jellyfin's own guidance still prefers Intel for a newly bought integrated-GPU server because of H.264 encoder quality and driver and package friction. A distribution shipping Mesa with H.264 and HEVC VA-API disabled, a licensing quirk rather than a hardware limit, is the classic reason a 780M appears not to transcode at all. For a living-room box rather than a server, our HTPC picks take a similar view.
| Spec | Detail |
|---|---|
| CPU | AMD Ryzen 7 8845HS (Zen 4), 8 cores / 16 threads, 3.8 to 5.1 GHz |
| iGPU | Radeon 780M (RDNA 3, 12 CUs), VCN 4 |
| Hardware codecs | H.264/HEVC encode/decode, AV1 encode/decode |
| Memory | 2 × DDR5-5600 SO-DIMM |
| Storage | 2 × M.2 2280 PCIe 4.0 x4 |
| Network | 2.5GbE |
| Ports | USB4, HDMI 2.1, DisplayPort 1.4 |
Pros
- AV1 encode and decode
- Dual PCIe 4.0 NVMe slots
- Strong choice when Jellyfin shares the box with other workloads
Cons
- Linux VA-API setup is less turnkey than Quick Sync
- Some distributions ship Mesa without H.264/HEVC VA-API
- Jellyfin's own guidance still favors Intel for a dedicated server
Verdict: A capable media machine if you are comfortable with VA-API. For a Jellyfin-only appliance, the Intel path is less work.
Perfect for: an AMD homelab host where Jellyfin is one role among many.
Check the Beelink SER8 on Amazon
#8 Minisforum UM890 Pro: Premium AMD With Expansion
The UM890 Pro is the AMD pick when the machine needs room to grow. The Ryzen 9 8945HS with Radeon 780M brings the same VCN 4 codec set, and Minisforum adds dual 2.5GbE, dual USB4 and an OCuLink PCIe 4.0 x4 port for later external expansion. Memory is documented up to 96 GB across two DIMMs, and it comes as a barebone or a configured system. The same Jellyfin caveats as the SER8 apply, and the extra CPU and GPU only earn their keep if the box does more than stream.
| Spec | Detail |
|---|---|
| CPU | AMD Ryzen 9 8945HS, 8 cores / 16 threads |
| iGPU | Radeon 780M (RDNA 3), VCN 4 |
| Hardware codecs | H.264/HEVC encode/decode, AV1 encode/decode |
| Memory | 2 × DDR5-5600 SO-DIMM, up to 96 GB documented |
| Storage | 2 × M.2 PCIe 4.0 x4 |
| Network | Dual 2.5GbE |
| Expansion | OCuLink (PCIe 4.0 x4), 2 × USB4 |
| Ports | HDMI 2.1, DisplayPort 1.4 |
Pros
- 96 GB memory ceiling for virtual machines and containers
- OCuLink and dual USB4 for later expansion
- Dual 2.5GbE out of the box
Cons
- AMD VA-API caveats, same as the SER8
- Far more machine than a Jellyfin-only server needs
- Barebone and configured SKUs differ, so verify the exact configuration
Verdict: The most expandable AMD option here. Buy it for the memory, networking and OCuLink, and treat Jellyfin as one of its jobs.
Perfect for: a long-lived AMD homelab host that will grow into more roles.
Check the Minisforum UM890 Pro on Amazon
Storage Companion: TerraMaster D4-320
Most of the picks above have at most a couple of internal drive positions, which is fine for the operating system and the transcode cache but not for a large library. A four-bay USB DAS like the TerraMaster D4-320 adds capacity over USB 3.2 Gen 2 without requiring a full NAS. Treat it as capacity and nothing more: direct-attached storage is neither RAID nor a backup by default.
Check the TerraMaster D4-320 on Amazon
Comparison Table
| Model | CPU | AV1 decode / encode | Memory | Internal storage | Network |
|---|---|---|---|---|---|
| Beelink MINI S12 Pro | Intel N100 | Yes / No | 1 × DDR4-3200, 16 GB official | M.2 + 2.5-inch SATA | 1GbE |
| GMKtec NucBox G3 Plus | Intel N150 | Yes / No | 1 × DDR4-3200, up to 32 GB | M.2 2280 + M.2 2242 | 2.5GbE |
| Beelink EQ12 Pro | Core i3-N305 | Yes / No | DDR5, 16 GB | M.2 + 2.5-inch SATA | Dual 2.5GbE |
| ASUS NUC 14 Pro | Core Ultra 5 125H | Yes / Yes | 2 × DDR5-5600 | M.2 2280 + M.2 2242 | 2.5GbE |
| ASUS NUC 13 Pro | Core i5-1340P / i7-1360P | Yes / No | 2 × DDR4-3200 | M.2 2280 + M.2 2242 SATA | 2.5GbE |
| Minisforum MS-01 | Core i5-12600H to i9-13900H | Yes / No | 2 × DDR5-5200 | 3 × M.2 + U.2 via adapter | 2 × 10GbE + 2 × 2.5GbE |
| Beelink SER8 | Ryzen 7 8845HS | Yes / Yes | 2 × DDR5-5600 | 2 × M.2 PCIe 4.0 | 2.5GbE |
| Minisforum UM890 Pro | Ryzen 9 8945HS | Yes / Yes | 2 × DDR5-5600, up to 96 GB | 2 × M.2 PCIe 4.0 | Dual 2.5GbE |
Which Jellyfin Mini PC Should You Buy?
Match the machine to the workload rather than to the budget ceiling.
- Dedicated Jellyfin, lowest spend: Beelink MINI S12 Pro. The N100 covers the common codecs and the box arrives ready to use.
- Budget box that reads from a NAS: GMKtec NucBox G3 Plus. The 2.5GbE port is the deciding feature. For tighter budgets, the sub-$300 picks cover the same ground.
- Jellyfin plus containers or light VMs: Beelink EQ12 Pro. Eight cores buy scheduling room for the services around Jellyfin.
- AV1 output or heavier server work: ASUS NUC 14 Pro. It is the only Intel pick here that hardware-encodes AV1.
- Predictable kernel support: ASUS NUC 13 Pro. Mature Quick Sync on both old and new distributions.
- Jellyfin inside a Proxmox lab with fast storage: Minisforum MS-01. The 10GbE and multiple storage paths are the value, not the CPU.
- AMD workspace with Jellyfin as one role: Beelink SER8 for the shorter chassis, Minisforum UM890 Pro when 96 GB of memory and OCuLink matter.
Frequently Asked Questions
Q: Can an Intel N100 mini PC transcode 4K?
Yes, in hardware. The N100's Quick Sync engine decodes AV1, H.264 and HEVC, which covers the common 4K source files, and it does so far above real time when acceleration is actually engaged in your container or VM. The variable is the workload, not the chip: HDR tone mapping, image-based subtitle burn-in and audio conversion all add work the video engine cannot take, and those are what make an N100 look slow.
Q: Is AMD good for a Jellyfin server?
Modern AMD is fully supported. Jellyfin accelerates through VA-API on Linux and AMF on Windows, and Radeon 780M hardware with VCN 4 encodes and decodes H.264, HEVC and AV1. The reason Intel remains the usual recommendation for a new dedicated server is friction, not capability: Quick Sync needs less package-level care on Linux, and Jellyfin's hardware guide flags AMD's H.264 encoder quality and driver situation. Check that your distribution ships Mesa with VA-API enabled before blaming the GPU.
Q: How much RAM does a Jellyfin server need?
8 GB is workable for Jellyfin on its own. 16 GB is a sensible default once an *arr stack and a few containers join it. 32 GB or more is really about ZFS, many VMs or a large container fleet rather than transcoding. Channel count matters more than raw capacity on a machine doing iGPU-heavy work such as HDR tone mapping, and note that N100 and N150 platforms are single-channel and cannot be upgraded to dual-channel with a memory kit.
Q: Does Jellyfin need a fast CPU?
Mostly no. The video engine does the transcoding, so a low-power N-series part can serve a household that a much faster CPU would not improve on. CPU cores start to matter when the same box handles audio transcoding, subtitle burn-in and metadata scans, or runs other services alongside Jellyfin.
Conclusion
For most households, a Jellyfin server does not need to be powerful; it needs the right media engine. The Beelink MINI S12 Pro is the simplest complete system and the budget default, the GMKtec NucBox G3 Plus is the current low-power choice with 2.5GbE, and the Beelink EQ12 Pro is what to buy when Jellyfin shares the box with containers or VMs. Each handles H.264, HEVC and AV1 decode in hardware, which covers the bulk of a real library.
Step up only for a reason. The ASUS NUC 14 Pro adds AV1 hardware encode and a stronger general-purpose server. The Minisforum MS-01 brings dual 10GbE and multiple storage paths for a converged Proxmox host. The AMD Beelink SER8 and Minisforum UM890 Pro make sense when Jellyfin is one workload among several, with the VA-API caveats that come with the platform.
Whichever you pick, budget for storage and software before silicon. A four-bay DAS, an SSD reserved for the database and transcode cache, and a correctly mapped /dev/dri inside the container will do more for playback than another tier of CPU. If you are still mapping the wider setup, start with the N100 buying guide, the NAS picks for storage, the Proxmox hosts for virtualization, and the Plex requirements for the client-side reality.
