Immich sizing reference
Immich Hardware Requirements: Minimum, Recommended, and Real-World Sizing
Immich’s published minimums are a starting line, not a shopping list. Real-world sizing needs to account for imports, transcoding, machine learning, storage growth, database responsiveness, and backups.
Quick answer
What to buy for this Immich workload
Use the official minimum only to confirm that a system can run Immich. For a new purchase, size above it so background jobs, multiple users, database work, and future library growth do not immediately consume all available headroom.
Live Amazon hardware
Current products that fit the categories in this guide
Listings come from this Immich sprint’s dedicated Amazon catalogue. Accessories, barebones mini PCs, ambiguous NAS bundles, wrong-capacity storage, and mismatched GPU models are excluded by the normalizer.
Buying decision
Choose the system architecture before chasing specifications
The most important distinction is between “can boot Immich” and “can serve your workload comfortably.” The calculator below turns library and feature choices into a practical hardware tier.
Interactive sizing
Immich Requirements Checker
Use your workload to get a hardware tier before comparing products. The result is planning guidance, not a substitute for checking the current Immich compatibility documentation.
Compatibility checklist
Four checks before you purchase
Workload first
Size users, library growth, video share, and background jobs before choosing hardware.
Fast application storage
Keep the database and generated application data on reliable SSD storage where practical.
Protected media capacity
Plan usable capacity after redundancy, reserve space, growth, and backup copies.
Verified acceleration
Confirm the exact hardware, drivers, operating system, and Immich acceleration path before purchase.
Official minimum versus buying recommendation
Immich publishes minimum requirements so administrators know the floor for a supported installation. A buyer should size above that floor, because minimum resources leave little room for large imports, concurrent services, database growth, video processing, or future features.
A requirements page must keep the support floor separate from a shopping target. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. In “Official minimum versus buying recommendation,” evaluate how much margin remains once imports, databases, video jobs, and other services run at the same time.
CPU cores and bursty background jobs
CPU demand is uneven. The interface may feel light while imports and media jobs produce sustained bursts. Core count matters for parallel work, but per-core performance and hardware acceleration can be equally important depending on what your library contains.
Published minimums answer whether software can start, while owners care about how it behaves under load. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. Use “CPU cores and bursty background jobs” to translate documentation into a configuration with breathing room rather than copying the smallest supported number.
RAM minimums and practical headroom
The current documentation distinguishes a minimum memory level from a higher recommended level. Treat even the recommended number as a starting point if the host also runs databases, Docker services, reverse proxies, monitoring, or other self-hosted applications.
Compatibility is a chain of hardware, operating system, drivers, containers, and storage. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. “RAM minimums and practical headroom” belongs in that chain, so a single supported component should never be treated as proof that the complete deployment is suitable.
Hardware transcoding support
Hardware transcoding can reduce CPU load for supported video operations, but capability depends on the hardware, operating system, drivers, codec support, and container access. A processor marketed with integrated graphics is not enough evidence by itself.
Long-term sizing is easier when each resource has a reason to exist. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. For “Hardware transcoding support,” tie extra CPU, memory, SSD space, or network speed to a real workload instead of adding specifications without a measurable benefit.
Machine-learning acceleration options
Machine-learning features such as Smart Search and face processing can use CPU or supported acceleration paths. The initial indexing phase is often the moment when insufficient compute becomes obvious, so decide how quickly you need a large library processed.
A requirements page must keep the support floor separate from a shopping target. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. In “Machine-learning acceleration options,” evaluate how much margin remains once imports, databases, video jobs, and other services run at the same time.
Database and thumbnail storage
Immich relies on responsive database and generated-asset storage. Put those high-I/O workloads on reliable SSD storage where practical. Capacity planning should include the application’s generated data rather than counting only original photos and videos.
Published minimums answer whether software can start, while owners care about how it behaves under load. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. Use “Database and thumbnail storage” to translate documentation into a configuration with breathing room rather than copying the smallest supported number.
Media capacity and generated assets
Original media is only one part of the capacity equation. Generated thumbnails and transcoded assets add storage, and the filesystem needs free space to behave well. Keep a reserve instead of planning to run the storage pool at nearly 100 percent.
Compatibility is a chain of hardware, operating system, drivers, containers, and storage. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. “Media capacity and generated assets” belongs in that chain, so a single supported component should never be treated as proof that the complete deployment is suitable.
Network requirements for home and remote use
Network requirements depend on where clients and media live. A single local user may be comfortable on gigabit, while NAS-backed storage, several uploaders, and bulk imports benefit from faster LAN links. Remote performance is also limited by internet upload speed.
Long-term sizing is easier when each resource has a reason to exist. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. For “Network requirements for home and remote use,” tie extra CPU, memory, SSD space, or network speed to a real workload instead of adding specifications without a measurable benefit.
Virtual machines and containers
Containers are common for Immich, and virtualization can work when device access and storage paths are designed correctly. If you expect to pass a GPU or iGPU into a VM, validate that architecture before buying hardware rather than solving passthrough after deployment.
A requirements page must keep the support floor separate from a shopping target. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. In “Virtual machines and containers,” evaluate how much margin remains once imports, databases, video jobs, and other services run at the same time.
Filesystem and storage reliability
Reliability comes from the whole storage stack: healthy media, stable power, adequate cooling, filesystem integrity, and tested recovery. Fast hardware does not compensate for a single unprotected disk holding the only copy of irreplaceable photos.
Published minimums answer whether software can start, while owners care about how it behaves under load. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. Use “Filesystem and storage reliability” to translate documentation into a configuration with breathing room rather than copying the smallest supported number.
Backup requirements
A useful recovery plan protects both media files and the database. Database-only backups cannot recreate the original photo library. Schedule copies, keep at least one independent location, and periodically confirm that restoration steps are understood.
Compatibility is a chain of hardware, operating system, drivers, containers, and storage. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. “Backup requirements” belongs in that chain, so a single supported component should never be treated as proof that the complete deployment is suitable.
A sensible five-year upgrade margin
Hardware purchased today should have room for tomorrow’s library. A little additional RAM capacity, an extra drive bay, another NVMe slot, or faster networking can be worth more than a small CPU benchmark advantage when it prevents an early platform replacement.
Long-term sizing is easier when each resource has a reason to exist. Separate the official minimum from a new-purchase recommendation. Minimums establish whether Immich can run; practical sizing adds headroom for imports, video jobs, machine learning, databases, backups, and other services. For “A sensible five-year upgrade margin,” tie extra CPU, memory, SSD space, or network speed to a real workload instead of adding specifications without a measurable benefit.
Questions people ask
Immich hardware questions for this workload
What are the minimum hardware requirements for Immich?
The official requirements are a support floor, not a purchasing target. Current documentation lists Linux/*nix 64-bit, 2 CPU cores minimum and 4 recommended, and 6GB RAM minimum with 8GB recommended. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
How much RAM is recommended for Immich?
Immich’s current requirements page lists 6GB as a minimum and 8GB as recommended; a new family server often benefits from 16GB or more when background jobs and other containers share the host. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
How many CPU cores does Immich need?
Immich’s current requirements page lists 2 CPU cores as a minimum and 4 as recommended, but a new purchase should be sized around import, video, and machine-learning concurrency rather than stopping at the minimum. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
Does Immich require hardware transcoding?
Immich does not require hardware transcoding to function, but supported acceleration can reduce CPU load for compatible video jobs. Support depends on the hardware, operating system, drivers, codec, and device access. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
Does Immich require a GPU for machine learning?
No. Many Immich servers can use CPU processing or supported integrated acceleration. A discrete GPU is justified when measured transcoding or machine-learning queues need more throughput than the existing hardware can provide. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
How much SSD space should I reserve for Immich?
Reserve SSD capacity for the operating system, containers, database, thumbnails, and temporary/generated assets, then leave free space for growth. The exact number depends on library size and how much application data is retained. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
How much extra storage do thumbnails and transcodes use?
Immich’s current requirements guidance notes that thumbnails and transcoded video can add roughly 10–20% of average library size, so capacity planning should not count original media alone. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
Can Immich run in a virtual machine?
Immich can be deployed with virtualization, but GPU/iGPU passthrough, storage paths, networking, and device permissions add complexity. Validate those layers before buying hardware whose value depends on passthrough. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
What network speed does Immich need?
Gigabit Ethernet works for many homes, while 2.5GbE becomes useful for large local imports, NAS-backed media, fast backups, and several active clients when the rest of the network supports it. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
What should I back up in an Immich installation?
Protect both the original photo/video media and the database/recovery data. A database backup does not contain the media files, so recovery requires a plan for both parts. Use the current Immich documentation as the support floor, then add workload headroom for imports, generated assets, database activity, transcoding, machine learning, and other hosted services.
References and methodology
Verify changing requirements before you buy
Cloudzat separates product classes, rejects accessories and ambiguous configurations, and uses the sprint’s dedicated Amazon catalogue. Prices are displayed only when a current featured offer is returned; otherwise the page links to Amazon buying options without inventing a price.
- Immich requirements
- Immich hardware transcoding
- Immich machine-learning acceleration
- Immich backup and restore
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Product availability, prices, seller terms, and compatibility can change.