Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

CCTV Storage · 8MP

Avigilon H6A Dome (8MP) storage & retention

Problem. A fleet of Avigilon H6A Dome (8MP) cameras generates far more footage per day than a standard-definition camera, so a 30-day retention target can quietly outgrow a modest NVR if storage is sized by guesswork. Getting the per-camera daily figure right before ordering hardware avoids either an under-sized head-end or an over-bought one.

Answer. At 8MP with H.265 encoding and a typical 8 Mbps bitrate at 30 fps, one Avigilon H6A Dome writes roughly 86 GB per day of continuous recording. Across 16 cameras at 30-day retention that totals about 41 TB, which sits comfortably within an Entry NVR architecture class.

02 / In depth

How this preset reads — the engineering view.

The H6A Dome's 8MP sensor is the reason storage adds up quickly: at a typical 8 Mbps encode rate (30 fps, H.265) it works out to roughly 86 GB of video per camera per day. H.265's smart-codec efficiency is doing real work here — the same scene at plain H.264 would typically need a meaningfully higher bitrate to hold equivalent detail, so the H.265 figure already reflects a leaner file than an older-codec camera of the same resolution would produce.

Scaling is linear and predictable: 16 cameras x 86 GB/day x 30 days works out to roughly 41 TB of raw capacity. Add cameras or stretch retention and the figure moves in direct proportion — doubling either one roughly doubles the number. At 16 cameras this preset sits in the Entry NVR class, the architecture band the calculator assigns before a deployment needs mid-tier or enterprise-class recording infrastructure.

Use the calculator by dragging the camera count and retention-days sliders and switching the recording schedule — the storage total recomputes live as you move each control. Switching from an always-on schedule to a motion-only schedule applies a duty factor that reduces the effective recording hours per day, which can noticeably shrink the total without changing camera count or retention.

The calculator does not decide real-world scene-activity bitrate variance (a busy entrance encodes differently to a quiet corridor even on the same camera model), RAID or redundancy overhead, failover or long-term archive tiering, network write-throughput limits at the switch or NVR, or the exact drive model and count to populate a bay with. Those remain a design step for a qualified installer working from the site's actual footage profile.

What this preset deliberately does not solve

  • The 8 Mbps bitrate is a scene-average figure for typical scenes; higher-motion or higher-detail scenes can push actual bitrate higher for the same camera and codec settings.
  • The 41 TB figure assumes continuous 24/7 recording; a motion-only or scheduled-recording configuration will use less storage than shown here for the always-on preset.
  • No RAID, redundancy, or archive-tier overhead is included — the figure is raw video storage only, before any resilience margin an installer would add.

How this preset differs from its siblings

The H6A Dome's 8MP sensor and H.265 codec at ~8 Mbps sit meaningfully above a typical 2MP or 4MP camera's daily footprint, so its per-camera-per-day figure and resulting NVR class differ from lower-resolution presets even at the same camera count and retention. This preset exists separately because swapping in a different resolution, codec, or bitrate changes the storage arithmetic directly — a reader searching for this specific camera's numbers should not have to recompute from a generic default.

03 / Hydrated calculator

Try the configuration — live.

The calculator below is preloaded with this preset’s state. Adjust any input — your URL stays shareable.

Loading the calculator…

· Next

Brief us on the project — with this configuration.

Presets are a typology starting point. The brief wizard captures the room geometry, programme and constraints we need to translate this configuration into a real design.