How Much Free Space Should You Leave on a NAS?

The practical answer is to keep at least 20% of your NAS pool free. For ZFS, copy-on-write filesystems, frequent snapshots, virtual machines, databases, or heavy file churn, a 25–30% reserve is often a safer planning target.

Measure that percentage from the NAS’s usable pool capacity, not from the combined raw capacity printed on the drives.

For example, if your NAS reports 30 TB of usable pool capacity:

• 20% free means keeping about 6 TB unused.
• You should plan to store no more than about 24 TB of active data.
• A 25% reserve means keeping 7.5 TB free.
• A 30% reserve means keeping 9 TB free.

This free space is not a substitute for backups. RAID can keep a system available after some drive failures, but it does not protect against accidental deletion, ransomware, corruption, theft, or a failed NAS.

Why a NAS needs unused capacity

A NAS uses free space for more than storing files. It may also need room for:

• Filesystem metadata and directory updates
• Temporary files and uploads
• Snapshot changes
• RAID or parity maintenance
• Scrubs, resilvering, and other recovery operations
• File versioning and recycle bins
• Docker containers, virtual machines, databases, or surveillance recordings
• Drive replacement and pool expansion workflows
• Future data growth

When a pool becomes nearly full, routine operations have fewer free blocks to use. Performance may become less consistent, snapshots can consume capacity faster than expected, and some NAS platforms may issue critical capacity warnings.

The exact warning thresholds vary by NAS operating system and filesystem. Treat the vendor’s warnings as operational limits, not as your long-term capacity target.

Use usable capacity, not raw drive capacity

NAS capacity passes through several reductions before it becomes available for files.

1. Raw drive capacity

Raw capacity is the sum of the advertised drive capacities.

For example:

4 drives × 12 TB = 48 TB raw capacity

Drive manufacturers normally use decimal terabytes:

1 TB = 1,000,000,000,000 bytes

Your NAS may display capacity in TB, TiB, or a mixture of decimal and binary units, so the number shown in the interface will not necessarily match the number on the drive labels.

2. RAID or parity overhead

RAID protects availability by using mirroring or parity, but the protection consumes capacity.

Simplified examples:

Layout	Approximate usable capacity before filesystem overhead
Two-way mirror	About 50% of raw capacity
Three-way mirror	About one-third of raw capacity
Single-parity layout	Roughly the capacity of all drives minus one drive
Dual-parity layout	Roughly the capacity of all drives minus two drives
RAID 10-style layout	Commonly about 50% of raw capacity

These are planning approximations. Actual capacity depends on the NAS implementation, drive sizes, reserved space, and whether the system uses a RAID group, storage pool, RAIDZ vdev, or another layout.

3. Filesystem and system overhead

The filesystem and NAS operating system use some capacity for:

• Metadata
• Allocation structures
• Journaling or copy-on-write records
• System partitions
• Reserved blocks
• Snapshots and version history

This overhead varies by platform and workload. Do not assume that every byte left after RAID calculations is available for normal files.

4. Free-space headroom

After RAID and filesystem overhead, leave your operating reserve. For most general-purpose NAS pools, start with:

• 20% free: sensible minimum planning target
• 25% free: safer for snapshots, ZFS, and changing workloads
• 30% or more: useful for virtual machines, databases, frequent large-file changes, or uncertain growth

A NAS that is “only” 80% full may be healthy for one workload and too full for another. The filesystem, snapshot policy, and rate of data change matter.

Recommended free-space targets by workload

NAS workload	Suggested free-space target
Documents, photos, and ordinary file sharing	At least 20%
Media library with limited snapshots	About 20%
ZFS or another copy-on-write filesystem	20–30%
Frequent snapshots or file versioning	25–30% or more
Virtual machines and databases	25–30% or more
Active video editing or large temporary files	25–30% or more
Surveillance with continuous recording	20% minimum, plus planned recording reserve
Unknown or rapidly changing workload	30% is a safer starting point

These are capacity-planning guidelines, not universal technical limits. Check the documentation for your NAS operating system and filesystem.

Snapshots need their own capacity allowance

Snapshots do not usually consume a fixed percentage of the pool. They consume space as data changes after the snapshot is created.

A snapshot of a mostly unchanged dataset may use little additional capacity. A snapshot of a dataset where large files are rewritten or deleted can consume much more. Video editing projects, virtual machines, databases, and frequently modified file shares can create snapshot growth quickly.

A useful planning model is:

Required usable capacity =
current data
+ expected growth
+ snapshot growth
+ temporary or working space
+ backup staging space
+ free-space headroom

Snapshot space should be monitored over time rather than estimated once and ignored. Set retention policies deliberately, such as keeping frequent snapshots for a short period and less frequent snapshots for longer-term recovery.

Deleting a file may not immediately return all of its space if snapshots still reference the old blocks. If a NAS appears not to regain space after deletion, check snapshots, recycle bins, replication copies, and backup jobs.

Worked example: sizing a four-drive NAS

Suppose you are considering four 12 TB drives in a single-parity layout.

Step 1: Calculate raw capacity

4 × 12 TB = 48 TB raw capacity

Step 2: Account for parity

For a simplified single-parity estimate:

48 TB - 12 TB parity equivalent = about 36 TB before filesystem overhead

The actual value shown by the NAS may be lower because of unit conversion, filesystem overhead, reserved space, and the specific storage layout.

Step 3: Leave operational headroom

Using a 20% target on the approximate 36 TB usable figure:

36 TB × 20% = 7.2 TB free

That leaves roughly:

36 TB - 7.2 TB = 28.8 TB for planned data

