Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

CCTV Storage · 8MP

Axis P3268-LVE — storage & retention planning

Problem. An 8MP camera recording continuously produces a meaningfully larger daily file than the 2-4MP cameras most storage rules of thumb are written for, so a fleet-level estimate has to start from this camera's own bitrate rather than a generic assumption. Getting the per-camera-per-day figure right before specifying an NVR avoids under-sizing storage or over-buying a head-end class the fleet does not need.

Answer. At its typical 8 Mbps H.265 stream, a single Axis P3268-LVE recording continuously works out to roughly 86 GB per camera per day. Across 16 cameras and a 30-day retention window that comes to about 41 TB of usable storage, which sits comfortably within an Entry NVR architecture class.

02 / In depth

How this preset reads — the engineering view.

The Axis P3268-LVE is an 8MP fixed dome, and at its typical H.265 operating point of 8 Mbps and 30 fps that resolution is the dominant driver of the storage sum — roughly 86 GB per camera per day at continuous recording. H.265's smart-codec efficiency is doing real work here: the same 8MP sensor encoded in plain H.264 at a comparable frame rate would typically push meaningfully more data per day for a similar visual result, so the codec choice is not a footnote, it is a large share of the saving.

Scaling from one camera to a fleet is linear: 16 cameras across a 30-day retention window comes to roughly 41 TB (16 x 86 GB x 30 days, before overhead). Longer retention or a larger camera count scales the same way — doubling either input roughly doubles the storage figure. At 16 cameras and this data rate, the resulting head-end sits in the Entry NVR class rather than requiring a rack-mount or enterprise platform.

Use the calculator by dragging camera count, retention days and recording schedule and watching the storage total recompute live. Switching from an always-on schedule to a motion-only or scheduled-hours pattern applies a duty factor that reduces the effective recording time per day, which is usually the single largest lever available once the camera model and count are fixed.

The calculator does not decide real scene-activity bitrate variance (a busy loading bay or heavy foliage will push actual bitrate above the camera's typical figure, while a static, low-motion scene can sit below it), RAID or redundancy overhead, a separate failover or long-term archive tier, network write-bandwidth limits at the switch, or the exact drive make, count and capacity plan — those remain sizing decisions for the system design stage.

What this preset deliberately does not solve

  • The 8 Mbps figure is a typical scene-average bitrate for this camera at 30 fps H.265; busier scenes with more motion or detail will record at a higher instantaneous bitrate than this planning figure.
  • The default schedule here is continuous 24/7 recording; switching to motion-only or scheduled-hours recording applies a duty-cycle reduction and will lower the storage total below the continuous figure shown.
  • The 41 TB total is usable recording capacity only — it excludes RAID/redundancy overhead, spare capacity margin, and any separate archive or failover tier, all of which add to the physical drive capacity actually purchased.

How this preset differs from its siblings

This preset exists separately because the Axis P3268-LVE's 8MP sensor and 8 Mbps H.265 operating point produce a materially different per-camera-per-day figure than lower-resolution or differently-codec'd cameras in the catalogue — a 2MP or 4MP camera preset would land at a fraction of this storage draw and a different NVR class entirely. Naming the exact model keeps the ~41 TB / ~86 GB-per-day figures tied to a real, verifiable spec rather than a generic megapixel-tier estimate.

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.