How Much Bandwidth Smart Thermostats, Cameras, and Speakers Actually Use

August 15, 2026 · Fiber internet for real communities

CC0, via Wikimedia Commons

Most smart home devices use almost nothing. A smart thermostat or speaker typically uses **under 50 MB a day**, which is a rounding error on any modern connection. The exception is cameras, especially ones that record continuously or stream in high definition. A single always-on camera can use more bandwidth than every other smart device in your house combined.

The camera math people miss: it's upload, not download

Homeowners plan their network around download speed because that's the number on the bill. Cameras flip that. Every clip, every livestream, every cloud backup goes out from your house, not in. That means camera bandwidth eats your upload bandwidth, which on many connections (especially cable and older DSL) is much smaller than download.

Here are rough, honest ranges. Actual usage depends on resolution, frame rate, compression, and whether the camera records motion clips or streams continuously:

• Smart thermostat: 5 to 50 MB per day. Negligible, even with frequent check-ins from an app.
• Smart speaker (voice assistant, no music streaming): 10 to 100 MB per day, mostly small bursts during a query.
• Smart speaker streaming music or a podcast for hours: closer to 40 to 150 MB per hour, similar to any audio streaming device.
• Motion-triggered camera (clips only, standard security cam use): roughly 1 to 10 GB per month per camera.
• Continuous recording HD camera (1080p, uploading 24/7): 30 to 100+ GB per month per camera, sometimes more at higher resolutions.
• 4K continuous recording camera: can push past 200 GB per month per camera.

Multiply that last category by three or four cameras around a house, and you can see how a household that felt fine on paper starts choking during a video call or a livestream, especially on the upload side.

What actually happens when it goes wrong

The usual failure isn't total bandwidth running out. It's upload contention at a bad moment. A doorbell camera starts uploading a clip right as someone starts a video call for work. A security system backs up overnight footage while a kid is gaming. Individually these devices are small. Together, at the same second, they compete for a narrow upload pipe and everything gets choppy.

Municipal and community broadband planners run into a version of this at scale. A neighborhood full of smart cameras and doorbells, each modest on its own, adds up to steady upload demand that older network designs never accounted for. Networks built around "most people mostly download" assumptions get strained by neighborhoods full of connected cameras, even before anyone's watching Netflix.

What to actually do

Start by checking your upload speed, not just download. Most speed test tools show both.

• Set cameras to motion-triggered clips instead of continuous recording if you don't need 24/7 footage. This alone can cut camera bandwidth by 80 to 90 percent.
• Lower camera resolution or frame rate for cameras watching low-activity areas like a side yard or storage shed.
• Use your router's Quality of Service (QoS) settings, if it has them, to prioritize video calls and work traffic over camera uploads.
• Wire cameras to ethernet where you can. It won't reduce bandwidth use, but it takes camera traffic off the Wi-Fi so it doesn't compete with laptops and phones for airtime.
• If you're adding four or more cameras, budget for real upload capacity, not just a fast download number.

Fiber connections like the ones GigSpeed builds typically offer symmetrical upload and download speeds, which matters more here than most marketing explains. A smart home with several cameras is an upload-heavy household, and that's the number worth checking before you assume your connection can handle it.

Related: How many devices your home Wi-Fi can realistically support before speeds start to suffer.