Immich virtualization planning
Immich on Proxmox Hardware: VM Sizing and GPU Access
Immich can run well in a full virtual machine, which makes Proxmox attractive when the same physical server hosts several services. The performance trap is treating the VM as free: CPU scheduling, RAM allocation, storage placement and accelerator access still come from the physical host, and those resources must be sized for Immich plus every other VM and container that can become busy at the same time.
Quick answer
What this Immich workload needs
Use a full VM for the supported path rather than assuming Docker inside an LXC is equivalent. Immich currently says it runs well virtualized in a full VM and does not recommend Docker in LXC containers. Give the VM enough dedicated memory and CPU headroom, then plan GPU/iGPU access before buying the host.
Live Amazon hardware
Current products that fit this decision
These listings come from this sprint's dedicated Amazon catalogue. Barebones systems, laptops, enclosures, adapters, unrelated accessories, ambiguous product classes and obvious multipacks are excluded by the normalizer.
Buying decision
Match the hardware to the bottleneck
Choose the Proxmox host by total concurrent workload, not the Immich VM alone. A compact Intel system can work well, but add CPU, RAM and storage headroom for Home Assistant, databases, media servers or other VMs sharing the node.
Interactive decision tool
Immich Proxmox Host Sizer
Use the workload inputs to identify a practical hardware tier or likely bottleneck before comparing live products. Results are planning guidance; verify current Immich support and the exact hardware configuration before deployment.
Compatibility checklist
Four checks before you purchase
Use a supported deployment
Immich currently favors Linux and Docker Compose for production; full VMs are supported while Docker-in-LXC is not recommended.
Keep PostgreSQL local
Do not treat a faster network as permission to move the standard database data path onto a network share.
Verify hardware access
Quick Sync, NVENC, VAAPI and ML acceleration need the right host, drivers and container device access.
Measure before upgrading
CPU, RAM, SSD, GPU and network bottlenecks create different symptoms. Change the measured bottleneck first.
Immich officially supports the full-VM route
Immich’s requirements page says the application runs well in a virtualized environment when deployed in a full virtual machine. It specifically does not recommend Docker in LXC containers. For Proxmox buyers, that makes a VM the safer baseline when you want to stay close to the project’s supported deployment expectations.
Size the physical host, not just the guest
A VM with four vCPUs and 8GB of RAM still competes for real CPU time and memory on the Proxmox node. If other guests can be active during photo imports or video processing, the host needs margin beyond the sum of nominal minimums. Oversubscription is not automatically bad, but performance becomes less predictable when several workloads peak at once.
Memory headroom matters during imports
Immich recommends at least 6GB RAM and 8GB for a smoother experience, especially during uploads. On Proxmox, that memory allocation is only useful if the host itself is not under pressure from ZFS, other VMs and cache-hungry applications. A 16GB host can become tight quickly; 32GB or more is easier to justify for a multi-service node.
Keep the database path fast and predictable
Immich stresses the importance of stable PostgreSQL performance and does not support placing the database data directory on a network share in its standard Docker Compose setup. In a VM, use reliable local virtual storage backed by suitable SSDs. Do not add extra network latency to the database merely because the photo library itself lives on a NAS.
Plan iGPU or GPU passthrough before purchase
Hardware acceleration can be one of the hardest parts of a virtualized build. If Quick Sync, VAAPI, NVENC or machine-learning acceleration is important, confirm how the chosen Proxmox hardware exposes the device to the VM. A mini PC with the right processor but no practical passthrough path is a poor fit if video offload was the main reason to buy it.
Avoid assuming LXC is automatically faster and better
Containers have less overhead than full VMs, but Immich’s current guidance does not recommend Docker-in-LXC deployments. Advanced users may still experiment, yet a buyer guide should not turn an unsupported shortcut into the default recommendation. Use a supported VM first, then optimize only when you understand the maintenance and device-passthrough trade-offs.
CPU topology affects mixed workloads
Immich needs responsive CPU for general work even when graphics handles video or machine learning. A host with more cores can separate background jobs from other VMs, while stronger per-core performance helps latency-sensitive services. There is no single ideal topology: the right host depends on what else Proxmox is running and whether those workloads peak together.
2.5GbE is a useful baseline for shared storage
If the Immich library is on a NAS while the database remains local, the VM may move large originals and backups across the network. Gigabit can work, but 2.5GbE gives more headroom for imports and backups without the cost of a full 10GbE fabric. Use 10GbE when repeated multi-terabyte transfers or several fast storage clients can actually use it.
Backups need both VM and application thinking
A Proxmox VM backup is useful, but Immich still needs an application-aware strategy for database and original media. Do not assume a hypervisor snapshot equals a complete photo backup, especially when media lives outside the VM disk. Document which data is inside the guest, which is mounted from elsewhere and how each layer will be restored.
Mini PCs trade expansion for efficiency
Compact Proxmox hosts can be quiet and efficient, but limited RAM slots, NVMe slots and PCIe expansion may constrain long-term growth. If Immich will eventually need a discrete GPU or 10GbE NIC, check the physical expansion path before choosing a tiny system. A slightly larger SFF desktop can offer a much easier upgrade route.
Use reservations where predictability matters
Proxmox lets administrators control CPU and memory allocation, but aggressive overcommit can make background queues unpredictable. If Immich is a family’s primary photo system, give it enough guaranteed memory and CPU access to stay responsive during other lab activity. The point of consolidation should be efficiency, not turning every service into a noisy neighbor.
Treat the hypervisor as part of the availability plan
One powerful node can host many services but also concentrates failure. Keep current backups, document VM configuration and maintain a recovery path if the Proxmox host fails. Hardware authority means planning the failure domain as well as the benchmark: the best host is one you can recover, cool, power and expand without rebuilding the entire home lab.
Questions people ask
Immich on Proxmox Hardware questions
Can Immich run in a Proxmox VM?
Yes. Immich says it runs well in a virtualized environment when deployed in a full virtual machine.
Does Immich recommend Docker in Proxmox LXC?
No. The current requirements page says Docker in LXC containers is not recommended, though advanced users may make it work.
How much RAM should I give the Immich VM?
Immich recommends 8GB for a smooth experience. Add more when the VM also handles heavy imports, other services or memory-intensive workloads.
Should the Immich database be on NAS storage?
The standard Immich Docker Compose guidance says network shares are not supported for the database data location. Keep database storage local and fast.
Can I pass Intel Quick Sync to the VM?
It can be possible depending on the hardware and Proxmox configuration. Verify the exact device and passthrough path before choosing a host around QSV.
Is 2.5GbE enough for Immich on Proxmox?
For many home deployments, yes. 10GbE becomes more valuable for repeated large transfers, fast NAS storage and multiple simultaneous clients.
Should I use a mini PC for Proxmox and Immich?
A mini PC can be excellent when its RAM, storage and accelerator options fit the whole VM stack. Check expansion before buying.
Do Proxmox backups replace Immich backups?
No. Hypervisor backups can protect the VM, but media and database recovery still need an application-aware plan, especially when originals live on separate storage.
How many CPU cores does Immich need?
Immich lists 2 cores minimum and 4 cores recommended. A Proxmox host needs additional capacity for the hypervisor and other guests.
Is a dedicated Immich server faster than Proxmox?
It can be simpler, but a properly sized VM can perform very well. The decision depends on consolidation goals, hardware access and recovery strategy.
Official references and methodology
Verify current Immich support before deployment
Cloudzat uses Immich’s current virtualization guidance as the support baseline: full VM good, Docker in LXC not recommended. The calculator sizes the physical host for Immich plus other guests. Live offers come from a dedicated performance catalogue and are not declarations of Proxmox compatibility without checking the exact system’s virtualization and device-passthrough capabilities.
- Immich - Requirements
- Immich - Hardware Transcoding
- Immich - Hardware-Accelerated Machine Learning
- Immich - Remote Machine Learning
- Immich - Docker Compose Installation
- Immich - System Settings
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, seller terms, exact configurations, firmware and software support can change.