32
Mbps
345.6
GB/day
11,404.8
GB
11.4
TB
12
TB
32
Mbps
345.6
GB/day
11,404.8
GB
11.4
TB
12
TB
Planning a CCTV or IP video surveillance system requires accurate estimates of storage capacity and network bandwidth — two of the most critical and frequently underestimated factors in any security installation. Buy too little storage and footage gets overwritten before an incident is reviewed. Provision too little bandwidth and video streams lag, drop frames, or fail entirely during peak recording times. The CCTV Hard Drive & Bandwidth Calculator eliminates guesswork by computing both figures from a handful of straightforward inputs.
The core inputs are the bitrate per camera (in Megabits per second), the number of cameras, the daily recording hours, and the desired retention period in days. From these, the calculator derives total storage in both gigabytes and terabytes, total simultaneous bandwidth, and daily storage consumption — everything a system designer or IT administrator needs to specify hard drives and network switches.
Understanding bitrate is essential. Modern IP cameras encode video using H.264, H.265 (HEVC), or H.265+ compression codecs. A 2 MP (1080p) camera using H.264 typically streams at 2–6 Mbps depending on scene activity, quality settings, and frame rate. The same camera using H.265 might achieve comparable quality at 1–3 Mbps — roughly half the storage requirement. High-definition 4K cameras may need 8–25 Mbps per stream. Motion-based recording or variable bitrate (VBR) encoding can reduce average bitrate by 30–60% compared to constant bitrate (CBR), but for planning purposes using the peak CBR value is the conservative approach.
The formula underlying this calculator is straightforward: Storage (GB) = Bitrate (Mbps) × 3600 s/h × Hours/Day × Cameras × Days ÷ 8 ÷ 1000. Breaking this down: multiplying Mbps by 3600 converts to megabits per hour; multiplying by hours and cameras gives total megabits; dividing by 8 converts to megabytes; dividing by 1000 converts to gigabytes (using 1 GB = 1000 MB, the disk manufacturer standard).
Bandwidth is simply Bitrate × Number of Cameras — all cameras streaming simultaneously consume that much network capacity. A 16-camera system at 4 Mbps each requires 64 Mbps of network bandwidth on the surveillance LAN. This affects the choice of network switches (100 Mbps vs. Gigabit), the NVR's network interface, and storage server throughput.
When sizing NAS or NVR hard drives, always add a 15–20% overhead to the calculated figure. Drive manufacturers and file systems consume some space for metadata, parity data (if using RAID), and the file system itself. A calculated requirement of 10 TB becomes a practical requirement of 12 TB of raw drive capacity. For mission-critical installations, RAID-5 or RAID-6 configurations provide redundancy at the cost of additional drives.
Retention period requirements vary by application: retail environments typically keep 30–90 days of footage; financial institutions may require 90–180 days; critical infrastructure or government facilities sometimes mandate 365 days. Local regulations and insurance requirements may also specify minimum retention periods — always verify these before finalizing storage specifications.
This calculator is equally useful for both analog HD systems (HD-CVI, HD-TVI, AHD) connected to DVRs and IP camera systems connected to NVRs. The bitrate concept applies universally — enter the camera's configured or typical bitrate and the math is identical.
The storage formula derives from unit analysis: Storage_GB = bitrate_Mbps × 3600 × hours_per_day × cameras × days / 8 / 1000.
bitrate_Mbps × 3600: converts Mbps to megabits-per-hour× hours_per_day: total megabits per camera per day× cameras: total megabits across all cameras per day× days: total megabits over the retention period÷ 8: converts megabits → megabytes÷ 1000: converts megabytes → gigabytes (SI prefix standard, consistent with hard drive labeling)Total live bandwidth is simply bitrate_Mbps × cameras — the simultaneous aggregate stream when all cameras are recording.
Daily storage is derived before multiplying by retention days, giving a per-day figure useful for monitoring consumption rates.
Total Storage (GB / TB): This is the minimum raw storage needed. Add 15–20% overhead for RAID, file system, and metadata before purchasing drives.
Total Live Bandwidth (Mbps): Ensure your network switch and NVR/DVR have sufficient throughput. A Gigabit switch handles up to ~950 Mbps usable bandwidth. If total stream bandwidth exceeds 500 Mbps, consider separate surveillance VLANs or 10GbE infrastructure.
Storage per Day (GB/day): Useful for monitoring how quickly footage accumulates and setting NVR overwrite policies. Divide your actual drive capacity by this number to find the true retention period achievable with your hardware.
Inputs
Results
An 8-camera 1080p H.264 system at 4 Mbps each requires ~4.15 TB for 30 days of continuous recording. A 6 TB NAS drive provides comfortable headroom including overhead. Total network bandwidth of 32 Mbps is easily handled by any modern Gigabit switch.
Inputs
Results
H.265 compression at 2 Mbps per camera dramatically reduces storage vs. H.264 at 4 Mbps. 32 cameras recording 12 hours/day for 90 days needs ~24.9 TB. A 4-drive NAS with 8 TB drives in RAID-5 (24 TB usable) is the practical solution. Bandwidth of 64 Mbps is manageable on standard Gigabit infrastructure.
A 1080p camera using H.264 codec typically streams at 2–6 Mbps. Using H.265 (HEVC), the same quality is achievable at 1–3 Mbps. 4K (8MP) cameras range from 8–25 Mbps depending on codec and scene complexity. Always check your specific camera's datasheet for the configured bitrate, as this varies significantly by manufacturer settings.
Hard drive manufacturers label capacity using SI units (1 GB = 1,000,000,000 bytes = 1000 MB). This calculator uses the same convention for consistency with storage product specifications. Note that Windows reports drive sizes in GiB (1 GiB = 1,073,741,824 bytes), which makes drives appear smaller than labeled. To convert: actual usable GiB = labeled GB × 0.931.
Motion-triggered or motion-optimized recording can reduce storage by 40–70% compared to continuous recording, depending on scene activity levels. However, for planning purposes, always calculate continuous recording requirements first, then apply a reduction factor (e.g., 0.4–0.6 multiplier) only if your NVR supports reliable motion detection and you are comfortable with potential gaps in coverage.
Standard Gigabit Ethernet (1000 Mbps) is sufficient for most installations. Practical usable bandwidth is about 700–900 Mbps after protocol overhead. If total camera bitrate exceeds 500 Mbps, consider 10GbE uplinks or segmenting cameras across multiple switches. PoE switches also need adequate power budgets: budget 15W per 1080p PoE camera, 30W per PoE+ PTZ camera.
For VBR cameras, use the average bitrate rather than the maximum. Most NVR manufacturers recommend using 70–80% of the maximum bitrate as a planning average for typical scenes. If you have access to historical recordings, analyze the actual average bitrate over representative time periods for the most accurate estimate.
RAID-5 (minimum 3 drives) is the most common choice for surveillance NAS systems, providing one-drive fault tolerance with good storage efficiency (N−1 drives of usable space). RAID-6 (minimum 4 drives) tolerates two simultaneous drive failures — recommended for large arrays with long rebuild times. Avoid RAID-0 (no redundancy) for surveillance systems where footage integrity is critical.
Audio codecs (G.711, AAC) used in IP cameras typically stream at 32–128 Kbps per channel — far less than video bitrates measured in Mbps. Audio adds roughly 0.5–2% to total storage, which is negligible for planning purposes. Round up your total storage figure slightly to account for audio if your cameras support it.
Many IP cameras support dual streaming: a high-resolution main stream for recording and a lower-resolution sub-stream for live monitoring or remote viewing. Storage is typically consumed only by the recorded (main) stream. Add both bitrates together only if you are recording both streams simultaneously to separate storage destinations.
Roboculator Team
The Roboculator Team explains calculations, planning tools, and practical formulas in clear language for real-life situations.
How helpful was this calculator?
Be the first to rate!
Delta-Y (Delta-Wye) Impedance Converter
Electrical Conversion & Reference Tools
Horsepower to Kilowatts (HP to kW) Converter
Electrical Conversion & Reference Tools
Kilowatts to Horsepower (kW to HP) Converter
Electrical Conversion & Reference Tools
BTU to Kilowatts (BTU/hr to kW) Converter
Electrical Conversion & Reference Tools
Temperature Converter for Electrical Applications
Electrical Conversion & Reference Tools
Pressure Converter for Electrical Applications
Electrical Conversion & Reference Tools