Search for how much RAM a Proxmox server needs and you’ll usually get a number.
16 GB is enough.
Get 32 GB to be safe.
64 GB if you’re serious.
That’s not really how it works.
Proxmox itself isn’t usually the reason you need a lot of memory. What matters is what you’re going to run on top of it, what you’re doing with storage, and how much room you want to leave for things you haven’t added yet.
So instead of starting with:
Should I buy 16 GB or 32 GB?
Start with:
What am I actually going to run?
Start with the host
Proxmox doesn’t automatically require a huge amount of RAM.
The official Proxmox VE system requirements recommend at least 2 GB for the OS and Proxmox services, plus the memory required by your guests.
That’s the important part.
A more useful way to think about the machine is:
RAM budget =
Proxmox host
- VMs
- containers
- storage overhead
- headroom
The host is only one piece of it.
Then add the actual workloads
This is where two people asking “how much RAM for Proxmox?” can get completely different answers.
Take a small home server running something like:
- Home Assistant
- Pi-hole or AdGuard Home
- a few lightweight containers
You don’t need 64 GB just because Proxmox is involved.
16 GB can be a perfectly reasonable place to start for a light setup.
Now change the workload:
- Home Assistant
- Jellyfin
- Immich
- several containers
- one or two VMs
Suddenly 32 GB starts making a lot more sense.
Not because Proxmox changed.
The workload did.
And if the point of the machine is to run several Windows/Linux VMs, databases, Kubernetes experiments, test environments, and whatever you decide to install next weekend, memory can disappear surprisingly quickly.
These aren’t hard requirements.
They’re planning examples.
That’s the distinction that gets lost when the answer is just:
“Buy 32 GB.”
VMs make the calculation easier to see
Suppose you have 32 GB.
It sounds like a lot until you start dividing it up.
Proxmox host
↓
Linux VM
↓
Windows VM
↓
Home Assistant
↓
containers
↓
storage/cache
↓
room for the next thing
You don’t necessarily use all allocated memory all the time, and technologies like memory ballooning can make utilization more flexible.
But you still need to plan around what happens when several workloads actually need memory at once.
That’s why I’d rather have some headroom than build a machine that only works when everything behaves exactly as expected.
Storage changes the calculation too
RAM isn’t only for VMs and containers.
If you’re planning to use ZFS, storage becomes part of the memory discussion as well.
Proxmox explicitly notes additional memory requirements for ZFS and Ceph.
You’ll also see this rule repeated everywhere:
ZFS needs 1 GB of RAM per TB of storage.
It’s better treated as a rough planning heuristic than a law.
ZFS uses RAM for ARC caching, and its behavior can be configured. The exact amount of memory you should dedicate to it depends on the system and workload.
The useful takeaway isn’t:
I have 12 TB, therefore I mathematically require exactly 12 GB for ZFS.
It’s:
Storage also consumes resources, so don’t calculate your entire RAM budget from VM allocations alone.
But RAM might not be your problem
This is where I think hardware discussions get more interesting.
Let’s say you work through your services and decide:
32 GB is enough.
Great.
That still doesn’t tell you which machine to buy.
Maybe you’re running Jellyfin and need hardware transcoding.
Maybe Immich adds enough processing that CPU performance matters more than you expected.
Maybe you want ZFS across four physical drives.
Now the problem isn’t RAM.
It’s drive bays.
Or SATA ports.
Or PCIe expansion.
Maybe you want faster networking.
Now you’re looking for 2.5GbE or 10GbE.
Maybe the tiny mini PC with the better benchmark score can’t physically support the storage configuration you want.
Meanwhile, a boring used office PC can.
So the question changes again.
It’s no longer:
How much RAM do I need?
It’s:
What is likely to limit this server first?
That’s a much more useful question.
Work backwards from the workload
I’ve started thinking about home-server hardware in this order:
Workload
↓
CPU / RAM / storage / network requirements
↓
Likely limitation
↓
Hardware
Not:Cool mini PC
↓
Buy it
↓
Figure out what fits
It sounds obvious when written out.
But a lot of hardware shopping happens the second way.
You see an N150 mini PC for a good price.
Or a Ryzen mini PC with a great benchmark.
Then you start asking:
Can this run Jellyfin?
Can I add Immich?
What about three VMs?
Can I use ZFS?
How do I attach four drives?
The hardware decision already happened.
Now you’re trying to make the workload fit it.
I built a small planner for this
I got tired of doing the calculation backwards, so I built a small Home Server Build Planner.
You select what you want the server to run, what matters for storage, whether you’re willing to use existing hardware, and a few other constraints.
It then gives you a starting direction based on the workload rather than asking you to choose a CPU first.
try the Home Server Build Planner
It’s not a benchmark database and it’s not supposed to tell you that one specific machine is universally “the best.”
The point is to narrow the decision before you start comparing hardware.
So: 16 GB, 32 GB, or 64 GB?
There still isn’t one answer.
For a lightweight Proxmox box, 16 GB can be plenty.
For a mixed home server with several services and some VMs, 32 GB gives you considerably more room.
For a VM-heavy lab or a machine you’re deliberately building with room to grow, 64 GB may make sense.
But I’d decide that after listing the workloads.
Because buying 64 GB doesn’t fix a CPU that can’t handle your workload.
It doesn’t add drive bays.
It doesn’t add SATA ports.
It doesn’t give you faster networking.
And it doesn’t turn a machine designed around one kind of workload into the right machine for another.
RAM is one constraint.
Figure out the workload first.
Then figure out which constraint matters.
Then buy the hardware.
Sources: Proxmox publishes its current hardware requirements and ZFS guidance in its official documentation:Proxmox VE system requirements and Proxmox VE documentation