There's no single right answer here, and anyone who gives you one number is guessing. A home server running Plex needs a fraction of what one running a dozen VMs needs. A NAS holding backups needs less than most forum threads claim. A box running local AI models needs a completely different kind of math altogether.

Here's the real number, broken down by what you're actually running.

Just Serving Files? You Need Less Than You Think

A plain file server, backup target, or basic NAS doesn't need much. 4 to 8 GB handles this comfortably for most home setups. The operating system, file sharing protocols, and basic backup jobs just aren't RAM-hungry.

If someone tells you a simple file server needs 32 GB or more, they're probably thinking of a different workload, or repeating advice meant for something bigger.

Running ZFS or TrueNAS? Ignore the "1GB Per TB" Rule

This is the single most repeated, most misleading rule of thumb in the whole homelab world.

The idea is that ZFS needs 1 GB of RAM for every terabyte of storage. Plenty of forum threads treat this as gospel. It isn't. That number actually comes from deduplication specifically, a RAM-hungry ZFS feature most home users never turn on. Skip dedup, and a comfortable TrueNAS box runs fine on 16 GB, regardless of whether you're storing 8 TB or 80 TB.

Server memory does still help ZFS, just not in the way the rule implies. More RAM means a bigger ARC, ZFS's read cache, and a bigger cache means faster repeated reads. That's a real benefit worth having. It's just not a hard requirement scaling directly with your drive count.

Running Plex or Jellyfin

Media servers are lighter than people expect. 4 GB is plenty for most home libraries, even fairly large ones.

The bigger lever here isn't RAM at all; it's whether transcoding happens on the CPU or gets offloaded to a GPU. Hardware transcoding barely touches system RAM. Software transcoding on an underpowered CPU can make a server feel sluggish long before RAM becomes the bottleneck.

Running Proxmox or ESXi With Several VMs

This is where the number actually starts climbing, and it climbs based on what you're running, not a fixed rule.

Each VM needs its own allocated RAM, on top of what the host itself uses. Three or four lightweight VMs, a Linux box here, a firewall appliance there, might fit comfortably in 32 GB. A more ambitious homelab running several services plus some headroom for testing new things usually wants 64 GB.

Buy more than your current plan needs if the budget allows it. Adding RAM later means matching modules exactly and sometimes buying a whole new set instead of just adding one stick, so a little headroom upfront usually saves a second purchase down the line.

Running Local AI Models

This is the newest category, and the one most homelab guides haven't caught up to yet.

Here's the part that surprises people: for local AI, VRAM on a graphics card matters far more than system RAM. Model size and speed are gated by VRAM first. System RAM mostly matters for what doesn't fit on the GPU, or for running a model on CPU alone, which works but runs much slower.

As a rough guide, figure on 1 to 2 GB of RAM per billion parameters at typical 4-bit quantization. A 7B model is comfortable around 8 to 16 GB. A 13B model wants closer to 16 to 32 GB. A 70B model, especially without a GPU carrying most of the load, wants 64 GB or more.

If local AI is the main reason you're speccing a new server, the graphics card is the decision that matters most. RAM is the secondary decision, not the primary one.

Running Everything at Once

Most home servers aren't doing just one of these. That's the scenario worth planning around.

Add these together rather than picking the single highest number. A box running TrueNAS, Plex, and a handful of Docker containers isn't one workload; it's three stacked on top of each other, and the RAM needs to stack too.

Frequently Asked Questions

Is 16 GB enough for a general-purpose home server?

For a single workload like file sharing or a modest Plex library, yes. Once you start layering in virtualization or local AI, 16 GB becomes a starting point rather than a destination.

Does more RAM always make a home server faster?

No, only up to the point where RAM was actually the bottleneck. A CPU-limited transcode or a VRAM-limited AI model won't speed up just because you added more system RAM.

Should I buy RAM based on what I need today, or what I might need later?

Some headroom is worth paying for, especially since matching modules later can be harder than buying enough the first time. Buying far beyond any realistic plan just to be safe usually isn't worth the cost.

Is ECC memory necessary for a home server?

Not required for most home use, though it's worth considering for a NAS holding data you can't afford to lose. That tradeoff gets its own full breakdown in a separate piece on ECC versus non-ECC memory.

Sizing Your Own Build

Skip the single universal number. Add up what you're actually running: a file server here, Plex there, a handful of VMs, maybe a local AI model, and size RAM against that real list instead of a forum rule of thumb built for someone else's setup.

Get the workload list right first. The RAM number follows from that, not the other way around.