Best NAS for Immich: Storage, Docker, and Expansion Guide

Immich NAS buying guide

Best NAS for Immich: Storage, Docker, and Expansion Guide

The best NAS for Immich balances compute capability with drive bays, memory, SSD options, networking, and a realistic path for photo and video growth.

Quick answer

What to buy for this Immich workload

Treat drive bays and usable capacity as first-class requirements. A capable 4-bay or larger NAS usually gives a family library more breathing room than buying the smallest enclosure that meets today’s storage total.

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.

Checking the dedicated Immich catalogue…

Buying decision

Choose the system architecture before chasing specifications

An all-in-one NAS is attractive when you want one appliance, while separating Immich compute from NAS storage can give you more CPU freedom. Do not pay for a populated bundle unless the exact included drives and warranty are clear.

Interactive sizing

Immich NAS Capacity & Bay Planner

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.

01

Choose bays before brand

Drive-bay count determines more of the long-term experience than the logo on the front. Estimate current data, growth, redundancy, and backup requirements first, then choose an enclosure that can reach that usable capacity without filling every bay on day one.

NAS buying starts with protected capacity and bay economics. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. Under “Choose bays before brand,” calculate what remains usable after redundancy and growth before comparing processors or vendor application stores.

02

Two-bay NAS limits

A two-bay NAS is compact and easy to understand, but redundancy consumes half of raw capacity in a mirror. It suits modest libraries with predictable growth; it becomes restrictive when a household expects years of 4K video or wants room for snapshots and other services.

An appliance is only convenient when its configuration is unambiguous. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. For “Two-bay NAS limits,” distinguish diskless hardware from populated bundles and confirm memory, network, and M.2 behavior on the exact enclosure.

03

Why four bays change the growth plan

Four bays offer more layout choices and a better upgrade path. You can combine redundancy with higher usable capacity, add disks as the storage plan evolves on platforms that support expansion, and avoid replacing both drives just because the original mirror is full.

Storage expansion rules can matter more than a small performance difference. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. “Why four bays change the growth plan” should be checked against the vendor’s supported pool, disk, and upgrade methods so today’s purchase does not trap tomorrow’s library.

04

Six-bay and larger systems

Six or more bays are valuable when capacity, backup targets, or multiple workloads share the appliance. Extra bays do not automatically make Immich faster, so buy them for storage design and future expansion rather than as a substitute for checking CPU and memory capability.

Separating storage and compute is always an available design choice. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. Use “Six-bay and larger systems” to test whether the NAS should run Immich itself or simply provide durable media storage to a separate application host.

05

CPU and container capability

If Immich will run directly on the NAS, the processor must handle containers plus background application work. Confirm the architecture, container environment, and hardware acceleration path. Some NAS CPUs are excellent storage controllers but modest application hosts.

NAS buying starts with protected capacity and bay economics. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. Under “CPU and container capability,” calculate what remains usable after redundancy and growth before comparing processors or vendor application stores.

06

Memory and database responsiveness

Memory affects database caching, containers, and concurrent services. Check installed RAM, maximum supported memory, and whether expansion slots are accessible. A platform with upgradeable memory can remain useful much longer than an otherwise similar sealed configuration.

An appliance is only convenient when its configuration is unambiguous. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. For “Memory and database responsiveness,” distinguish diskless hardware from populated bundles and confirm memory, network, and M.2 behavior on the exact enclosure.

07

M.2 SSDs for application data

M.2 slots can keep the Immich database and generated assets on fast flash while bulk media remains on HDDs. Do not assume every NAS supports the same use of NVMe slots; vendor rules may distinguish cache, storage pools, and application volumes.

Storage expansion rules can matter more than a small performance difference. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. “M.2 SSDs for application data” should be checked against the vendor’s supported pool, disk, and upgrade methods so today’s purchase does not trap tomorrow’s library.

08

Network speed for imports and backups

Network speed matters when large media transfers cross the LAN. 2.5GbE is a useful baseline for modern multi-drive NAS systems, while 10GbE is most valuable for heavy workstations, very large imports, or multiple fast clients. Match the switch and endpoints too.

