Monday – Friday, 09:00 – 18:00 (UTC+3) WhatsApp 24/7

CCTV Storage and PoE Budget Calculator

Terabytes, bit rate, drive count and switch power from camera count, resolution and retention period — plus the pixels per metre your lens actually delivers.

Calculator

From camera count, resolution and retention period to terabytes and a switch power budget.

The bit-rate band is derived from the resolution

The calculator uses a different example bit rate for each codec; the gap varies with the camera, settings and scene — measure it on your own footage

Bit rate does not rise linearly with frame rate; on busy scenes plan against the top of the band

24 for continuous recording; on motion-only recording enter the hours you actually expect to record

How many days of footage must remain available

Surveillance-rated drive capacity

Consumption peaks when the IR illuminator cuts in at night — enter the MAXIMUM figure from the datasheet, not the typical one

How far the person you need to identify is from the camera. Leave at 0 if you do not know it

Listed as “horizontal FOV” on the datasheet. Rough guide: 2.8 mm ≈ 100–110° · 4 mm ≈ 80–90° · 6 mm ≈ 55° · 12 mm ≈ 28°

Optional. You enter the px/m that your specification or your own standard asks for; the page carries no ready-made threshold — read it from your specification or from IEC 62676-4, or see the manufacturer summary (Axis) under Sources. Write it without a thousands separator. Leave it blank and only the calculated px/m is shown; fill it in and the result also says whether it is met and how far away, at most, this lens still meets it

Result

—Total bit rate
—Data per day
—Raw storage needed
—Drives suggested
—PoE budget
—Pixel density

The calculation runs entirely in your browser; nothing you type is sent to our servers. Only if you press “Request a quote with this calculation” are your inputs and the result written to your browser’s session storage, so it can be carried into the quote form.

Worked example

Opened with its default case — Number of cameras: 16 · Resolution: 4 MP (2560×1440) · Compression: H.265 — the calculator returns the figures below. They are written out here so the output is readable without running JavaScript: in print, with scripts disabled, or by a search engine.

Worked example — inputs
InputValue
Number of cameras16
Resolution4 MP (2560×1440)
CompressionH.265
Frame rate15 fps
Recording hours per day24
Retention period (days)30
Capacity of one drive (TB)8
Maximum camera power (W)6.5
Target distance (m)0
Lens horizontal field of view (degrees)90
Worked example — results
ResultValue
Total bit rate44 Mbps
Data per day475.2 GB/day
Raw storage needed14.3 TB
Drives suggested3 × 8 TB
PoE budget104 W (switch: 130 W)

Change any field above and the calculator recomputes; this table is the default case only. The px/m threshold that comes from a standard is not built into the tool: the “Required px/m” field starts empty and you type the value your specification or your own standard asks for. While it is empty only the calculated pixel density is shown.

Short answer

How many terabytes does a CCTV system need?

Storage is set by bit rate, not by resolution. The formula is storage (GB) = bit rate (Mbps) × 3600 × hours/day × days × cameras ÷ 8 ÷ 1000. As a shortcut, 1 Mbps recorded continuously for 24 hours ≈ 10.8 GB/day. Worked example: 16 cameras, 4 MP, H.265 at 15 fps (mid-band ≈ 2.75 Mbps), 24 hours, 30 days → about 14 TB raw, or 16.4 TB with a 15% margin — three 8 TB surveillance drives. The same system at the top of the band (3 Mbps) needs 15.6 TB raw (before the margin), and a busy scene at 4 Mbps needs 21 TB raw. That is why the bit-rate assumption matters as much as the answer. H.265 aims for a lower bit rate than H.264 at the same picture; the gap varies with the camera, settings and scene — measure it on your own footage. On the power side, the switch budget is built on maximum draw, not typical (IR at night is the peak), with a further 20–25% headroom.

The storage formula

