"How many terabytes do we need?" is one of the first questions on every video surveillance project. Guessing usually goes wrong in one of two ways: the recorder fills up and overwrites footage after a week instead of a month, or the budget is spent on disks that will never be used. A short calculation avoids both.
The formula
Storage depends on four numbers: the average bitrate of each camera, the number of cameras, how many hours a day they record and how many days you keep the footage.
storage per camera per day (GB) = bitrate (Mbit/s) × 86,400 s ÷ 8 ÷ 1,000
A camera averaging 4 Mbit/s recording continuously produces about 43 GB per day. Keep 30 days and that single camera needs roughly 1.3 TB.
What drives the bitrate
- Resolution. A 4 MP stream needs more bits than a 1080p one, all else equal.
- Codec. H.265 typically needs noticeably less bandwidth than H.264 for similar quality. Check that your recorder and viewing software support it before switching.
- Scene activity. A busy loading bay produces more data than an empty corridor, because modern codecs only encode what changes.
- Frame rate. 12–15 frames per second is enough for most security use; 25–30 fps roughly doubles storage for little practical benefit.
- Night time. Image noise in low light raises bitrate. Measure at night, not just during the day.
The most reliable approach is to measure: run a sample camera for a few days and read the average bitrate from the recorder.
A worked example
A warehouse with 40 cameras, average 3 Mbit/s each, recording continuously, 30-day retention:
- Per camera per day: 3 × 86,400 ÷ 8 ÷ 1,000 ≈ 32 GB
- All cameras per day: 32 × 40 ≈ 1.3 TB
- 30 days: ≈ 39 TB of usable capacity
Then add headroom. RAID protection reduces usable space, and disks should not run at 100%. We usually plan for 20–30% more raw capacity than the calculation.
Mistakes we see often
- Sizing from the camera datasheet's maximum bitrate instead of a measured average.
- Forgetting RAID overhead, so a "40 TB" recorder holds far less footage than expected.
- Motion-only recording without testing. It saves space, but misconfigured motion zones miss events.
- No monitoring of retention. If nobody checks how many days are actually stored, the first sign of a problem is missing footage after an incident.
Retention rules
Retention is often set by internal policy, insurance requirements or sector regulation. Confirm the required period before sizing, and make sure the oldest recording is checked automatically, not only when someone needs it.
If you are planning a new system or extending an existing one, our CCTV and access control service covers design, installation and monitoring, and Caddy Cloud can hold long-term archives in-region.
