How Much NAS Storage for a Small Business?

The short answer: size for usable capacity plus growth

A small business should usually plan for three to five years of usable NAS capacity, while keeping roughly 15–20% of that usable space free for normal operation, snapshots, temporary files, and growth.

Do not size the system from the drive labels alone. A NAS advertised with a certain raw capacity loses space to:

1. RAID or parity protection
2. Filesystem metadata and reserved space
3. Snapshots, recycle bins, and temporary files
4. Required free-space headroom
5. Future data growth
6. Backup versions, if backups are stored on the NAS

A practical planning formula is:

Required raw capacity = projected primary data / (RAID-adjusted efficiency × filesystem allowance × free-space target)

The exact result depends on the RAID level, filesystem, snapshot policy, drive sizes, and backup design.

Raw capacity is not usable capacity

Raw capacity is the sum of the drive labels:

Raw capacity = number of drives × advertised drive capacity

For example, six 8 TB drives provide:

6 × 8 TB = 48 TB raw capacity

That does not mean 48 TB is available for files. Drive manufacturers generally label capacity in decimal TB, while operating systems may display capacity in tebibytes (TiB). The displayed number will therefore look smaller even before RAID and filesystem overhead are considered.

When comparing NAS options, use the same unit and ask whether a capacity figure is:

• Raw capacity
• RAID-adjusted capacity
• Filesystem-reported capacity
• Recommended usable capacity after free-space headroom

These are different numbers.

RAID and parity reduce usable capacity

RAID protects availability against certain drive failures, but it consumes capacity. The approximate usable capacity before filesystem overhead is:

Layout	Approximate usable capacity	Main trade-off
RAID 1 or two-drive mirror	One drive’s capacity	Simple protection, but about half of raw capacity is used for the mirror
RAID 5	(number of drives - 1) × smallest drive	One-drive parity; less overhead, but greater rebuild and failure-risk considerations
RAID 6	(number of drives - 2) × smallest drive	Two-drive parity; more capacity overhead but stronger fault tolerance
RAID 10	About half of raw capacity	Mirroring plus striping; capacity and failure tolerance depend on which drives fail
ZFS mirror or RAIDZ layouts	Depends on the vdev layout	Expansion, redundancy, and usable capacity depend heavily on how the pool is designed

These formulas are planning approximations. The smallest drive generally limits a RAID group, and the NAS operating system may report less capacity than the simple formula suggests.

RAID is not a backup. A RAID array can remain available after a drive failure, but it does not protect against accidental deletion, ransomware, fire, theft, severe hardware failure, or corrupted files being replicated across the array.

Consider the cost of parity before buying drives

A higher-capacity RAID level can look attractive because it provides more usable space, but the number of drives and the required fault tolerance matter. For business data, choosing a layout only because it produces the most capacity may leave too little protection or too few expansion options.

Check:

• How many drive bays the NAS has
• Whether the system supports the RAID or ZFS layout you want
• Whether replacing a failed drive with a larger one is supported
• Whether the array can expand safely
• Whether expansion requires replacing every drive
• Whether a backup exists before changing the pool

Do not assume that a RAID group can be expanded one drive at a time or that every ZFS pool layout can be expanded in the same way. Confirm the storage platform’s documented behavior before relying on future expansion.

Allow for filesystem overhead and free space

After RAID, the filesystem uses some capacity for metadata, checksums, allocation structures, snapshots, and other functions. The exact allowance varies by filesystem and configuration, so there is no universal percentage that applies to every NAS.

ZFS, for example, can also use space for copy-on-write behavior, snapshots, and special dataset settings. SSD cache does not eliminate this overhead and should not be counted as a replacement for primary storage.

For an early planning estimate, you can apply an explicit allowance:

Post-filesystem planning capacity = RAID-adjusted capacity × (1 - assumed filesystem allowance)

If you use a 5% planning allowance in a spreadsheet, label it as an assumption rather than a guaranteed specification. Replace it with the NAS vendor’s or filesystem’s documented guidance when available.

You should also avoid filling a business NAS to its absolute reported maximum. A practical target is to keep approximately 15–20% free, although the ideal amount depends on snapshots, applications, database workloads, and the filesystem.

Recommended working capacity = post-filesystem planning capacity × 0.80 to 0.85

This free-space target is not lost forever; it is capacity you deliberately reserve to keep the system easier to manage and less likely to become constrained.

Calculate current data and future growth

Start with an inventory rather than guessing from the number of employees.

Include:

• Shared documents and project folders
• Existing file-server or cloud data to be migrated
• Email exports and business databases
• Photos, video, design files, and other media
• User home directories
• Application data
• NAS snapshots and recycle bins
• Local computer backups
• Surveillance recordings
• Plex or other media libraries, if the NAS will host them

Separate data into categories with different growth rates. Office documents may grow slowly, while video, design projects, surveillance footage, and local computer backups can grow much faster.

A basic projection is:

Projected primary data = current data + (annual growth × planning years)

Add a contingency if the business expects new employees, acquisitions, larger projects, regulatory retention, or a migration from another storage system.

Backups need their own capacity calculation

Decide where backups will live before finalizing the NAS capacity. A backup stored only on the same NAS does not provide full protection against failure, theft, ransomware, or a site-level incident.

A sound design normally follows the 3-2-1 principle:

• Keep at least three copies of important data
• Use at least two different types of storage or media
• Keep at least one copy off-site

Backup capacity depends on:

• The amount of source data
• Full and incremental backup behavior
• Retention period
• Number of computers and servers
• Versioning frequency
• Deduplication and compression
• Whether immutable or offline copies are used

