Running out of recording days is one of the most common CCTV complaints, and it is nearly always a sizing problem rather than a fault. Storage is simple arithmetic once you have a real bitrate. This guide gives the formula, works through a complete example for a 20-camera site, and shows how RAID and disk labels change the answer.
The formula
A camera’s bitrate is how many megabits of video it produces each second. Everything else follows from it:
- 1 Mbps for one hour = 1 × 3,600 seconds = 3,600 megabits.
- 3,600 megabits ÷ 8 bits per byte = 450 megabytes = 0.45 GB per hour.
- So one camera at 1 Mbps recording all day needs 0.45 × 24 = 10.8 GB per day.
For a whole site:
Storage (GB) = cameras × average Mbps × 0.45 × hours recorded per day × retention days × share of time recorded
“Share of time recorded” is 100 % for continuous recording and lower for motion or event recording. Add headroom (10 % is a sensible minimum) so the recorder is never writing to a completely full disk. This guide uses decimal units, as disks are sold: 1 GB = 1,000,000,000 bytes and 1 TB = 1,000 GB.
Getting a real bitrate
The formula is only as good as the bitrate you put into it. Brochure figures are measured on easy scenes. Real bitrate depends on resolution, frame rate, codec, the camera’s bitrate control (constant or variable), any “smart” codec, the scene and, above all, the light: at night, image noise and IR make the encoder work harder and bitrate rises.
- Existing site: read the average bitrate per camera from the recorder or VMS statistics across a full day and night, not a five-minute look at noon.
- New site: estimate from resolution, frame rate, codec and scene with the camera bitrate lab, then check on a test camera on site before ordering disks.
- Constant bitrate (CBR): the camera’s set bitrate is close to the real figure. Variable bitrate (VBR): the set figure is a ceiling; the average is lower in quiet scenes and close to the ceiling in busy ones.
Worked example: 20 cameras, 30 days
An office building has 20 IP cameras recording continuously. The recorder’s statistics show an average of 3 Mbps per camera over a full day and night. The client needs 30 days of footage.
- Per camera per hour: 3 Mbps × 0.45 GB = 1.35 GB
- Per camera per day: 1.35 GB × 24 h = 32.4 GB
- All cameras per day: 32.4 GB × 20 = 648 GB
- 30 days: 648 GB × 30 = 19,440 GB = 19.44 TB
- With 10 % headroom: 19.44 TB × 1.1 = 21.384 TB, call it 21.4 TB
The recorder needs at least 21.4 TB of usable space.
Check it the other way round: 20 cameras × 3 Mbps = 60 Mbps arriving at the recorder. 60 × 10.8 GB = 648 GB per day, the same answer.
Choosing disks and RAID
Usable space depends on how the disks are arranged. Without RAID each disk is used in full but a failed disk loses its footage. RAID 5 gives up one disk’s capacity for parity and survives one failed disk. RAID 6 gives up two and survives two. RAID 1 and RAID 10 give up half.
| Layout | Disks | Usable | Fits? |
|---|---|---|---|
| RAID 5, 6 TB disks | 4 disks: (4 − 1) × 6 | 18 TB | No, short by 3.4 TB |
| RAID 5, 6 TB disks | 5 disks: (5 − 1) × 6 | 24 TB | Yes |
| RAID 5, 8 TB disks | 4 disks: (4 − 1) × 8 | 24 TB | Yes, fits a 4-bay recorder |
| RAID 6, 6 TB disks | 6 disks: (6 − 2) × 6 | 24 TB | Yes |
| RAID 6, 8 TB disks | 5 disks: (5 − 2) × 8 | 24 TB | Yes |
| No RAID, 8 TB disks | 3 disks: 3 × 8 | 24 TB | Yes, but no protection |
The number of drive bays decides a lot. A 4-bay recorder cannot hold five 6 TB disks, so in this example 8 TB disks in RAID 5 are the practical choice. Check that the recorder supports the RAID level and the disk size you plan to use, and use disks intended for continuous surveillance recording.
Mixed and motion recording
Most sites are not uniform. Work out each group of cameras separately and add them up. Suppose the same site instead has:
- Outdoor: 8 × 4 Mbps × 0.45 × 24 h × 30 days = 10,368 GB
- Indoor at 2 Mbps, recording about 40 % of the time: 12 × 2 × 0.45 × 24 × 30 × 0.40 = 3,110.4 GB
- Total: 10,368 + 3,110.4 = 13,478.4 GB
- With 10 % headroom: 13,478.4 × 1.1 = 14,826 GB ≈ 14.8 TB
Be cautious with motion percentages. Trees, rain, headlights, insects near IR lights and night noise all trigger motion. Estimate high, then measure after a week and adjust.
Why the recorder shows less than the label
Disk makers count in decimal (1 TB = 1012 bytes). Many recorders and operating systems count in binary units (1 TiB = 240 = 1,099,511,627,776 bytes) but still label them “TB”. So 24 TB of usable decimal space appears as about 21.8 TB on the recorder (24 × 1012 ÷ 240 ≈ 21.83). The requirement shrinks the same way — 21.384 TB is about 19.45 in binary units — so the design still fits. Just compare like with like, and expect a little more to be lost to formatting.
Checklist
- Use the measured average bitrate across day and night, per camera group.
- Confirm the retention period the client or sector actually requires, in writing.
- Add at least 10 % headroom.
- Choose the RAID level for the protection the site needs, then the disk size that fits the bays.
- Check the recorder’s maximum disk size, RAID support and incoming bandwidth.
- After commissioning, check the oldest recording date after the first month: it is the real retention.
The NVR storage sizing lab runs this calculation, including RAID and the number of disks, for your own numbers.
