How to Calculate CCTV Storage Requirements: Complete Guide

Understanding CCTV Storage Basics

Before running any calculations, you need to understand the three factors that determine how much storage a CCTV system consumes: bitrate, compression codec, and resolution. These three variables interact with each other, and getting any one of them wrong will throw off your entire storage estimate.

Bitrate is the amount of data a camera produces per second, measured in megabits per second (Mbps) or kilobits per second (Kbps). A camera streaming at 4 Mbps produces 4 megabits of data every second, which translates to roughly 1.7 GB per hour or 42 GB per day of continuous recording. Bitrate is the single most important number in storage calculation because it directly determines data volume. Cameras with higher resolution, faster frame rates, or scenes with more motion all produce higher bitrates.

Compression is how the camera encodes video data to reduce file size. The two dominant codecs in surveillance are H.264 and H.265 (also called HEVC). H.264 has been the industry standard for over a decade and is supported by virtually every NVR and VMS on the market. H.265 is the newer standard that achieves the same image quality at 30 to 50 percent lower bitrate compared to H.264. For a 16-camera system running 30 days, the difference between H.264 and H.265 can easily be 15 to 25 TB of storage — which translates to one or two fewer hard drives and significant cost savings.

Resolution determines the amount of detail in each frame, which directly affects bitrate. A 4K (8MP) camera produces roughly four times the data of a 1080p (2MP) camera at the same frame rate and compression level. Higher resolution means sharper images and better zoom capability in playback, but it also means dramatically more storage. The decision on resolution should be driven by the surveillance objective for each camera position — not every camera needs to be 4K. Use our storage calculator to model different resolution scenarios and see the storage impact instantly.

Frame rate also plays a role. Most surveillance systems record at 15 fps (frames per second) as a balance between smooth video and storage efficiency. Increasing to 25 or 30 fps produces smoother footage but increases storage by 67 to 100 percent. For most security applications, 15 fps is sufficient. Traffic monitoring and fast-moving scenes may benefit from 25 fps, while static scenes like hallways or storage rooms can often drop to 10 fps without losing critical detail.

The Storage Calculation Formula

The fundamental formula for calculating CCTV storage is straightforward. Once you know the bitrate of each camera, the rest is arithmetic.

The Formula

Storage (GB) = Bitrate (Mbps) x 0.125 x 3600 x Hours per Day x Days x Number of Cameras / 1000

Breaking this down: multiply the bitrate in Mbps by 0.125 to convert to megabytes per second. Multiply by 3600 to get megabytes per hour. Multiply by recording hours per day (24 for continuous recording). Multiply by the number of retention days. Multiply by the number of cameras. Divide by 1000 to convert from MB to GB.

A simplified version: Storage (TB) = Bitrate (Mbps) x 0.0108 x Days x Cameras — this assumes 24-hour continuous recording and gives the result in terabytes.

Example 1: Small Retail Store

8 cameras, 4MP resolution, H.265 compression, 15 fps, 30-day retention, continuous recording.

Typical bitrate for 4MP H.265 at 15 fps: approximately 3 Mbps per camera.

Storage = 3 Mbps x 0.0108 x 30 days x 8 cameras = 7.78 TB

With RAID 5 overhead (one drive for parity in a 4-drive array): approximately 10.4 TB raw capacity needed, which fits in a 4-bay NVR with 4 x 4 TB surveillance drives.

Example 2: Office Building

32 cameras, mixed resolution (16 x 2MP + 16 x 4MP), H.265, 15 fps, 60-day retention, 12 hours/day recording (business hours + buffer).

2MP H.265 bitrate: approximately 2 Mbps. 4MP H.265 bitrate: approximately 3 Mbps.

Storage for 2MP cameras = 2 x 0.0108 x 60 x 16 x 0.5 (12hr/24hr) = 10.37 TB

Storage for 4MP cameras = 3 x 0.0108 x 60 x 16 x 0.5 = 15.55 TB

Total: 25.92 TB usable, approximately 34.6 TB raw with RAID 5.

Example 3: Large Campus