If the NAS is the primary file store, plan a separate backup destination—such as another NAS, cloud storage, removable media, or an off-site system. Do not simply add “one extra copy” to the same RAID pool and call the business protected.

Worked example: a small team with four years of growth

Suppose a small business has:

• 12 TB of current primary data
• 2 TB of expected annual growth
• A four-year planning horizon
• A requirement to retain about 20% free space
• An assumed 5% filesystem planning allowance for this estimate

First calculate projected primary data:

12 TB + (2 TB × 4) = 20 TB

Now consider a six-drive array using 8 TB drives with a two-drive parity layout:

Raw capacity = 6 × 8 TB = 48 TB

Approximate parity-adjusted capacity:

(6 - 2) × 8 TB = 32 TB

Apply the illustrative 5% filesystem allowance:

32 TB × 0.95 = 30.4 TB

Reserve 20% as operating headroom:

30.4 TB × 0.80 = 24.32 TB recommended working capacity

Under these assumptions, the array provides about 24.32 TB of planned working capacity, compared with 20 TB of projected primary data. That leaves approximately 4.32 TB for variation in growth and operational data.

This example is not a claim about the exact capacity reported by a particular NAS. The actual figure depends on drive formatting, the NAS operating system, RAID or ZFS implementation, snapshots, reserved space, and the unit conversion shown by the interface.

The example also does not include an independent backup target. If the business needs multiple backup versions, the backup destination may require capacity comparable to—or greater than—the primary data set.

Account for special workloads

File sharing and office documents

Documents are usually easy to estimate from current usage and historical growth. The more important issues are permissions, snapshots, backup retention, and whether cloud synchronization will create duplicate local data.

Workstation and server backups

A NAS used for endpoint backups needs room for multiple versions, not just one copy of each current file. Include operating-system images, application data, and retention rules in the estimate.

Surveillance

Surveillance capacity is driven by camera count, resolution, frame rate, codec, motion activity, and retention days. A useful planning relationship is:

Required storage = total recording bitrate × retention time

For multiple cameras:

Total bitrate = number of cameras × average bitrate per camera

Use the camera and surveillance-platform documentation for actual bitrate behavior. Motion-triggered recording can use less space than continuous recording, but the saving depends on the environment and motion settings.

Plex and media libraries

A NAS hosting a Plex library needs space for the original media, subtitles, artwork, metadata, and possibly transcoding-related temporary files. Transcoding performance is a separate hardware and network question; adding SSD cache does not create more media capacity.

Databases and active applications

Databases, virtual machines, containers, and heavily changing files may need more free space and faster storage behavior than ordinary shared folders. Size capacity and performance separately. A large HDD array may provide enough space but still be unsuitable for a workload that requires low latency or sustained random I/O.

SSD cache does not change the storage calculation

SSD cache can sometimes improve access patterns, but it is not a substitute for:

• More primary drive capacity
• RAID or other redundancy
• A proper backup
• More memory or CPU resources
• Faster network infrastructure
• A suitable storage layout

Treat cache as a performance feature with workload-specific benefits. Do not add its nominal SSD capacity to the NAS’s usable storage total.

Plan networking separately from capacity

Network speed does not change how many terabytes the NAS can store, but it affects how practical the system is for the team.

For a rough theoretical conversion:

Bandwidth (Gbps) / 8 = theoretical GB/s

Real file-transfer performance is lower because of protocol overhead, drive speed, RAID behavior, encryption, client limitations, and simultaneous users. A business choosing a NAS for large media files, backups, or virtualization should evaluate the full path:

• NAS network ports
• Switch capacity
• Client network adapters
• Cabling
• Drive and RAID performance
• Number of concurrent users

Capacity and networking should be selected together, but one cannot compensate for the other.

Choose expansion capacity deliberately

Buying a NAS with just enough bays for today’s drives can force an expensive migration later. Before purchase, decide whether you prefer:

• A larger initial array
• Empty bays for future drives
• Drive-by-drive replacement with larger models
• A second NAS as a separate storage or backup system
• Cloud or off-site expansion

More bays do not automatically guarantee simple expansion. Some platforms require a particular pool layout, replacement sequence, or rebalancing process. Check the documented expansion method and the backup requirements before treating unused bays as guaranteed future capacity.

If the business cannot tolerate downtime during expansion or a rebuild, that requirement should influence the NAS layout and backup plan from the beginning.

Small-business NAS sizing checklist

Use this checklist before choosing the NAS and drives:

• [ ] Measure current data in each category rather than estimating from employee count.
• [ ] Project growth for at least three years, or longer if replacing the system is difficult.
• [ ] Decide whether the NAS will store primary files, backups, surveillance, media, or all of them.
• [ ] Calculate raw capacity from the number and size of drives.
• [ ] Subtract RAID, mirror, or parity capacity.
• [ ] Account for decimal TB versus displayed TiB.
• [ ] Allow for filesystem metadata, snapshots, checksums, and reserved space.
• [ ] Keep approximately 15–20% free for normal operation unless the platform recommends otherwise.
• [ ] Size backup storage separately from the primary NAS.
• [ ] Apply the 3-2-1 rule and keep at least one backup off-site.
• [ ] Confirm drive compatibility and the smallest-drive limitation for the chosen array.
• [ ] Verify how the NAS expands, rebuilds, and replaces drives.
• [ ] Check whether the NAS has enough bays for the expected growth.
• [ ] Separate capacity requirements from network and application performance requirements.
• [ ] Treat SSD cache as a performance option, not usable capacity.
• [ ] Test restores instead of assuming that a completed backup is recoverable.

After calculating the required working capacity, compare the available bay count, supported storage layouts, networking, backup options, and expansion path. You can Browse NAS or review NAS and storage servers before narrowing the choices to systems that fit the capacity plan.