CCTV & cameras
Business Security Camera Bandwidth Planning
Estimate recording and remote-viewing traffic separately so the network design matches the video workflow.
The short answer
Camera bandwidth is not one fixed number. Resolution, codec, frame rate, scene activity, quality settings, multiple streams and viewing patterns all matter. Calculate local recording traffic separately from internet upload and remote playback.
What deserves a closer look
Follow the path of each stream
A local camera-to-recorder stream may never cross the internet, while cloud recording usually does. Remote live viewing and evidence exports can create separate bursts. Drawing those paths prevents overbuying internet service or underbuilding a switch uplink.
Many systems use a high-quality stream for recording and a lower-quality stream for thumbnails or mobile viewing. Confirm which stream each feature consumes.
Protect business traffic
Video should be segmented and managed with appropriate switching, security and quality-of-service decisions. The goal is not to give cameras priority over critical business systems, but to prevent uncontrolled contention.
Test packet loss, latency and recovery, not just an internet speed-test headline. Upload capacity and provider data policies are especially important for cloud services.
What changes the quote
- Use representative measured bitrates for busy and quiet periods.
- Map traffic paths from cameras to recorders, viewers and cloud services.
- Reserve capacity for failover, exports and business applications.
Options compared
| Approach | Where it fits | What to scrutinize |
|---|---|---|
| Local recording | Keeping continuous video on the site | LAN uplinks and remote viewing |
| Cloud recording | Off-site administration and storage | Sustained upload and outages |
| Event upload | Reducing wide-area traffic | Missed events and local buffer behavior |
Practical review notes
Draw arrows for the video rather than writing one bandwidth total. Camera-to-recorder traffic, cloud upload, mobile viewing and evidence export may cross different links. That sketch often reveals that an expensive internet upgrade was assumed for traffic that never leaves the building—or that a small uplink carries far more than expected.
Ask IT to review the plan before the quote is final, then preserve the agreed switch ports, addressing, segmentation and traffic assumptions. A last-minute network conversation can turn a sound camera design into an avoidable change order.
A planning example
Illustration, not a price prediction.
Add the expected bitrate of cameras that share each network link, then apply a documented engineering allowance. Do not multiply a camera's maximum bitrate by count and call it an internet requirement when recording remains local.
Questions worth putting in writing
- Which streams cross each LAN, internet and wide-area link during normal use?
- What peak viewing, export and failover activity was allowed for?
- How will the team measure actual traffic and revisit the design after launch?
Common questions
Do I use download or upload speed for cloud cameras?
Camera video leaving the site primarily consumes upload capacity; viewing and software traffic can use both directions.
Can variable bitrate be budgeted reliably?
Yes, with representative measurements and a prudent peak allowance rather than a single marketing value.
Should cameras share the office network?
They may share physical infrastructure, but segmentation, capacity and security should be deliberately designed.