Upgrade when clients frequently cannot Direct Play high-resolution media. HDR-to-SDR tone mapping and full video conversion are much heavier than Direct Play; supported Dolby Vision profiles also depend on the specific playback and tone-mapping path.
For libraries with 4K HDR, HEVC, supported Dolby Vision profiles or mixed client compatibility.Hardwareanforderungen für Jellyfin-Server: CPU, RAM, Speicher und 4K-Transkodierung
Erfahren Sie mehr über die Serveranforderungen von Jellyfin für Direct Play, 1080p- und 4K-Transkodierung, HDR-Tonemapping, Remote-Streaming und die passende ZimaOS-Hardware.
Jellyfin server requirements at a glance
Start with client compatibility. Direct Play adds very little server load; video transcoding, subtitle burn-in and HDR-to-SDR tone mapping are what usually determine CPU and GPU demand.
- CPU
- Jellyfin recommends modern Intel processors with supported integrated graphics, Apple silicon, or a suitable dedicated GPU for a good server experience. Direct Play is light; software video transcoding is CPU-intensive.
- RAM
- Jellyfin recommends 8 GB system RAM for servers using integrated graphics. More memory is useful when ZimaOS also runs containers, virtual machines or other services.
- Storage
- Jellyfin recommends about 100 GB of SSD capacity for the OS, Jellyfin files and transcoding cache. Size the media library separately for capacity, redundancy, backup and growth.
- Network
- Jellyfin recommends Gigabit Ethernet or faster and at least 20 Mbps upload bandwidth for remote access. Actual demand depends on simultaneous stream bitrates.
- Hardware acceleration
- Jellyfin supports hardware-accelerated transcoding on several GPU platforms, including Intel, NVIDIA, AMD, Apple and Rockchip. Support does not mean every platform is equally recommended for a new server, and ZimaOS device access must be verified before relying on acceleration.
- Best Zima starting point
- For mostly Direct Play workloads, start with ZimaBoard 2 only when paired with adequate SSD storage for Jellyfin data and cache. Choose ZimaCube 2 when you need a larger multi-drive library, more services or recurring hardware-accelerated transcoding.
From official requirements to the right setup
Jellyfin sizing starts with its published recommended hardware, then changes according to client codec support, transcoding, HDR tone mapping, simultaneous streams, storage growth and other ZimaOS services.
-
Official requirements
Use Jellyfin's published recommended hardware as the planning baseline: 8 GB RAM for integrated-graphics servers, about 100 GB SSD capacity for the OS, Jellyfin files and transcoding cache, Gigabit Ethernet or faster, and at least 20 Mbps upload bandwidth for remote access.
-
Confirm your needs
Check representative files on every important client. Direct Play is the lightest path; unsupported containers, audio, subtitles or video codecs can trigger remuxing, audio conversion or full video transcoding.
-
Leave room to grow
If video conversion is expected, select a supported hardware-acceleration path and verify the complete stack: GPU capability, host driver, device exposure to the container, permissions, Jellyfin FFmpeg support, codecs, subtitles and HDR tone mapping.
-
Run it on ZimaOS
Install Jellyfin from the ZimaOS App Store, map persistent media, configuration and cache storage, then test local playback, remote playback and hardware acceleration with your own library.
Check every playback client
- Video codec: H.264, HEVC, VP9 or AV1
- Bit depth, HDR and supported Dolby Vision profiles
- Audio codec and channel format
- Container: MP4, MKV or another supported format
- Subtitle format and whether burn-in is required
- Resolution, bitrate and frame rate
- Local or remote playback and number of simultaneous streams
- Client app, browser and playback-device codec support
Official minimum requirements
Jellyfin publishes recommended hardware for a good experience rather than one universal minimum specification. The table below separates those published recommendations from workload-dependent planning for media storage and transcoding.
Treat 8 GB RAM, about 100 GB SSD capacity, Gigabit Ethernet and at least 20 Mbps upload for remote access as Jellyfin's recommended planning baseline, not a universal minimum. Direct Play can run on lighter compute; recurring video transcoding, subtitle burn-in and HDR tone mapping justify stronger acceleration hardware.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Integrated-graphics CPU | Modern Intel CPUs with supported integrated graphics are a strong new-server option; Jellyfin lists examples such as Core i5-11400, Pentium Gold G7400 and Intel N100 | The official hardware-selection guide distinguishes between supported platforms and preferred choices for new purchases. Actual transcoding capability depends on GPU generation, codec support and software configuration. |
| System memory | 8 GB RAM recommended | Jellyfin recommends 8 GB for integrated-graphics servers and dedicated-GPU servers; 4 GB may be sufficient for a Linux dedicated-GPU server without its own GUI. |
| OS, app and transcode storage | About 100 GB SSD capacity recommended | Jellyfin recommends this space for the operating system, Jellyfin files and transcoding cache. Large source files and several concurrent transcodes can require more cache headroom. |
| Media-library storage | Depends on your files and retention plan | Movies, TV, music, home video, redundancy and future additions determine capacity. Keep irreplaceable media and Jellyfin configuration protected by an independent backup plan. |
| Local and remote network | Gigabit Ethernet or faster; at least 20 Mbps upload for remote access | Jellyfin does not recommend Wi-Fi or Powerline for the server connection. Size real bandwidth from the total bitrate of simultaneous streams plus headroom. |
| Hardware acceleration | Not required for Direct Play | A supported GPU can greatly reduce CPU load during video transcoding. Hardware acceleration is especially valuable for 4K conversion and HDR-to-SDR tone mapping, but the complete driver/container/application path must work. |
When to upgrade your hardware
Upgrade for a defined Jellyfin workload change rather than simply because the server stores more files. The strongest triggers are recurring conversion, HDR tone mapping and simultaneous users.
Recurring 4K, HEVC, HDR or supported Dolby Vision transcoding
More simultaneous remote users
Jellyfin shares the server with more services
More users increase upload-bandwidth demand and may create several simultaneous transcodes when remote devices or connections cannot accept the original media bitrate or codec.
For households sharing one Jellyfin server across several local and remote devices.Background scans, backups, photo apps, containers, virtual machines and file transfers compete with Jellyfin for CPU, memory, storage I/O and network capacity.
For ZimaOS systems evolving from a dedicated media server into a broader home server.Plan hardware growth with confidence
Treat Jellyfin application data, transcode cache, media capacity and network bandwidth as separate resources. This makes it easier to grow the library without turning one bottleneck into a full server replacement.
Keep Jellyfin data and cache on responsive storage
Use persistent SSD storage for Jellyfin configuration, database, metadata and transcode cache. Jellyfin's hardware guide recommends about 100 GB of SSD capacity for the OS, Jellyfin files and transcode cache.
On ZimaBoard 2, the onboard 32 GB or 64 GB eMMC alone is below that recommended capacity. Plan additional SSD storage, and avoid placing heavy transcode-cache activity on undersized system storage.Protect the media library and server data
Size media drives for current capacity, redundancy and expected growth, and back up Jellyfin data before major upgrades. Jellyfin's built-in backup can preserve its database, metadata, subtitles and Trickplay data.
RAID can improve availability but does not replace an independent backup of irreplaceable media or Jellyfin configuration.Size local and remote networking
Use a wired server connection and estimate bandwidth from the combined bitrate of simultaneous streams. Jellyfin recommends at least 20 Mbps upload for remote access and Gigabit Ethernet or faster for the server.
Faster LAN becomes more useful for large media imports, backups and multiple high-bitrate local users, while remote playback is still limited by internet upload.Leave headroom for other ZimaOS apps
Jellyfin shares resources with backups, photo management, home automation, downloaders, databases, containers and virtual machines running on the same ZimaOS server.
Choose additional memory, CPU and storage-I/O headroom for the services that will actually run at the same time.Can it run on ZimaOS?
Jellyfin is available in the ZimaOS App Store. The practical setup is to map persistent media, configuration and cache storage correctly, then verify the complete hardware-acceleration path inside the running Jellyfin container with representative files.
Install Jellyfin from the ZimaOS App Store
Install Jellyfin, open its web interface and complete the first-run setup before creating media libraries.
Open Jellyfin in the ZimaOS App StoreMap media, configuration and cache storage
Attach or mount the folders containing your media and keep Jellyfin configuration and cache on persistent storage. Verify that the container can read the media paths before starting a large library scan.
Read the Jellyfin setup guideVerify hardware acceleration end to end
Do not assume that a CPU with Quick Sync automatically means Jellyfin hardware transcoding is active in ZimaOS. Confirm the graphics device is exposed to the container, permissions and drivers are correct, Jellyfin detects the accelerator, and a real test transcode uses the intended hardware path.
Read the ZimaOS hardware acceleration guideChoose Zima hardware for your Jellyfin workload
Confirm Direct Play compatibility, recurring transcodes, subtitle burn-in, HDR tone mapping, simultaneous users, storage growth and other ZimaOS services first. Then choose the smallest configuration with enough SSD capacity, media storage and verified acceleration headroom.
Will your important clients Direct Play most of your media?
Yes — Direct Play is the normal path
Prioritize reliable wired networking, adequate SSD space for Jellyfin data and cache, and the media capacity you need. Compute demand is usually modest.
- Mostly Direct Play, paired with at least ~100 GB SSD capacityZimaBoard 2 832 + SSD
- Mostly Direct Play plus more ZimaOS apps, paired with SSDZimaBoard 2 1664 + SSD
No — recurring video transcoding or HDR tone mapping is expected
Choose stronger and verified hardware acceleration, then validate codecs, subtitles, HDR formats and simultaneous conversions. Move to a dedicated GPU only when that workload is explicit.
- Regular supported video transcoding and a growing multi-drive libraryZimaCube 2 Standard
- More simultaneous transcodes, tone mapping and other always-on servicesZimaCube 2 Pro
- Dedicated GPU, CUDA/AI or heavy VM workload in addition to JellyfinZimaCube 2 Creator Pack
This is a workload guide, not a guaranteed stream-count benchmark. Results depend on codecs, bitrate, subtitles, HDR and Dolby Vision behavior, client support, Jellyfin settings, drivers, container GPU access and the selected hardware configuration.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A compact Jellyfin server focused on Direct Play, provided you add adequate SSD capacity for Jellyfin data and transcode cache. | Mostly local Direct Play, a small number of clients and light additional ZimaOS services, with media on SATA or other appropriate persistent storage. |
|
Do not treat the base 32 GB eMMC configuration as meeting Jellyfin's recommended SSD capacity, and do not advertise a fixed 4K transcode count without workload testing. | Get Now |
| ZimaBoard 2 1664 | Direct Play plus more ZimaOS apps, containers or memory headroom in the same compact form factor. | Jellyfin alongside backups, automation or other containers when the media workload is primarily Direct Play with occasional tested conversion. |
|
Choose it for memory and app headroom, not as an automatic transcoding upgrade over the 832. | Get Now |
| ZimaCube 2 Standard | A growing multi-drive Jellyfin library with more storage integration and stronger Intel CPU/GPU headroom for supported hardware transcoding. | Several Direct Play clients, media management and recurring supported conversion after testing the actual codecs, subtitles and HDR formats. |
|
Hardware capability does not by itself prove the Jellyfin container is using acceleration. Validate the actual ZimaOS/Jellyfin path before publishing stream-count claims. | Get Now |
| ZimaCube 2 Pro | More Jellyfin users, a large library and additional always-on ZimaOS services with stronger CPU, memory and network headroom. | Concurrent media use, supported hardware transcoding, large imports and other self-hosted services running beside Jellyfin. |
|
Additional CPU, memory and media-engine headroom is not a guarantee of a fixed number of 4K, HDR or subtitle-burn-in transcodes. | Get Now |
| ZimaCube 2 Creator Pack | Jellyfin combined with a real dedicated-GPU requirement, local AI, CUDA workloads, heavy virtual machines or creator workflows. | A mixed server where Jellyfin can use a dedicated NVIDIA acceleration path while the system also handles heavier compute and storage tasks. |
|
Usually excessive for a Jellyfin-only Direct Play server. Choose it because the dedicated GPU, AI, CUDA or VM workload is required, not simply because the Jellyfin library is larger. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers cover purchase, playback, networking and migration questions that are not fully addressed in the sections above.
Does Jellyfin require a subscription for hardware transcoding?
No. Jellyfin includes supported hardware acceleration without a paid pass. You still need compatible graphics hardware, the correct drivers or device access, and the appropriate QSV, VA-API, NVENC or other acceleration configuration for the server platform.
Which Zima device should I choose for Jellyfin?
Choose ZimaBoard 2 832 for a compact Direct Play-first server only when you add adequate SSD capacity; choose 1664 when the same system also needs more memory for other apps. Choose ZimaCube 2 Standard for a growing multi-drive library and regular supported Intel-accelerated transcoding, Pro for more concurrent media work plus other services, and Creator Pack only when a dedicated NVIDIA GPU, AI, CUDA or heavy VM workload is part of the requirement.
Can ZimaBoard 2 run 4K Jellyfin?
It can serve compatible 4K files through Direct Play, and the Intel N150 has Quick Sync-capable integrated graphics. That does not guarantee a specific 4K transcode count in ZimaOS. Actual results depend on codec, bitrate, HDR, supported Dolby Vision profile, subtitles, client support, drivers, container GPU access and Jellyfin's acceleration configuration.
How much RAM does a Jellyfin server need?
Jellyfin recommends 8 GB system RAM for a server using integrated graphics. More memory is mainly useful when the same machine also runs other apps, containers, virtual machines or memory-heavy services rather than as a direct way to increase the GPU's transcoding capability.
Does Jellyfin need a GPU?
Not for Direct Play. A supported GPU becomes valuable when Jellyfin must transcode video, burn in subtitles or tone-map HDR content. For demanding HDR-to-SDR tone mapping, hardware acceleration is strongly preferred over software-only processing.
How much upload speed do I need for remote Jellyfin?
Jellyfin recommends at least 20 Mbps upload bandwidth for remote access. If total upload is below 100 Mbps, its hardware guide recommends setting Jellyfin's bandwidth limit to about 70% of the available upload so other internet activity retains headroom. The actual requirement still depends on the total bitrate of simultaneous remote streams.
Can subtitles force Jellyfin to transcode?
Yes. Unsupported subtitle formats or client combinations can require subtitle burn-in, which can trigger full video transcoding even when the video codec itself would otherwise be compatible. Because subtitle handling is client- and format-dependent, test the formats used by your library.
Can I back up or move an existing Jellyfin server to ZimaOS?
Yes, but preserve Jellyfin data carefully and keep media paths consistent where possible. Jellyfin 10.11 includes a built-in backup and restore system for its database, metadata, subtitles and Trickplay data. Back up before major upgrades or migration, then map persistent configuration and media paths correctly in ZimaOS.
What sources and further reading informed this Jellyfin hardware guide?
Jellyfin's official hardware-selection and hardware-acceleration documentation provide the primary technical baseline for CPU, memory, storage, networking and transcoding. Jellywatch and RapidSeedbox add current planning context for Jellyfin server sizing and transcoding, while the Linus Tech Tips discussion provides a community perspective on building a server for multiple users. The XDA migration guide adds practical context for users moving an existing Plex library to Jellyfin. These sources should be used together with testing on the actual clients, codecs, subtitles, network conditions and ZimaOS hardware configuration.
