How to Plan NAS Capacity for 5 Years of Growth

Start with usable capacity, not raw drive capacity

For a five-year NAS purchase, size the system to provide enough usable capacity after RAID or parity, filesystem overhead, and free-space headroom. Do not treat the sum of the drive capacities as storage available for files.

A practical planning formula is:

Required usable NAS capacity = projected five-year data / target utilization

For example, if your data is expected to reach 30 TB and you want to keep the NAS at no more than 75% full:

30 TB / 0.75 = 40 TB of usable capacity

That 40 TB must be available after RAID or parity overhead and after allowing for filesystem and metadata overhead. Your backup target is a separate capacity decision.

The safest buying process is:

1. Measure how much data you have today.
2. Estimate annual growth and large one-time additions.
3. Choose the required free-space headroom.
4. Account for RAID, parity, and filesystem overhead.
5. Size backups separately.
6. Check drive bays, expansion options, networking, and workload requirements.

Separate the capacity numbers

NAS capacity is commonly described using several different numbers. Keep them separate when comparing systems.

Raw capacity

Raw capacity is the sum of the advertised drive capacities:

Raw capacity = number of drives × capacity of each drive

Eight 12 TB drives therefore have:

8 × 12 TB = 96 TB raw capacity

Raw capacity does not account for RAID, parity, a filesystem, snapshots, or the free space needed for healthy long-term operation.

Drive manufacturers generally advertise capacity in decimal units, while operating systems may display capacity using decimal or binary units. The same drive can therefore appear to have a smaller number in a NAS interface without anything being wrong.

RAID or parity capacity

RAID protects against some drive failures and can improve availability, but it consumes capacity. The exact result depends on the RAID level, number of drives, drive sizes, filesystem, and implementation.

Approximate planning formulas for equal-size drives are:

• RAID 0: number of drives × drive capacity
• RAID 1: approximately one drive's capacity in a two-drive mirror
• RAID 5: approximately (number of drives - 1) × drive capacity
• RAID 6: approximately (number of drives - 2) × drive capacity
• RAID 10: approximately half of the raw capacity with matched mirrored pairs

These are planning estimates, not guaranteed usable-capacity figures. Mixed drive sizes, reserved space, metadata, sector layout, hot spares, and the NAS operating system can reduce the result.

ZFS requires additional care. RAIDZ1, RAIDZ2, RAIDZ3, mirrors, special vdevs, metadata allocation, record sizes, and reserved space can all affect the amount of storage available for files. Use the NAS or ZFS calculator for the specific drive layout rather than assuming a simple RAID formula is exact.

Filesystem and system overhead

A filesystem needs space for metadata and internal structures. Snapshots, deduplication metadata, checksums, quotas, shared folders, and reserved space can also consume capacity.

The exact overhead is implementation-dependent, so do not subtract a made-up fixed percentage from every NAS. Treat the vendor's displayed usable capacity as an estimate and leave additional room for operational headroom.

Free-space headroom

A NAS should not be planned to run permanently at 95% or 100% full. Low free space can make expansion, snapshots, temporary files, indexing, virtual machines, and large file operations more difficult.

A useful planning range is to reserve roughly 20% to 30% of usable capacity for headroom, depending on the workload. Media storage with few snapshots may tolerate a different target from a busy NAS running databases, containers, surveillance recording, or frequent snapshots.

If you want to keep the NAS at 75% full or less:

Required usable capacity = projected data / 0.75

If you want a 70% utilization ceiling:

Required usable capacity = projected data / 0.70

These percentages are planning choices, not universal technical limits. Workloads that create large temporary files or snapshots may require more room.

Estimate five years of growth

Start with actual data rather than the capacity of the disks currently installed.

Include:

• Documents, photos, and personal files
• Existing desktop and laptop backups
• Phone and camera imports
• Video projects and other large working files
• Plex or other media libraries
• Security-camera recordings
• NAS snapshots and recycle-bin retention
• Virtual machines, containers, and application data
• Shared data from additional users or offices
• One-time migrations that may occur during the five-year period

