Storage sizing for CCTV: resolution, frame rate and retention days

Key Takeaways

• The core storage formula is straightforward once you have a bitrate: file size (in bytes) = bitrate (in bits/second) × duration (in seconds) ÷ 8, which scales linearly with however many cameras and days of retention you're planning for.
• Bitrate varies enormously by resolution: 1080p video typically runs 3-8 Mbit/s, while 4K (2160p) runs 8-35 Mbit/s, meaning a single resolution upgrade can more than quadruple the storage requirement per camera before frame rate or retention are even factored in.
• Frame rate has a similar multiplying effect to resolution: a 1080p stream at 60fps needs roughly 4-10 Mbit/s against 3-8 Mbit/s at standard frame rate, so "higher frame rate" and "higher resolution" both independently inflate storage need and shouldn't be decided without checking the combined effect.
• Total storage need is the product of per-camera bitrate, camera count, and retention days together, which is why increasing retention from 30 to 90 days, say, doesn't just add "some" storage, it roughly triples the entire system's storage requirement.

CCTV storage sizing goes wrong most often not because the formula is complicated, it isn't, but because resolution, frame rate, camera count, and retention days are each treated as small independent choices when their effect on total storage is actually multiplicative. Bump two of those variables up "a bit" each and the total storage requirement can jump by a factor that surprises whoever specified the recorder.

The core formula, and why it's simpler than it looks

The underlying relationship between bitrate and file size is direct: file size in bytes equals bitrate in bits per second multiplied by duration in seconds, divided by eight (to convert bits to bytes) (Wikipedia, Bit rate, retrieved 2026-09-10). For a full sizing calculation: total storage = bitrate × 3600 (seconds per hour) × 24 (hours per day) × retention days × camera count, divided by 8 to get bytes, then converted to the storage unit you're planning in (typically terabytes for any real system). Every other consideration in CCTV storage sizing ultimately feeds into that one number, the bitrate, and how many camera-days it has to sustain.

Why resolution is the single biggest lever on bitrate

Video bitrate scales sharply with resolution: 1080p video typically runs 3-8 Mbit/s, while 4K (2160p) runs 8-35 Mbit/s, and even the more modest step from 720p (roughly 2.5 Mbit/s) to 1080p represents a meaningful jump on its own (Wikipedia, Bit rate, retrieved 2026-09-10). Moving a camera fleet from 1080p to 4K without recalculating storage capacity is one of the most common CCTV budget surprises, since the resolution upgrade alone can more than quadruple the per-camera storage requirement before anything else in the system changes.

Why frame rate compounds the resolution effect rather than replacing it

Frame rate has its own independent multiplying effect: standard 1080p runs roughly 3-8 Mbit/s, while 1080p at 60fps runs roughly 4-10 Mbit/s (Wikipedia, Bit rate, retrieved 2026-09-10). This matters because resolution and frame rate are often decided by different people for different reasons, resolution for image detail, frame rate for smooth motion capture, without either decision-maker checking the combined storage effect of both choices together. A system specified at 4K and a higher frame rate for a security-critical area can end up with a per-camera bitrate several times higher than a baseline 1080p standard-frame-rate assumption, which needs to be caught at the planning stage, not discovered when the recorder runs out of space early.

Why retention days is a direct multiplier, not a marginal adjustment

Because total storage scales linearly with retention days in the core formula, moving from a 30-day retention policy to 90 days doesn't add a modest increment, it roughly triples the entire system's storage requirement, camera count and bitrate held constant. Retention policy is frequently set by a compliance or insurance requirement rather than a technical one, so it's worth confirming the actual required retention period early and explicitly, since a late change to retention policy after storage hardware is already specified can mean the system is under-provisioned from day one, silently overwriting footage sooner than intended.

Putting the multipliers together before specifying hardware

Because resolution, frame rate, camera count, and retention days all multiply together rather than adding, the practical approach is to fix all four inputs explicitly before sizing storage, rather than deciding each one independently and hoping the total comes out reasonable. Run your specific camera count, target resolution, frame rate, and required retention period through the smart security calculator to get an actual storage figure, rather than estimating and discovering the gap once the system is already installed and recording.

Frequently asked questions

Does upgrading to 4K cameras really need that much more storage than 1080p?

Yes, meaningfully. At roughly 8-35 Mbit/s for 4K against 3-8 Mbit/s for 1080p, a straight resolution upgrade can require four times or more the storage per camera, per day, before any other variable changes.

Is there a way to reduce storage need without lowering resolution?

Compression efficiency (the codec used, e.g. H.265 versus older H.264) affects achievable bitrate at a given resolution and quality level, and can meaningfully reduce storage need without a visible quality drop. Smart/motion-triggered recording (only recording when activity is detected) is another common lever that reduces effective storage need versus continuous 24/7 recording at the same resolution.

How do I decide the right retention period if there's no explicit compliance requirement?

Check whether your industry, insurance policy, or local regulation sets a minimum, since many jurisdictions and insurers have specific CCTV retention expectations for commercial premises. Absent an external requirement, balance the storage cost of longer retention against how long after an incident you'd realistically need to review footage, since most incidents are identified and footage pulled within days to a few weeks, not months.

The bottom line

CCTV storage sizing is one formula, but four multiplying inputs: resolution, frame rate, camera count, and retention days. Fix all four explicitly and calculate the total before specifying storage hardware, because changing any one of them later, especially retention period, doesn't adjust the total modestly, it rescales the entire requirement. Once those four inputs are fixed, folding the recorder and storage spec into a wider remote access control infrastructure plan makes sense if CCTV is being deployed alongside access control on the same sites.

Figures verified 10 September 2026 against Wikipedia's Bit rate article for bitrate-by-resolution benchmarks. This session's WebSearch budget was exhausted, so research relied on WebFetch against stable reference material; the bitrate figures cited are general streaming/encoding benchmarks rather than CCTV-specific manufacturer data, so confirm actual bitrate output with your specific camera and codec (H.264/H.265) before finalising a storage purchase, since real CCTV encoder output can differ from these general video-bitrate figures.