20TB Immich build planning
Immich Server for a 20TB Photo Library: Storage Plan
A 20TB Immich library is no longer a small home-server storage problem. Capacity overhead, redundancy, backup copies and future growth can push the total purchasing requirement far beyond the size of the current originals. The design should preserve an expansion path, keep application data on responsive local SSD storage and use a chassis that can cool multiple high-capacity drives during long backup and rebuild workloads.
Quick answer
What to buy for this Immich workload
For a 20TB starting library, model six- or eight-bay options alongside four-bay high-capacity builds before purchasing. Larger drive sizes can preserve bays, while more bays can reduce the capacity required per disk and provide broader parity choices. The right answer depends on annual growth, protection level, noise/power tolerance and how the independent backup will be stored.
Live Amazon storage
Current storage products for this Immich decision
Listings come from this storage sprint’s dedicated Amazon catalogue. External drives, enclosures, SAS drives, wrong capacities, populated NAS bundles, accessories, and multipacks are excluded when they do not match the focused query.
Buying decision
Choose the system architecture before chasing specifications
At 20TB, optimize the system rather than an individual drive. The calculator shows how a seemingly modest growth rate can turn into a much larger raw-capacity and backup budget over five years.
Interactive sizing
20TB Immich Storage Planner
Use your library size and protection goals to size storage before comparing products. Results are planning estimates; verify filesystem, RAID, NAS, and current Immich requirements before deployment.
Compatibility checklist
Four checks before you purchase
Separate storage roles
Treat the database, generated media, originals, and backups as different jobs before choosing devices.
Keep database storage local
Use reliable local SSD storage for database files instead of assuming a network share is suitable.
Plan beyond today
Include library growth, generated files, free-space reserve, redundancy, and independent backups.
Verify the exact listing
Confirm interface, capacity, condition, seller terms, NAS bay count, and warranty before purchase.
Twenty terabytes needs a multi-layer plan
A 20TB archive has enough data that a storage mistake becomes expensive to unwind. Start by separating application storage, primary media storage and backup storage. The database can stay on a modest local SSD, originals can live on a protected HDD pool and backups should occupy an independent destination. This role separation prevents the bulk size of the library from forcing every component into the same expensive or inflexible storage tier.
Confirm the 20TB baseline
Measure original photos and videos, not a directory that includes snapshots, exports, duplicates or generated derivatives. At this scale, a ten-percent counting error equals 2TB before growth and protection are even added. Record the current originals, generated directories and backup sizes separately. Those measurements make later expansion decisions evidence-based and allow the storage calculator to model each layer without double-counting the same bytes.
Five-year growth can dominate the design
A 20TB library adding 2TB per year reaches 30TB of originals in five years before generated files, reserve or redundancy. That changes the sensible drive and chassis classes. Large families with frequent 4K video may grow faster still. Use multiple scenarios rather than one optimistic forecast: expected growth, high growth and a longer horizon. The hardware choice should survive the expected case without making the high case impossible to reach.
Four bays versus six or eight
Four very large drives can provide substantial protected capacity, but an array that consumes every bay has a narrower expansion path. Six- and eight-bay systems cost more upfront and add power/noise, yet they can accept smaller drives, more parity or future additions. Compare the total five-year cost of both approaches. A larger chassis is justified when it avoids replacing healthy high-capacity drives at the first major expansion.
Drive size and bay count trade places
Higher-capacity disks buy bay efficiency; more bays buy layout flexibility. The optimal point depends on current drive prices and the target protection scheme. A 24TB drive may preserve slots but cost more per device, while multiple 16TB or 18TB drives can distribute capacity across a larger array. Use price per TB only after verifying that each exact model is SATA, compatible, correctly conditioned and suitable for the planned chassis.
Dual parity becomes worth evaluating
As drive count and capacity rise, the consequences of a long rebuild deserve more attention. That does not mean one parity scheme is universally correct, but a 20TB library is large enough to compare dual-parity and mirror-based designs rather than defaulting to the smallest overhead. Availability requirements, backup quality, rebuild behavior and the storage platform’s implementation should guide the final choice. This page uses only planning estimates, not a blanket RAID prescription.
Backups may equal another large storage system
A full independent copy of a 20TB-plus projected library can require its own NAS, DAS or set of large drives. That expense belongs in the original project budget. If the backup is offsite, transfer time and bandwidth may also influence strategy. A backup plan that exists only on paper because the required capacity was never purchased is not protection. Calculate primary and backup storage as separate, funded layers.
Application SSD remains a small fraction
Even with tens of terabytes of photos, the application/database SSD can remain a relatively small component. A 1TB or 2TB internal SSD provides generous headroom when it also hosts generated media or other services, while originals continue on the HDD pool. This tiering keeps flash spending focused on latency-sensitive work. It also makes application backup and server replacement easier because the media pool does not have to move with the operating system.
Networking affects migration and backup windows
Twenty terabytes takes time to move. Gigabit Ethernet can serve normal browsing, but major migrations, local backup seeding and workstation imports may benefit from 2.5GbE or 10GbE if both endpoints and the switch support those speeds. Faster networking does not replace storage planning, and disk throughput may become the next bottleneck. Size the network around the largest recurring transfer job rather than the web interface.
Power, acoustics and UPS size grow with the array
Six or eight high-capacity drives add startup current, steady-state power, fan demand and seek noise. A home deployment should account for where the chassis will live and whether the UPS can support the full system long enough for a controlled shutdown. High-capacity storage is not only a capacity purchase; it is also a cooling, power and physical-placement decision. Check the enclosure design before buying all drives at once.
Expansion should not require a crisis migration
Write down the next two capacity milestones before choosing the initial pool. Can you add drives? Must you replace existing members? Can the chassis attach an official expansion unit, and would that create a failure domain you accept? If every path becomes complex at 30TB, address it while the library is still 20TB. The best architecture makes routine growth boring instead of turning it into a weekend-long data relocation project.
A balanced 20TB architecture
For many large home archives, the clearest pattern is local SSD application storage, a six- or eight-bay-capable protected media system sized from projected originals, and an independent backup destination with comparable usable capacity. Four-bay systems can still work with sufficiently large disks when growth is moderate. Use the live catalogue to price both chassis and drive-size scenarios, then choose the design whose five-year expansion story is easiest to explain.
Questions people ask
Immich Server for 20TB Photos questions
How much raw storage do I need for 20TB of Immich photos?
It depends on future growth, generated media, reserve and redundancy. The raw primary requirement can be much larger than 20TB, and backups should be budgeted separately.
Is a 4-bay NAS enough for a 20TB library?
It can be with large drives and a suitable layout. Six or eight bays may offer a better expansion path when growth is fast or more parity is desired.
What drive sizes should I consider for 20TB Immich?
Compare 16TB through 24TB and larger SATA drives based on the whole array’s usable capacity, price, warranty, bay efficiency and future expansion path.
Should a 20TB Immich library use dual parity?
It is worth evaluating, especially in larger arrays, but there is no universal rule. Consider the storage platform, backup quality, rebuild behavior and downtime tolerance.
Do I need 10GbE for 20TB of photos?
Not for ordinary browsing. It can be useful for large local migrations and backups when the complete network path and storage system can sustain the higher speed.
How large should the application SSD be?
The application SSD can remain far smaller than the media pool. One or two terabytes can provide generous headroom when generated media or other services share it.
How should I back up 20TB?
Use an independent destination sized for the data you need to recover. The exact method can be another storage system, rotated media or offsite storage, but it should not be the same primary array.
Is one 20TB or 24TB drive enough?
It may hold the current data but provides no internal redundancy and little headroom. For valuable archives, plan usable capacity, protection and backups rather than matching the library to one disk.
Will a 20TB library become expensive to migrate?
Yes, data movement can take significant time and temporary capacity. A strong expansion path reduces how often full migrations are necessary.
What should I buy first for a 20TB build?
First establish the storage architecture and usable-capacity target. Then select a compatible chassis, exact SATA drive models, application SSD and independent backup destination as parts of that plan.
References and methodology
Verify changing requirements before you buy
Cloudzat treats 20TB as a starting workload, not a one-disk shopping query. The planner models growth, generated media, reserve, primary protection and backups separately. The dedicated catalogue focuses on internal SATA drives, diskless multi-bay NAS systems and internal SSDs, with live prices shown only when Amazon returns a current featured offer.
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Product availability, prices, seller terms, and compatibility can change.