Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

— CCTV Storage · 8MP

Uniview IPC2328SB-DZK-I0 (8MP) storage & retention

Problem. A fleet of Uniview IPC2328SB-DZK-I0 (8MP LightHunter) cameras generates far more footage per day than a 2MP or 4MP fleet, so the real decision is how much drive capacity and what NVR class a 30-day retention policy actually needs. Getting the storage math wrong at design stage means a mid-project drive upgrade or a head-end that cannot keep pace with continuous recording.

Answer. At 16 cameras recording continuously for 30 days, this camera's 8MP resolution and H.265 smart codec profile works out to roughly 76 GB per camera per day, or about 36 TB of storage in total. At that camera count the recommended architecture class is an Entry NVR.

02 / In depth

How this preset reads — the engineering view.

The IPC2328SB-DZK-I0's 8MP sensor at a typical 7 Mbps (H.265 smart, 25 fps) is the storage driver behind the ~76 GB-per-camera-per-day figure. The H.265 smart codec profile compresses static scene detail more aggressively than plain H.264, which is why this camera's footprint stays proportionate to its resolution rather than ballooning further — but 8MP still records noticeably more data per day than a 2MP or 4MP camera at the same frame rate.

Storage scales linearly from the per-camera figure: 16 cameras x 30 days at ~76 GB/camera/day works out to roughly 36 TB. Add more cameras or extend retention and the total moves in direct proportion — doubling either roughly doubles the figure. At 16 cameras, the head-end sits in the Entry NVR class; larger counts or longer retention windows typically push the architecture into a higher class.

Use the calculator by dragging the camera count, retention period, and recording schedule to watch the storage total recompute live. Switching from an always-on schedule to a motion-only or scheduled-hours profile applies a duty-cycle factor that reduces the effective recording hours per day, cutting total storage accordingly.

The calculator does not decide real scene-activity bitrate variance (busy versus static scenes push actual bitrate above or below the 7 Mbps typical figure), RAID or redundancy overhead, a failover or archive tier, network write-throughput limits at the switch or NVR, or the exact drive count and capacity plan for a given enclosure.

What this preset deliberately does not solve

  • The 7 Mbps bitrate is a scene-average typical figure for H.265 smart encoding; busier scenes with more motion will record at a higher effective bitrate than quieter ones.
  • The 36 TB figure assumes continuous 24/7 recording; switching to motion-only or scheduled-hours recording reduces the total via a duty-cycle factor, not a flat resolution change.
  • The estimate does not include RAID, redundancy, or archive-tier overhead — actual usable drive capacity in a real deployment will be lower than the raw storage figure shown.

How this preset differs from its siblings

This camera's 8MP resolution paired with H.265 smart encoding at a typical 7 Mbps sits well above a typical 2MP or 4MP camera's per-day footprint, so the same 16-camera, 30-day preset would produce a materially smaller total on a lower-resolution model. The resolution and codec profile are the two inputs that most change the storage outcome, which is why this camera warrants its own preset rather than sharing a generic 8MP assumption with other models.

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…

· Other presets for cctv storage retention 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.

Open in the toolSend the brief