Workload-based Unraid memory sizing
Unraid RAM Requirements: File Server, Docker and VMs
Unraid itself can run on modest hardware, but the applications people add to it can turn memory into the limiting resource. Docker containers, media servers, Immich, game servers, databases, ZFS pools and virtual machines all compete for the same RAM. This guide sizes the whole server instead of treating the NAS operating system as the only workload.
Quick answer
Buy RAM for the services you will run simultaneously
A basic file server can stay modest, while Docker-heavy systems and active VMs should move quickly into 32GB, 64GB or higher tiers. Unraid’s current VM guidance recommends 16GB or more for VM-oriented builds and says each active VM needs its own allocation. Leave host and filesystem headroom instead of assigning nearly all installed memory to guests.
Live Amazon hardware
Current hardware for this Unraid decision
Products come from this sprint's dedicated catalogue. NVMe, SATA SSD, RAM, PCIe NIC, DAC, optical and switch classes stay separate. Conflicting capacities, external SSDs, enclosures, USB NICs, complete computers and obvious wrong product types are rejected.
Buying decision
Count persistent services, peak VMs and filesystem cache separately
Add the memory needed by always-on containers, the peak concurrent VMs, and a comfortable host/storage reserve. If ZFS is used, remember that Unraid currently limits ZFS ARC to a reasonable portion of system RAM by default, so old one-gigabyte-per-terabyte folklore is not a valid purchasing rule.
Interactive decision tool
Unraid RAM Sizing Calculator
Use the inputs to narrow the hardware role before shopping. Results are planning guidance. Verify current Unraid behavior, motherboard lane sharing, exact SSD endurance, memory compatibility, NIC media and independent backups before deployment.
Compatibility checklist
Four checks before buying Unraid performance hardware
Cache and array are different paths
Fast cache can absorb writes at SSD speed, but Mover still has to drain data to the parity array later.
Measure before upgrading the network
2.5GbE or 10GbE only helps when the local pool, array or aggregate client workload can use the bandwidth.
Verify exact SSD and NIC details
NAND, DRAM, TBW, controller, connector and PCIe generation are shown only when the listing supports them.
Redundancy is not backup
Mirrored cache pools and parity protect specific hardware failures. Keep independent backups for valuable appdata, VMs and files.
Unraid OS is rarely the part that needs most of the memory
A storage-only server with a handful of shares can operate comfortably with far less memory than a system hosting applications and virtual machines. The operating system, filesystem cache and management layer need headroom, but the big memory consumers are usually workloads added afterward.
This means a blanket “Unraid needs X GB” answer is incomplete. Build a service inventory first, then size the host so the peak combination can run without swapping or starving storage caching.
Docker containers vary from tiny utilities to database-heavy applications
A DNS container and a media automation service can use modest RAM, while photo platforms, databases, search indexes and collaboration stacks can consume several gigabytes each. Memory also grows as libraries and users grow.
Check the real applications you plan to run and sum their steady-state usage with a reserve for upgrades and transient tasks. Do not estimate all containers as identical 512MB services.
Plex and Jellyfin usually care more about transcoding hardware than huge RAM
Media servers need memory for the application, metadata and transcode buffers, but ordinary direct playback does not demand enormous system RAM. Hardware transcoding capacity is often a more important limit than adding another 64GB.
Large metadata libraries, thumbnail generation and several related containers can still raise memory use. Size the complete media stack rather than Plex or Jellyfin in isolation.
Immich can turn a NAS into an application server
Immich combines database, thumbnail, machine-learning and media-processing services. On Unraid, those containers often live on the cache pool and can use meaningful CPU and memory during imports and indexing.
If the server will run Immich alongside media automation and other applications, 32GB can become a practical starting tier and 64GB may provide more comfortable growth, depending on the rest of the stack.
Virtual machines require explicit memory reservations
Unraid’s current VM guidance lists 8GB as the minimum system memory for VM capability and recommends 16GB or more, with additional memory allocated to each active guest. Lightweight servers may use 1–2GB, desktops 4–8GB and heavier GPU-passthrough guests more.
Plan for VMs that run simultaneously, not the total number defined. A host with four VMs that are never active together can need less RAM than two large guests running at the same time.
ZFS does not require one gigabyte per terabyte
Unraid’s ZFS documentation explicitly calls the old 1GB-per-1TB rule outdated for most users and notes that the system limits ZFS ARC to a reasonable share of total memory by default. More RAM can still improve cache effectiveness, but pool capacity alone does not dictate a fixed ratio.
Use working-set behavior, snapshots, applications and VM demands to decide whether additional memory will help. A huge cold-media pool can need less active memory than a much smaller VM-oriented ZFS pool.
BTRFS and XFS pools leave more memory to applications in many builds
BTRFS and XFS do not introduce the same ARC planning discussion as ZFS, but Linux still uses available memory for filesystem cache. Free memory on a healthy server is therefore not necessarily wasted.
The practical approach remains the same: keep a host reserve, watch real usage and avoid pinning every gigabyte to containers or VMs simply because the dashboard shows memory available.
Game servers can dominate memory even when storage is light
Minecraft, modded servers and other game workloads may use several gigabytes or tens of gigabytes independent of NAS storage size. A server hosting multiple game instances can therefore need a high RAM tier even if the Unraid array is modest.
Treat these services like application servers with their own player-count and mod requirements. Do not size them from drive count or cache capacity.
ECC is optional but platform support can be valuable
Unraid does not require ECC memory. For important data and always-on servers, ECC-capable platforms can still provide an additional layer against some memory errors, especially when the cost and motherboard support fit the build.
Do not buy an ECC DIMM assuming it will work in a consumer board. CPU, motherboard, firmware and module type must support the configuration. Cloudzat’s RAM catalogue therefore avoids claiming ECC behavior unless the listing explicitly provides it.
DIMM density affects the long-term upgrade path
Two 32GB modules can leave two slots open on a four-DIMM board, while four 16GB modules may force replacement to reach 128GB later. Higher-density DIMMs can cost more now but reduce future waste.
Check maximum supported memory, ranks, speeds and population rules for the exact motherboard. A cheap kit that consumes every slot can be expensive when the server grows.
Memory speed usually ranks below capacity and stability
Unraid workloads are diverse, but most file-serving and container builds gain more from sufficient stable capacity than from small differences in DDR transfer rate. Integrated GPU workloads can be more sensitive because they share system memory bandwidth.
Choose a speed supported by the CPU and motherboard, prioritize stability, and test the completed system thoroughly. Overclocked memory is rarely the best risk trade for a storage server holding valuable data.
Recalculate after adding a major workload
A server that starts as file storage can later add Home Assistant, Frigate, Immich, a Windows VM and game servers. Those changes can invalidate the original RAM plan even though the disk array is unchanged.
Review peak usage after major deployments. If the host is close to memory pressure during normal operations, increase RAM before adding more services or aggressive caching layers.
Questions people ask
Unraid memory questions
Is 8GB RAM enough for Unraid?
It can be enough for a basic file server, but Docker-heavy or VM-oriented systems should plan more headroom.
Is 16GB enough for Docker on Unraid?
For a modest container set, often yes. Database-heavy applications, photo platforms and multiple services can justify 32GB or more.
How much RAM should I use for Unraid VMs?
Add host headroom plus memory for the VMs that will run simultaneously. Unraid recommends 16GB or more for VM-oriented systems and each guest needs its own allocation.
Does Unraid ZFS need 1GB RAM per TB?
No. Unraid documentation describes that rule as outdated for most users and manages ARC to coexist with applications and the host.
Does Unraid require ECC memory?
No. ECC can be a valuable platform feature for data integrity, but it is not a software requirement.
Is 32GB enough for Plex and Docker?
Frequently, yes, depending on the number of containers, metadata size and other services. Heavy VMs or photo/AI workloads can move the target higher.
Should I buy 64GB for Immich on Unraid?
It can provide useful headroom when Immich runs alongside other services, but measure the total stack rather than treating 64GB as mandatory.
Does cache-pool size determine RAM needs?
Not directly. Workload, containers, VMs and filesystem behavior matter more than cache capacity alone.
Should I fill all DIMM slots?
Only if that layout fits the final expected capacity. Leaving slots open can make future upgrades cheaper.
Is faster DDR5 worth it for Unraid?
Usually supported capacity and stability matter more. Workloads using integrated graphics can benefit more from memory bandwidth than basic file serving.
Official references and methodology
Verify the exact Unraid and hardware behavior
The calculator sizes RAM from host reserve, Docker/app requirements, concurrent VMs, ZFS use and growth rather than pool terabytes alone. Marketplace memory remains a candidate until exact DDR generation, capacity, DIMM type and platform compatibility are verified.
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, model revisions, memory compatibility, SSD endurance, NIC firmware and marketplace conditions can change. Verify the exact part before purchase.