NVR storage is driven by bitrate and recording time—not resolution alone. Two 4K cameras can produce very different storage requirements depending on compression, frame rate, scene complexity, bitrate controls, and recording schedule.
The core calculation
A simplified storage model uses:
- Number of cameras
- Average bitrate per camera
- Hours recorded per day
- Retention days
Use the free NVR Storage Calculator for a quick estimate.
Why bitrate matters most
Resolution is only one influence on bitrate. Frame rate, compression codec, image quality, motion, lighting, foliage, rain, and camera firmware settings can all change the actual amount of data generated.
Continuous versus motion recording
Continuous recording is easy to estimate because recording duration is known. Motion recording can reduce storage substantially, but the amount saved depends on the environment.
A quiet hallway may record very little motion. A hotel lobby, parking lot, roadway, or windy tree line may trigger activity much of the day.
H.264 versus H.265
H.265 can reduce bandwidth/storage compared with H.264 at similar visual quality, but actual savings depend on camera implementation and scene content. Do not assume a fixed percentage without validating your platform.
Retention planning
Decide how many days the customer actually needs. More retention sounds better, but it increases drive count, chassis requirements, and replacement cost.
For commercial projects, document the agreed retention target rather than promising an exact number of days under every condition.
Example
Suppose 16 cameras average 4 Mbps each and record continuously for 30 days. That is a very different storage requirement from 16 cameras averaging 2 Mbps and recording only during active hours.
Small changes in average bitrate multiply across every camera and every day of retention.
Leave operating headroom
Do not size a recorder so tightly that the expected retention requires every usable byte. File-system overhead, reserved space, bitrate spikes, firmware behavior, and drive replacement strategy can all reduce practical capacity.
Surveillance drives and redundancy
Drive selection should reflect the NVR manufacturer’s compatibility guidance and workload expectations. RAID or other redundancy can improve fault tolerance, but usable capacity is lower than raw installed capacity.
Bandwidth matters too
Storage and network bandwidth are closely related. The same camera bitrates used for NVR sizing also affect switch uplinks, recorder interfaces, remote viewing, and WAN upload if footage is transmitted off site.
Frequently asked questions
How many TB do I need for 30 days of recording?
There is no single answer without camera count, bitrate, and recording schedule. Use those inputs rather than resolution alone.
Does motion recording guarantee a certain retention period?
No. Motion activity varies by scene. If retention is contractually important, validate with real recording behavior.
Should I size storage from camera maximum bitrate?
For conservative planning, maximum or expected upper-range bitrate can be useful. For existing systems, observed average bitrate may produce a more realistic estimate.
NVR storage depends on bitrate—not just camera resolution
For a practical estimate, multiply the average bitrate of each camera by recording time and retention, then add headroom. Two 4K cameras can require very different storage if one records at 4 Mbps and the other at 12 Mbps.
Use the free calculator to estimate raw surveillance storage from camera count, bitrate, recording hours, and retention period.
Open NVR Storage Calculator →