CCTV cameras slowing your WiFi? The upload nobody counted
Two WiFi cameras can drag a whole house down because they upload all day. Here is the ten-minute test that proves it and how to cap each camera.
A friend bought two cheap WiFi cameras for the front gate and the back door. The shop said connect them to WiFi, done in five minutes. Two weeks later he was telling me his video calls had started freezing and his wife's phone felt slow in the kitchen. Nothing new was installed except two small white cameras.
Nobody checks upload. Every speed test we run, every plan we compare, talks about download — and cameras use almost none of it. They use the other direction, all day, without ever stopping. That is the part that hurts.
The ten-minute test
You do not need an app with a subscription. You need two numbers and one pause.
- Open your router's app and find the page that lists connected devices with current traffic — usually called Device Management, Traffic, or Client List. Note the upload figure beside each camera.
- Run an upload test from a laptop or phone near the router with the cameras running. Write the number down.
- In the camera app, pause recording or switch the cameras off at the plug for two minutes.
- Run the same upload test again.
If the second number is noticeably higher than the first, the cameras are the cost. If both numbers are the same and low, your slowdown is somewhere else — start with our WiFi troubleshooting order instead of buying anything.
One warning about the router page: many routers report traffic in KB/s while speed tests report Mbps. Eight times out of ten the "tiny" camera figure is not small once you convert it. 250 KB/s is roughly 2 Mbps.
What each camera actually sends
| Camera setup | Upload while idle | Upload while recording | Notes |
|---|---|---|---|
| 1080p, cloud continuous | Almost zero | ~1–2 Mbps, 24 hours | The expensive default |
| 1080p, cloud motion-only | Almost zero | Bursts of 2–4 Mbps | Much cheaper, misses the quiet stuff |
| 1080p, SD card only | Almost zero | Almost zero | No off-site copy |
| 2K or 4K, cloud continuous | Almost zero | ~4–8 Mbps | One camera can fill a small uplink |
| Any camera on Ethernet / PoE | — | Same as above | Still uploads, but stops eating airtime |
The figures are ranges, not guarantees — bitrate depends on the app's setting, the scene, and how much movement there is. What matters is the shape: a camera that uploads continuously costs you every hour of the day, including the hours you are on a call.
How to limit it, cheapest first
- Switch cloud recording to motion-triggered. In almost every camera app this is a toggle, not a purchase. You keep the alerts you actually look at and lose hours of empty corridor footage.
- Drop the mainstream to a lower resolution than the recording stream. Most cameras send a full-quality stream to storage and a smaller one to your phone. If your app has a "sub-stream" or "HD/SD" switcher, the phone view is the one to shrink.
- Cap the camera's bandwidth in the router. Many routers let you set a per-device upload limit. Set it just above what the camera's own app reports and it will keep working, just at a lower quality. This is the cleanest fix because it applies to every device at once.
- Move the camera to 5GHz or to a cable. Only if the camera supports it. This does not reduce upload, it removes the airtime problem below.
- Record locally. An SD card or a small NVR keeps the footage off your uplink entirely. Accept that a camera stolen along with its card takes the recording with it.
The part the story usually leaves out
The upload number is only half of it. Most budget cameras are 2.4GHz only — the band with the longest range and the most neighbours — and they transmit continuously. WiFi is not a pipe where each device gets its own lane; all devices on one band take turns using the same air.
A camera sending a steady 1 Mbps is on the air far more of the time than a phone that downloads in short bursts, because it never stops. So the kitchen tablet gets slower even though the tablet is not talking to the camera at all, and the camera's traffic has nothing to do with the internet at that moment. This is why "but the camera only uses 1 Mbps, my plan is 100" does not settle the argument.
The test for this one: pause the cameras and see whether a device in a far room improves. If it does, the problem is airtime, and the answer is 5GHz, a cable, or fewer cameras on the same band — not more download speed.
When a bigger plan is genuinely the fix
It can be, but only after the numbers agree. If your upload is small, the cameras are eating most of it, and you cannot reduce their bitrate, then the uplink is your ceiling and a plan with more upload is the honest remedy. Compare plans on upload rather than on the big download number they advertise, and check the current figures on each provider's own site — they change, and we do not quote them here.
If instead your upload stays healthy while calls still stutter, stop shopping. You have a WiFi problem wearing a bandwidth costume.
The short version
Count the upload before you blame the line. Cap the cameras, switch cloud to motion-only, and get the 2.4GHz ones off the busiest band. Two cameras should be a security upgrade, not a reason your house feels like it has one bar.