Introduction
Upload speed is a critical factor in the performance of cloud‑connected camera systems. Most internet service providers (ISPs) advertise download speed prominently, but provide significantly lower upload speeds. Because cameras primarily upload video to the cloud, limited upload bandwidth can restrict how many cameras can stream simultaneously.
Many ISPs offer asymmetric plans; for example, a plan advertised as 150 Mbps may include 150 Mbps download but only 5 Mbps upload. While this is adequate for general internet use, it can cause issues when deploying multiple cameras. Understanding available upload speed helps determine how many cameras can be supported or whether a higher‑capacity internet plan is required.
Rough Estimation Method
Use the following approximate values to estimate upload requirements based on camera resolution:
720p: ~0.5 Mbps per camera
1080p: ~1 Mbps per camera
4 MP: ~2.5 Mbps per camera
4K: ~3.5 Mbps per camera
Actual bitrate varies by camera model, settings, and scene complexity, but these estimates are sufficient for initial planning.
Calculating the number of cameras when the upload speed is known
If you know your available upload speed, divide it by the bandwidth requirement per camera.
Examples with 10 Mbps upload speed:
10 Mbps / 0.5 Mbps = 20 cameras at 720p
10 Mbps / 2.5 Mbps = 4 cameras at 4 MP
Calculating the required upload speed when the number of cameras is known
If you know how many cameras you need to install, multiply the number of cameras by the estimated bandwidth per camera.
Examples for 5 cameras:
5 × 0.5 Mbps = 2.5 Mbps for 720p
5 × 3.5 Mbps = 17.5 Mbps for 4K
Advanced estimation method
For a more accurate estimate, calculate the total upload bandwidth required when all cameras are streaming simultaneously.
Step 1: Determine the average bitrate per camera
For cameras on a Fixed plan, the average bitrate is shown in the Billing Plan tab of the camera properties.
For cameras on a Pay As You Go plan, use the bitrate configured in the Quality tab.
Step 2: Multiply the average bitrate by 2
This accounts for bandwidth spikes caused by I-frames. Cameras transmit a mix of I-frames and P-frames. I-frames contain full image data and are significantly larger, while P-frames contain only changes between frames and are much smaller.
Typically, one I-frame is sent every two seconds, with the remaining frames being P-frames. Because of this behavior, a camera with an average bitrate of 700 Kbps may briefly consume up to 1.3–1.4 Mbps when sending an I-frame. Doubling the average bitrate accounts for these spikes and prevents buffering and dropped frames.
Step 3: Multiply by the number of cameras
Multiply the doubled bitrate by the number of cameras with the same configuration. If you have multiple groups of cameras with different bitrates, calculate each group separately and then add the results together.
This represents the minimum bandwidth required for stable video streaming. Without accounting for bitrate spikes, frames will queue up, buffers will overflow, and cameras will begin dropping frames or reconnecting frequently.
With very large deployments (20+ cameras), the likelihood of all cameras sending I-frames simultaneously decreases, but the calculation becomes more complex and depends on multiple variables.
Step 4: Add overhead for metadata
In addition to video, Cameras also transmit:
Events
Health checks
Connection metadata
This overhead is small per camera but can add several hundred Kbps across large deployments.
Step 5: Add buffer for other network usage
Most internet connections are shared with other devices and users. Allocate an additional 3–4 Mbps to accommodate non-camera traffic and ensure stable performance.
The total required upload bandwidth is the sum of steps 3, 4, and 5.
Example calculation
A system with 10 cameras:
• 6 cameras at 700 Kbps average bitrate
• 4 cameras at 400 Kbps average bitrate
Total required upload speed:
((700 × 2) × 6 + (400 × 2) × 4) + 4,000 Kbps
= 15,600 Kbps, or approximately 15.5 Mbps
If the connection is dedicated and extremely stable, the system may function with 8–9 Mbps, but operating at the bare minimum increases the risk of:
Frame drops
Buffer overflows
Frequent reconnections
Note on Satellite Internet
Traditional satellite internet (excluding Starlink) often has very high latency—sometimes up to 5 seconds, with typical values around 1.5–2 seconds.
High latency forces cameras to buffer frames while waiting for server responses.
Round‑trip delays of several seconds can cause: