Lead Forensics

Call Us Now +44 (0) 20 3475 5743

How do you calculate storage capacity for HD surveillance?

  • Posted by: admin

To calculate HD surveillance storage capacity, multiply the bitrate of each camera (in Mbps) by the number of cameras, the number of hours of retention required, and a conversion factor to reach terabytes. The result tells you how much raw storage your system needs before accounting for compression, redundancy, or RAID overhead. The key variables are camera resolution, frame rate, compression codec, scene complexity, and how many days of footage you need to retain. The sections below walk through each factor in detail, from the fundamentals of compression to enterprise-scale deployment planning.

What factors affect how much storage HD surveillance needs?

The storage demand of an HD surveillance system is determined by six core variables: camera resolution, frame rate, compression codec, scene activity, the number of cameras, and the required retention period. Each variable has a compounding effect on the total, so a change in one can dramatically shift your overall storage requirement. Understanding how they interact is the foundation of any accurate CCTV storage calculation.

  • Resolution: Higher resolution cameras such as 4K or 5MP produce significantly larger files than 1080p or 720p units. More pixels per frame means more data per second.
  • Frame rate: Recording at 25 frames per second (fps) generates roughly twice the data of recording at 12 fps. Reducing frame rate is one of the fastest ways to cut storage demand without switching cameras.
  • Scene activity: A busy car park or transport hub generates far more motion data than a static server room. High-motion environments produce larger files even at the same resolution and frame rate.
  • Number of cameras: Storage scales linearly with camera count. A 200-camera deployment requires proportionally more capacity than a 20-camera one, though compression efficiencies can partially offset this.
  • Retention period: Whether you need 7, 14, 30, or 90 days of footage stored on-site has a direct and linear impact on total storage volume.
  • Compression codec: The codec your cameras and VMS use to encode video is one of the most influential factors of all, which is why it deserves its own section below.

How does video compression change your storage requirements?

Video compression reduces the amount of data that needs to be stored by removing redundant visual information between frames. The codec your system uses can reduce storage requirements by anywhere from 50% to over 80% compared to uncompressed video, making it one of the most powerful levers in any IP camera storage requirements calculation.

The most widely used codecs in modern HD surveillance are H.264 and H.265 (also called HEVC). H.265 is the current industry standard for high-efficiency encoding and typically delivers the same image quality as H.264 at roughly half the bitrate. For large deployments, this difference translates directly into significant savings on storage hardware.

A newer generation codec, H.266 (VVC), offers further gains, though camera and VMS support is still maturing as of 2026. Some manufacturers also use proprietary codecs such as Axis’s Zipstream, which applies smart compression selectively to areas of low activity within the frame, reducing bitrate in quiet scenes without sacrificing detail where motion occurs.

One important caveat: compression performance varies with scene complexity. A codec like H.265 performs best in low-to-moderate motion environments. In high-activity scenes, the efficiency gains narrow because there is less redundant information to remove between frames. This means storage estimates based solely on codec type without accounting for scene activity will often underestimate real-world requirements.

What is the formula for calculating surveillance storage capacity?

The standard formula for calculating video surveillance storage is: Storage (TB) = Bitrate (Mbps) × Number of Cameras × Seconds per Day × Retention Days ÷ 8,000,000. This converts megabits into terabytes and gives you the raw storage volume required before factoring in RAID overhead or redundancy.

Breaking this down step by step:

  1. Determine the bitrate per camera. This is typically listed in your camera’s datasheet and varies by resolution, frame rate, and codec. A 1080p H.264 camera might run at 4 Mbps, while a 4K H.265 camera might run at 6 to 10 Mbps depending on scene activity.
  2. Multiply by the number of cameras. If you have 50 cameras each at 6 Mbps, your total system bitrate is 300 Mbps.
  3. Multiply by seconds per day. A 24-hour recording day equals 86,400 seconds. If cameras only record during business hours (12 hours), use 43,200.
  4. Multiply by the number of retention days. For a 30-day retention requirement, multiply by 30.
  5. Divide by 8,000,000 to convert megabits to terabytes.

Using the example above: 300 Mbps × 86,400 × 30 ÷ 8,000,000 = approximately 97 TB of raw storage. Add 20 to 30% overhead for RAID parity and OS isolation, and you are looking at roughly 120 to 130 TB of usable physical storage for that deployment.

Tools such as Secure Logiq’s proprietary Logiqal Benchmark utility allow systems designers to simulate this entire calculation virtually, inputting exact camera resolutions, compression formats, frame rates, and analytics workloads to stress-test and validate server throughput before any physical hardware is deployed.

How much storage do you need per camera per day?

As a practical reference, a single HD surveillance camera recording continuously at 1080p with H.264 compression at around 4 Mbps will generate approximately 43 GB of data per day. At the same resolution but with H.265, that figure drops to roughly 20 to 25 GB per day. A 4K camera using H.265 at 8 Mbps will produce around 86 GB per day under continuous recording.

