Jellyfin System Requirements: Minimum and Recommended Specs

Quick answer

Jellyfin does not have one useful hardware requirement that fits every server. The important question is whether your clients Direct Play the original files or whether the server must transcode them.

For a small home server where most media Direct Plays, a practical starting point is:

CPU:       Modern 64-bit dual-core or better
RAM:       4GB workable; 8GB recommended
Storage:   SSD for the OS, Jellyfin data and cache
Network:   Gigabit Ethernet recommended
GPU:       Not required for Direct Play
Media:     Separate disk, NAS or other reliable storage

For a server that may need regular video transcoding, use hardware acceleration rather than relying on a weak CPU to software-transcode everything. Jellyfin supports hardware-accelerated transcoding on suitable Intel, AMD, NVIDIA, Apple and Rockchip hardware.

For most low-power Linux builds, an Intel CPU with integrated graphics is a straightforward option because Jellyfin supports Intel Quick Sync and VA-API. If you are buying hardware specifically for Jellyfin, avoid Intel processor models ending in F, because those models do not have an integrated GPU.

Before buying anything, read Jellyfin Direct Play vs Transcoding so you know which workload you actually need to size for.

---

Jellyfin requirements by workload

Workload	Practical CPU	RAM	GPU / hardware acceleration	Network
One or two local Direct Play streams	Modern low-power dual/quad-core	4–8GB	Not required	Gigabit recommended
Jellyfin plus a few Docker services	Modern quad-core	8–16GB	Optional	Gigabit recommended
Occasional 1080p video transcoding	Modern CPU plus supported iGPU/GPU	8GB+	Recommended	Gigabit recommended
Several simultaneous transcodes	Stronger modern platform	16GB+ practical	Strongly recommended	Gigabit or better
4K library with capable clients	Modest server can work if clients Direct Play	8GB+	Optional if nothing transcodes	Wired network strongly recommended
4K transcoding or HDR tone mapping	Modern supported platform	8–16GB+	Strongly recommended	Depends on source and remote bitrate

These are SmallGrid planning ranges, not hard Jellyfin limits. Library size, plugins, other services, subtitle burn-in, HDR tone mapping, codec support and the number of simultaneous users all change the workload.

---

Minimum Jellyfin requirements for Direct Play

Direct Play is the lightest workload.

When the client supports the original:

• container
• video codec and profile
• audio codec
• subtitles
• resolution
• bitrate

Jellyfin mostly reads the file from storage and sends it to the client. The server does not need to re-encode the video.

A modest machine can therefore be an excellent Jellyfin server when the clients are compatible.

A sensible minimum home-lab target is:

64-bit CPU
4GB RAM
SSD for the operating system and Jellyfin data
Reliable media storage
Wired Ethernet where possible

If the same machine also runs Docker, download automation, monitoring or other services, move to 8GB or 16GB RAM rather than sizing only for Jellyfin.

Use Best Jellyfin File Format for Direct Play to reduce avoidable compatibility problems.

---

Recommended Jellyfin specs for most homes

For a new small home server, a balanced target is:

CPU:       Intel 8th-generation Core or newer, or a newer low-power Intel platform
Graphics:  Intel integrated graphics with Quick Sync
RAM:       8GB minimum; 16GB if the machine runs other services
System:    SSD
Media:     Separate internal, USB, NAS or server storage
Network:   1Gb Ethernet
OS:        Supported 64-bit Linux or another supported Jellyfin platform

You do not need an i7 simply because you are running Jellyfin. A used business mini PC with an efficient Intel iGPU can be a better home server than an older high-wattage desktop.

For specific buying advice, use Best Mini PC Specs for Jellyfin.

---

How much RAM does Jellyfin need?

Jellyfin itself is not normally a huge RAM consumer in a small household setup.

RAM	Practical use
4GB	Small Jellyfin-only server; limited headroom
8GB	Good baseline for Jellyfin and light extra services
16GB	Better for Docker, larger homelabs or Proxmox
32GB+	Usually driven by other workloads rather than Jellyfin itself

More RAM does not make an incompatible client Direct Play a file. Playback compatibility and transcoding capability matter more than simply adding memory.

---

CPU requirements for Jellyfin

Direct Play

CPU demand is usually low. Prioritise:

• reliable modern hardware
• low idle power
• storage and network throughput
• enough headroom for library scans and background tasks

Software transcoding

Software video transcoding is much more demanding. The required CPU depends on:

• codec
• resolution
• frame rate
• source bitrate
• target bitrate
• subtitle filters
• HDR tone mapping
• simultaneous streams

This is why a single CPU benchmark number is a poor universal Jellyfin requirement.

If a low-power server regularly software-transcodes video, first check whether the client or media format is causing avoidable conversion.

Use How to Check Why Jellyfin Is Transcoding before replacing hardware.

---

GPU and hardware acceleration requirements

A GPU is not required for Direct Play.

It becomes valuable when Jellyfin must convert video in real time. Jellyfin currently supports hardware acceleration methods including:

