CCTV Storage Calculator: NVR Drives, PoE and UPS

Plan a camera system from the numbers that decide it: each camera’s bitrate, the hours it records and how many days you keep. The planner turns them into usable storage, the drives an NVR needs, the PoE budget for the switch and the load on the UPS, and shows every formula and assumption it used.

The interactive planner on this page takes camera groups (count, bitrate, recording hours, motion share), retention days, NVR drive layout, bays and drive size, PoE classes and switch budget, and UPS equipment, and shows each formula with your numbers.

Example: 8 cameras, 30 days

  • 8 cameras at 4 Mbps, recording 24 hours a day, write 43.2 GB each per day and 345.6 GB together.
  • 30 days of footage is 10.37TB; with a 10% planning reserve, plan for 11.4TB usable.
  • With 8TB drives: 2 drives as independent disks (no protection), or 4 drives in RAID 6 (survives any 2 drive failures).
  • PoE: 8 class 3 cameras need up to 103.6 W at the cameras; a switch that reserves by class sets aside 123.2 W of its PoE budget.

Decimal TB as drives are sold; binary TiB as many NVRs and operating systems show it. Bitrate is the camera’s own setting, not derived from resolution. Every estimate here is for planning: confirm bitrates, power and drive support against your equipment datasheets.

Storage per camera by bitrate (continuous recording)

BitratePer camera per day1 camera, 30 days8 cameras, 30 days16 cameras, 30 days
1 Mbps10.8 GB0.32TB2.59TB5.18TB
2 Mbps21.6 GB0.65TB5.18TB10.37TB
4 Mbps43.2 GB1.3TB10.37TB20.74TB
6 Mbps64.8 GB1.94TB15.55TB31.1TB
8 Mbps86.4 GB2.59TB20.74TB41.47TB
16 Mbps172.8 GB5.18TB41.47TB82.94TB

GB/day = Mbps × 86,400 s ÷ 8 ÷ 1,000. Motion recording writes only part of the day: multiply by the share of time actually recorded.

Days one drive holds at 4 Mbps per camera (continuous)

Drive4 cameras8 cameras16 cameras
4TB23115
8TB462311
12TB693417
16TB924623
24TB1386934

Whole days, decimal capacity, no reserve. Real NVRs keep a little space for their own database; leave headroom.

Drives for 11.4TB usable (the example above)

Drive sizeIndependent disksRAID 6
4TB3 (12TB)5 (12TB)
6TB2 (12TB)4 (12TB)
8TB2 (16TB)4 (16TB)
12TB1 (12TB)4 (24TB)
16TB1 (16TB)4 (32TB)
20TB1 (20TB)4 (40TB)

Count of drives, with usable capacity in brackets. Check the NVR’s bay count and maximum drive size before choosing.

PoE classes: power at the switch port and at the device

ClassStandardSwitch port (PSE)At the device (PD)
Class 1802.3af (PoE)4 W3.84 W
Class 2802.3af (PoE)7 W6.49 W
Class 3802.3af (PoE)15.4 W12.95 W
Class 4802.3at (PoE+)30 W25.5 W
Class 6802.3bt Type 3 (PoE++)60 W51 W
Class 8802.3bt Type 4 (PoE++)90 W71.3 W

IEEE 802.3af/at/bt values. The difference is the most that can be lost in 100 m of cable at full class power.

Bitrate decides storage, not resolution

Storage is bitrate multiplied by time. A camera recording at 4 Mbps for a full day writes 4 × 86,400 seconds = 345,600 megabits, which is 43.2 GB.

Resolution only sets a range. Two 4 MP cameras can record at very different bitrates depending on frame rate, codec (H.264 or H.265), the camera’s quality setting, how busy the scene is, and low light, where image noise can raise the bitrate considerably. That is why the planner asks for bitrate and treats its resolution presets as starting points. The camera’s web page or the NVR’s channel settings show the configured bitrate: use the maximum for variable-bitrate (VBR) streams if you want a worst case.

Continuous, scheduled and motion recording

Scheduled recording is modelled exactly: hours per day. Motion or event recording is modelled as the share of those hours actually written, including the pre- and post-event buffers the NVR keeps. That share is an estimate. A camera watching a busy entrance can record most of the day; one watching a back corridor may record a few percent. If you are unsure, plan with continuous recording: it is the upper bound.

Required, raw and usable capacity

The planner keeps three numbers apart. Required is the footage plus any overhead and reserve you chose. Raw is the manufacturer-rated capacity of every drive you buy, hot spares included. Usable is what the layout leaves for footage: all of it with independent disks, less with RAID.

Many NVRs write to independent disks and overwrite the oldest footage when full. That gives the most capacity, but a failed disk loses whatever was recorded on it. NVRs that support RAID 5, 6 or 10 trade capacity for surviving a drive failure; see the RAID calculator for the full arithmetic and the hot spare guide for what a spare does and does not add.

TB on the box, TiB on the screen

