redzilla
All tools
CCTV

CCTV Project

Sum the bandwidth (Mbps) and storage (TB) of a project with several cameras of different profiles, to size the NVR and the uplink. Add a row per group of cameras. These are estimates using a typical VBR bitrate. 100% in your browser.

Camera profiles

Each row is a group of identical cameras. Set the count, resolution, FPS, codec, activity, recording hours per day and retention days.

redzilla.cl — cctv-project
 
Total storage
Bandwidth (uplink)
recording from all cameras
Cameras in project
TB
Mbps
Cameras

Per-profile breakdown

Profile Cams Bitrate/cam Row Mbps Row TB
How it is calculated · bitrate, storage and uplink

1. Base bitrate (Mbps) at H.264 / 15 fps / medium activity: 1MP=2, 2MP=4, 4MP=8, 5MP=10, 8MP=16.

2. Per row: bitrate/cam = base × (fps/15) × codec × activity. Codec: H.264=1.0, H.265=0.5, H.265+=0.35. Activity: low=0.6, medium=1.0, high=1.4.

3. GB/cam/day = bitrate(Mbps) × 3600 × hours / 8 / 1000 · row TB = GB/cam/day × cameras × retention / 1000 · row Mbps = bitrate/cam × cameras.

4. Project totals = sum of all rows: total TB (NVR capacity) and total Mbps (required uplink).

5. These are estimates: real bitrate is VBR and depends on the scene, lighting, manufacturer and encoder settings. Size with headroom.

Runs locally in your browser · no sign-up · nothing leaves your browser.

How it works

The planner totals the bandwidth and storage of a complete CCTV project working with profiles: each row groups identical cameras with their quantity, resolution (1 to 8 MP), FPS, codec, activity level, recording hours per day and retention days. Per row it applies the same bitrate model as the storage calculator: bitrate/cam = base × (fps/15) × codec × activity, with H.264 = 1.0, H.265 = 0.5 and H.265+ = 0.35.

From each profile bitrate it derives the row Mbps (bitrate × cameras) and the row TB (GB/cam/day × cameras × retention / 1000), then sums everything into the two numbers that size the project: the NVR capacity in TB and the required uplink in Mbps. These are VBR estimates: real bitrate depends on the scene and the encoder, so leave headroom.

Example: a project with entrances, perimeter and parking lot

  1. Entrances: 4 × 4 MP H.265+ at 15 fps → 8 × 0.35 = 2.8 Mbps per camera: 11.2 Mbps and 3.6 TB over 30 days.
  2. Perimeter: 8 × 2 MP H.265 at 12 fps, high activity → 4 × 0.8 × 0.5 × 1.4 = 2.24 Mbps: 17.9 Mbps and 5.8 TB over 30 days.
  3. Parking: 2 × 8 MP H.265 at 20 fps → 16 × 1.33 × 0.5 ≈ 10.7 Mbps: 21.3 Mbps and 3.5 TB over 15 days.
  4. Totals: 14 cameras, ≈50 Mbps of uplink and ≈12.9 TB → an NVR with 2 × 8 TB drives and a Gigabit port has plenty of margin.

Frequently asked questions

How much bandwidth does a 16-camera system need?
With 1080p cameras on H.265 at 15 fps (about 2 Mbps each) the recording stream is around 32 Mbps; with 4 MP it rises to about 64 Mbps. A Gigabit LAN handles that easily; the critical point is the uplink when the NVR records remote cameras or is viewed from outside.
Why split cameras into profiles instead of averaging?
Because in a real project cameras are not identical: an entrance needs more resolution for identification, a perimeter tolerates fewer FPS but has more night-time activity, and a parking lot may need 4K with shorter retention. Calculating each group separately avoids undersizing the demanding groups and oversizing the rest.
How do I size the NVR drives from the result?
Take the total TB and add 20–30 % margin for VBR bitrate peaks and system-reserved space. For an estimated ~13 TB, plan around 16 usable TB (for example 2 × 8 TB surveillance drives). If you use RAID 1 or RAID 5, count the usable capacity after redundancy.
Is my project data stored on any server?
No. Profiles are computed entirely in your browser and never sent to a server; reloading the page restores the example values. Use the copy button to take the summary into your quotation or design document.
Was this tool useful?
Disclaimer We take great care to keep every tool accurate and review it thoroughly; even so, we can't guarantee it is free of errors or take responsibility for how the results are used. We recommend double-checking anything critical.
Found an error? Let us know →