Remote users add upload-bandwidth demand and may also add conversion work when their devices, connection quality or selected playback quality cannot Direct Play the source file.
For households sharing one Plex server with family members or friends outside the local network.Requisitos de hardware para un servidor Plex: CPU, RAM, almacenamiento y transcodificación
Conoce los requisitos del servidor Plex para la reproducción directa, la transcodificación en 1080p y 4K, la transmisión remota y varios usuarios. Compara las configuraciones de ZimaBoard 2 y ZimaCube 2.
Plex server requirements at a glance
Start with how every client will play your files. Direct Play is light; video conversion is what usually determines processor and graphics demand.
- CPU
- Direct Play needs little processing. Software transcoding, simultaneous conversions and subtitle burn-in create the main CPU load.
- RAM
- Plex says 4 GB is typically more than sufficient for a typical installation. Choose more when ZimaOS also runs other apps or virtual machines.
- Storage
- Keep Plex metadata on responsive persistent storage and size the media library separately for capacity, redundancy, backup and future growth.
- Network
- Plan around the total bitrate of simultaneous streams plus safety headroom. Remote use is also limited by the server location's upload speed.
- Plex Pass
- An active Plex Pass is required for Plex hardware-accelerated streaming. Remote video playback access depends on the server and viewer account arrangement.
- Best Zima starting point
- Start with ZimaBoard 2 for lighter Direct Play workloads. Choose ZimaCube 2 for a growing multi-drive library, more services or recurring transcoding.
From official requirements to the right setup
Plex sizing starts with the official baseline, then changes according to client compatibility, conversion, simultaneous use, storage growth and the other services sharing ZimaOS.
-
Official requirements
Use Plex's published server guidance as the baseline: an Intel Core i3 or equivalent processor or faster, with 4 GB RAM typically more than sufficient for a typical installation.
-
Confirm your needs
Check every playback device and file. A compatible client can use Direct Play; incompatible video, audio, subtitles, quality settings or bandwidth can trigger conversion.
-
Leave room to grow
Plan Plex metadata, the media library, redundancy, backup, network capacity and additional ZimaOS services separately so one baseline number does not hide future demand.
-
Run it on ZimaOS
Install Plex from the ZimaOS App Store, map persistent media and metadata locations, create libraries and test local and remote playback with your own files and clients.
Check every playback client
- Video codec: H.264, HEVC or AV1
- Audio codec: AAC, AC3, DTS or TrueHD
- Container: MP4, MKV or another supported format
- Subtitle format and whether burn-in is required
- Resolution, bitrate and HDR support
- Local playback or remote playback
- Client app and playback-device compatibility
- Playback quality and bandwidth settings
Official minimum requirements
This table separates Plex's published server guidance from workload-dependent planning. The baseline does not promise that every codec, client or transcoding workload will run on the same hardware.
Use Intel Core i3 or equivalent performance as Plex's published CPU baseline. Plex says 4 GB RAM is typically more than sufficient for a typical installation; recurring conversion, other services and library growth determine the additional headroom.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | Intel Core i3 or equivalent performance, or faster | This is Plex's published recommendation. Actual demand rises with software transcoding, subtitle burn-in and simultaneous conversions. |
| Typical server memory | 4 GB is typically more than sufficient | Plex notes that some Linux installations can run with less. Add memory when ZimaOS also runs other apps, containers or virtual machines. |
| App and metadata storage | No fixed capacity published for every library | Reserve persistent storage for the Plex database, metadata, artwork, previews and logs; size it separately from the media library. |
| Media-library storage | Depends on your files and growth plan | Movies, TV, music, home video, redundancy and future additions determine the required capacity. RAID can improve availability but is not a backup. |
| Network | No single official minimum for every stream | Size local and remote capacity around actual media bitrate, simultaneous streams, Wi-Fi conditions and the server location's upload speed. |
| Hardware-accelerated streaming | Not required for Direct Play | Plex requires compatible hardware and an active Plex Pass for hardware-accelerated streaming. Codec, client and operating-system compatibility still matter. |
When to upgrade your hardware
Upgrade for a defined workload change, not simply because Plex is installed. The main pressure points are remote use, conversion and higher-resolution media.
More remote users
A client needs transcoding
Your library adds 4K, HEVC or HDR media
Upgrade when video, audio, subtitles, bandwidth or quality settings require Plex to convert content instead of using Direct Play. Software conversion can buffer when the CPU cannot keep up.
For users with mixed client support, subtitle burn-in or recurring remote conversion.Higher-resolution and HEVC workloads can require more processing when conversion is needed. Hardware acceleration can reduce CPU load, but codec, resolution, HDR, subtitles and client support still determine the result.
For users adding higher-bitrate media or converting content for less capable clients.Plan hardware growth with confidence
Plex can grow in several independent directions. Plan the media, network and always-on system around the data you cannot replace and the services you intend to keep online.
Protect the media library
Choose drive capacity and redundancy for the current library and expected growth. RAID improves availability but does not replace an independent backup, especially for family video and photos.
Keep at least one separate copy of irreplaceable media and back up Plex metadata when preserving watch state and library organization matters.Size local and remote networking
Estimate required capacity from the total bitrate of simultaneous streams plus safety headroom. Evaluate wired LAN, Wi-Fi, remote upload speed and every remote user's playback quality separately.
Do not choose a single Mbps promise without checking the bitrate of the actual files and testing the intended clients.Plan for 24/7 operation
Consider idle power, cooling, fan and drive noise, drive sleep behavior, automatic startup, recovery after an outage and whether critical storage needs UPS protection.
Place the server where it can stay cool, connected and available without making the living space noisy.Leave room for other ZimaOS apps
Plex shares CPU, memory, storage I/O and network capacity with photo apps, backups, home automation, containers and virtual machines running on the same system.
Add memory and compute headroom for the services that will actually run at the same time instead of sizing for Plex alone.Can it run on ZimaOS?
Plex is available through the ZimaOS App Store. The practical setup work is to attach persistent storage, create libraries and verify playback with the clients and files you actually use.
Install from the ZimaOS App Store
Install Plex, open its web interface and complete the initial server setup with your own Plex account.
Open Plex in the ZimaOS App StoreMap media and metadata storage
Attach the disk or folder that contains your media and use persistent storage for the Plex database and metadata before building libraries.
Read the Plex setup guideTest Direct Play, remote access and acceleration
Test representative files on each client. Enable hardware acceleration only after confirming Plex Pass, compatible hardware, drivers, formats and the intended playback path.
Read Plex hardware acceleration guidanceChoose Zima hardware for your Plex workload
Confirm Direct Play, conversion, simultaneous use, storage growth and the other ZimaOS services first. Then choose the smallest configuration with enough headroom for the real workload.
Will every important client Direct Play your media?
Yes — Direct Play is expected
Prioritize reliable networking, metadata storage and media capacity; processor demand is usually modest.
- Plex only or light additional appsZimaBoard 2 832
- Several ZimaOS apps or more memory headroomZimaBoard 2 1664
No — recurring transcoding is expected
Choose more processor and acceleration headroom, then validate the codecs, clients and number of simultaneous conversions you expect.
- Occasional supported conversion and a growing libraryZimaCube 2 Standard
- Multiple users plus other always-on servicesZimaCube 2 Pro
- Plex plus GPU, AI or heavy virtual machinesZimaCube 2 Creator Pack
This is a workload guide, not a guaranteed stream-count benchmark. Results depend on codecs, bitrate, subtitles, client support, Plex settings, drivers and the selected hardware configuration.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A compact Plex server focused on Direct Play and a small number of light ZimaOS services. | Local Direct Play, light remote use after testing and externally attached media storage. |
|
Do not treat it as a guaranteed multi-stream 4K transcoding appliance. | Get Now |
| ZimaBoard 2 1664 | Direct Play plus more ZimaOS apps, containers or memory headroom in the same compact form factor. | Plex alongside backups, home services or a larger metadata workload when recurring heavy conversion is not the goal. |
|
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 Plex library with occasional supported conversion and room for storage expansion. | Direct Play across several clients, media management and occasional conversion after compatibility testing. |
|
Add memory or select a higher configuration when several other services will run beside Plex. | Get Now |
| ZimaCube 2 Pro | Multiple users, a large library and more always-on ZimaOS services with additional processor and memory headroom. | Concurrent Plex use, supported hardware conversion and other self-hosted services after testing the real media set. |
|
It is additional headroom, not a promise of a fixed number of 4K streams. | Get Now |
| ZimaCube 2 Creator Pack | Plex combined with GPU workloads, local AI, heavy virtual machines or creator workflows. | A mixed server where Plex is only one part of a much heavier compute and storage environment. |
|
Usually excessive for a Plex-only Direct Play server; choose it for the additional GPU, AI or VM workload. | 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 and migration questions that are not fully addressed in the sections above.
Do I need Plex Pass to use Plex on ZimaOS?
No. You can install and use Plex Media Server without Plex Pass. An active Plex Pass is required for Plex hardware-accelerated streaming. For remote video playback, access also depends on whether the server administrator has Plex Pass or the viewer has Plex Pass or Remote Watch Pass under Plex's current policy.
Which Zima device should I choose for Plex?
Choose ZimaBoard 2 832 for a light Direct Play-focused server, ZimaBoard 2 1664 when the same compact server also needs more memory for other apps, ZimaCube 2 Standard for a growing multi-drive library and occasional supported conversion, and ZimaCube 2 Pro for more users and services. Creator Pack is intended for Plex combined with GPU, AI or heavy virtual-machine workloads.
Can ZimaBoard 2 run 4K Plex?
It can serve compatible 4K files through Direct Play, but 4K playback is not the same as 4K transcoding. The result depends on the video and audio codecs, subtitles, bitrate, HDR, client support and connection quality. Test representative files and move to ZimaCube 2 when recurring conversion is part of the workload.
Does Plex need 10GbE?
Usually not for ordinary playback. Size the network from the combined bitrate of simultaneous streams plus safety headroom. Faster networking becomes more useful for large media imports, backups, multiple high-bitrate local users and other file services sharing the server; remote playback is still constrained by internet upload speed.
Can subtitles force Plex to transcode?
Yes. Some subtitle formats or client combinations require subtitle burn-in, which can trigger video transcoding even when the video file would otherwise Direct Play. Test the subtitle formats used by the library on every important playback client.
How much internet upload speed do I need for remote Plex?
Plan from the total bitrate of simultaneous remote streams plus headroom and test the real connection in both directions. Automatic remote access normally uses TCP port 32400 internally, while a manually selected external port may differ. Plex Relay can help when a direct connection is unavailable, but its stream bandwidth is limited and it should not replace proper network planning.
Can I move my existing Plex library to ZimaOS?
Yes, but preserve the existing Plex data directory and media paths carefully. Back up the server data first, stop the old server before copying, map persistent locations in ZimaOS, keep file permissions readable and follow Plex's migration guidance so metadata and watch history are not lost.
Where should Plex metadata be stored?
Use persistent, responsive storage with enough space for the database, artwork, thumbnails, previews and logs. Keep it separate from disposable container storage, back it up if watch history and library organization matter, and do not assume the media library's RAID arrangement automatically protects Plex metadata.
What sources and further reading informed this Plex hardware guide?
The official Plex documentation is the primary reference for requirements and features. The following independent articles and forum discussions provide additional planning perspectives; they are listed for further reading and do not replace current official documentation or testing with your own files and clients.