For steady percentage growth, use compound growth:

Future data = current data × (1 + annual growth rate)^number of years

For example, 12 TB growing by 20% annually for five years becomes approximately:

12 TB × 1.20^5 = 29.9 TB

A simple linear estimate can be useful when growth comes from a known recurring amount:

Future data = current data + (annual added data × number of years)

Use both approaches when possible. Compound growth is useful for expanding photo, video, or business datasets. Linear growth may be more realistic when you add a predictable number of surveillance cameras or a fixed amount of media each year.

Also model large events separately. A planned migration of 8 TB, a new camera system, or a major video project should not disappear inside a small annual-growth assumption.

Worked example: sizing a five-year NAS

Assume the following:

• Current files and application data: 12 TB
• Expected annual growth: 20%
• Planning period: five years
• Desired maximum utilization: 75%
• Separate backup target: to be sized independently
• Equal-capacity data drives
• No assumed exact filesystem overhead

Step 1: Project the data

12 TB × 1.20^5 = approximately 29.9 TB

The NAS therefore needs to hold about 30 TB of actual data at the end of year five.

Step 2: Add free-space headroom

With a 75% maximum utilization target:

29.9 TB / 0.75 = approximately 39.9 TB

You should therefore look for about 40 TB of usable NAS capacity after RAID or parity and before relying on any unverified assumptions about filesystem overhead.

Step 3: Compare an illustrative drive layout

Consider eight 12 TB drives as a planning example:

8 × 12 TB = 96 TB raw

With an approximate RAID 6 calculation:

(8 - 2) × 12 TB = 72 TB before filesystem overhead

That appears to exceed the approximately 40 TB usable-capacity target, but the final NAS display will be lower or different depending on the NAS platform and filesystem. It may also be appropriate to reserve additional space for snapshots, applications, or future growth beyond the five-year estimate.

A six-drive RAID 6 example would be:

(6 - 2) × 12 TB = 48 TB before filesystem overhead

That is much closer to the target and leaves less flexibility for unexpected growth, snapshots, or a lower utilization target. It may be adequate for one workload but a poor fit if the NAS will later become a media server, backup repository, or surveillance recorder.

This example does not recommend a particular drive size or NAS model. It shows why raw capacity alone is not enough and why a near-term calculation should not be the only sizing criterion.

Size backups as a separate system requirement

RAID is not backup.

RAID or parity can help keep a NAS available after certain drive failures. It does not protect against accidental deletion, ransomware, file corruption, theft, fire, water damage, or a failed NAS enclosure. Some corruption and deletion can also be replicated across a redundant array.

Plan backup capacity separately by deciding:

• Which data must be backed up
• How many historical versions to retain
• How often backups run
• Whether backups are local, off-site, or cloud-based
• Whether the backup target uses deduplication or compression
• How long deleted files should remain recoverable
• Whether the backup must cover the NAS configuration and applications

A backup target does not always need to equal the NAS's raw capacity, but it must be large enough for the protected data plus retention and versioning. A versioned backup of 30 TB of changing data can require substantially more than 30 TB, while a backup of mostly static data may grow more slowly.

Use a separate capacity estimate:

Backup capacity = protected data + retained versions + backup metadata + future growth

Keep at least one backup copy independent of the NAS. For important data, also consider an off-site copy.

Account for Plex, surveillance, and other workloads

The files you store are only part of the capacity calculation.

Plex and media libraries

Plex capacity depends on your existing library, acquisition rate, remuxes, duplicate formats, subtitles, and whether you retain original and optimized copies. Transcoding is primarily a CPU, GPU, or hardware-acceleration decision, but transcoding jobs can also create temporary files.

Include space for:

• Original media
• Alternate encodes or optimized versions
• Subtitles and artwork
• Plex metadata
• Temporary transcoding files
• Downloads or staging folders

If your library is growing quickly, size from the actual average monthly addition rather than assuming a small percentage growth rate.

