Camera bandwidth planning

How much internet upload speed do security cameras need?

Count the cameras that can upload at the same time, test speed where they are installed and leave headroom for calls, backups and the rest of the household.

Upload speed is the number that matters

Cloud cameras send video out of the property, so a fast download headline can hide a weak upload connection. Manufacturers commonly quote requirements per active camera: current examples include roughly 2 Mbps per many 1080p/2K devices, around 3 Mbps for some 4K lines and materially more for newer high-bitrate 4K products.

Planning upload = sum of all cameras likely to transmit simultaneously × 1.5 headroom, then add the household’s normal peak upload use.

Do not use a single speed test beside the router. Test beside every wireless camera at busy times, then trigger multiple cameras together. Internet capacity, Wi-Fi signal and device-to-router transmit speed are different bottlenecks.

Worked examples

System	Camera allowance	Calculation	Planning target
One 1080p doorbell	2 Mbps	2 × 1.5	At least 3 Mbps spare upload
Doorbell + two 2K cameras	2 + 2 + 2 Mbps	6 × 1.5	At least 9 Mbps spare upload
Four mixed cameras	2 + 2 + 3 + 4 Mbps	11 × 1.5	At least 16.5 Mbps spare upload
Two high-bitrate 4K cameras	15 + 15 Mbps if specified	30 × 1.5	At least 45 Mbps spare upload

These are planning examples, not universal product requirements. Use the current specification for each exact model, resolution, codec and recording mode.

Why real use differs from the box

Resolution

Pixels are only one factor

4K normally needs more bandwidth than 1080p, but frame rate, compression, scene detail, HDR and manufacturer bitrate settings can matter just as much.

Activity

Several cameras can trigger together

A person walking around the property may activate the doorbell, driveway and side camera in seconds. Plan for realistic concurrency, not one camera at a time.

Remote view

Live viewing adds traffic

Opening clear live streams while event clips upload can increase demand. Sub-streams reduce bandwidth but may not preserve identification detail.

Other users

Video calls and cloud backup compete

Work calls, gaming streams, phone photo backup and off-site NAS sync all consume upload. Test when the household is busiest.

Cloud, local and hybrid designs

Cloud-first cameras

Simple remote access, but clips and live views depend heavily on broadband and vendor services. Include subscription, bandwidth and outage behaviour in the buying decision.

Local NVR or hub

Cameras record across the local network, so routine recording does not need internet upload. Remote viewing, notifications and off-site backup still use the connection.

On-camera storage

microSD or internal storage reduces continuous cloud traffic, but a thief may remove the evidence. Pair important cameras with protected NVR or selective off-site clips.

Hybrid recording

Local full-quality footage plus cloud event clips can reduce upload while retaining off-site evidence. Confirm what happens if the internet fails during an event.

Test in this order

1. Internet upload

Use several tests across ordinary and busy periods. Record median and worst results—not merely the highest result.

2. Camera-location Wi-Fi

Test at the mounting position with doors closed and the camera installed. Exterior walls, foil insulation, metal and distance can destroy throughput.

3. Simultaneous events

Trigger every overlapping camera, open live views and make a video call. Check clip delay, missing frames, audio and notification timing.

4. Failure mode

Disconnect broadband. Confirm which devices record locally, which alerts stop and how the household or monitoring provider is informed.

Mobile-data estimate

Data per hour (GB) ≈ bitrate in Mbps × 0.45.
Example: a 3 Mbps live stream uses about 1.35 GB per hour before protocol overhead and other traffic.

Event-only cameras use less than continuous streaming, but busy roads, trees or poor detection zones may create far more uploads than expected. Reolink notes that cellular-camera usage varies with bitrate and activity; exact products can range from a few gigabytes a month under standard use to gigabytes per hour during sustained high-quality live viewing.

Five-country connection checks

Country	Common issue	Planning response
United Kingdom	Older FTTC/ADSL connections may advertise download prominently but have limited upload.	Check guaranteed/typical upload, fibre availability and 4G/5G backup before adding several cloud cameras.
United States	Cable plans can be highly asymmetric and rural availability varies.	Compare upload tier, data caps, equipment fees and outage backup—not download alone.
Canada	Rural distance and mobile/satellite caps can constrain uploads.	Prefer local recording, selective cloud clips and cold-rated outdoor networking equipment.
Australia	NBN technology and property location create large upload differences.	Check the exact access technology, evening performance, mobile backup and data allowance.
Ireland	Urban fibre and rural fixed/mobile connections can differ sharply.	Verify local upload, fair-use/caps and whether a cellular camera roams across the required area.

If upload is too slow

Reduce demand safely

Use local NVR or camera storage
Upload event clips rather than continuous video
Lower frame rate before sacrificing identification detail
Use sub-streams for routine remote viewing

Improve the path

Run Ethernet or PoE to fixed cameras
Add a correctly placed wired access point
Move the router/hub away from interference
Upgrade upload tier or add cellular failover

Bandwidth examples were checked against official Google Nest, Ring, Arlo and Reolink information on 1 September 2026. Requirements vary by model, firmware, settings and network conditions.

Compare outdoor cameras → Add connectivity to five-year cost →