These figures assume 24-hour continuous recording. In practice, many deployments use motion-triggered recording or scheduled recording windows, which can reduce per-camera daily storage by 40% to 70% depending on scene activity patterns. Retail environments and transport hubs tend to have high enough activity levels that continuous recording remains the safer design choice.

For a quick reference across common configurations:

  • 720p H.264 at 2 Mbps: approximately 21 GB per camera per day
  • 1080p H.264 at 4 Mbps: approximately 43 GB per camera per day
  • 1080p H.265 at 2 Mbps: approximately 21 GB per camera per day
  • 4MP H.265 at 4 Mbps: approximately 43 GB per camera per day
  • 4K H.265 at 8 Mbps: approximately 86 GB per camera per day

These are baseline estimates. Always source the actual bitrate from your camera manufacturer’s datasheet and account for the specific scene conditions of your deployment.

Should you use RAID or cloud storage for HD surveillance servers?

For enterprise HD surveillance deployments, on-premise RAID storage within a dedicated surveillance server is the preferred architecture. RAID provides the continuous, high-throughput sequential write performance that video recording demands, while cloud storage introduces latency, bandwidth costs, and dependency on network uptime that make it poorly suited as a primary recording destination for high-camera-count systems.

Why RAID remains the standard for on-site surveillance storage

HD video recording is a sustained, sequential write workload. Surveillance-optimised drives arranged in hardware-accelerated RAID configurations, typically RAID 5, RAID 6, or RAID 60, are purpose-built to handle this without frame drops. RAID 6, for example, tolerates two simultaneous drive failures, which is critical in environments where a dropped frame or system downtime is operationally unacceptable, such as transport hubs, stadiums, or critical infrastructure sites. Hot-swappable spare drives configured as standard mean a failed drive is automatically rebuilt without any manual intervention or recording interruption.

Where cloud storage fits into surveillance architecture

Cloud storage is best used as a secondary or archival tier rather than a primary recording destination. Offloading older footage, beyond 30 or 60 days for instance, to cloud storage can reduce the physical footprint of on-site NVR storage capacity while keeping recent footage immediately accessible on-site. Hybrid architectures that combine local RAID storage for active recording with cloud archiving for long-term retention represent the most practical balance for most enterprise deployments in 2026.

What storage capacity do you need for enterprise surveillance deployments?

Enterprise surveillance deployments, typically defined as systems with 100 or more cameras, commonly require between 100 TB and several petabytes of storage depending on camera resolution, retention requirements, and whether analytics workloads are running alongside recording. A 200-camera 4K deployment with a 30-day retention requirement will typically demand 300 to 500 TB of usable storage, once RAID overhead and OS isolation are accounted for.

At enterprise scale, several additional factors become significant beyond the basic storage formula:

  • Analytics processing overhead: AI-driven analytics platforms such as those used in smart city or stadium deployments add GPU compute and additional metadata storage requirements on top of raw video storage.
  • OS isolation: Enterprise servers should use dedicated SSD pairs in hardware RAID 1 for the operating system, completely separate from the video storage arrays. This protects the recording environment from OS-level drive degradation and software instability.
  • Scalability planning: Designing for current camera counts is not enough. Enterprise deployments should be sized with future expansion in mind, typically adding 20 to 30% headroom above the calculated requirement.
  • Redundant power infrastructure: At this scale, dual or quad hot-swappable power supplies eliminate the power infrastructure as a single point of failure, a non-negotiable requirement for mission-critical environments.
  • VMS certification: Storage servers should be validated and certified for the specific VMS platform in use, whether Milestone XProtect, Genetec Security Center, Avigilon Unity, or another leading platform, to guarantee throughput and compatibility at scale.

Sectors with particularly demanding storage profiles include football stadiums and concert venues, where live analytics and event safety create simultaneous high-throughput recording and processing workloads, and transport hubs such as airports and rail networks, where continuous multi-stream recording across hundreds of cameras is combined with ANPR and access control integration.

How Secure Logiq helps with HD surveillance storage capacity

Secure Logiq designs and manufactures dedicated HD surveillance servers purpose-built to meet the storage and throughput demands described throughout this article. Rather than adapting generic IT hardware, every server is engineered from the ground up for continuous HD video workloads. Key capabilities include:

  • Enterprise-grade RAID arrays (RAID 5, 6, and 60) with hot-swappable spares and battery-backed controllers for zero-frame-drop resilience
  • Dual SSD operating system drives in hardware RAID 1, fully isolated from video storage arrays
  • Redundant hot-swappable power supplies as standard on all enterprise units
  • Pre-sales storage and bandwidth calculation reports, delivered as part of a comprehensive tender-ready technical package
  • Logiqal Benchmark, a proprietary simulation utility that validates server and storage throughput against your exact camera mix before hardware is ordered
  • Certification across leading VMS platforms including Milestone XProtect, Genetec Security Center, and Avigilon Unity
  • A five-year next-business-day onsite warranty covering all internal components

Whether you are sizing storage for a 20-camera retail site or a 500-camera transport hub, Secure Logiq’s pre-sales engineering team will calculate your exact requirements and guarantee the performance of the proposed solution. Contact the team to get a storage calculation for your project.

Related Articles