• Intel Quick Sync Video
• Intel/AMD VA-API on Linux
• NVIDIA NVENC/NVDEC
• AMD AMF on Windows
• Apple VideoToolbox
• Rockchip RKMPP on supported Linux hardware

Hardware acceleration can cover video decoding, encoding and, on supported platforms, parts of scaling and HDR tone mapping. Some stages may still use the CPU depending on hardware, drivers and media.

For an Intel Linux server, Jellyfin documents QSV as the preferred method on mainstream supported GPUs, with VA-API available for compatibility.

Use Jellyfin Hardware Transcoding on Ubuntu for setup and verification.

---

Jellyfin requirements for 1080p

For predominantly Direct Play 1080p media:

Modern low-power CPU
4–8GB RAM
SSD system drive
Gigabit Ethernet
No dedicated GPU required

If 1080p files regularly transcode, a supported Intel iGPU or other hardware-acceleration device is more useful than simply adding CPU cores.

Check the dashboard during playback. If Jellyfin reports Direct Play, upgrading the server CPU is unlikely to improve picture quality or reduce buffering caused elsewhere in the network.

---

Jellyfin requirements for 4K

The best small-server strategy for 4K is usually:

4K file
→ capable playback client
→ Direct Play

A modest server can serve high-quality 4K media when it is only reading the file and sending it across a fast local network.

The difficult workload is:

4K HEVC/HDR source
→ incompatible client or bandwidth limit
→ real-time video transcode / tone mapping

For that workload, use supported hardware acceleration and verify the exact codec support of the GPU or iGPU.

Do not assume that a device advertised as “4K” supports every HEVC profile, bit depth, HDR format, audio codec and subtitle format.

---

Storage requirements

Use an SSD for:

• the operating system
• Jellyfin configuration
• metadata
• database files
• cache
• transcode temporary files where appropriate

Media can live on:

• internal HDD or SSD storage
• USB storage
• a NAS
• another Linux server
• a mounted network share

Capacity depends entirely on your library.

For performance, the important question is whether the storage can sustain the combined bitrate of the active streams plus background activity.

If Jellyfin cannot see mounted media, use Jellyfin Library Not Showing Files.

---

Network requirements

Use wired Ethernet for the server where possible.

For most home setups:

1Gb Ethernet: excellent default
2.5Gb Ethernet: useful for faster file transfers and larger homelabs
10Gb Ethernet: rarely required for Jellyfin alone

One high-bitrate stream is normally well within Gigabit Ethernet. Multiple clients, NAS traffic and other services share the same links, so reliable switching and cabling still matter.

Remote streaming is different. Your home upload speed can become the limiting factor and may force Jellyfin to transcode to a lower bitrate.

---

Docker and Proxmox requirements

Running Jellyfin inside Docker or a VM does not fundamentally change the playback workload, but the host must have enough resources for the virtualisation layer and other services.

For Docker:

• leave RAM and CPU headroom for other containers
• map media paths correctly
• pass the GPU device correctly if using hardware acceleration

For Proxmox:

• 16GB RAM is a more comfortable starting point if the host runs several VMs or LXCs
• plan GPU/iGPU access before relying on hardware transcoding
• do not allocate every CPU core or all host RAM to one guest

Use Run Jellyfin on Proxmox and Pass an Intel GPU Through to Jellyfin in Proxmox for the platform-specific setup.

---

Do you need a dedicated graphics card?

Usually not for a small Jellyfin home server.

A modern supported integrated GPU can provide excellent media-engine capability at much lower idle power than a gaming graphics card.

Consider a discrete GPU when:

• the existing CPU has no suitable iGPU
• the platform already contains a supported GPU
• you need more concurrent hardware-transcode capacity
• another workload also benefits from the GPU

Do not add a high-power GPU merely because one client is forcing unnecessary transcoding. Fix the compatibility reason first.

---

Buying checklist

Before buying a Jellyfin server, confirm:

• The CPU is 64-bit and supported by your chosen operating system.
• The machine has enough RAM for Jellyfin and the other services you plan to run.
• The system drive is an SSD.
• Media storage is large enough and reliably mounted.
• The server has Gigabit Ethernet or better.
• If transcoding matters, the iGPU/GPU supports the codecs you actually use.
• If buying Intel for Quick Sync, the processor has an integrated GPU.
• Your main clients support the formats in your library.
• Power use and noise make sense for an always-on server.
• You have a backup plan for Jellyfin configuration and important data.

---

Related guides

• Best Mini PC Specs for Jellyfin
• Jellyfin Direct Play: Formats, Clients and Transcoding
• Jellyfin Direct Play vs Transcoding
• Best Jellyfin File Format for Direct Play
• How to Check Why Jellyfin Is Transcoding
• Jellyfin Hardware Transcoding on Ubuntu
• Jellyfin on a Mini PC
• Jellyfin on Ubuntu

---

Recap

For most home users, Jellyfin does not require powerful server hardware when the clients Direct Play the media.

A practical default is an efficient 64-bit mini PC, 8GB of RAM, an SSD system drive, Gigabit Ethernet and reliable media storage. Choose a supported iGPU or GPU when real-time video transcoding is genuinely required.

Size the server around what must transcode, not the size of the media library alone.