128 cameras, 4MP average, H.265, 15 fps, 90-day retention, continuous recording.

Storage = 3 x 0.0108 x 90 x 128 = 373.25 TB

This level of storage requires enterprise-grade NVR servers or dedicated storage arrays. With RAID 6 overhead, budget for approximately 450+ TB raw capacity. Skip the guesswork and model your exact scenario with our storage calculator.

Resolution and Bitrate Reference Table

The following table provides typical bitrate values for common surveillance camera resolutions at 15 fps with both H.264 and H.265 compression. These are average values for scenes with moderate motion. High-motion scenes (busy intersections, retail entrances) may produce 20 to 40 percent higher bitrates, while static scenes (hallways, storage rooms) may produce 20 to 30 percent lower bitrates.

Resolution	Megapixels	H.264 Bitrate	H.265 Bitrate	H.264 GB/Day	H.265 GB/Day
1920 x 1080	2MP	3-4 Mbps	1.5-2 Mbps	32-43 GB	16-22 GB
2560 x 1440	4MP	5-6 Mbps	2.5-3 Mbps	54-65 GB	27-32 GB
2592 x 1944	5MP	6-8 Mbps	3-4 Mbps	65-86 GB	32-43 GB
3840 x 2160	8MP (4K)	10-16 Mbps	5-8 Mbps	108-173 GB	54-86 GB
4000 x 3000	12MP	16-24 Mbps	8-12 Mbps	173-259 GB	86-130 GB

These values assume constant bitrate (CBR) encoding at 15 fps. Variable bitrate (VBR) encoding will produce lower average storage consumption but higher peaks during busy periods. When sizing storage with VBR, use the peak bitrate value for capacity planning to ensure you never run out of space during high-activity periods.

Retention Period Planning

The retention period — how many days of footage you keep before it is overwritten — is often dictated by industry regulations, insurance requirements, or internal security policy rather than technical preference. Choosing the wrong retention period can result in regulatory fines or the inability to investigate incidents that are discovered after the footage has been overwritten.

Industry	Typical Retention	Regulatory Notes
Retail	30 days	Covers typical inventory audit cycles; some retailers extend to 60 days for high-shrinkage locations
Banking / Financial	90 days	Regulatory requirements vary by jurisdiction; ATM and vault cameras often require 90+ days
Government / Critical Infrastructure	180 days	Federal buildings, utilities, and defense installations often mandate 6 months to 1 year
Healthcare	30-90 days	HIPAA does not specify CCTV retention, but facilities typically align with incident reporting timelines
Education	30-60 days	School districts often follow state-specific guidelines; some states mandate 30 days minimum
Hospitality	30-45 days	Hotels and casinos; casinos often retain gaming floor footage for 30+ days per gaming commission rules
Transportation	30-90 days	Airports, train stations, and bus depots; TSA and local transit authorities set requirements

When planning retention, always add a 10 to 15 percent buffer above your minimum requirement. If regulations mandate 30 days, design for 34 to 35 days. This accounts for timing differences in how NVRs calculate retention, filesystem overhead, and the delay between when footage should expire and when the system actually overwrites it. Running at exact minimum capacity means any temporary spike in bitrate (busy holiday periods, unusual weather causing more motion) could cause the oldest footage to be overwritten before the required retention window expires.

Consider using tiered retention for large systems. Critical cameras — entrances, POS, cash rooms — might retain footage for 90 days, while hallway and parking lot cameras retain for 30 days. This approach can reduce total storage requirements by 30 to 40 percent compared to applying the longest retention period uniformly across all cameras. Most NVR and VMS platforms support per-camera or per-group retention settings.

RAID and Redundancy

Hard drives fail. In a surveillance system running 24/7 with continuous write operations, drive failure is not a question of if, but when. RAID (Redundant Array of Independent Disks) protects your footage by distributing data across multiple drives so that the loss of one or two drives does not result in data loss. Choosing the right RAID level is a critical part of storage planning because RAID overhead reduces your usable capacity.

RAID 5 — One Drive of Parity

