0333 900 0101

Calculating Storage & Bandwidth Requirements for 4K CCTV Systems

4 K cameras deliver beautiful clarity, but that detail comes with bigger files and heavier network traffic. Too little storage and yesterday’s footage could be overwritten before you even know an incident happened; too little bandwidth and frames start dropping just when you need them most. Luckily, you do not need to be a network engineer—or carry a scientific calculator—to get the numbers right. This step-by-step guide uses plain English, round numbers and real-world examples drawn from everyday ACCL projects.

Already wrestling with a storage quote? Feel free to jump ahead to the quick-reference tables and “rule-of-thumb” formulas—copy them into your own proposal checklist.

  1. Why 4 K Changes the Equation

A traditional 1080 p camera captures about two megapixels per frame. A 4 K unit grabs four times that. The jump is worth it—faces remain sharp when you zoom, number plates pop at distance and wide scenes still show detail. But the recorder must hold four-times-bigger files, and your PoE switch must push four-times-more data every second.

Good news: modern video compression (H.265) shrinks files by roughly half compared with the older H.264 standard, so the upgrade is not a four-fold cost increase. The trick is to balance resolution, frame rate and retention against realistic risk appetite.

The Only Three Numbers You Need

  1. Bitrate per camera (how much data leaves the lens every second)

  2. Recording hours per day (continuous 24 × 7 or schedule-based)

  3. Days of retention (often 30–90 days for UK businesses)

Multiply those three, add a safety margin and you have your storage plan.

Choosing a Sensible Bitrate

Most 4 K cameras let you set bitrate in the menu. We recommend:

Use Case

       Bitrate (H.265)

      Why

Indoor, stable lighting

       4 Mb/s

 Quiet background, fewer changes per frame

Outdoor with movement

       6 Mb/s

 Trees, traffic and shadows add data

Busy car park or warehouse

        8 Mb/s

 Constant motion needs higher quality

If your camera lists kilobits rather than megabits, divide by 1,000 to keep things simple (e.g., 6,000 kb/s ≈ 6 Mb/s).

Tip: Start with the higher number. You can always dial down during testing, but you cannot recover lost detail.

The Five-Minute “Back-of-Envelope” Storage Formula

Storage (GB)=Bitrate (Mb/s)×0.54×Hours per day×Days\text{Storage (GB)} = \text{Bitrate (Mb/s)} \times 0.54 \times \text{Hours per day} \times \text{Days}Storage (GB)=Bitrate (Mb/s)×0.54×Hours per day×Days

Where 0.54 converts megabits-per-second into gigabytes-per-hour.

Example: 10 indoor 4 K cameras

  • Bitrate: 4 Mb/s each

  • Hours: 24

  • Days: 30

4×0.54×24×30=1,555 GB per camera4 \times 0.54 \times 24 \times 30 = 1,555 \text{ GB per camera}4×0.54×24×30=1,555 GB per camera

Ten cameras × 1,555 GB = 1.55 TB total. Add a 20 % safety margin for disk formatting and metadata, and you need a 2 TB drive set. Small, isn’t it? Compression really earns its keep.

Example: 20 outdoor cameras at 6 Mb/s, 45 days

6×0.54×24×45=3,499 GB per camera6 \times 0.54 \times 24 \times 45 = 3,499 \text{ GB per camera}6×0.54×24×45=3,499 GB per camera

Twenty cameras × 3.5 TB ≈ 70 TB. Here we step into multi-bay NVR territory or a NAS/SAN array.

If you prefer a visual tool, our sales team use a simple Excel sheet—contact us and we’ll send you a copy, no strings attached.

Quick Reference Table

Cameras        Bitrate (Mb/s)        Days        Approx. Storage Needed
8 × office domes              4      30            ~ 1 TB
16 × retail shop             4      60            ~ 4 TB
24 × car park bullets             6      45             ~ 24 TB
32 × mixed indoor/outdoor            6–8      90            50–60 TB

(Numbers rounded; include 20 % extra for overhead and RAID redundancy.)

Understanding Network Load

Peak vs Average

Peak load is what your switch sees when all cameras send full bitrate at once—think 8 AM shift change.
Average load smooths over 24 hours. Design for peak; average looks after itself.

Total Peak (Mb/s)=Number of cameras×Bitrate\text{Total Peak (Mb/s)} = \text{Number of cameras} \times \text{Bitrate}Total Peak (Mb/s)=Number of cameras×Bitrate

A 24-camera warehouse at 6 Mb/s peaks at 144 Mb/s—well within a 1 Gb Ethernet uplink, but remember other traffic (Wi-Fi, VoIP) rides on that pipe too. Segregating CCTV to its own VLAN keeps jitter out of phone calls.

PoE Budget

Check the switch’s total PoE watts. A 4 K camera with IR LEDs draws about 12 W; thirty of those need 360 W. A typical 24-port PoE+ switch supplies 370 W—tight but workable. Add lighting or pan-tilt motors and you may need a second switch or mid-span injector.

Tricks to Reduce File Size Without Killing Quality

  1. Enable VBR (Variable Bitrate): lets the camera throttle data in quiet scenes.

  2. Tune the frame rate: 15 fps is plenty for most security footage; 25 fps mainly helps fast-moving sports.

  3. Use motion regions: record full-time but at lower bitrate outside critical areas.

Schedule high quality: ramp up bitrate overnight when theft risk spikes, dial down during daytime if needed.

Thinking Beyond Disks—Data Lifecycle

  • Archive vs Active storage: Keep last 30 days on fast local disks; move older clips to cheaper cloud buckets.

  • Legal hold: If the police request evidence, flag those files so housekeeping scripts skip them.

Health monitoring: Use VMS alerts to warn when free space drops below 15 %; never wait for a “disk full” error. See our upcoming guide to CCTV health monitoring for auto-alerts.

Case Snapshot: Right-Sizing Saves £7,000

A South-East manufacturing plant budgeted for 40 TB because “4 K equals big files.” ACCL measured real-world bitrate during a two-week pilot—average 4.8 Mb/s, even in their bustling packing hall. By switching to VBR and trimming frame rate to 18 fps, we cut estimated storage to 22 TB, halved the RAID chassis cost and shaved energy use by 40 %. Quality stayed courtroom-sharp.

Your Next Steps

  1. List cameras: count indoor vs outdoor, note planned bitrate.

  2. Pick retention: align with risk and any insurer mandate.

  3. Run the formula or table: eyeball storage volumes.

  4. Check switch uplinks and PoE budget.

  5. Add 20 % safety margin for peace of mind.

Need a sanity check? Call ACCL on 0333 900 0101 or use our contact form. We’ll crunch the numbers and send you a no-obligation sizing sheet.