CCTV & security systems tool

CCTV Hard Drive Storage Calculator

Work out how much hard drive storage your CCTV or IP camera system needs, from camera count, resolution, frame rate and retention period - vendor-neutral, with UK retention guidance built in.

Vendor-Neutral ICO 31-Day Benchmark H.264 / H.265 Aware Free To Use Instant Results

Calculator Inputs

Storage Breakdown

Step Calculation Result
Per-camera bitrateEnter your camera settings above-
Combined bitrate--
Daily storage--
Total storage (retention period)--

Resolution Scenario Analysis

Resolution Per-Camera Bitrate Total Storage Needed
2MP / 1080p--
4MP--
5MP--
8MP / 4K--

What Is A CCTV Hard Drive Storage Calculator?

Most CCTV storage calculators that rank for this search come from a hard drive manufacturer - Seagate, Western Digital, SanDisk - and exist to sell you their own drives. This one is vendor-neutral: enter your camera count, resolution, frame rate, codec and retention period, and get a storage figure and drive recommendation, plus the UK data-protection context (the ICO's commonly used ~31-day CCTV retention benchmark, checked 2026-08-08) that the vendor tools don't mention.

How Is The Storage Requirement Calculated?

The calculator works out a per-camera bitrate from your resolution and frame rate, calibrated against two industry-standard reference points: ~4 Mbps for 2MP/1080p and ~8 Mbps for 4MP, both at 25fps H.264 with typical scene motion (checked 2026-08-08) - giving 0.08 Mbps per megapixel per fps. Your scene-activity and codec choices scale that bitrate further, the combined bitrate across all cameras converts to daily storage (1 Mbps sustained for 24 hours ≈ 10.8 GB, checked 2026-08-08), and daily storage x retention days gives the total, rounded up to a recommended drive size.

Choosing A Codec: H.264 vs H.265

H.265 (HEVC) typically needs only about 55% of the bitrate of H.264 for the same visual quality (checked 2026-08-08) - so switching codecs on the same camera setup can cut your storage requirement by nearly half. This is often a more cost-effective way to control storage costs than dropping resolution or frame rate, provided your cameras, NVR and any client software all support H.265 playback.

How Long Should You Keep CCTV Footage In The UK?

The ICO's guidance on video surveillance, including CCTV (ico.org.uk, checked 2026-08-08), explains that UK GDPR's storage limitation principle means footage should not be kept longer than necessary for its purpose. Around 30-31 days is commonly used as a starting point for general commercial security CCTV - which is why this calculator defaults to 31 days - but it isn't a fixed legal maximum or minimum. You should set and be able to justify your own retention period based on your specific purpose, and the calculator's Assessment module flags much longer periods as worth a second look.

When Do You Need Multiple Drives Or RAID?

Once your total storage exceeds the largest commonly available single drive (around 24TB as of 2026-08-08), you need a multi-drive or RAID array rather than a single disk. If you use a redundant RAID level (such as RAID 5 or RAID 6) for protection against drive failure, some of your raw capacity is used for parity data rather than footage - this calculator states the raw capacity needed but does not calculate that RAID overhead, since it varies by RAID level and drive count.

Common Mistakes And What Happens Next

Common mistakes include sizing storage for a "typical" scene when the real installation faces a busy road or retail floor, forgetting that H.265 can roughly halve storage needs, leaving retention at a default figure without reviewing whether it's actually justified, and not planning for RAID overhead when specifying drives. Use the figures above to size your NVR or storage appliance, confirm codec and resolution support with your camera and recorder hardware, and document your own retention decision with reference to the ICO's guidance.

Method And Limits (Dated 2026-08-08)

This calculator estimates storage capacity only, from camera count, resolution, frame rate, codec, scene activity, recording mode and retention period. It deliberately does not model: exact per-scene bitrate (real-world bitrate varies with lighting, compression settings, camera model and genuine scene complexity - the motion multiplier is a planning approximation, not a guarantee); network and NVR channel capacity (very large camera counts are flagged as enterprise-scale, but switch bandwidth, PoE budget and NVR throughput are a separate design question); RAID overhead and drive failure margins (the multi-drive/RAID recommendation states raw capacity needed, not usable capacity after parity); data protection compliance beyond retention length (the ICO benchmark is cited for planning only - this is not legal advice, and does not cover camera positioning, signage or other UK GDPR obligations); and variable frame rate or smart/event-based encoding, which some modern cameras use to reduce bandwidth further during static periods within "continuous" recording.

Frequently Asked Questions

How much storage do I need for a CCTV system?

It depends on your camera count, resolution, frame rate, codec, scene activity and how long you need to retain footage. As a reference point, 4 cameras at 2MP/25fps H.264 with typical activity, recording continuously for 31 days, needs about 5.36TB. Enter your own setup above for an exact figure.

What resolution and bitrate does a typical CCTV camera use?

Industry-standard reference figures (checked 2026-08-08) put a 2MP/1080p stream at around 4 Mbps and a 4MP stream at around 8 Mbps, both at 25fps H.264 with typical scene motion - roughly doubling as resolution doubles. Busier scenes with more motion need a noticeably higher bitrate at the same resolution and compression settings.

How much difference does H.265 make to storage needs?

H.265 (HEVC) typically needs only about 55% of the bitrate of H.264 for the same visual quality (checked 2026-08-08) - so switching from H.264 to H.265 on the same camera setup can cut your storage requirement by nearly half.

How long should I keep CCTV footage in the UK?

The ICO's guidance on video surveillance, including CCTV, explains that UK GDPR's storage limitation principle means footage should not be kept longer than necessary for its purpose. Around 30-31 days is commonly used as a starting point for general commercial security CCTV, but this isn't a fixed legal maximum or minimum - you should set and be able to justify your own retention period based on your specific purpose.

Why does the calculator flag long retention periods?

If you enter a retention period well beyond the commonly used ~31-day benchmark (over 90 days, for example) without an obvious reason, the Assessment module flags it as worth double-checking against the UK GDPR storage limitation principle - not because longer retention is banned, but because it should be a documented, purpose-led decision rather than a default setting left unreviewed.

What is the difference between continuous and motion-triggered recording?

Continuous recording writes footage to storage 24/7 regardless of activity. Motion-triggered recording only writes footage when the camera detects movement, which can cut storage needs dramatically - this calculator models moderate motion-triggered activity at roughly 30% of the day and low activity at roughly 15%, though actual figures depend heavily on your camera's motion sensitivity settings and how busy the scene genuinely is.

Why does the storage figure keep the network bandwidth the same in motion-triggered mode?

Even if a camera only records to storage when it detects motion, most systems still need to support the camera's full streaming bitrate on the network for live viewing at any time. This calculator's combined-bitrate figure reflects the full streaming bitrate; only the daily/total storage figures apply the recording-mode reduction.

What happens if my total storage exceeds a single hard drive's capacity?

Once your total exceeds the largest commonly available single drive (around 24TB as of 2026-08-08), the calculator recommends a multi-drive or RAID array sized to your total capacity, rather than suggesting a single drive that doesn't exist at that size.

Does RAID reduce my usable storage?

Yes, if you use a redundant RAID level (such as RAID 5 or RAID 6) for protection against drive failure, some of your raw drive capacity is used for parity data rather than footage - this calculator states the raw capacity needed and does not calculate RAID overhead, which varies by RAID level and number of drives.

Does scene activity really change how much storage I need?

Yes, meaningfully. A camera pointed at a busy road or a retail floor has far more motion between frames than one covering a quiet corridor, and modern compression (H.264/H.265) works by encoding the differences between frames - more motion means more data per frame, even at the same resolution and frame rate settings.

Should I use 25fps or 30fps for my cameras?

25fps is the standard UK/European frame rate (matching the PAL broadcast standard many CCTV systems still reference), while 30fps is more common in US/NTSC-influenced equipment. Either is normally smooth enough for security footage; higher frame rates increase both bitrate and storage needs roughly proportionally, with limited practical benefit for most static security scenes beyond about 15-25fps.

Is this calculator specific to any hard drive brand?

No - unlike the manufacturer calculators from Seagate, Western Digital and SanDisk that dominate this search, this tool is vendor-neutral. It estimates the storage capacity you need in TB; which brand or model of drive you then buy to reach that capacity is entirely up to you.

Is this legal or data protection advice?

No. The ICO retention benchmark is cited for storage-planning purposes only. This calculator does not provide legal advice on UK GDPR compliance, camera positioning, signage, or your obligations under the Surveillance Camera Code of Practice - consult the ICO's guidance directly or a data protection professional for those questions.

Sources

Last updated: 2026-08-08. This page gives a storage-quantity estimate only and is not legal or data protection advice.