Surveillance recording

Surveillance storage is driven by camera count, resolution, frame rate, codec, motion activity, retention period, and recording schedule.

A simple conceptual formula is:

Recording capacity = cameras × average bitrate × recording time × retention period

Convert the bitrate into a consistent unit before calculating. Motion-triggered recording can use less capacity than continuous recording, but the difference depends on the environment and camera settings.

Surveillance can also change the RAID decision. A continuously written array may benefit from a layout and drive type intended for sustained NAS workloads, while a large retention requirement can dominate the capacity calculation.

Snapshots, containers, and virtual machines

Snapshots are not automatically a full second copy, but they consume space as blocks change. The amount depends on change rate and retention policy. A NAS running virtual machines, databases, containers, or active project files may need more free space than a simple file archive.

If snapshots are important, define a retention policy before buying:

• Frequent short-term snapshots for accidental deletion
• Less frequent long-term snapshots for older recovery points
• A separate backup for disasters and ransomware recovery

Choose expansion capacity deliberately

A smaller NAS can meet today's requirement and still be the wrong five-year purchase if it has no practical expansion path.

Check:

• Number of internal drive bays
• Whether empty bays can be added later
• Whether expansion shelves are supported
• Whether expansion creates a separate pool or expands the existing pool
• Whether the RAID or storage platform supports replacing drives with larger ones
• Whether expansion requires replacing every drive
• Maximum supported volume or pool size
• Whether the network connection can support the future workload

Expansion is not always simple. Some arrays can be expanded one drive at a time; others require a particular sequence, matching drive groups, or a rebuild after each replacement. Rebuilds can take a long time and place additional stress on the remaining drives.

If future expansion is important, compare the cost and risk of:

• Buying more bays now
• Installing larger drives later
• Adding an expansion enclosure
• Creating a second storage pool
• Replacing the NAS before the original reaches its limit

Buying more bays does not automatically provide more usable capacity. The storage layout, supported expansion method, and future drive availability matter.

Capacity is not the same as performance

A high-capacity NAS may still be a poor fit if the workload needs more network or compute performance.

Consider:

• Network speed and whether clients can use it
• Number of simultaneous users
• Plex transcoding requirements
• Surveillance write workload
• Virtual machines and databases
• CPU and memory requirements
• SSD storage for applications or metadata
• Backup windows and restore speed

SSD cache usually does not solve a capacity problem. It may help selected repeated-access or metadata-heavy workloads, but it consumes bays, adds cost, and does not replace adequate RAM, network bandwidth, or a properly sized hard-drive pool. Do not subtract cache capacity from the main storage requirement unless the NAS design specifically uses it as a permanent data tier.

NAS sizing checklist

Before buying, confirm the following:

• [ ] Current data has been measured rather than estimated from computer drive sizes.
• [ ] Five-year growth has been calculated using realistic annual and one-time additions.
• [ ] Raw capacity has been separated from RAID or parity capacity.
• [ ] Filesystem, metadata, snapshot, and reserved-space effects have been considered.
• [ ] A free-space target, such as 70% to 80% maximum utilization, has been selected.
• [ ] Plex media, surveillance recordings, applications, and temporary files are included.
• [ ] Backup capacity and retention are calculated separately.
• [ ] The selected RAID or ZFS layout matches the failure-tolerance requirement.
• [ ] Drive bays and expansion methods support the expected growth.
• [ ] Larger future drives can be used if the plan depends on replacing drives.
• [ ] Network, CPU, memory, and transcoding requirements match the intended workload.
• [ ] A restore test is part of the backup plan.
• [ ] The purchase still leaves room for unexpected growth rather than only meeting the forecast.

If your projected capacity is close to the limit, choose the next practical tier instead of planning to fill the array immediately. Then compare NAS enclosures and storage servers using the required bay count, expansion approach, RAID or ZFS support, networking, and workload needs. You can Browse NAS or review NAS and storage servers before narrowing the capacity and drive layout.