RAID 5 stripes data across all drives and uses one drive's worth of capacity for parity data. It can survive the failure of any single drive without data loss. Usable capacity is (N-1) x drive size, where N is the number of drives. For example, four 8 TB drives in RAID 5 provide 24 TB usable storage (3 x 8 TB). RAID 5 is the most common configuration for small to medium surveillance systems (up to 32 cameras). The risk is that if a second drive fails during the rebuild process after the first failure, all data is lost. Rebuild times for large drives (8 TB+) can take 12 to 24 hours, during which the array is vulnerable.

RAID 6 — Two Drives of Parity

RAID 6 uses two drives' worth of parity, allowing the array to survive two simultaneous drive failures. Usable capacity is (N-2) x drive size. Six 8 TB drives in RAID 6 provide 32 TB usable (4 x 8 TB). RAID 6 is recommended for systems with more than 4 drives and for enterprise deployments where data loss is unacceptable. The double-parity protection is particularly valuable during rebuild operations — if a second drive fails while the array is rebuilding from the first failure, RAID 6 continues operating normally while RAID 5 would lose all data.

RAID 10 — Mirrored Stripes

RAID 10 combines mirroring (RAID 1) with striping (RAID 0). Every drive is mirrored, providing the highest read/write performance and the ability to survive multiple drive failures as long as no mirror pair loses both drives. Usable capacity is 50 percent of total raw capacity — four 8 TB drives provide 16 TB usable. RAID 10 offers the best write performance, which matters for high-camera-count systems generating heavy write loads. The trade-off is that you lose half your raw capacity. It is typically used in high-performance enterprise NVR servers where write speed is a bottleneck.

Hot Spares

A hot spare is a drive installed in the array that sits idle until a drive fails, at which point the RAID controller automatically begins rebuilding onto the hot spare without human intervention. This minimizes the window of vulnerability. For any RAID 5 array, a hot spare is strongly recommended. For mission-critical systems, configure one hot spare for every 4 to 6 active drives. The hot spare consumes a drive bay and its capacity is not available for storage, so factor this into your capacity planning.

When calculating total raw storage needed, take your usable storage requirement and multiply by the RAID overhead factor: RAID 5 = usable x (N / (N-1)), RAID 6 = usable x (N / (N-2)), RAID 10 = usable x 2. Then add one drive for each hot spare. Use our storage calculator to automatically factor in RAID overhead for your specific configuration.

Cloud vs On-Premise Storage

The choice between cloud and on-premise storage for CCTV footage involves trade-offs in cost, bandwidth, reliability, and control. Neither option is universally better — the right choice depends on your camera count, retention requirements, internet connectivity, and operational preferences.

On-Premise Storage

On-premise storage uses NVRs (Network Video Recorders) or server-based VMS systems with local hard drives. The upfront cost is higher — you purchase the hardware, drives, and any RAID controller — but the ongoing cost is minimal (electricity and occasional drive replacements). A typical 16-camera NVR with 4 x 8 TB surveillance drives costs $1,500 to $3,000 for the hardware and provides 24 TB of usable RAID 5 storage with no monthly fees.

On-premise systems do not depend on internet connectivity. If your internet goes down, recording continues uninterrupted. This makes on-premise the default choice for critical security applications where footage continuity cannot be compromised. The downside is that on-premise systems are vulnerable to physical threats: fire, flood, theft, or vandalism at the site can destroy both the cameras and the stored footage simultaneously.

For most installations with 8 or more cameras and 30+ days retention, on-premise storage remains the most cost-effective option. The total cost of ownership over 5 years is typically 60 to 80 percent lower than equivalent cloud storage.

Cloud Storage

Cloud-based CCTV storage eliminates on-site hardware by streaming footage to remote data centers. Providers like Verkada, Rhombus, Eagle Eye Networks, and others offer camera-as-a-service models with monthly per-camera fees that include cloud storage. Typical costs range from $10 to $30 per camera per month for 30 days of cloud retention, scaling up for longer retention periods.

