How Much RAM Do You Need for a Home Server? — Complete Guide | Mini PC Lab
By Mini PC Lab Team · January 27, 2026 · Updated March 27, 2026
This article contains affiliate links. If you purchase through our links, we may earn a commission at no extra cost to you. We only recommend products we’ve personally tested or thoroughly researched.
The right amount of RAM for your home server depends entirely on your workload. 8GB is the floor. 16GB handles most setups comfortably. 32–64GB is for serious multi-VM Proxmox environments. This guide gives you specific numbers for every common homelab use case.
Quick Answer by Workload
| Workload | Minimum | Comfortable | Overkill |
|---|---|---|---|
| Pi-hole only | 1GB | 4GB | 8GB |
| Pi-hole + Home Assistant | 2GB | 8GB | 16GB |
| Docker (5–8 containers) | 8GB | 16GB | 32GB |
| Docker (10–15 containers) | 16GB | 32GB | 64GB |
| Proxmox (2–4 VMs) | 8GB | 16GB | 32GB |
| Proxmox (5–8 VMs) | 16GB | 32GB | 64GB |
| Proxmox (8–12 VMs) | 32GB | 64GB | 96GB |
| TrueNAS SCALE / ZFS | 8GB | 16GB | 1GB/TB storage |
| Plex (software transcode) | 4GB | 8GB | 16GB |
| Local AI (7B model) | 8GB | 16GB | 32GB |
| Local AI (13B model) | 16GB | 32GB | 64GB |
Why RAM Matters for a Home Server
RAM is the most common bottleneck in homelab setups. Unlike a workstation where you can tolerate occasional slowdowns, a home server running 24/7 hits RAM limits consistently when undersized.
When RAM is the bottleneck:
- Containers start paging to disk (swapping) — causing slowdowns across all services
- Proxmox VMs with oversized RAM allocations compete and thrash
- ZFS ARC cache shrinks, causing more disk reads and slower NAS performance
- OS overhead grows with each additional service, leaving less for applications
The right approach: calculate your expected RAM usage, add 30% headroom for growth, then buy that amount.
Docker Container RAM Usage
Docker containers share the host OS kernel and are memory-efficient. A typical container uses 50–500MB, far less than a full VM.
Per-container RAM estimates:
| Container | Typical RAM |
|---|---|
| Pi-hole | 64–128MB |
| Vaultwarden | 64–128MB |
| Uptime Kuma | 64–128MB |
| Home Assistant | 256–512MB |
| Nginx Proxy Manager | 128–256MB |
| Portainer | 128–256MB |
| Nextcloud (web) | 256–512MB |
| Nextcloud (database) | 256–512MB |
| Gitea | 256–512MB |
| n8n | 256–512MB |
| Immich (app) | 512MB–1GB |
| Immich (machine learning) | 512MB–2GB |
| Plex | 512MB–2GB |
| Jellyfin | 256–512MB |
| Sonarr / Radarr | 256–512MB each |
Example Docker stack calculations:
Basic home stack (Pi-hole + HA + Vaultwarden + Nginx PM + Portainer): ~1.2GB active + 2GB OS overhead = 8GB is comfortable
Media server stack (above + Plex + Sonarr + Radarr + Prowlarr + qBittorrent): ~4GB active + 2GB OS overhead = 16GB is comfortable
Full self-hosted stack (20 containers including Nextcloud, Immich, Gitea): ~8–10GB active + 2GB OS overhead = 16–32GB needed
Proxmox VM RAM Requirements
Virtual machines allocate RAM statically — the amount assigned to a VM is unavailable to the host. Plan carefully.
Typical VM RAM allocations:
| VM Type | Minimum | Comfortable |
|---|---|---|
| Lightweight Debian/Ubuntu container | 512MB | 1GB |
| Ubuntu Server with services | 1GB | 2–4GB |
| OPNsense / pfSense | 1GB | 2–4GB |
| TrueNAS SCALE | 8GB | 16GB+ |
| Home Assistant OS | 2GB | 4GB |
| Windows 10/11 VM | 4GB | 8–16GB |
| Frigate NVR | 2GB | 4GB |
Proxmox host overhead: Reserve 2GB for the Proxmox hypervisor itself. The formula:
Required RAM = Sum(all VM allocations) + 2GB Proxmox overheadExample Proxmox builds:
Light Proxmox server (3 VMs: OPNsense 2GB + Ubuntu Docker 8GB + Home Assistant 2GB): 2 + 8 + 2 + 2 = 14GB → buy 16GB
Medium Proxmox server (5 VMs: OPNsense 2GB + TrueNAS 8GB + Docker 8GB + HA 2GB + Dev 4GB): 2 + 8 + 8 + 2 + 4 + 2 = 26GB → buy 32GB
Dense Proxmox server (8 VMs averaging 4GB each): 32 + 2 = 34GB → buy 64GB
TrueNAS SCALE and ZFS
ZFS uses RAM for the Adaptive Replacement Cache (ARC) — frequently accessed data lives in RAM, dramatically improving read performance. The ARC grows to fill available RAM (up to a configured maximum) and shrinks when other processes need memory.
ZFS RAM guidelines:
- Minimum: 8GB (ZFS recommends at least 8GB for reliable operation)
- Rule of thumb: 1GB RAM per 1TB of storage
- Example: 4-drive mirror with 4TB usable → 8–16GB RAM is appropriate
Below 8GB, ZFS ARC is too small for effective caching and performance suffers. Above the 1GB/TB guideline, additional RAM improves cache hit rates with diminishing returns.
For TrueNAS in a Proxmox VM: allocate 8–16GB to the VM depending on storage size, and ensure the VM has hardware disk passthrough (not virtual disks) for ZFS to function correctly.
Plex and Jellyfin RAM
Plex and Jellyfin RAM usage is driven primarily by the number of simultaneous transcoding streams and library size.
- Direct play (no transcoding): ~256MB per active stream
- 1080p software transcode: ~512MB–1GB per stream
- 4K software transcode: ~1–2GB per stream
- Hardware transcode (Quick Sync / VCN): Minimal RAM overhead (~256MB)
For most setups with hardware transcoding enabled:
- 1–3 simultaneous streams: 8GB total is comfortable
- 4–6 simultaneous streams: 16GB for headroom
Plex also indexes metadata into RAM for fast library browsing. Large libraries (10,000+ items) use more RAM for the metadata cache.
Local AI (Ollama)
LLM models load entirely into memory for inference — either RAM or GPU VRAM. On mini PCs with AMD Radeon iGPUs, the GPU uses shared system DDR5 memory.
Model sizes at common quantizations:
| Model | Quantization | Memory Required |
|---|---|---|
| Llama 3.2 3B | Q4 | ~2.2GB |
| Llama 3.1 8B | Q4 | ~4.5GB |
| Llama 3.1 8B | Q8 | ~8.5GB |
| Gemma 3 9B | Q4 | ~6GB |
| Llama 3.1 70B | Q4 | ~42GB (CPU only) |
Example on a SER9 PRO+ with 32GB LPDDR5X (soldered):
- OS overhead: ~4GB
- 7B Q4 model in AMD 780M iGPU: ~4.5GB GPU VRAM (from shared pool)
- Remaining for other services: ~23.5GB
32GB is comfortable for running a 7B model alongside a typical container stack. For 13B+ models, 64GB is recommended.
RAM Buying Guidance
For most new mini PC home server builds, the recommended amounts are:
| Budget | RAM | Best For |
|---|---|---|
| Entry ($190–230) | 16–32GB DDR4/DDR5 | Docker containers, basic HA + Pi-hole |
| Mid ($380–450) | 32–64GB DDR5 | Proxmox with 4–6 VMs, media + AI |
| Power ($500–600) | 64–96GB DDR5 | Dense VM environments, production homelab |
Buy the next tier up from what your current workload needs. RAM requirements only grow as you add services. The cost difference between 16GB and 32GB DDR5 SO-DIMMs is typically $20–40 — that’s a one-time cost vs. the friction of under-speccing and needing to upgrade later.
Quick Price Summary
- Beelink EQ14 — 2× DDR4 SO-DIMM, upgradeable to 32GB
- Beelink SER9 PRO+ — 32GB LPDDR5X soldered, 8W idle
- GMKtec K11 — 2× DDR5 SO-DIMM, upgradeable to 64GB
- Minisforum UM790 Pro — 2× DDR5 SO-DIMM, upgradeable to 64GB
Frequently Asked Questions
Is 16GB enough for a home server?
16GB is comfortable for most homelab setups: Pi-hole, Home Assistant, Vaultwarden, Jellyfin, Nextcloud, and several more containers run easily within 16GB. For Proxmox with more than 2–3 lightweight VMs, 32GB is more appropriate.
Is 8GB RAM enough for Proxmox?
8GB is the practical minimum for Proxmox — it runs the hypervisor plus 1–2 lightweight LXC containers (512MB–1GB each). For actual VMs, 16GB is the starting point for anything practical. 8GB is the floor, not the comfortable working amount.
How much RAM does Home Assistant use?
Home Assistant in a Docker container or dedicated VM uses 256–512MB for basic setups. Add-ons like Mosquitto, Zigbee2MQTT, and the Piper/Whisper local voice processing add 256–1GB more. A full Home Assistant installation with common add-ons uses 1–2GB total.
Does more RAM improve NAS performance?
Yes, indirectly. ZFS uses available RAM for the ARC cache. More RAM means more frequently-read data stays in RAM (fast) rather than being read from disk (slow). For TrueNAS SCALE, 16GB with a 4-drive pool provides a meaningful ZFS cache. 8GB works but the cache fills quickly.
What RAM type does my mini PC use?
Most 2024–2026 mini PCs use DDR5 SO-DIMM (GMKtec K11, Minisforum MS-01, UM790 Pro). Budget models like the Beelink EQ14 use DDR4 SO-DIMM. Some models use soldered RAM — the Beelink SER9 PRO+ has 32GB LPDDR5X soldered, not upgradeable. Always verify before purchasing if RAM upgrade capacity matters to you.
Check Prices
→ Check Current Price: Beelink EQ14 on Amazon — 2× DDR4 SO-DIMM, upgradeable to 32GB, $6W idle → Check Current Price: Beelink SER9 PRO+ on Amazon — 32GB LPDDR5X soldered (not upgradeable), 8W idle → Check Current Price: GMKtec K11 on Amazon — 2× DDR5 SO-DIMM, upgradeable to 64GB → Check Current Price: Minisforum UM790 Pro on Amazon — 2× DDR5 SO-DIMM, upgradeable to 64GB → Check Current Price: Minisforum MS-01 on Amazon — 2× DDR5 SO-DIMM, upgradeable to 96GB
See also: how to choose RAM for your mini PC server | best mini PC for Proxmox | best mini PC for home server guide