This does not mean you should immediately fill the pool to 28.8 TB. You still need to account for snapshots, temporary files, surveillance retention, application data, and growth.

If the NAS will use ZFS with frequent snapshots or host virtual machines, a 30% target may be more appropriate:

36 TB × 30% = 10.8 TB free

That leaves roughly 25.2 TB for planned active data before considering other workload-specific reserves.

A better growth-based calculation

Capacity should be sized for the end of your planning period, not just today’s files.

Assume:

• Current data: 20 TB
• Expected growth: 2 TB per year
• Planning period: 3 years
• Snapshot allowance: 4 TB
• Temporary or backup staging space: 2 TB
• Desired free headroom: 20%

First calculate the planned occupied capacity:

20 TB current data
+ (2 TB × 3 years) growth
+ 4 TB snapshots
+ 2 TB staging
= 32 TB planned usage

Then account for the 20% free-space target:

32 TB / 0.80 = 40 TB required usable capacity

A pool that provides only about 36 TB before filesystem overhead would not meet this plan comfortably. You would need larger drives, more drives, a different RAID layout, a second NAS, or a shorter growth horizon.

The same formula can be adapted for a 25% reserve:

Planned usage / 0.75 = required usable capacity

For a 30% reserve:

Planned usage / 0.70 = required usable capacity

How backups affect NAS capacity planning

Backups can require substantial capacity, but they should not be confused with RAID.

RAID is not a backup

RAID or parity can help a NAS continue operating after certain drive failures. It does not protect against:

• Accidental deletion
• Ransomware or malware
• A damaged or corrupted file replicated across the array
• Theft, fire, flooding, or power events
• A failed NAS motherboard or storage controller
• Incorrect sync or deletion commands

Maintain an independent backup using a 3-2-1-style approach where practical:

• At least three copies of important data
• On at least two types of storage or devices
• With at least one copy off-site or otherwise isolated

A second NAS, external drives, cloud storage, or another backup target may be suitable depending on the data and recovery requirements. A backup copy inside the same RAID pool is not independent protection.

Include backup staging when necessary

Some backup jobs temporarily create local snapshots, deduplication databases, or staging files. If your NAS performs local backup tasks, include that working space in the capacity calculation.

If the NAS is only the primary storage and backups go directly to an external destination, you may not need to reserve a second full copy inside the primary pool. Confirm how your backup software works before reducing the reserve.

Special considerations for Plex and media libraries

Plex libraries often contain large files that are relatively stable, so a 20% reserve may be adequate for the media pool. However, account for:

• New media added over time
• Temporary download and transcoding directories
• Metadata and artwork
• Multiple versions of the same media
• Separate storage for recordings or personal video
• Snapshots of the media share

Transcoding may use local storage for temporary files, particularly when the workload involves large or multiple streams. Keep that space outside your main media estimate where possible.

An SSD cache does not increase the NAS’s usable storage capacity. It may affect access patterns, but it should not be counted as a replacement for free pool capacity or a backup.

Special considerations for surveillance

Surveillance storage is driven by camera count, resolution, frame rate, codec, motion detection, retention period, and recording schedule. Exact requirements cannot be calculated reliably without those inputs.

Use the recording system’s own storage estimate when available, then add a safety margin for:

• Continuous rather than motion-based recording
• Longer retention during busy periods
• Camera replacements or higher recording quality
• Exported incident footage
• Database and application overhead
• Snapshot or backup requirements

Do not use the general 20% rule as the only surveillance calculation. First size the retention requirement, then keep the free-space reserve on top of it.

What to do when a NAS is already too full

If free space falls below your target:

1. Check the NAS storage dashboard and identify the largest shares, datasets, snapshots, and applications.
2. Empty or review recycle bins only after confirming the contents are not needed.
3. Review snapshot retention and delete obsolete snapshots safely.
4. Move archived data to another storage tier.
5. Remove duplicate or temporary files.
6. Stop nonessential downloads, recordings, or virtual machines.
7. Expand the pool using a supported procedure.
8. Replace drives with larger models only if the NAS and RAID layout support the process.
9. Recalculate the capacity plan after expansion.

Do not delete snapshots or change a RAID layout without understanding the recovery implications. Some expansion operations require replacing drives one at a time and waiting for rebuilds, while others require adding a new storage group or creating a new pool. Exact procedures depend on the NAS platform.

NAS sizing checklist

Before buying drives or creating a pool, check the following:

• [ ] Calculate current data in TB or TiB consistently.
• [ ] Estimate annual growth and choose a planning horizon.
• [ ] Convert raw drive capacity into usable capacity after RAID or parity.
• [ ] Account for filesystem, system, and reserved capacity.
• [ ] Reserve at least 20% of usable capacity for general file storage.
• [ ] Consider 25–30% for ZFS, snapshots, virtual machines, databases, or heavy file churn.
• [ ] Estimate snapshot growth from changed data, not just snapshot count.
• [ ] Add space for surveillance retention, Plex transcoding, downloads, or temporary files.
• [ ] Decide whether backup staging needs space on the primary NAS.
• [ ] Keep backups separate from the RAID pool.
• [ ] Confirm drive compatibility and the NAS manufacturer’s expansion method.
• [ ] Plan for drive replacement, rebuild time, and future expansion.
• [ ] Set capacity alerts before the pool reaches its operating limit.
• [ ] Revisit the plan when usage, applications, or snapshot retention changes.

If you are comparing systems and drive layouts, Browse NAS options at NASFit before committing to a pool size. The right choice depends on usable capacity after parity, your free-space target, and how easily the system can expand later.