The primary advantage of cloud storage is off-site redundancy — footage survives even if the physical site is destroyed. Cloud systems also simplify multi-site management, providing a single interface to access footage from all locations. Remote access is seamless since footage is already in the cloud.

The major constraint is bandwidth. A single 4MP H.265 camera at 3 Mbps requires approximately 2.8 GB of upload bandwidth per hour. Sixteen cameras at this rate require a sustained upload speed of 48 Mbps, which exceeds the upload capacity of many commercial internet connections. Cloud storage also creates a recurring cost that compounds over time — a 32-camera system at $20 per camera per month costs $7,680 per year, which exceeds the cost of on-premise hardware within 12 to 18 months.

Hybrid Approach

A hybrid approach combines on-premise recording with selective cloud backup. All cameras record locally to an NVR for the full retention period. Critical cameras (entrances, cash rooms, high-value areas) simultaneously upload to the cloud, either as continuous streams or triggered by motion and alarm events. This provides the cost efficiency of local storage with the off-site protection of cloud backup for the most important footage.

Many modern NVRs and VMS platforms support hybrid operation natively. You can configure rules such as "upload the last 60 seconds before and after any motion event on entrance cameras to the cloud" or "back up all footage from the cash room camera to cloud storage daily." This selective approach reduces bandwidth requirements to a fraction of full cloud recording while protecting the footage that matters most.

Storage Optimization Tips

Raw calculation gives you the maximum storage needed for continuous recording. In practice, several optimization techniques can reduce actual storage consumption by 30 to 70 percent without compromising security effectiveness. Apply these strategies to reduce hardware costs and extend retention periods within your existing storage capacity.

Motion-Based Recording

Instead of recording 24/7, configure cameras to record only when motion is detected. A hallway camera that sees activity 4 hours out of 24 reduces its storage consumption by approximately 83 percent. Most NVRs support pre-event buffering (recording the 5 to 10 seconds before motion was detected) to ensure you capture the beginning of any event, not just the middle. Motion-based recording is ideal for low-traffic areas like hallways, storage rooms, stairwells, and perimeter cameras. Avoid using motion-only recording on critical cameras (entrances, POS) where continuous footage may be needed for investigations.

Scheduled Recording

For businesses that operate fixed hours, schedule cameras to record continuously during business hours and switch to motion-only recording after hours. An office building operating 10 hours per day with motion-only recording for the remaining 14 hours can reduce storage by 40 to 50 percent compared to continuous 24-hour recording. Create different schedules for different camera groups — exterior cameras should always record continuously for perimeter security, while interior office cameras can follow the business schedule.

Variable Bitrate (VBR)

Variable bitrate encoding adjusts the bitrate dynamically based on scene complexity. A camera viewing a static hallway with no motion uses very low bitrate (0.5 to 1 Mbps), but ramps up to full bitrate (4 to 6 Mbps) when someone walks through. Over a 24-hour period, VBR typically produces 30 to 50 percent less data than constant bitrate (CBR) encoding. Most modern cameras support VBR by default. Ensure your NVR or VMS is configured to accept variable bitrate streams — some older systems require CBR.

Dual-Stream (Sub-Stream) Recording

Most IP cameras output two simultaneous streams: a high-resolution main stream (for recording) and a low-resolution sub-stream (for live viewing). Configure your NVR to use the sub-stream for live monitoring and the main stream for recording. Some advanced systems take this further by recording the sub-stream for non-critical cameras and switching to the main stream only when motion is detected or an alarm triggers. This reduces storage for idle cameras by 80 to 90 percent while preserving full-resolution recording for events that matter.

Smart Codec Technologies

Camera manufacturers have developed proprietary encoding enhancements that go beyond standard H.265 compression. Hikvision's H.265+ , Dahua's Smart H.265+, and Axis Zipstream are examples. These technologies analyze each frame and apply maximum compression to static background areas while preserving detail on moving objects and regions of interest. In practice, they can reduce storage by an additional 50 to 70 percent compared to standard H.265 encoding. If your cameras and NVR support these smart codecs, enabling them is one of the most impactful storage optimization steps available.