5TB Immich deployment
Immich Server for 5TB of Photos and Videos: Hardware and Storage Plan
A 5TB library is large enough that storage growth, redundancy, backups, and rebuild strategy matter as much as the CPU that runs Immich.
Quick answer
What to buy for this Immich workload
Do not build a 5TB Immich system around exactly 5TB of raw capacity. Allow room for future uploads, generated assets, redundancy, snapshots, and at least one independent backup copy.
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
For a 5TB starting library, choose the storage architecture first, then fit compute around video and machine-learning load. A 4-bay NAS or expandable server usually offers a cleaner growth path than a single large drive.
Interactive sizing
5TB Immich Storage Growth 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.
Why 5TB needs a storage plan
Five terabytes is already beyond the point where “buy one drive that fits” is a comfortable strategy. The system needs spare space for growth, generated files, maintenance, and failure recovery, so capacity planning should begin with several years rather than today’s exact library size.
At five terabytes, capacity mistakes become costly to undo. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. For “Why 5TB needs a storage plan,” model the protected, backed-up library after several years rather than building an array that merely fits the initial migration.
Estimate five-year library growth
Project annual growth from real upload behavior. A household that adds mostly phone photos grows very differently from one shooting 4K video. The planner should include the current 5TB, expected yearly growth, and the number of years you want before the next storage expansion.
The storage plan should survive both growth and a failed component. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. “Estimate five-year library growth” is therefore a usable-capacity problem first and a drive-shopping problem second; raw labels alone do not describe the space you can safely consume.
Separate raw capacity from usable capacity
Raw drive labels do not equal usable protected storage. Redundancy consumes capacity, manufacturers quote decimal terabytes, filesystems reserve space, and snapshots need breathing room. Size the array from usable capacity backward instead of adding drive labels until the arithmetic looks close.
Large migrations expose network, disk, and backup weaknesses quickly. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. Apply “Separate raw capacity from usable capacity” to the first 5TB ingest as well as normal daily uploads so the design is realistic from day one.
Two-disk mirror option
A two-drive mirror is simple and gives straightforward single-drive redundancy, but half of raw capacity is dedicated to the mirror. At a 5TB starting point, choose drives large enough to leave growth headroom or you may be replacing both members sooner than expected.
A 5TB server benefits from modularity. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. Use “Two-disk mirror option” to decide which parts can be replaced independently—compute, application SSD, media pool, and backup target—before committing to a single appliance.
Four-bay redundancy options
Four-bay layouts can provide better usable capacity and more choices about redundancy. The exact RAID or ZFS layout should reflect how much fault tolerance you need, how easy replacement drives are to source, and whether the platform supports expansion without destructive rebuilding.
At five terabytes, capacity mistakes become costly to undo. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. For “Four-bay redundancy options,” model the protected, backed-up library after several years rather than building an array that merely fits the initial migration.
SSD space for database and thumbnails
Keep the operating system, database, thumbnails, and other high-I/O application data on SSD when possible. That prevents small random database work from competing with large sequential media reads on capacity HDDs and gives the user interface a more responsive foundation.
The storage plan should survive both growth and a failed component. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. “SSD space for database and thumbnails” is therefore a usable-capacity problem first and a drive-shopping problem second; raw labels alone do not describe the space you can safely consume.
Video percentage changes compute needs
The percentage of video changes compute requirements substantially. A 5TB library dominated by JPEG photos is different from 5TB of phone and camera video that may need playback conversion. Use video share and resolution to decide how much hardware-transcoding headroom is worthwhile.
Large migrations expose network, disk, and backup weaknesses quickly. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. Apply “Video percentage changes compute needs” to the first 5TB ingest as well as normal daily uploads so the design is realistic from day one.
Choosing CPU and memory for the workload
Compute for a 5TB server should be selected by active work, not total capacity alone. A large but mostly static archive can run on modest hardware, while several users importing and searching simultaneously may justify more cores, RAM, or accelerator capability.
A 5TB server benefits from modularity. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. Use “Choosing CPU and memory for the workload” to decide which parts can be replaced independently—compute, application SSD, media pool, and backup target—before committing to a single appliance.
Network speed for bulk imports
Bulk migration of 5TB can take many hours over 1GbE even before verification and backups. A 2.5GbE network can materially reduce local ingest time when both storage and source devices support it, but the server should not be upgraded in isolation from the rest of the network.
At five terabytes, capacity mistakes become costly to undo. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. For “Network speed for bulk imports,” model the protected, backed-up library after several years rather than building an array that merely fits the initial migration.
Local backup capacity
A local backup for 5TB needs its own capacity plan. It should accommodate future growth and versioning rather than matching the current library exactly. Decide whether the second copy lives on another NAS, DAS, removable drives, or a separate server before the primary array is built.
The storage plan should survive both growth and a failed component. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. “Local backup capacity” is therefore a usable-capacity problem first and a drive-shopping problem second; raw labels alone do not describe the space you can safely consume.
Offsite copy strategy
An offsite copy protects against events that affect the entire home or primary server. Cloud storage is one option; rotating drives or a second-location NAS are others. The critical point is independence from the same power supply, enclosure, and physical location.
Large migrations expose network, disk, and backup weaknesses quickly. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. Apply “Offsite copy strategy” to the first 5TB ingest as well as normal daily uploads so the design is realistic from day one.
Expansion without a disruptive rebuild
Expansion is easiest when planned before bays are full. Leave a drive bay, choose a platform with a documented expansion path, or separate compute from storage so the capacity layer can be replaced later without rebuilding the Immich application host.
A 5TB server benefits from modularity. A 5TB starting library needs growth and protection capacity. Model several years of uploads, redundancy, filesystem reserve, generated assets, snapshots, and backup copies before deciding how many drives or bays to purchase. Use “Expansion without a disruptive rebuild” to decide which parts can be replaced independently—compute, application SSD, media pool, and backup target—before committing to a single appliance.
Questions people ask
Immich hardware questions for this workload
How much raw storage do I need for a 5TB Immich library?
Start with the future usable library, add generated-data and free-space reserve, then account for the chosen redundancy. The resulting raw target will be materially larger than the starting 5TB. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
Is a 2-bay NAS enough for 5TB of Immich photos?
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 a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
What drive sizes make sense for a 5TB library?
Choose drives that leave meaningful growth headroom after redundancy instead of assembling an array that is almost full on day one. The best size depends on the number of bays and the redundancy layout. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
How much SSD space should a 5TB Immich server have?
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. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
Does a 5TB library require a powerful CPU?
Capacity alone does not dictate CPU power. A mostly static 5TB photo archive can run on modest compute, while several users, heavy 4K video, and fast machine-learning indexing can justify a stronger processor. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
Is 2.5GbE worth it for importing 5TB?
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 a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
How much backup storage should I buy for 5TB?
The backup target should cover the projected protected library plus any versioning or retention you intend to keep. Matching only today’s 5TB leaves no room for growth. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
Should I use RAID 1, RAID 5, RAID 6, or ZFS?
Choose redundancy from fault-tolerance needs, bay count, rebuild behavior, platform support, and usable capacity. The calculator provides a planning target, but the actual array should follow the NAS or ZFS implementation you deploy. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
How much room should I leave for library growth?
The right answer depends on library size, video share, users, background-job urgency, storage architecture, and the exact hardware configuration. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
Can I expand the server later without moving Immich?
The right answer depends on library size, video share, users, background-job urgency, storage architecture, and the exact hardware configuration. For a 5TB starting library, project several years of growth and size primary storage, redundancy, reserve space, and independent backups before choosing drive sizes.
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.