Proxmox VM Sizing Calculator

Planning a Proxmox box or another home server that runs several virtual machines and containers? Pick the services you want to run, adjust the RAM, vCPU and disk figures if you know better, and this calculator adds them up with the host’s own overhead and ZFS cache, then suggests a hardware tier.

VM or containerHow manyRAM GBvCPUDisk GB
Home Assistant OS (VM)HA docs minimum: 2 GB, 2 vCPU
Pi-hole or AdGuard Home (LXC)Pi-hole docs: 512 MB, 4 GB disk
Jellyfin or Plexmedia files stored separately
Frigate NVRFrigate docs: 4 GB basic, 8 GB+ with enrichments
Immich photosImmich docs: 6 GB min, 8 GB recommended
TrueNAS (VM)TrueNAS docs: 8 GB minimum
Nextcloudtypical; files stored separately
Docker host VM (several containers)typical
General Linux VM or LXCtypical
Windows 11 VMMicrosoft minimum: 4 GB, 64 GB
WireGuard, Tailscale or reverse proxy (LXC)typical
Something elseenter its numbers

Figures marked “docs” are the minimums from each project’s own documentation; “typical” figures are common starting points. Disk is the VM or container’s own system disk, not your media, photos or recordings.

RAM to install–
CPU cores–
Boot / VM SSD–
  • Guests–
  • Guest RAM–
  • Host OS and services–
  • ZFS ARC–
  • Total with headroom–
  • vCPUs allocated–
  • Guest disks + host–

How this is calculated

  • RAM = the RAM of every guest + 2 GB for the host + ZFS ARC (if used), plus the headroom you set, rounded up to a common memory size. The 2 GB host figure is the Proxmox VE recommended minimum for the OS and its services.
  • ZFS ARC uses the Proxmox rule of thumb of 2 GB base + 1 GB per TB of pool storage. Proxmox VE 8.1 and later cap the ARC at 10% of RAM (up to 16 GB) by default on new installs, so ZFS will run with less, just with a smaller read cache.
  • CPU cores = whichever is larger: the biggest single VM’s vCPU count, or half the total vCPUs. Most home services sit idle most of the time, so sharing cores this way is normal. If several guests are busy at once (transcoding, game servers, builds), plan one core per vCPU.
  • Storage = all guest system disks + 32 GB for the host, rounded up to a common SSD size. Keep media, photos and camera recordings on separate drives or a NAS.

Sources for the defaults

Minimums come from each project’s own documentation, checked November 20, 2026: Proxmox VE system requirements, Proxmox ZFS memory guidance, Home Assistant OS VM requirements, Pi-hole prerequisites, Frigate planning guide, Immich requirements and the TrueNAS hardware guide. Real use is often higher than the minimum, especially for Frigate with many cameras and Immich during the first photo import.

VM or container?

On Proxmox, an LXC container shares the host’s kernel and uses noticeably less RAM than a full VM running the same service. Lightweight Linux services such as Pi-hole, a reverse proxy or Jellyfin often run well in containers. Home Assistant OS, TrueNAS and Windows need a full VM.

Related: Which mini PC? picker · Best N150 and N100 mini PCs for a home server · HP EliteDesk Proxmox home server build · Best NVMe SSD for Proxmox and VM storage

For general informational purposes only; not professional advice. Posts may contain affiliate links. Learn more.
Scroll to Top