Rack of network video recorders and storage in a CCTV control room
CCTV & Surveillance

How to Calculate CCTV Storage: A Worked Example for a 64 Camera Site

A step by step storage calculation for an IP camera system, with the formula, a 64 camera example, RAID overhead and the mistakes that leave recorders short of space.

Shruti IT Service Engineering Team

Survey, design and maintenance engineers, Nashik

Published On

16 Nov 2026

Read Time

7 min read
Share Guide:
Rack of network video recorders and storage in a CCTV control room

Most CCTV storage problems start with a guess. Someone picks a recorder that sounds big enough, and a few months later the system keeps only nine days of footage when the client was told thirty. The calculation is not hard. It needs a bitrate for each camera, a retention period, and an honest allowance for overhead. This guide walks through it with one example you can copy for your own site.

Key Engineering Takeaways

  • Storage per camera per day in gigabytes is the bitrate in megabits per second multiplied by 10.8.
  • Bitrate depends on resolution, frame rate, codec, lighting and how busy the scene is, so measure it on site before you finalise.
  • Add overhead for RAID, file system and an overwrite margin, or the system will not reach the retention you promised.
  • Network and recorder throughput matter as much as disk capacity.

The formula, and where 10.8 comes from

A camera sending 1 megabit per second sends 1,000,000 bits every second. There are 86,400 seconds in a day, so that is 86,400,000,000 bits, or 10,800 megabytes after dividing by eight. In round numbers that is about 10.8 gigabytes per day for each megabit per second of bitrate.

Written as a rule you can use on a calculator: storage per camera per day in gigabytes equals bitrate in megabits per second multiplied by 10.8. A camera at 3 Mbps writes 32.4 GB each day. Multiply by the number of cameras and by the days of retention, and you have the raw requirement.

Worked example: 64 cameras, 30 days

Take a warehouse and office site with 64 cameras. Assume 4 megapixel cameras using H.265 at 15 frames per second, averaging 3 Mbps. These are planning assumptions. The real figure comes from testing a few cameras on site, as described below.

One camera: 3 x 10.8 = 32.4 GB per day. All 64 cameras recording continuously: 64 x 32.4 = 2,073.6 GB per day, which is about 2.07 TB. For 30 days that is 62.2 TB.

Now be realistic about the scenes. Suppose 24 of the cameras cover corridors and storerooms that are empty most of the night and are set to record on motion, active about 40 percent of the time. Those 24 cameras need 24 x 32.4 x 0.4 = 311 GB per day. The other 40 cameras still record all the time: 40 x 32.4 = 1,296 GB per day. The site total is 1,607 GB per day, and 30 days comes to about 48.2 TB.

Motion recording only saves space if the scene really is quiet. A camera that sees swaying trees, headlights or a dusty window triggers all night and stores almost as much as continuous recording.

Add overhead before you choose disks

The 48.2 TB figure is the amount of footage. It is not the amount of disk. Three things take capacity away.

  • Overwrite margin: allow 10 to 15 percent so the recorder never runs at the edge of its capacity. In the example, 48.2 TB plus 15 percent is about 55.4 TB usable.
  • RAID parity: in RAID 6, two disks of the group store protection data, not footage. With 12 disks, 10 hold data, so raw capacity must be about 1.2 times the usable figure.
  • File system and index overhead: small compared with the other two, but it is real, and drive makers quote decimal terabytes while operating systems often report binary ones.

Turning the number into hardware

The example needs about 55.4 TB usable. A 12 bay recorder with 6 TB disks gives 72 TB raw, and in RAID 6 that leaves 10 x 6 = 60 TB usable. That clears the requirement with a little room. If the client later asks for 45 days instead of 30, the same calculation says 83 TB usable, and the design has to change before purchase, not after.

Bandwidth is the second check. Sixty four cameras at 3 Mbps send about 192 Mbps into the recorders. Confirm that each recorder's rated incoming bandwidth, the switch uplinks and the storage network all carry that load with headroom, because peaks in busy scenes run well above the average.

How to get the bitrate right

Bitrate is the least certain input, so it deserves a short test. Install three or four representative cameras, a gate, a corridor, a loading bay and a dim storeroom, with the compression and frame rate you plan to use. Let them record for a full week and read the real daily storage from the recorder.

Night scenes are the usual surprise. Cameras raise gain in low light and the picture gets noisy, which pushes the bitrate up. Smart codecs reduce this, but only if they are switched on and tested. Record the settings you tested with, because the same numbers must go into every camera at commissioning.

Mistakes that leave recorders short

  • Using the camera's maximum bitrate or a catalogue figure instead of a measured one.
  • Forgetting that audio, a second stream for mobile viewing or analytics metadata also take space.
  • Counting usable capacity as raw capacity, or ignoring RAID parity.
  • Promising a retention period in the contract without writing down the assumptions behind it.
  • Leaving no room for growth, when most sites add cameras within two years.

Conclusion & Next Steps

A storage calculation fits on one page, and it should be part of the design documents you receive. Ask for the bitrate per camera, the retention in days, the overhead allowances and the resulting disk count. If you want it done for your site, our engineers will survey the cameras, measure real bitrates and give you a storage sheet you can check.

Certified Engineering Partner

Need a site survey or project quote?

Our engineers provide comprehensive BOQs, system designs, and turn-key execution across Maharashtra and neighboring states.

Related services

Want this done at your site? These pages explain the scope, the process and the standards we work to.