TL;DR: NVR storage is calculated from bitrate, not resolution: GB per camera per day = Mbps x 86,400 / 8 / 1,000, then multiply by camera count and retention days. Sixteen cameras at 4 Mbps recording 24/7 for 30 days need about 20.7 TB before headroom and before RAID overhead. Use the camera manufacturer’s bitrate data or storage calculator for final numbers, and confirm the retention requirement with the customer before you quote drives.
Storage is the step after camera selection on every job, and it is the line item customers notice when the footage they need is already gone. The math fits on one line. The work is getting the inputs right: bitrate, recording hours, retention days, and how much of the raw drive capacity survives RAID.
The NVR storage formula
Storage in gigabytes equals bitrate in Mbps x 3,600 x recording hours per day x retention days / 8 / 1,000. Dividing by 8 converts megabits to megabytes, and dividing by 1,000 converts megabytes to gigabytes.
For a camera recording around the clock, 3,600 seconds x 24 hours = 86,400 seconds, so the per-camera daily number simplifies to:
GB per camera per day = Mbps x 86,400 / 8 / 1,000
The full system formula is:
Total GB = (GB per camera per day) x number of cameras x retention days
If cameras run at different bitrates (a 4K parking lot camera and a 1080p hallway camera, for example), calculate each group separately and add them. Divide the final GB figure by 1,000 to get TB.
Worked example: 16 cameras, 30 days, 24/7
Sixteen cameras at 4 Mbps recording 24/7 for 30 days need 20,736 GB, or about 20.7 TB, before headroom. Here is every line.
- Seconds per day. 3,600 seconds x 24 hours = 86,400 seconds.
- Megabits per camera per day. 4 Mbps x 86,400 = 345,600 megabits.
- Megabytes per camera per day. 345,600 / 8 = 43,200 MB.
- Gigabytes per camera per day. 43,200 / 1,000 = 43.2 GB.
- System per day. 43.2 GB x 16 cameras = 691.2 GB.
- System for 30 days. 691.2 GB x 30 = 20,736 GB.
- Terabytes. 20,736 / 1,000 = 20.736 TB, about 20.7 TB.
That 20.7 TB does not include headroom, file system overhead, or RAID. For illustration, 20% headroom brings the target to about 24.9 TB of usable space. Set your own headroom figure with the NVR manufacturer’s guidance.
Why the drive label and the operating system disagree
Drive makers label capacity in decimal terabytes (1 TB = 1,000,000,000,000 bytes), while many operating systems and some NVR interfaces report binary units (TiB). One TB equals about 0.91 TiB. The 20.7 TB in the example shows up as about 18.9 TiB on a screen that reports binary units, and a 4 TB drive shows about 3.6. Nothing is missing. Keep the whole calculation in decimal TB so it matches the drive labels you are buying from.
The four levers that change the answer
Codec, frame rate, recording mode, and retention days move the storage number more than anything else on the job. Each one changes the bitrate or the hours that feed the formula.
| Lever | Typical effect on storage | Cautions |
|---|---|---|
| Codec (H.265 vs H.264) | HEVC (H.265) achieves about 50% bit-rate reduction at the same subjective quality, per Fraunhofer HHI | Lab figure. Surveillance savings vary by scene, camera, and settings. Confirm the NVR and VMS can record and play back H.265 |
| Frame rate | Less than proportional. In IPVM testing, 30 fps used about double the bitrate of 10 fps, not triple | Varies by codec, scene motion, and I-frame interval |
| Continuous vs motion or event recording | Can cut recorded hours sharply on quiet scenes, very little on busy ones | Depends on scene activity and trigger settings. Some specs require continuous recording |
| Retention days | Directly proportional. 60 days needs twice the storage of 30 days | Set by the customer, insurer, or industry rules. Confirm before quoting |
Figures are general ranges from published sources, not guarantees. Use the camera manufacturer’s bitrate data or storage calculator for the models on the job.
- Codec. Halving the example bitrate to 2 Mbps drops the 30-day total from about 20.7 TB to about 10.4 TB. Manufacturers add their own bitrate-reduction features on top of the codec (Axis says its Zipstream cuts bandwidth and storage by 50% or more). Treat vendor figures as a direction, not a number to quote.
- Recording mode. A camera that records about 12 hours of motion per day needs about half the storage of continuous recording: 21.6 GB per day instead of 43.2 GB at 4 Mbps. A loading dock may trigger all day.
Resolution is not the input, bitrate is
Two 4K cameras can need very different amounts of storage because the formula runs on bitrate, and resolution is one of several things that set bitrate. Codec, compression settings, frame rate, scene complexity, lighting, and motion all change how many megabits per second a camera sends.
A 4K camera on a quiet stairwell may run at a fraction of the bitrate of the same camera facing a busy entrance or a parking lot at night with IR and sensor noise. A 4K camera averaging 8 Mbps uses 86.4 GB per day, twice the 4 Mbps example.
Pull bitrate from the manufacturer’s published data at the settings you plan to record. Tools like Axis Site Designer and the Hanwha Vision bandwidth and storage calculator estimate bandwidth and storage from camera configuration and recording schedules. On a takeover or expansion, check the average bitrate the existing NVR reports for each stream. For help choosing cameras, see our IP camera selection guide for commercial security integrators.
Headroom and drive choice
Size to usable capacity after headroom and RAID, and use drives built for continuous video recording. Raw capacity printed on the drives is the starting point, not the answer.
- Leave headroom. Bitrates climb at night, in weather, and when the customer adds cameras.
- Use surveillance-rated drives. Product families such as WD Purple and Seagate SkyHawk are designed for 24/7 recording. Western Digital rates WD Purple for workloads of up to 180 TB per year, which it says is up to three times a desktop drive’s rating.
- Match the NVR. Confirm the recorder’s drive count, maximum capacity per drive, supported RAID levels, and compatibility list before you pick drive sizes.
RAID and redundancy in plain terms
RAID protects recordings from a single drive failure, but it costs capacity, so calculate storage against usable space after RAID. Western Digital’s RAID capacity calculator summarizes the common levels this way:
| RAID level | Usable capacity | Drive failures it survives |
|---|---|---|
| RAID 1 | One drive per mirrored pair | 1 |
| RAID 5 | Total minus one drive | 1 |
| RAID 6 | Total minus two drives | 2 |
| RAID 10 | Half the total, four or more drives | 1 per mirrored pair |
Quick example. Six 8 TB drives give 48 TB raw. Against the 24.9 TB target from the worked example:
- RAID 5: 48 – 8 = 40 TB usable. Covers the target.
- RAID 6: 48 – 16 = 32 TB usable. Covers the target and survives two drive failures.
- RAID 10: 48 / 2 = 24 TB usable. Falls short of 24.9 TB.
RAID makes sense when the spec calls for it, when lost footage would hurt the customer, or when the drive count makes a failure during the retention period likely. RAID 6 adds protection on larger arrays because a second drive can fail during a rebuild. RAID keeps the recorder running through a drive failure, but it is not a backup: it does not protect against a failed recorder, a fire, or deleted footage. Check which RAID levels the NVR supports, and see Before You Wire the Rack for the network side of the head end.
Where retention requirements come from
Retention days come from the customer’s policy, their insurer, or rules that apply to their industry, so confirm the number in writing before you size anything. Do not guess and do not assume one figure applies everywhere.
Ask the customer:
- Do you have a written retention policy?
- Does your insurer require a minimum?
- Do industry rules apply? The customer and their compliance or legal team own that answer.
- Which cameras need it? Entrances and cash areas may need more days than a stockroom.
Put the confirmed requirement in the proposal. If it changes, the storage math changes with it.
What to bring to the counter
Bring the inputs to the formula and your SDS franchise team can help you match NVRs, drives, and accessories to the job. Security Data Supply does not design or install the system. The licensed contractor owns the design and the install.
- Camera count and models. Manufacturer bitrate data comes from the model.
- Resolution, frame rate, and codec. Per camera group.
- Recording mode. Continuous, motion, event, or scheduled.
- Required retention days. Confirmed with the customer.
- RAID requirement. If the spec or customer calls for redundancy.
- Your calculation. Total TB before and after headroom.
Security Data Supply carries recorder and VMS lines including Digital Watchdog, Hanwha Vision, Milesight, Uniview (UNV), VIGI by TP-Link, Exacq, Geovision, IDIS, and Speco. Ask your franchise team which recorders and surveillance-rated drives they keep on hand, since stock can vary by franchise.
For camera cabling, see Cat5e vs. Cat6 vs. Cat6A for PoE camera installs. Our fire alarm battery backup calculations post uses the same formula-first method for standby power, and the video surveillance page lists the product categories.
Bring your camera list and retention requirement to your SDS franchise team, and they will help you find the recorders and drives that fit the job.
Frequently asked questions
How much storage do I need for security cameras?
Multiply each camera’s bitrate in Mbps by 86,400, divide by 8, then divide by 1,000 to get GB per day. Multiply by the number of cameras and the retention days. Sixteen cameras at 4 Mbps recording 24/7 for 30 days need about 20.7 TB before headroom and RAID.
How do I calculate NVR hard drive size?
Use storage (GB) = bitrate (Mbps) x 3,600 x recording hours per day x retention days / 8 / 1,000 for each camera group, add the groups, and divide by 1,000 for TB. Add headroom, then choose drives so the usable capacity after RAID meets that total. Use the camera manufacturer’s bitrate data or storage calculator for the inputs.
How many days of recording will a 4TB drive hold?
Divide 4,000 GB by the system’s daily GB. One camera at 4 Mbps uses 43.2 GB per day, so a 4 TB drive holds about 92 days for that camera. Sixteen of those cameras use 691.2 GB per day, so the same drive holds about 5.8 days, before file system overhead and headroom.
How much storage does a 4K camera use per day?
It depends on the camera’s bitrate, not the 4K label. A 4K camera averaging 8 Mbps around the clock uses 86.4 GB per day, while one averaging 4 Mbps uses 43.2 GB. Codec, frame rate, scene activity, and lighting set the bitrate, so check the manufacturer’s data for the model and settings.
Does H.265 save storage over H.264?
Usually, yes. Fraunhofer HHI reports that HEVC (H.265) achieves about 50% bit-rate reduction at the same subjective quality compared with H.264. Real surveillance savings vary by scene and camera settings, and the NVR and VMS need to support H.265 recording and playback.
Continuous vs. motion recording: how much storage does it save?
It depends on how much activity the camera sees. A camera that records about 12 hours of motion per day uses about half the storage of continuous recording, while a busy entrance may save very little. Confirm the project spec allows motion recording before you size around it.
Should I use surveillance-rated hard drives, and what RAID level should I use for an NVR?
Use surveillance-rated drives such as the WD Purple or Seagate SkyHawk families, which are designed for 24/7 recording, and check the NVR’s compatibility list. RAID 5 gives up one drive of capacity and survives one failure, RAID 6 gives up two and survives two, and RAID 10 gives up half. Size storage to usable capacity after RAID.
About the author
Ron Broussard is Chief Executive Officer of Security Data Supply and has more than 30 years of experience in the security industry. He has held executive leadership roles across distribution and manufacturing, giving him a broad perspective on the challenges contractors, integrators, and distributors face every day. At Security Data Supply, he guides the company’s franchise network, vendor relationships, and long-term growth strategy.
Methodology
This guide combines Security Data Supply’s distribution experience with published codec research, IP camera frame rate testing, and manufacturer documentation on surveillance drives, RAID capacity, and storage calculators. The worked example uses an illustrative bitrate to show the method and should not be used to size a real system. Actual bitrates vary by camera model, settings, and scene, and product availability can vary by franchise. Confirm final numbers with the camera and NVR manufacturers’ data and calculators, the project specification, and the customer’s confirmed retention requirement.
Sources and further reading
- Fraunhofer HHI: HEVC Technology
- IPVM: Training: Frame Rates for IP Cameras
- Axis Communications: Zipstream
- Axis Communications: AXIS Site Designer
- Hanwha Vision (via ScanSource): Bandwidth and Storage Calculator
- Western Digital: WD Purple Surveillance Hard Drives
- Western Digital: RAID Storage Capacity Estimate Calculator
- IP Camera Selection Guide for Commercial Security Integrators
- Before You Wire the Rack: Three Networking Decisions Every Security Contractor Needs to Make
- Cat5e vs. Cat6 vs. Cat6A for PoE Camera Installs: How to Choose
- Fire Alarm Battery Backup Calculations: How to Size Standby Power Correctly
- Video Surveillance & IP Cameras
- Security Data Supply: Find Your Local SDS