Choosing the Right CCTV Resolution and Storage Strategy
More megapixels aren't always better. Balancing resolution, frame rate, and retention is the key to footage that's useful and affordable to store.

On this page14 sections
It's tempting to spec every camera at the highest resolution available — but that decision ripples straight into your storage and network costs. The right strategy matches each camera to the job it actually has to do. This guide explains how to choose CCTV resolution and plan a storage strategy that keeps footage useful as evidence without over-spending on disks, bandwidth, and recorders, with a worked storage calculation you can adapt to your own sites.
Resolution where it counts
A camera identifying faces at a turnstile needs more detail than one watching a wide car park. Higher resolution improves evidentiary value but multiplies bandwidth and storage. Mapping resolution and frame rate to each zone's purpose keeps quality high where it matters and costs sensible everywhere else.
Think in pixels per metre, not megapixels
Megapixels describe the sensor; what matters operationally is how many pixels land on the subject. Pixel density is usually expressed as pixels per metre (px/m) across the scene at the distance you care about. The IEC 62676-4 standard gives commonly used reference levels:
- Detection (is someone there?): around 25 px/m
- Observation (what are they doing?): around 62 px/m
- Recognition (is this someone we know?): around 125 px/m
- Identification (who is this, beyond reasonable doubt?): around 250 px/m
As a worked example, a 4 MP camera with a horizontal resolution of 2,560 pixels covering a scene 10 metres wide delivers roughly 256 px/m — enough for identification across that width. The same camera covering a 40-metre car park delivers around 64 px/m, which is observation level. Rather than buying a higher-resolution camera for the car park, you might add a dedicated camera at the entry barrier where identification actually matters. Our CCTV camera resolution guide covers lens selection and placement in more depth.
Frame rate and lighting matter as much as resolution
Frame rate drives storage almost as strongly as resolution. Many general surveillance views work well at 10–15 frames per second (fps); cash counters, gates with fast-moving vehicles, or areas where you need to follow hand movements may justify higher rates. Low light is the other variable: a high-resolution sensor that produces noisy night images will generate higher bitrates and less useful footage than a lower-resolution camera with good low-light performance and appropriate illumination.
How to size CCTV storage
Storage requirements follow directly from bitrate. The basic formula is:
Storage per camera = average bitrate × recording hours × retention days
The bitrate depends on resolution, frame rate, codec, scene complexity, and lighting, so use the manufacturer's calculator or measure a sample camera on site where possible. The figures below are assumptions for illustration only.
A worked example
Assume a 4 MP camera using H.265 at 15 fps, averaging 4 Mbps, recording continuously.
- Per second: 4 megabits = 0.5 megabytes
- Per day: 0.5 MB × 86,400 seconds = 43,200 MB, or about 43 GB
- Per 30 days: about 1.3 TB per camera
For 50 such cameras, that is roughly 65 TB of usable storage for 30 days. Then add allowances for:
- RAID overhead. In a RAID 6 array, the capacity of two drives goes to parity, so raw disk capacity must be higher than usable capacity.
- Headroom. Bitrates rise at night, in rain, or when scenes get busy. Build in a margin rather than sizing to the average.
- Growth. Cameras are usually added after go-live; plan for expansion bays or a scalable storage tier.
If a camera only records on motion or events, scale the recording hours accordingly — but measure real activity first. A camera covering a busy lobby may be "in motion" for most of the working day.
Reduce storage without losing evidence
- Efficient codecs. H.265 and vendor "smart" codecs typically reduce bitrate compared with H.264 for the same image quality, especially on static scenes. Check that your recorder or video management software supports them.
- Event-based or hybrid recording. Record continuously at a lower frame rate and boost frame rate on motion or alarm.
- Dual streams. Record the main stream for evidence and use a lower-resolution sub-stream for live viewing and remote access, which also reduces network load.
- Tiered storage. Keep recent footage on fast local storage and move older footage to a cheaper archive tier or cloud, if your retention and data policies allow.
Plan retention deliberately
How long must footage be kept — 7 days, 30, 90? Compliance, insurance, and incident-investigation needs all factor in. Smart codecs, motion-based recording, and tiered storage (fast local plus cloud archive) let you hold footage longer without runaway cost.
Retention is not only a storage decision. Under the Digital Personal Data Protection Act, 2023, footage of identifiable people is personal data, so keeping it far longer than your stated purpose requires creates risk rather than reducing it. Set a defined period for each class of footage, make sure the system enforces it automatically, and keep a documented process for preserving clips relating to an incident. Our guides on setting a CCTV footage retention period and what the DPDP Rules mean for CCTV footage cover the policy side in detail.
Don't forget the network and power
High-resolution cameras put real load on the network. Calculate aggregate bitrate per switch and uplink, use PoE switches with enough power budget for cameras with IR or heaters, and keep surveillance traffic on its own VLAN. Recorders, storage, and core switches should sit on a UPS sized for your site's outage pattern, and drives should be monitored for health so a failing disk is replaced before footage is lost.
A planning checklist
- List every camera with its purpose: detection, observation, recognition, or identification.
- Calculate the pixel density needed for each view and choose resolution and lens accordingly.
- Set frame rate per camera based on what moves in the scene.
- Estimate bitrate per camera, ideally from a measured sample.
- Define retention periods by footage type and confirm them with your compliance or legal team.
- Calculate usable storage, then add RAID overhead, headroom, and growth.
- Check network capacity, PoE budget, and UPS coverage.
- Configure health alerts for cameras, recorders, and disks.
Frequently asked questions
Is 4K always better than 4 MP or 2 MP?
No. Higher resolution helps only when the extra pixels are needed on the subject, and it brings higher bitrate, storage, and often poorer low-light performance. Choose resolution based on the pixel density each view requires.
How much storage does a CCTV camera need for 30 days?
It depends on bitrate. As an illustration, a camera averaging 4 Mbps continuously needs roughly 1.3 TB for 30 days. Your actual figure will vary with resolution, frame rate, codec, scene activity, and lighting, so measure where possible.
Is cloud storage suitable for CCTV footage?
Cloud storage can work well for archives, multi-site access, and off-site resilience, but it depends on upload bandwidth and cost per terabyte. Many organisations use a hybrid approach: local recording for recent footage and cloud for selected cameras or longer-term archives.
Can motion-based recording miss important events?
It can if sensitivity, detection zones, or pre-event buffers are poorly configured. Use pre- and post-event recording, test detection under day and night conditions, and consider continuous recording at a lower frame rate for critical views.
Foxnet sizes every deployment end to end — cameras, network, and storage — so your footage is clear when you need it and economical to keep. To review an existing system or plan a new one, explore our surveillance services or contact our team for a site assessment.




Leave a comment