Storage (GB) = bit rate (Mbps) × 3600 × hours/day × days × cameras ÷ 8 ÷ 1000
Drive makers sell decimal terabytes (1 TB = 1,000 GB) while the operating system and the NVR report binary units (TiB). A drive labelled 8 TB therefore shows as roughly 7.3 TiB in the system — the same capacity in binary units, not a loss. This calculator works in decimal TB, so compare its result with the label directly and expect the NVR to show about 9% less.

Example bit-rate bands (the calculator’s assumption)

Bit rate by resolution and codec
ResolutionH.264 (Mbps)H.265 (Mbps)Horizontal pixels
2 MP (1080p)3–41.5–21920
4 MP (2560×1440)5–62.5–32560
5 MP6–83–42592
8 MP (4K)10–165–83840

These bands are examples — read the bit rate from your own camera’s setting or recording. The calculator uses the mid-point of each band for a normally busy scene at 15 fps. A car park at night sits near the bottom; a production line with constant movement, or a scene with rain, foliage and headlights, sits at the top or above it. Smart codecs (the manufacturer names vary) can lower these figures on static scenes; how much they help depends on the scene, so measure it on your own footage.

Two settings change the number more than the camera choice does. Frame rate: going from 15 to 25 fps does not multiply the bit rate by 1.67 — encoders exploit the similarity between consecutive frames, so the real factor is closer to 1.4. Recording mode: motion-triggered recording is only a saving if the scene is genuinely quiet. On a busy corridor the trigger fires most of the day and you get continuous recording with gaps in the evidence.

Pixels per metre, not megapixels

“8 MP so we will be able to read faces” is a costly mistake in camera specification. What decides whether a face is identifiable is pixels per metre at the target distance, and that depends on the lens as much as the sensor. Scene width = 2 × distance × tan(FOV ÷ 2); pixel density = horizontal pixels ÷ scene width.

IEC 62676-4 detail levels
EditionLevels (lowest to highest)What it supports
IEC 62676-4:2014 (DORI)Detect → Observe → Recognise → IdentifyDetect: someone is present · Observe: how many people and distinguishing details such as clothing · Recognise: whether a person has been seen before · Identify: the person is identified
IEC 62676-4:2025 (OODPCVS)Overview → Outline → Discern → Perceive → Characterize → Validate → ScrutinizeCharacterize: telling a person apart by type, gait and behaviour · Validate: confirming the identity of a known person · Scrutinize: establishing identity with high certainty

The pixels per metre each level requires are in the standard itself and are not reproduced here: write the level the target needs into the specification. The 2025 revision replaces the four DORI levels with seven. The levels of the two editions are not equivalents and cannot be matched row by row: Characterize does not mean what Identify meant under DORI, since at Characterize a person is told apart by type, gait and behaviour, while confirming the identity of a known person is Validate and establishing identity with high certainty is Scrutinize, as summarised in Axis’s white paper on the 2025 edition. Our reading: the closest 2025 levels to the old DORI “identify” are Validate and Scrutinize. The calculator reports the density your lens and distance actually give you.

The calculator names no level and carries no ready-made threshold: it computes the px/m the camera really delivers at the target distance. Type the px/m your specification or your own standard asks for into the “Required px/m” field and the result says whether it is met, and up to what distance this lens still meets it. Reading the threshold from the standard is up to you or to whoever writes the specification; we do not reproduce its values.

The practical consequence: a 4 MP camera on a 12 mm lens covering a till at 3 m beats an 8 MP camera on a 2.8 mm lens covering the whole shop floor, for the one job that matters in a dispute. Wide lenses buy coverage and spend pixels; narrow lenses do the opposite. A site may need both, on separate cameras, rather than a compromise on every camera.

PoE budget and cabling

PoE classes and what they carry
StandardPower at the portGuaranteed at the cameraTypical use
802.3af (PoE)15.4 W12.95 WFixed dome or bullet, IR included
802.3at (PoE+)30 W25.5 WPTZ, heater, long-range IR
802.3bt Type 360 W51 WHeated PTZ, multi-sensor housings