Drives are sold in decimal terabytes; many NVRs and operating systems show binary tebibytes. 11.4TB is 10.37 TiB: nothing is missing, it is the same number of bytes. The planner shows both. More detail in TB vs TiB.

Drive bays and drive size limits

An NVR can only use the bays it has and the drive sizes its firmware supports. Both are on the datasheet, often as "up to N SATA HDDs, up to X TB each". Enter them and the planner refuses a plan that does not fit instead of quietly suggesting one. If no size fits, the options are larger drives (if supported), a layout with less overhead, shorter retention, lower bitrates, or expansion storage.

PoE budget is not switch power consumption

A PoE switch has two power figures. Its PoE budget is how much it can deliver to cameras and access points across all ports. Its power consumption is what it draws from the wall, which includes the switch itself and losses in its power supply.

Some switches reserve the full class power for each device, whatever the device actually draws: Cisco documents this as the default for its Catalyst switches, which lower the reservation only when the device reports its needs over CDP or LLDP. Check how your switch allocates. That is why the planner budgets by class unless you choose measured draw. A class 3 camera reserves 15.4 W even if it uses 8 W; 8 of them reserve 123.2 W.

Check two things on the switch datasheet: the total PoE budget, and the highest class each port supports (802.3af, at, or bt). A PTZ camera or a heated housing may need PoE+ or PoE++ ports.

UPS: size on watts, and treat runtime as an estimate

Add the NVR, its drives, the switch’s own draw, the PoE power it delivers (converted back to wall power) and anything else on the UPS. Count PoE cameras once, through the switch. With example values (NVR 20 W, 2 drives at 6 W, switch 20 W, 76.1 W of PoE at 90% efficiency) the load is 136.6 W, so a UPS rated at least 171 W keeps it at 80% of the rating.

Size on the UPS watt rating: the VA figure alone can mislead. Runtime depends on the battery, its age, temperature and the UPS cut-off, so the planner only gives an upper bound from battery energy (216 Wh, such as two 12 V 9 Ah batteries, at 90% inverter efficiency gives at most 85 minutes here) and points you to the manufacturer’s runtime chart.

Check these on the datasheets before you buy

Cameras: configured bitrate (or maximum for VBR), PoE class, maximum power with IR and heater on.

NVR: channel count, incoming bandwidth (Mbps), bays, maximum drive size, supported RAID levels, power without drives.

Drives: capacity, operating power, and whether the NVR maker lists them as compatible.

Switch: total PoE budget, per-port class, power consumption without PoE.

UPS: watt rating and the runtime chart at your load.

Common planning mistakes

Using the main-stream resolution instead of the bitrate. Bitrate is what fills disks.

Forgetting night-time. Many cameras use more bitrate in low light; measure at night.

Mixing up TB and TiB. A shortfall of about 9% that is only a change of unit.

Counting PoE cameras twice on the UPS. Their power is already inside the switch’s load.

Treating RAID as a backup. RAID keeps recording through a drive failure; it does not protect against deletion, theft of the recorder or a failed controller.

8TB surveillance drives

In-stock surveillance-class drives of the example size, with live prices. This is a drive class, not a compatibility check: confirm the model is on your NVR maker's compatibility list.

Shop for this plan

Frequently asked questions

How much storage do I need for 8 cameras for 30 days?

At 4 Mbps each, recording continuously, 10.37TB of footage; plan for about 11.4TB usable with a 10% reserve. At a different bitrate, scale in proportion: half the bitrate, half the storage.

How many days will a 4TB drive record?

It depends on the total bitrate. At 4 Mbps per camera, recording continuously, a 4TB drive holds about 23 days for 4 cameras and 11 days for 8.

Does H.265 use less storage than H.264?

Usually, for similar image quality, because it compresses more efficiently, but the saving varies by camera and scene. Use the bitrate each camera is actually set to rather than a fixed percentage.

Should an NVR use RAID?

Only if it supports it and losing footage from one failed disk is unacceptable. Independent disks give the most capacity; RAID 5 survives one drive failure, RAID 6 two, RAID 10 at least one, at the cost of extra drives.

How much power does a PoE camera use?

Check the camera datasheet for its maximum power with IR and any heater on. Its PoE class caps it: a class 3 device gets at most 12.95 W, class 4 at most 25.5 W. Many switches reserve the full class power per port.

What size UPS do I need for an NVR and cameras?

Add up the NVR with its drives, the switch with the PoE power it delivers, and other equipment, then choose a UPS whose watt rating is comfortably above the total. In the example here the load is 137 W, so at least a 171 W UPS at 80% loading.

How long will a UPS keep my cameras running?

Read the manufacturer’s runtime chart at your load. A calculation from battery watt-hours gives only an upper bound, because battery capacity falls at high discharge rates, with age and in the cold, and the UPS shuts down before the battery is empty.

Sources

Related tools and guides

Updated 2026-10-22.

Part of

Enterprise Storage Hub

View all 172 pages →

Enterprise HDDs, SSDs, NVMe, SAS, SATA, RAID controllers, drive caddies and storage array hardware.