Immich hardware authority

Best Home Server for Immich: Mini PC, NAS, and DIY Builds

Choose an Immich server by library growth, video workload, machine-learning features, redundancy, and expansion headroom—not by a generic mini-PC ranking.

See live hardware Size my workload

Quick answer

What to buy for this Immich workload

For most family libraries, prioritize a modern x86-64 system with hardware video acceleration, enough memory for imports and background jobs, fast SSD space for application data, and storage that can grow without rebuilding the whole server.

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

A mini PC is the easiest low-power compute node, a NAS is the cleanest all-in-one storage appliance, and a DIY server gives the most expansion. The right answer depends on where the media lives and how much video or machine-learning work you expect.

Interactive sizing

Immich Server Sizing Calculator

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.

Start with the Immich workload, not the chassis

Immich stresses several resources at different times. Browsing is usually light, while first imports, thumbnail generation, video conversion, facial recognition, and Smart Search can create bursts of CPU, storage, and accelerator demand. Start with your library behavior before choosing a box.

A home-server shortlist should be judged as an architecture, not as a CPU contest. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. In the context of “Start with the Immich workload, not the chassis,” favor the design that keeps media protected, background jobs responsive, and the next storage upgrade straightforward.

Small, family, and heavy workload tiers

A small personal library and a multi-user video-heavy household should not receive the same recommendation. Workload tiers let you buy enough headroom without paying for workstation hardware that will sit mostly idle after the first indexing pass.

This part of the home-server decision is about avoiding a hidden bottleneck. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. For “Small, family, and heavy workload tiers,” compare how the compute node, application SSD, media pool, and network work together before paying for a faster processor.

Mini PC as a dedicated compute node

A mini PC works especially well when media is stored on a separate NAS or DAS. It keeps application compute independent from disk expansion and often offers strong performance per watt, but you need to confirm RAM, SSD, networking, and media-engine details on the exact configuration.

Think several years beyond the first installation here. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. “Mini PC as a dedicated compute node” matters because the most expensive mistake is often choosing a platform whose bays, memory, or expansion options are already exhausted when the library grows.

NAS as an all-in-one appliance

A NAS reduces cabling and administration by combining storage and compute. The tradeoff is that CPU choice is tied to the enclosure. Check container support, memory expansion, M.2 options, and network speed rather than assuming every modern NAS is equally suitable for Immich.

The strongest home-server choice is the one that remains understandable when something fails. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. Apply “NAS as an all-in-one appliance” to recovery, replacement, and migration as well as performance so the server is practical to own.

DIY server when expansion matters

A DIY tower makes sense when you expect many disks, a discrete GPU, 10GbE, or frequent upgrades. It costs more space and usually more idle power, but standard components make future storage and accelerator changes much easier than with a sealed appliance.

A home-server shortlist should be judged as an architecture, not as a CPU contest. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. In the context of “DIY server when expansion matters,” favor the design that keeps media protected, background jobs responsive, and the next storage upgrade straightforward.

CPU and hardware video acceleration

The CPU does more than serve the web interface. Import jobs, metadata processing, database work, and software fallbacks all depend on it. Hardware video acceleration can reduce the cost of transcoding, so the CPU and media engine should be evaluated together.

This part of the home-server decision is about avoiding a hidden bottleneck. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. For “CPU and hardware video acceleration,” compare how the compute node, application SSD, media pool, and network work together before paying for a faster processor.

RAM for imports and background jobs

Memory demand depends on concurrent services and the size of background jobs. A server running only Immich can be modest, while Docker stacks, databases, reverse proxies, and other self-hosted applications justify more RAM. Leave headroom instead of buying at the minimum.

Think several years beyond the first installation here. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. “RAM for imports and background jobs” matters because the most expensive mistake is often choosing a platform whose bays, memory, or expansion options are already exhausted when the library grows.

SSD placement for database and generated assets

Fast SSD storage is best used where small random I/O matters: operating system, containers, database, thumbnails, and temporary transcoding work. The original photo and video library can live on capacity-oriented disks as long as the storage path is reliable and backed up.

The strongest home-server choice is the one that remains understandable when something fails. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. Apply “SSD placement for database and generated assets” to recovery, replacement, and migration as well as performance so the server is practical to own.

HDD capacity, redundancy, and growth

Raw terabytes are not usable terabytes once redundancy, filesystem reserve, snapshots, and growth are included. Plan the next several years of uploads before selecting drive count, because adding capacity later may require larger disks, another bay, or a different RAID layout.

A home-server shortlist should be judged as an architecture, not as a CPU contest. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. In the context of “HDD capacity, redundancy, and growth,” favor the design that keeps media protected, background jobs responsive, and the next storage upgrade straightforward.

Network speed and remote access

Gigabit Ethernet is adequate for many households, but large initial imports, multiple clients, NAS-backed storage, and fast local backup can expose it. 2.5GbE is a practical step up when the rest of the network supports it; faster links matter mainly for heavier workflows.

This part of the home-server decision is about avoiding a hidden bottleneck. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. For “Network speed and remote access,” compare how the compute node, application SSD, media pool, and network work together before paying for a faster processor.

Power, noise, and always-on cost

An always-on server should be judged at idle as well as under load. A very powerful desktop may complete imports quickly but cost more to run and cool. Balance sustained performance, acoustic comfort, and energy use instead of optimizing only for peak benchmark numbers.

Think several years beyond the first installation here. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. “Power, noise, and always-on cost” matters because the most expensive mistake is often choosing a platform whose bays, memory, or expansion options are already exhausted when the library grows.

Backup and upgrade path

Immich is not the backup. Keep database protection and media protection in the same recovery plan, maintain an independent copy, and decide how you will replace failed disks or the compute host. A good server design includes a migration path before a failure forces one.

The strongest home-server choice is the one that remains understandable when something fails. Use the workload calculator and compare complete systems rather than a single specification. A family server should balance compute, fast application storage, bulk media capacity, network speed, backups, and future expansion. Apply “Backup and upgrade path” to recovery, replacement, and migration as well as performance so the server is practical to own.

Questions people ask

Immich hardware questions for this workload

How much RAM should an Immich home server have?

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. Judge the final choice as a complete home-server architecture with compute, protected media storage, application SSD space, network capacity, and a recoverable backup path.

Is a mini PC or NAS better for Immich?

The right answer depends on library size, video share, users, background-job urgency, storage architecture, and the exact hardware configuration. Judge the final choice as a complete home-server architecture with compute, protected media storage, application SSD space, network capacity, and a recoverable backup path.

Does Immich need a GPU?

Should Immich photos live on SSD or HDD?

Is 2.5GbE worth it for an Immich server?

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. Judge the final choice as a complete home-server architecture with compute, protected media storage, application SSD space, network capacity, and a recoverable backup path.

Can I run Immich and other services on the same server?

How much spare storage should I leave?

Is RAID enough to protect an Immich library?

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. Judge the final choice as a complete home-server architecture with compute, protected media storage, application SSD space, network capacity, and a recoverable backup path.

Can I separate Immich compute from storage?

What should I upgrade first when Immich feels slow?

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.