Separating storage and compute is always an available design choice. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. Use “Network speed for imports and backups” to test whether the NAS should run Immich itself or simply provide durable media storage to a separate application host.

09

Diskless versus populated listings

Diskless and populated NAS listings must be separated. A cheap populated bundle may include drives you would not have selected, while a diskless price omits the largest part of the storage budget. Cloudzat treats the configuration as part of the product identity.

NAS buying starts with protected capacity and bay economics. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. Under “Diskless versus populated listings,” calculate what remains usable after redundancy and growth before comparing processors or vendor application stores.

10

Drive selection and CMR verification

For photo archives, choose drives based on verified recording technology, workload class, warranty, noise, power, and price per usable terabyte. Capacity alone is not enough, and ambiguous marketplace listings should not be treated as equivalent to a clearly specified drive.

An appliance is only convenient when its configuration is unambiguous. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. For “Drive selection and CMR verification,” distinguish diskless hardware from populated bundles and confirm memory, network, and M.2 behavior on the exact enclosure.

11

Snapshots are not a second backup

Snapshots help recover from accidental deletion or bad changes, but they live on the same storage system and are not an independent backup. Plan a local second copy or another device plus an offsite copy for irreplaceable family media.

Storage expansion rules can matter more than a small performance difference. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. “Snapshots are not a second backup” should be checked against the vendor’s supported pool, disk, and upgrade methods so today’s purchase does not trap tomorrow’s library.

12

When to separate NAS storage from Immich compute

Separating compute from storage is often the best upgrade path. The NAS can focus on resilient capacity while a mini PC or server runs Immich. That architecture makes it easier to replace application hardware without moving the entire photo library.

Separating storage and compute is always an available design choice. Start with usable protected capacity and bay count. Then check whether the NAS CPU, memory, container environment, NVMe options, and Ethernet meet the workload. Diskless and populated bundles must not be compared as if they were identical. Use “When to separate NAS storage from Immich compute” to test whether the NAS should run Immich itself or simply provide durable media storage to a separate application host.

Questions people ask

Immich hardware questions for this workload

Can Immich run directly on a NAS?

Yes, when the NAS supports the required container environment and has enough CPU, RAM, storage performance, and any needed hardware acceleration. A storage-focused NAS can also serve media to a separate Immich compute node. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Is a 2-bay NAS enough for Immich?

A 2-bay NAS can fit a modest library, but a mirrored layout gives up half of raw capacity and leaves little bay-level expansion. Larger or fast-growing libraries usually benefit from four or more bays. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Why is a 4-bay NAS better for a growing Immich library?

Four bays create more useful redundancy and expansion choices than two bays, which is why they are a strong default for a family library expected to grow for several years. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Should I buy a diskless or populated NAS?

Diskless and populated NAS products should be treated as different configurations. A populated bundle is only comparable when the exact included drives, capacity, condition, and warranty are known. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Does an Immich NAS need NVMe slots?

NVMe slots are valuable when the NAS permits application or storage use for the Immich database and generated assets, but vendor rules vary and some platforms restrict M.2 devices to cache or specific pool types. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

How much RAM should a NAS have 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. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Is 2.5GbE important on an Immich NAS?

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. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

What hard drives should I use for Immich?

Choose hard drives by verified capacity, recording technology, workload class, noise, power, warranty, and price per usable terabyte. Avoid ambiguous marketplace listings that hide the exact drive model. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Are NAS snapshots a backup for Immich?

No. Redundancy and snapshots improve availability or rollback, but they remain on the primary storage system. Irreplaceable media still needs an independent local or remote backup copy. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

Should I run Immich on a mini PC and keep photos on the NAS?

The right answer depends on library size, video share, users, background-job urgency, storage architecture, and the exact hardware configuration. For NAS purchases, calculate protected usable capacity first and verify the exact enclosure’s CPU, memory, M.2, Ethernet, container, and expansion rules.

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.

As an Amazon Associate, Cloudzat may earn from qualifying purchases. Product availability, prices, seller terms, and compatibility can change.

Scroll to Top