The gap between the two power columns is cable loss, and it is why the port figure is always higher. Size the switch on the port side and check the camera datasheet on the device side.

Three cabling rules decide whether the installation works on the day: the 100 m limit on a copper run is the total from switch port to camera including patch leads, not just the horizontal cable; solid copper conductors are required, and copper-clad-aluminium sold as “CCA network cable” will not carry PoE reliably over distance; and the switch’s total power budget must exceed the sum of maximum camera draws, not the sum of typical ones. A 24-port switch with a 185 W budget is too tight for 24 cameras drawing 6.5 W each at night: the sum is 156 W, and with a 20–25% margin the budget needs 187–195 W.

How long to keep footage

Retention is a policy decision with a legal edge, and the legal edge differs by country: some jurisdictions set a maximum, some set a minimum for particular premises, and data-protection law may require that the period be justified and documented. Because the answer is jurisdiction-specific, this calculator does not assume one — you enter the number of days your own policy or regulator requires and it sizes the storage for that.

What is universal is the arithmetic: retention scales storage linearly. Doubling from 30 to 60 days doubles the drive count, the drive cost and the rebuild time when a drive fails. If you need long retention on a few cameras and short retention on the rest, set the periods per camera group in the NVR rather than applying the longest one to everything.

What to send us for a quote

Send the calculator output plus three things and the quote comes back complete: the number of cameras by type (fixed dome, bullet, PTZ, multi-sensor), the longest cable run on site, and whether the recorder sits in a rack with existing UPS. We quote cameras, recorder, drives, PoE switch, cable and installation consumables as one line-by-line list, on one invoice, delivered to the site.

Frequently Asked Questions

How many TB do 16 cameras need for 30 days?

At 4 MP, H.265, 15 fps, recording continuously, roughly 14 TB raw or 16.4 TB with a 15% margin — three 8 TB surveillance drives. Change any one of codec, frame rate or scene activity and the answer moves noticeably, which is why the calculator asks for all of them.

How much does H.265 reduce storage?

At the same picture H.265 aims for a lower bit rate than H.264; the gap varies with the camera, settings and scene — measure it on your own footage. In the example table and the calculator H.265 = H.264 ÷ 2 is assumed — an assumption, not a measurement. The calculator uses a different example bit rate for each codec; the real gap on your cameras may be smaller or larger, so plan one drive of headroom if you are at the limit. The trade is decoding load — verify that your recorder, and any client machine that will play back several streams at once, supports H.265 in hardware.

Why does my 8 TB drive show as 7.3 TB?

Because the label is decimal (8 × 10¹² bytes) and the operating system reports binary units (TiB, 2⁴⁰ bytes). Nothing is missing; the two scales differ by about 9%. Size against the label in decimal TB, as this calculator does, and expect the recorder to display about 9% less.

Can I use ordinary desktop drives in an NVR?

They will work and then fail early. Surveillance-rated drives are specified for continuous sequential writing, for several drives vibrating in one chassis, and with firmware that gives up on a bad sector quickly instead of stalling the recording. The price difference is small against the cost of rebuilding an array.

How much PoE headroom should the switch have?

Size it on maximum camera draw, then add 20–25%. Maximum is the figure with IR illumination at full output, which is exactly when you need the system to stay up. A switch that browns out at 3 a.m. records nothing at 3 a.m.

Do you supply the whole system or only the cameras?

The whole list — cameras, recorder, surveillance drives, PoE switch, cable, connectors, cabinet and the small items that hold up an installation. One quote, one invoice, delivered to site. Send the calculator result and the site details and it comes back within one business day.

Send your list — your quote is ready within 1 business day.

A list, a photo or an Excel file — whatever is easiest. On standard items we aim to quote the same business day. Custom production, imports or 50+ line lists can take longer; when they do, we tell you the timeline in writing on the day we receive the request.