This NAS capacity growth planner works out when your NAS reaches the fill level you plan to act at, and when it would be full, from how fast your data really grows. It then shows what each upgrade buys you: the capacity after every drive you replace or add, the rebuilds it takes and the extra years of room.
Capacity comes from the same engine as the RAID Usable Capacity Calculator, with the rules Synology, QNAP, Unraid and OpenZFS publish for growing a pool. Results are in decimal TB (1 TB = 1,000 GB), the unit drives are sold in.
1. Your data and how fast it grows
Ticking presets adds their yearly amounts into the growth field. They are NTK starting points, not measured averages.
2. Your NAS
3. Your plan
Each option below is worked out with your platform's own rule for growing a pool, one drive at a time, and then run through the same forecast. Capacity often does not appear after the first bigger drive.
Drive costs for each option appear once you change a setting.
Rebuild time is the new drive's full capacity at the speed range you picked, an NTK planning assumption. For Synology Fast Repair, a custom speed and the risk while the array is degraded, use the RAID Rebuild Time and Risk Estimator.
Drive costs use the AU market price of each size, last changed 23 October 2026: the typical going rate across the Australian retailers we track, checked daily. A size stocked by fewer than 3 retailers shows no price. Confirm the price with the retailer before you buy.
Warranty: a drive's warranty term is the manufacturer's own, so check its datasheet. Your first step for a faulty product is usually the retailer that sold it. The ACCC explains your rights under the Australian Consumer Law at accc.gov.au.
Neither is the right answer for everyone. A 2-bay NAS suits data that will not outgrow it within the years you plan to keep it: it is smaller, quieter to place and a mirror is simple to run. When it fills, you grow it by replacing both drives with bigger ones, one at a time.
A 4-bay NAS costs more up front and holds more drives. It leaves room to add drives later, and with single parity more of its drive space holds your files: four 8 TB drives give 24 TB of layout capacity, two 8 TB drives mirrored give 8 TB.
The planner answers the question for your own numbers. With your data and growth, this is when each would reach your planning threshold:
Enter your data above to compare.
How each platform grows a pool, in the vendors' own terms. The planner applies these rules step by step.
| Layout | Adding a drive to an empty bay | Replacing drives with bigger ones |
|---|---|---|
| Synology SHR-1 and SHR-2 | Synology allows expansion by adding drives on JBOD, RAID 5, RAID 6, RAID TP, RAID F1, SHR-1 and SHR-2 (not RAID 0, RAID 1 or RAID 10). (Synology Knowledge Center) A drive added to a Synology SHR pool must be at least as large as the smallest drive in the pool. (Synology Knowledge Center) Adding a second drive to a single drive SHR pool adds redundancy only; capacity grows from the third drive. (Synology Knowledge Center) |
On an SHR pool of equal sized drives, capacity grows only after at least two drives (SHR-1) or four drives (SHR-2) have been replaced with larger ones, one at a time. (Synology Knowledge Center) On an SHR pool of mixed sizes, Synology says to replace the smallest drives with drives at least as large as the largest drive already in the pool. (Synology Knowledge Center) Synology's Replace Drive option needs a storage pool of at least two drives. On one-bay models without it, Synology says to back up your data to another place before replacing the drive. (Synology Knowledge Center) |
| Synology RAID 5 and RAID 6 | Synology allows expansion by adding drives on JBOD, RAID 5, RAID 6, RAID TP, RAID F1, SHR-1 and SHR-2 (not RAID 0, RAID 1 or RAID 10). (Synology Knowledge Center) | On classic RAID (not SHR) with equal sized drives, every drive must be replaced with a larger one before capacity grows. (Synology Knowledge Center) On classic RAID with mixed sizes, replacing a drive other than the smallest does not change capacity; the smallest must be replaced first. (Synology Knowledge Center) |
| Synology RAID 1 | Adding drives to a Synology RAID 1 pool adds mirror copies, not capacity (Synology RAID 1 is an N-way mirror). (Synology Knowledge Center) | On classic RAID (not SHR) with equal sized drives, every drive must be replaced with a larger one before capacity grows. (Synology Knowledge Center) |
| QNAP QTS RAID | QNAP can add disks to RAID 1, 5, 6, 50 and 60 groups while the pool stays online; each added disk must be at least as large as the smallest in the group. (QNAP) Adding disks to a QNAP RAID 1 group converts it to RAID 5. (QNAP) |
QNAP supports expanding by replacing disks on RAID 1, 5, 6 and 10; capacity then follows the smallest drive. (QNAP) On QNAP the Expand Capacity step becomes available only after every disk in the RAID group has been replaced and rebuilt. (QNAP) |
| Unraid array | Adding a data disk to an Unraid array expands its capacity. (Unraid documentation) A data disk added to an Unraid array must be no larger than the parity disks; a larger disk means upgrading parity first. (Unraid documentation) |
Replacing an Unraid data disk with a larger one rebuilds onto it and the file system grows to the new disk's size. (Unraid documentation) A parity swap procedure exists for replacing a data disk with one larger than the current parity disk. (Unraid documentation) |
| ZFS (TrueNAS and other OpenZFS) | RAIDZ expansion (adding a disk to an existing RAIDZ vdev) is a feature of OpenZFS 2.3.0. (OpenZFS) RAIDZ expansion keeps the parity level (a RAIDZ2 stays a RAIDZ2), can be repeated, and the added disk must be at least as large as the smallest disk in the vdev. (OpenZFS) Attaching a disk to a ZFS mirror adds another copy (two way becomes three way); it adds redundancy, not capacity. (OpenZFS) |
When ZFS drives are replaced with larger ones, the new space appears only after every disk in that mirror or RAIDZ group is larger (autoexpand, off by default). (OpenZFS) |
An expansion unit adds bays to some NAS models without replacing the NAS. Synology expansion units are supported on specific models only. (Synology, checked 2026-10-07) QNAP says a NAS storage pool cannot be expanded onto TR or TL series expansion units, except TL series SAS JBOD models such as the TL-R1620Sep-RP and TL-R1220Sep-RP. (QNAP, checked 2026-10-07) Check your own model before you plan on one; this planner does not model expansion units.
Four 4 TB drives in SHR-1 with Btrfs leave 11.48 TB available after Synology's system partitions and file system metadata. An 80% planning threshold is 9.19 TB.
| Start | Upgrade | Layout capacity after each step |
|---|---|---|
| Synology RAID 1, 2 x 4 TB (2-bay) | Replace both with 8 TB | 4 TB, then 8 TB |
| Synology SHR-1, 4 x 4 TB | Replace all four with 8 TB | 12, 16, 20, 24 TB |
| Synology RAID 5, 4 x 4 TB | Replace all four with 8 TB | 12, 12, 12, 24 TB |
| QNAP RAID 5, 4 x 4 TB | Replace all four with 8 TB | 12, 12, 12, 24 TB |
| Unraid, 8 TB parity, 3 x 4 TB data | Replace one data drive with 8 TB | 12 TB, then 16 TB |
| Unraid, 8 TB parity, 3 x 4 TB data | Upgrade parity to 12 TB, then one data drive to 12 TB | 12 TB (parity adds no space), then 20 TB |
Layout capacity before platform reserves, decimal TB. A 12 TB data drive is refused on the 8 TB parity array until parity is at least as large: that is the Unraid parity rule. Each replacement is one rebuild; an 8 TB drive at 50 to 100 MB/s takes about 22 h to 44 h.
Footage recorded at 7 GB a day and kept 30 days levels off at 0.21 TB once the first 30 days are recorded, and stays there however many years pass. Counting it as yearly growth instead would add the same footage again every year.
The presets in the planner are NTK starting points for readers with no history to measure, not averages measured from real NAS owners. Replace them with your own growth as soon as you can. This table runs each one through the planner's own formula: data after 5 years, and the space available you would need to stay under an 80% planning threshold.
| NTK starting point | Data now | Growth | Data after 5 years | Available space needed at 80% |
|---|---|---|---|---|
| Family photos and videos | 1 TB | 150 GB a year | 1.75 TB | 2.19 TB |
| Documents | 0.1 TB | 20 GB a year | 0.2 TB | 0.25 TB |
| Movie and TV library | 5 TB | 1,500 GB a year | 12.5 TB | 15.62 TB |
| Small business files | 1 TB | 300 GB a year | 2.5 TB | 3.12 TB |
| Computer and phone backups | 0.5 TB | 200 GB a year | 1.5 TB | 1.88 TB |
| Surveillance footage, kept a fixed number of days | 0 TB | 7 GB a day, kept 30 days (levels off at 0.21 TB) | 0.21 TB | 0.26 TB |
Space needed = data after 5 years / 80%. It is space available for your data, after redundancy and platform reserves; the RAID Usable Capacity Calculator turns it into drives.
Method last reviewed: 2026-10-14. Vendor rules checked at source: 2026-10-06 to 2026-10-14. Drive market prices last changed: 23 October 2026.
| Fact | Source | Checked |
|---|---|---|
| Synology expansion | ||
| On an SHR pool of equal sized drives, capacity grows only after at least two drives (SHR-1) or four drives (SHR-2) have been replaced with larger ones, one at a time. | Synology Knowledge Center | 2026-10-07 |
| On an SHR pool of mixed sizes, Synology says to replace the smallest drives with drives at least as large as the largest drive already in the pool. | Synology Knowledge Center | 2026-10-07 |
| On classic RAID (not SHR) with equal sized drives, every drive must be replaced with a larger one before capacity grows. | Synology Knowledge Center | 2026-10-07 |
| On classic RAID with mixed sizes, replacing a drive other than the smallest does not change capacity; the smallest must be replaced first. | Synology Knowledge Center | 2026-10-07 |
| Synology Storage Manager replaces one drive at a time. | Synology Knowledge Center | 2026-10-07 |
| Synology allows expansion by adding drives on JBOD, RAID 5, RAID 6, RAID TP, RAID F1, SHR-1 and SHR-2 (not RAID 0, RAID 1 or RAID 10). | Synology Knowledge Center | 2026-10-07 |
| A drive added to a Synology RAID 1, 5, 6 or F1 pool must be at least as large as the smallest drive in the pool. | Synology Knowledge Center | 2026-10-14 |
| A drive added to a Synology SHR pool must be at least as large as the smallest drive in the pool. | Synology Knowledge Center | 2026-10-14 |
| Adding a second drive to a single drive SHR pool adds redundancy only; capacity grows from the third drive. | Synology Knowledge Center | 2026-10-07 |
| Adding drives to a Synology RAID 1 pool adds mirror copies, not capacity (Synology RAID 1 is an N-way mirror). | Synology Knowledge Center | 2026-10-07 |
| Synology's Replace Drive option needs a storage pool of at least two drives. On one-bay models without it, Synology says to back up your data to another place before replacing the drive. | Synology Knowledge Center | 2026-10-14 |
| Synology expansion units are supported on specific models only. | Synology Knowledge Center | 2026-10-07 |
| Synology reserves | ||
| Synology's RAID Calculator reserves about 10 GB per drive for the DSM system and swap partitions. | Synology Knowledge Center | 2026-10-07 |
| When a volume is created, Synology reserves 4% of its capacity for Btrfs metadata, or 2% for ext4. | Synology Knowledge Center | 2026-10-07 |
| Synology's own RAID Calculator counts SHR-2 capacity only where at least four drives reach a size tier; capacity above the fourth largest drive is counted as unused. | Synology Knowledge Center | 2026-10-07 |
| QNAP expansion and reserves | ||
| QNAP supports expanding by replacing disks on RAID 1, 5, 6 and 10; capacity then follows the smallest drive. | QNAP | 2026-10-07 |
| On QNAP the Expand Capacity step becomes available only after every disk in the RAID group has been replaced and rebuilt. | QNAP | 2026-10-07 |
| QNAP can add disks to RAID 1, 5, 6, 50 and 60 groups while the pool stays online; each added disk must be at least as large as the smallest in the group. | QNAP | 2026-10-07 |
| Adding disks to a QNAP RAID 1 group converts it to RAID 5. | QNAP | 2026-10-07 |
| QNAP says a NAS storage pool cannot be expanded onto TR or TL series expansion units, except TL series SAS JBOD models such as the TL-R1620Sep-RP and TL-R1220Sep-RP. | QNAP | 2026-10-07 |
| QNAP reserves about 70 GB per storage pool and 20 GB per static volume for storage configuration data. | QNAP | 2026-10-07 |
| QNAP also reserves 1% of each RAID group's total capacity for RAID metadata, up to 150 GB per group. | QNAP | 2026-10-07 |
| On QNAP ext4 volumes over 100 GB, file system metadata takes between 0.8% and 1.8% of the volume (larger volumes need less). | QNAP | 2026-10-07 |
| Free space | ||
| QNAP's pool and volume usage alert threshold defaults to 80% and can be changed; it is an alert, not a limit. | QNAP | 2026-10-07 |
| QNAP lists slower performance, failed snapshots or backups and refused writes as risks once a pool or volume is nearly full. | QNAP | 2026-10-07 |
| TrueNAS calls 80% full a starting point, not a hard limit: write once archival pools can reasonably run to 90 or 95%, while heavy random I/O pools may need to stay below 80%. | TrueNAS (iXsystems) | 2026-10-07 |
| ZFS | ||
| When ZFS drives are replaced with larger ones, the new space appears only after every disk in that mirror or RAIDZ group is larger (autoexpand, off by default). | OpenZFS | 2026-10-07 |
| Attaching a disk to a ZFS mirror adds another copy (two way becomes three way); it adds redundancy, not capacity. | OpenZFS | 2026-10-07 |
| RAIDZ expansion (adding a disk to an existing RAIDZ vdev) is a feature of OpenZFS 2.3.0. | OpenZFS | 2026-10-07 |
| RAIDZ expansion keeps the parity level (a RAIDZ2 stays a RAIDZ2), can be repeated, and the added disk must be at least as large as the smallest disk in the vdev. | OpenZFS | 2026-10-07 |
| After RAIDZ expansion, blocks written before it keep their old data to parity ratio; only new blocks use the wider ratio, and tools may report slightly less space than expected. | OpenZFS | 2026-10-07 |
| OpenZFS reports RAIDZ pool space as if every block were 128K, using the vdev's original width. | OpenZFS | 2026-10-14 |
| The OpenZFS slop reserve is 1/32 of pool space, capped at 128 GiB, and never less than 128 MiB (or half the pool on a pool smaller than 256 MiB). | OpenZFS | 2026-10-14 |
| Unraid | ||
| Adding a data disk to an Unraid array expands its capacity. | Unraid documentation | 2026-10-07 |
| Replacing an Unraid data disk with a larger one rebuilds onto it and the file system grows to the new disk's size. | Unraid documentation | 2026-10-07 |
| A data disk added to an Unraid array must be no larger than the parity disks; a larger disk means upgrading parity first. | Unraid documentation | 2026-10-07 |
| Each parity disk must be at least as large as the largest data disk (dual parity: both, but they may differ in size from each other). | Unraid documentation | 2026-10-06 |
| A parity swap procedure exists for replacing a data disk with one larger than the current parity disk. | Unraid documentation | 2026-10-06 |
| Unraid does not stripe across drives: each file is stored on a single disk. | Unraid documentation | 2026-10-06 |
| Drive sizes | ||
| Seagate's IronWolf Pro NAS drive range goes up to 32 TB. | Seagate | 2026-10-07 |
More space is not a backup. RAID keeps your files available when a drive fails. It does not undo deletion, ransomware, theft or a fire, so keep a separate copy. Read our 3-2-1 backup guide.
Ask us anything about NAS, storage, or infrastructure. We reply by email.
Message sent!
We'll be in touch soon.