H.265 can reduce the data needed for comparable video, but a codec name does not guarantee a storage percentage or better evidence. Scene movement, noise, rate control, keyframes, decoder support and the camera’s own implementation determine the real result.
Treat codec as a workflow decision
H.264/AVC and H.265/HEVC are video coding standards, not fixed quality settings. H.265 uses more advanced prediction and block structures to encode video more efficiently, especially at higher resolutions, but it generally demands more processing and may be less compatible with older recorders, browsers, phones and evidence players. The ITU lists current in-force editions of both standards; neither has become invalid simply because another is newer. In a CCTV project, choose the codec that every critical part of the workflow can record, display, export and replay. A small storage saving has little value if an investigator cannot open the file on the required machine.
Measure savings instead of repeating a percentage
Do not promise ‘half the storage’ from the codec label. Savings vary with scene complexity, implementation and target quality. A quiet corridor with a stable background compresses differently from rain, foliage, traffic, sensor noise or a constantly moving PTZ. Manufacturer-enhanced modes may use dynamic frame rate, dynamic group-of-pictures and region-aware compression to save more in surveillance scenes; those figures are vendor measurements and should be validated on the exact model and firmware. Run parallel test profiles where possible, capture representative day and night periods, and compare both measured bitrate and moving-subject quality before changing an entire estate.
Choose VBR, CBR and caps deliberately
Bitrate control determines how the encoder spends data. Variable bitrate (VBR) allows demand to rise for complex scenes and fall when little changes, which usually protects quality efficiently but creates storage and network peaks. Constant bitrate (CBR) targets a steadier rate, useful where links have hard limits, yet may waste data in quiet scenes or lose detail when complexity exceeds the budget. Maximum bitrate caps can make capacity planning safer, but a cap set too low forces visible damage exactly when rain, crowds or motion make the scene important. Use a quality target plus a defensible maximum, monitor real percentiles and leave headroom rather than sizing links to the average alone.
Calculate storage from measured bitrate
Storage arithmetic starts with measured aggregate bitrate. Approximate daily storage in gigabytes as bitrate in megabits per second multiplied by 10.8. A camera averaging 4 Mb/s therefore uses about 43.2 GB per day before container, database and operational overhead; eight such cameras use about 346 GB per day. Multiply by retention days, then add free-space and resilience allowances. Motion recording changes the average only after the real activation ratio is measured across weather, lighting and seasonal activity. Calculate the main recording stream separately from substreams, audio and redundant copies. Never plan from resolution alone.
Understand GOP and keyframe trade-offs
GOP structure affects recovery, seeking and failure behaviour. An I-frame is independently decodable; following predicted frames depend on other frames. Longer intervals can improve efficiency but may increase the time to a clean image after packet loss and make precise seeking or export less responsive. Some smart codecs extend the GOP dramatically when a scene is quiet, then shorten it around motion. That can work well, provided the NVR and player understand the stream and event footage has been tested. For evidential systems, verify playback at the start of exported clips, frame stepping around the event and recovery after a simulated link interruption.
Judge moving evidence after dark
Image quality must be judged on movement at the evidence zone. Pause a walking face, moving plate or hand at the till and compare it with the operational requirement. Blockiness, mosquito noise and smeared texture can come from too little bitrate, aggressive noise reduction, slow shutter or a combination; increasing bitrate cannot recover detail already blurred by exposure. At night, sensor noise consumes data and can make a previously stable VBR stream surge. Tune lighting and exposure first, then codec and bitrate. Keep the original resolution and stream settings documented so a later firmware update or factory reset cannot silently change retention or quality.
Migrate one representative channel first
A safe migration is staged. Confirm that cameras, NVR/VMS, workstation decoders, mobile apps, export tools and any integration all support the selected H.265 profile. Enable it on one representative channel, record through day and night, test live grids, remote viewing, event search, export and third-party playback, then compare seven-day bitrate and storage with the H.264 baseline. Retain H.264 for devices or recipients that require it, and consider a lower-resolution substream for multi-camera viewing. Choose H.265 when measured savings survive the complete workflow; choose H.264 when interoperability and low decode load are more valuable.
Keep a measured codec baseline
Document the codec decision as a measured baseline. For each test channel, record resolution, frame rate, shutter limit, codec profile, rate-control mode, quality level, bitrate cap, I-frame interval, audio setting and smart-codec features. Capture average, 95th-percentile and peak bitrate during comparable time windows, then calculate expected retention with the same storage reserve. Keep short exported clips of quiet daylight, busy movement and difficult night conditions and verify them on a computer that is not the recorder. This evidence makes future tuning safer: if retention suddenly falls after a firmware update, the maintainer can compare settings and scene behaviour instead of reducing quality blindly. Re-run the baseline when lighting, foliage, traffic or camera position changes because the scene is part of the compression system.
Quick estimate: 1 Mb/s sustained for 24 hours is about 10.8 GB. Multiply the measured average Mb/s by 10.8, then by camera count and retention days; add recorder overhead and free-space margin.
Before you sign off
- Verify codec support across the complete evidence workflow
- Measure representative day and night bitrate
- Set quality and maximum bitrate deliberately
- Calculate storage from aggregate measured Mb/s
- Test keyframe seeking and recovery after packet loss
- Inspect moving evidence—not static screenshots
- Migrate one channel before changing the estate
Can another person prove the system still works?
Record the final view, night image, bitrate, alerts, firmware and access method. A system is not finished until the owner can verify recording and export without the installer standing beside it.
Every site is different. Confirm manufacturer instructions, electrical requirements, privacy obligations and local regulations before installation.
Sources used for this guide
Primary standards and manufacturer documentation are linked so you can verify thresholds, features and current product behaviour.
Frequently asked questions
Is H.265 better than H.264 for CCTV?
H.265 can deliver comparable quality at a lower bitrate, particularly at higher resolutions, but it needs compatible recorders, players and decoders. Test the complete workflow before switching.
Does H.265 always use 50 percent less storage?
No. Real savings vary with the scene, lighting, motion, noise, encoder and quality settings. Measure representative day and night footage on the exact camera.
How much storage does a 4 Mb/s CCTV camera use?
A sustained 4 Mb/s stream is approximately 43.2 GB per day before recorder overhead. Real VBR use changes with scene activity and camera settings.
Should CCTV use CBR or VBR?
VBR usually spends data more efficiently as scene complexity changes. CBR is useful for tightly limited links, but an overly low target can damage important motion detail.