Operations
How Much Bandwidth Do CCTV Cameras Need?
How much bandwidth do CCTV cameras need on your LAN and internet upload? Worked Mbps examples for 1080p and 4K, remote viewing, and cloud clip upload.

TL;DR
Each IP camera loads your network at its stream bitrate whether anyone is watching. Plan about 2 to 4 Mbps per 1080p H.264 camera at 30 fps, 8 to 16 Mbps for 4K, then add only the streams you view remotely to your upload budget.
How much bandwidth do CCTV cameras need? Each camera pushes its stream bitrate onto your network whether or not anyone is watching. For planning, assume about 2 to 4 Mbps per 1080p camera at 15 to 30 fps on H.264, and about 8 to 16 Mbps per 4K camera, then add up every concurrent stream on the LAN and only the streams you view off-site against your internet upload. This guide works the numbers step by step and ties them to the free CCTV Bandwidth Calculator.
What is CCTV bandwidth in practice?
Bandwidth here means megabits per second (Mbps) of video data leaving the camera encoder. Recording on a local NVR keeps most of that traffic inside the building. Remote viewing, mobile apps, and cloud backup send copies out through your upload.
Three budgets matter:
- LAN recording load — all cameras streaming to the NVR simultaneously.
- Remote viewing load — only the cameras someone watches from outside, often on a substream.
- Incident upload load — exporting clips or shift segments for review, legal, or video intelligence indexing.
Confusing storage (gigabytes on disk) with bandwidth (Mbps on the wire) is a common planning mistake. Storage answers how long you keep footage; bandwidth answers whether the switch, uplink, and upload can carry it. Our companion post how much storage CCTV cameras need covers terabytes; this one covers Mbps.
What bitrate should I plan per camera?
Start from the encoder settings on the camera or NVR. If you do not have them yet, use these H.264 planning values aligned with the CCTV Bandwidth Calculator:
| Resolution | Typical fps | H.264 planning bitrate | LAN load if always on |
|---|---|---|---|
| 1080p | 15 | 2 Mbps | 2 Mbps per camera |
| 1080p | 30 | 4 Mbps | 4 Mbps per camera |
| 4K | 15 | 8 Mbps | 8 Mbps per camera |
| 4K | 30 | 12 Mbps (mid-range) | 12 Mbps per camera |
Hikvision’s encoder guidance explains why scene complexity, noise, and codec implementation change bitrate even when resolution and fps stay fixed. Night noise and busy scenes push bitrates up; static hallways run lower.
H.265 (HEVC) usually cuts bitrate about 30 to 50 percent versus H.264 at similar quality. The calculator applies about 40 percent less when you select H.265.
How do I calculate LAN bandwidth for many cameras?
The formula is simple:
Total LAN Mbps = per-camera bitrate × number of cameras recording at once
Worked examples:
| Site | Assumption | Math | Result |
|---|---|---|---|
| Small retail | 8 × 1080p @ 4 Mbps | 8 × 4 | 32 Mbps |
| Warehouse | 24 × 1080p @ 4 Mbps | 24 × 4 | 96 Mbps |
| Campus edge | 48 × 4K @ 12 Mbps | 48 × 12 | 576 Mbps |
Axis network guidance notes that roughly 2 to 3 Mbps per device is typical for high-quality, high frame-rate streams, and recommends a gigabit backbone once you pass about twelve devices. A gigabit switch (1000 Mbps) comfortably carries sixteen 4 Mbps cameras (64 Mbps) with room for NVR management traffic.
Rules of thumb:
- Stay below 70 to 80 percent of rated switch capacity so bursts do not drop frames.
- Put cameras and NVR on a dedicated VLAN when possible so office traffic does not compete.
- If you use PoE switches, remember power budget is separate from bandwidth budget.

