Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

CCTV Storage · 8MP

Hanwha Wisenet XNB-9002 (4K) storage & retention

Problem. An 8MP camera at H.265 shifts the storage conversation from 'how many terabytes' to 'how many camera-days'. Once a fleet of Hanwha Wisenet XNB-9002 (4K) units is set to continuous recording at a 30-day hold, the daily footprint per camera becomes the number that decides the whole head-end.

Answer. For 16 Hanwha Wisenet XNB-9002 (4K) cameras recording continuously (24/7) at a 30-day retention, the working figure is about 52 TB of usable storage, or roughly 108 GB per camera per day. At that camera count the recorder sits in the Entry NVR architecture class.

02 / In depth

How this preset reads — the engineering view.

The XNB-9002 (4K) records 8MP video with H.265 compression at a typical 10 Mbps and 30 fps, which works out to roughly 108 GB per camera per day of continuous footage. H.265 is the reason that figure is manageable at all - the same 8MP stream on plain H.264 would need materially more bitrate to hold comparable detail, so the smart codec is doing real work before any schedule or motion setting is touched.

Multiply one camera's daily figure across the fleet and the timeline: 16 cameras x 108 GB/day x 30 days lands at approximately 52 TB. The relationship is linear, so stepping retention to 45 or 60 days, or adding cameras beyond 16, scales the total in direct proportion - there is no discount for scale in raw storage terms. At 16 cameras and this bitrate, the recording head-end falls in the Entry NVR class, which is the practical ceiling this preset is built around.

Inside the calculator, drag the camera-count slider and the retention-days field to see the total recompute instantly, and switch the recording schedule from continuous to a motion-only setting to see the duty factor pull the estimate down - motion-triggered recording only stores the portion of the day with detected activity, so the effective daily footprint per camera drops well below the continuous figure.

The calculator does not decide the exact bitrate a given scene will produce (busy, high-motion scenes push H.265 output above the 10 Mbps average used here, while static scenes push it below), it does not add RAID or redundancy overhead, it does not size a failover or archive tier, it does not check network write throughput against camera count, and it does not choose an exact drive make or model - those remain engineering decisions for the actual deployment.

What this preset deliberately does not solve

  • The 10 Mbps figure is a scene-average bitrate for H.265 at 8MP/30fps; genuinely busy or high-motion scenes will push actual per-camera usage above this estimate, and static scenes below it.
  • The continuous 24/7 default assumes recording never stops; switching to a motion-only or scheduled recording profile changes the effective daily storage well below the figures shown here.
  • The estimate is raw usable capacity only - it does not include RAID, redundancy, or archive-tier overhead, which add to the physical drive capacity actually required.

How this preset differs from its siblings

The XNB-9002 (4K)'s 8MP sensor and H.265 codec produce a materially different daily footprint than lower-resolution or H.264-only cameras - resolution and codec are the two biggest levers on storage math, ahead of camera count or retention window. A camera at a different megapixel class or bitrate profile would land on a different preset entirely, which is why this page is scoped to this specific model rather than folded into a generic 8MP example.

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.