SelfHostPlanner
Buying guide · verified June 19, 2026

Immich mini PC vs NAS: which setup should you buy?

A mini PC is usually the stronger compute box. A NAS is usually the cleaner storage appliance. For many growing photo libraries, the best answer is not either/or: it is a small compute server plus storage designed for recovery.

Short answer: choose a mini PC when you value responsive imports, machine learning flexibility and low-cost compute. Choose a NAS when simple drive management and storage expansion matter more. Use both when the library is important enough to justify separating compute from storage.

Start with Immich's actual requirements

Immich currently lists 6GB RAM and two CPU cores as minimums, with 8GB RAM and four cores recommended. It recommends a Unix-compatible filesystem and notes that generated thumbnails and transcoded video can add roughly 10–20% to the photo library. The PostgreSQL database should ideally live on a local SSD and never on a network share.

Those requirements immediately rule out one common mistake: buying a low-memory NAS only because it has enough drive bays. Storage capacity does not guarantee a smooth Immich workload.

Decision table

PriorityMini PCNASMini PC + NAS
Compute per dollarUsually strongestOften secondary to storage featuresStrong, but two devices to manage
Drive expansionLimited without external storageUsually the main advantageStrongest path for a growing library
Machine learning optionsGood when the CPU/GPU matches a supported backendModel-specific; verify before purchaseRun ML on the mini PC
Database placementLocal SSD is straightforwardUse an appropriate local SSD volumeKeep PostgreSQL on the compute box's SSD
Operational simplicityOne general-purpose Linux systemStorage-focused interface may be easierMore moving parts and network dependencies

When a mini PC is the better choice

Do not buy by processor name alone. Confirm RAM is upgradeable or sufficient, the storage connection is reliable, the network speed matches your storage path, and the exact graphics device is supported. Immich describes hardware-accelerated machine learning as experimental and warns that compatibility varies by backend and model.

When a NAS is the better choice

A mirrored or parity-protected array improves availability, but it does not replace backup. Deletion, corruption, software errors and device loss can affect the whole array. Budget an independent recovery copy before spending money on faster compute.

When the combined setup wins

Use the mini PC for Immich, Docker and the PostgreSQL database on local SSD. Use the NAS for originals and generated media only where the configuration is supported, and maintain a separate backup. This design allows compute upgrades without rebuilding the storage system.

The trade-off is operational complexity. Network failure can interrupt media access, permissions must be correct, and the database must not be moved onto a network share. A combined setup should be chosen for clear capacity or lifecycle reasons—not because two devices automatically make the system safer.

Buying checklist

  1. Calculate usable capacity for today, growth, generated media and headroom.
  2. Reserve an independent backup copy; RAID is not the copy.
  3. Require at least the official RAM and CPU minimums, preferably the recommended level.
  4. Keep PostgreSQL on a reliable local SSD.
  5. Check the exact CPU/GPU against Immich's current acceleration documentation.
  6. Price the complete system: drives, backup, power, adapters and replacement capacity.
  7. Benchmark with a representative batch before the return period ends.

Our recommendation

For a first 1–4TB family deployment, a capable mini PC with adequate RAM and a sound backup path is often the most flexible starting point. For a larger or rapidly growing library, separate compute and multi-drive storage become easier to evolve. A NAS-only deployment is sensible when its exact hardware meets the workload—not merely because the box is labelled a NAS.

Editorial note: this page currently contains no paid product placement or affiliate links. If commercial links are added later, they will be disclosed and will not change the selection criteria.

Calculate storage and three-year cost before buying →

购买指南 · 核对于 2026 年 6 月 19 日

Immich 小主机还是 NAS:应该买哪一种?

小主机通常有更好的计算能力,NAS 通常更适合管理硬盘。对于持续增长的照片库,最佳方案往往不是二选一,而是用小主机负责计算,并用适合恢复的存储系统保存数据。

简短答案:如果你重视导入速度、机器学习弹性和计算性价比,优先考虑小主机;如果你更重视硬盘管理和扩容,优先考虑 NAS;如果照片库非常重要并会持续增长,可以把计算与存储分开。

先看 Immich 的实际要求

Immich 目前列出的最低配置为 6GB 内存和双核 CPU,建议配置为 8GB 内存和四核 CPU。官方建议使用兼容 Unix 的文件系统,并指出缩略图和转码视频平均可能令照片库增加约 10–20%。PostgreSQL 数据库最好放在本地 SSD,绝不能放在网络共享上。

因此,只因为 NAS 有足够硬盘槽就购买低内存型号,是常见错误。存储容量足够,不代表 Immich 运行流畅。

决策表

重点小主机NAS小主机 + NAS
计算性价比通常最佳计算往往不是设计重点性能强,但需要管理两台设备
硬盘扩容内部空间有限通常是主要优势适合持续增长的照片库
机器学习硬件匹配官方后端时较灵活必须核对具体型号在小主机上运行机器学习
数据库位置容易使用本地 SSD应使用合适的本地 SSD 卷把 PostgreSQL 保留在计算主机 SSD
运维复杂度一台通用 Linux 主机存储界面可能更简单网络和权限配置更多

适合选择小主机的情况

不要只看处理器名称。购买前应确认内存、存储连接、网络速度和具体图形设备。Immich 把机器学习硬件加速列为实验性功能,不同后端和模型的兼容性并不相同。

适合选择 NAS 的情况

镜像或校验阵列可以提高可用性,但不能代替备份。误删、损坏、软件错误和设备遗失都可能影响整个阵列。购买更快的计算设备前,应先预算一份独立恢复副本。

何时采用组合方案

让小主机运行 Immich、Docker 和本地 SSD 上的 PostgreSQL;在配置获得支持的前提下,让 NAS 保存原始文件和生成媒体,并另外保留独立备份。这样将来升级计算设备时,不必重建整个存储系统。

代价是运维复杂度更高。网络故障会中断媒体访问,权限必须正确,而且数据库不能移到网络共享。只有在容量或设备生命周期确实需要时,才采用组合方案。

购买清单

  1. 计算当前容量、未来增长、生成媒体和预留空间。
  2. 预留独立备份;RAID 本身不是备份。
  3. 至少满足官方最低 CPU 与内存要求,最好达到建议配置。
  4. 把 PostgreSQL 放在可靠的本地 SSD。
  5. 根据 Immich 最新文档核对具体 CPU/GPU。
  6. 计算完整成本:硬盘、备份、电费、转接设备和更换容量。
  7. 在退货期限结束前,用代表性数据进行测试。

我们的建议

对于最初 1–4TB 的家庭部署,内存足够的小主机加可靠备份通常是最灵活的起点。对于更大或快速增长的照片库,分离计算与多盘存储更容易长期升级。只有当具体 NAS 硬件真正满足负载时,NAS 单机方案才合理。

编辑说明:本页目前没有付费产品推广或联盟链接。日后如加入商业链接,我们会清楚披露,并保持相同的选择标准。

购买前先计算存储与三年成本 →

Primary sources