How much upload do I need for remote viewing?
Remote viewing sends live streams (or relayed streams) outbound. The viewer’s download speed does not help if the site only has 5 Mbps upload and someone opens four 4 Mbps main streams.
A relay to a cloud service counts the same way: it sends the stream out all the time, even when nobody is watching. Our guide to relaying cameras from an OpenWrt router shows how to send the lighter sub stream instead.
Plan with:
Remote Mbps ≈ sum of bitrates for cameras watched at once × overhead factor
The CCTV Bandwidth Calculator assumes about 80 percent of advertised upload is usable after TCP and protocol overhead.
Example: 50 Mbps advertised upload → ~40 Mbps usable. You could theoretically carry ten 4 Mbps main streams, but in practice two or three full-quality streams plus NVR UI traffic is safer.
Mitigations operators use every day:
- Sub-stream for mobile — many cameras expose a 512 kbps to 1 Mbps stream for phones.
- Viewer limits — restrict concurrent remote sessions on the NVR or VMS.
- VPN plus local agent — some teams remote into a jump box on the LAN instead of pushing every stream over the internet.
If remote viewing is chronically choppy, measure upload during peak viewing before buying more cameras. Bandwidth is often the bottleneck, not the VMS brand.
How long do CCTV clip uploads take for review?
Investigations and AI video search workflows usually move files, not live RTSP. File size still comes from bitrate × duration.
At 4 Mbps:
- One hour ≈ 4 × 0.45 × 1 = 1.8 GB (same rule as storage guides)
- At 40 Mbps usable upload → ~6 minutes per hour-long export
| Clip length | 4 Mbps file size | Upload at 40 Mbps usable |
|---|---|---|
| 15 minutes | ~0.45 GB | ~1.5 minutes |
| 1 hour | ~1.8 GB | ~6 minutes |
| 8-hour shift (one camera) | ~14.4 GB | ~48 minutes |
Uploading an entire day from every camera for cloud review rarely fits consumer or small-business uplinks. Teams instead export incident windows or use on-prem indexing. The video file size calculator converts bitrate and duration when you need exact megabytes for a ticket attachment limit.
How does motion recording change bandwidth?
Motion-only recording lowers storage, not necessarily peak bandwidth. Cameras still encode live; the NVR decides what to retain.
Where motion settings do affect bandwidth:
- Dual-stream policies that drop main stream fps until motion
- Event-based cloud clips that upload short bursts
- Analytics on edge that send metadata instead of full video
For always-on compliance cameras, treat bandwidth as continuous.
How does CCTV bandwidth relate to video search?
Higher bandwidth lets you keep more detail in each frame, but it does not help investigators find a red vest or a licence plate. That is a search and indexing problem.
Typical pattern:
- Narrow time and camera on the VMS (see how to search CCTV footage for a person, vehicle, or event).
- Export a clip sized for your upload budget.
- Index the export in a video intelligence layer if you need natural-language queries across speech and on-screen text.
What is video indexing explains the indexing step. Bandwidth planning gets the clip to the reviewer; indexing gets the moment out of the clip.
Ceptory indexes recorded video you upload or add by URL through the video intelligence API. It does not replace your NVR or reduce camera bitrates. Pricing is metered on indexed minutes and queries — see /pricing. The first 10 minutes of indexing are included free per account.
Compare approaches honestly: VMS bandwidth tools size the network; video intelligence sizes the review bottleneck after export. Our video intelligence platforms vs traditional VMS guide separates the layers.
What should I do before adding cameras or enabling cloud features?
- Read actual bitrates from each camera stream page, not the box label.
- Run the CCTV Bandwidth Calculator with your camera count, resolution, codec, and remote viewer count.
- Run the CCTV Storage Calculator on the same assumptions so disk and wire budgets match.
- Test upload with a 1-hour export during business hours; compare to your calculator result.
- Document sub-stream policy for mobile users so they do not accidentally open sixteen main streams.
- Plan incident exports with the incident report template so reviewers know which clip lengths to pull.
If manual review hours dominate cost more than switch upgrades, estimate labour with the video review cost calculator and read beyond manual video review for the automation case.
Sizing Mbps correctly keeps recordings complete; sizing review workflows keeps investigations fast. When exports are ready to search, explore Ceptory search or start at the Ceptory home page.
How do I stress-test my network before go-live?
A spreadsheet estimate is a start; measurement catches POE reloads, spanning-tree surprises, and upstream caps your ISP never advertised clearly.
- Enable SNMP or switch counters on the camera VLAN during an evening peak shift. Compare port utilisation to your calculator total.
- Record a remote viewing session while someone on-site opens the same camera locally. If both stutter, you may be hitting camera encoder limits, not just WAN upload.
- Export a multi-gigabyte clip and time the upload to your review destination. Match the result against the upload table in this guide.
- Plan failover — if the primary uplink fails, decide whether local recording continues even when cloud features stop. Bandwidth planning should list what degrades gracefully.
Hikvision’s support portal points installers to vendor network and storage calculators when bitrate is unknown. Use those figures as inputs to the Ceptory tools, not as a substitute for reading the stream after install.
When should I upgrade switches or uplinks?
Upgrade triggers that show up in site audits:
| Symptom | Likely cause | Typical fix |
|---|---|---|
| NVR drops cameras nightly | Oversubscribed 100 Mbps edge switch | Move cameras to gigabit edge or reduce main-stream fps |
| Remote view works at 2 a.m. only | Contended upload with backups or VoIP | Schedule cloud jobs off peak or buy symmetric business fiber |
| Motion searches lag | Disk or CPU bound on NVR, not LAN | Separate analytics VLAN; keep recording on local RAID |
Adding cameras without revisiting Mbps is how sites end up with silent frame loss — video that looks fine live but gaps during incidents. Pair bandwidth work with the retention examples in how much storage CCTV cameras need so neither disk nor wire becomes the weak link.
For multisite organisations, standardise on one sub-stream profile for mobile apps. Field teams then know that 1 Mbps sub-stream + two concurrent viewers fits a 10 Mbps upload site without opening a ticket each time.
Frequently asked questions
How much bandwidth does one 1080p CCTV camera use?
At about 30 fps on H.264, many 1080p cameras run near 4 Mbps. At 15 fps or in quiet scenes, 2 Mbps is common. Read the stream bitrate in the camera or NVR settings instead of guessing.
How do I calculate total CCTV bandwidth for 32 cameras?
Multiply the per-camera bitrate by 32 for continuous recording on the LAN. Example: 32 cameras at 4 Mbps need about 128 Mbps on the recording network, which fits a gigabit switch with headroom.
Why does remote CCTV viewing buffer when my internet download is fast?
Remote viewing is limited by the site's upload speed, not the viewer's download. If concurrent streams exceed usable upload, switch viewers to each camera's lower-bitrate sub-stream.
How long does it take to upload an hour of CCTV for review?
At 4 Mbps, one hour is about 1.8 GB. At a usable 50 Mbps upload (after overhead), that is roughly six minutes. Uploading every camera for a full day usually is not practical.
Does H.265 reduce CCTV bandwidth?
Usually yes. H.265 often needs about 30 to 50 percent less bitrate than H.264 at similar quality. The CCTV Bandwidth Calculator assumes about 40 percent less when you pick H.265.
Does higher bandwidth mean I need a video intelligence platform?
Bandwidth and storage determine how much footage you keep, not how fast you find a moment inside it. Ceptory indexes exports or clips you choose so teams search in natural language without streaming every camera to the cloud.
Ceptory
Search your own footage in plain language. The free tier indexes 60 minutes of video.


