Affiliate Disclosure
Some links on this page are affiliate links. As an Amazon Associate, we earn from qualifying purchases — at no extra cost to you. We do not buy, install, or physically handle the cameras we cover; our rankings come from aggregated owner reviews, ratings and expert consensus. Commissions never change our verdicts. How we rank · full disclosure.
The short answer: a single motion-triggered cloud camera typically uses somewhere between 10 and 60 GB of data a month depending on resolution, and needs roughly 1 to 6 Mbps of upload while it is actively streaming a clip. Set the same camera to record continuously and the figure jumps into the hundreds of gigabytes. The number that governs everything here is your upload speed — cameras send data out of your house, the direction most US plans are worst at.
Two things make published figures vary so wildly. First, whether the camera records only on motion events or continuously — a difference of ten to twenty times. Second, how busy the view is: a quiet side yard may produce a handful of clips a day where a sidewalk at default sensitivity produces hundreds. Two identical cameras in one house can differ by an order of magnitude for that reason alone.
Recommended Cameras
Best for wired outdoor coverage with the deepest review base tracked on this site.
Best for front-door coverage with no wiring required.
Best for a no-subscription camera with local microSD recording.
Rough Data Use by Resolution
These are working ranges for motion-triggered recording at typical residential volumes — call it 20 to 60 clips a day of 20 to 30 seconds. Treat them as planning figures, not specifications; real usage depends on the encoder, the bitrate setting and how much moves in frame.
- 1080p, event recording: roughly 10–25 GB per month. Active bitrate around 1–2 Mbps.
- 2K / 4MP, event recording: roughly 20–45 GB per month. Active bitrate around 2–4 Mbps.
- 4K, event recording: roughly 45–100 GB per month. Active bitrate around 4–8 Mbps.
- Continuous 24/7 recording: multiply by ten or more. A single 2K camera in continuous mode can pass 400 GB a month; 4K can exceed 1 TB.
Add live viewing on top. Watching a stream pulls video down from the cloud or the camera, and long sessions — a feed left running on a tablet all day — are a common cause of an unexpected spike.
Two things cut these numbers materially. H.265 encoding produces 30 to 50 percent smaller files than H.264 at the same quality. And cameras recording to a local card or NVR, uploading only thumbnails or on-demand clips, use a fraction of these figures — why local storage is often the right answer on a slow connection. See NVR camera systems.
Upload Speed and WiFi: Where the Real Constraints Are
Home internet in the US is asymmetric. A cable plan advertised at 300 Mbps down commonly provides 10 to 20 Mbps up; DSL can be under 5 Mbps up. If you have symmetric fiber, this section stops mattering.
When motion triggers a clip the camera pushes that video to the vendor’s cloud, and several cameras trigger together — one person walking around a house sets off all of them in sequence — so their bitrates add up. Four 2K cameras at 3 Mbps each is 12 Mbps of simultaneous upload, enough to saturate a typical cable plan’s upstream entirely.
Saturation does not look like a camera failing loudly. It looks like clips arriving minutes late, live view that buffers or refuses to load, cameras showing offline for stretches, and video calls going bad exactly when someone walks up the driveway. Many one-star reviews describing a "broken" camera are describing an upload bottleneck.
Practical guidance: allow about 2 Mbps of upload headroom per 1080p camera, 4 Mbps per 2K and 8 Mbps per 4K, and do not plan to use more than two-thirds of your measured upload. If the arithmetic does not work, the options are fewer cameras, lower resolution, tighter activity zones, or local recording with cloud as backup.
What Several Cameras Do to Home WiFi
Most home cameras connect on 2.4GHz, the crowded band — shared with neighbors, microwaves, baby monitors, smart plugs and Bluetooth. It penetrates walls better than 5GHz, which is why cameras use it, but has fewer channels and far less capacity. Six cameras plus two dozen other smart-home devices is a congested radio environment, and the symptom is intermittent dropouts, not clean failure.
Distance compounds it. A camera holding a weak signal at the back fence transmits slowly, occupying airtime every other device waits for — which is why adding a second camera to a weak-signal spot makes both worse.
The fixes, cheapest first: separate your bands so cameras are not competing with laptops, add a mesh node or outdoor access point on the camera side of the house, move the cameras to a dedicated guest or IoT SSID, or take them off WiFi entirely. That last option is the reliable one — a PoE camera carries power and data on one cable and consumes zero wireless capacity, which is why professionals install it. See wired PoE cameras.
Cellular Cameras and Data Plans
Cameras with a built-in LTE or 5G modem exist for places with no internet at all — land, job sites, barns, cabins, remote gates — and they change the math, because data is metered and billed.
Cellular plans come in small monthly allowances — a few hundred megabytes to a few gigabytes, sometimes counted in clips rather than data. Against the ranges above that is a tight budget, so a cellular camera cannot be run the way a WiFi camera is. What makes them work is discipline: event-only recording, 1080p, short clips, narrow zones, person detection rather than any-motion, a local card holding the full-quality copy so only the alert clip travels over cellular, and live view as an occasional check rather than a habit.
Price the plan as part of the camera — over a few years the data subscription commonly exceeds the hardware cost, and some carriers' IoT plans undercut the vendor’s bundled plan for the same SIM. See no-WiFi and cellular cameras.
How to Cut Data Use Without Losing Coverage
Almost all of the available reduction is configuration, and none of it costs anything. Turn off continuous recording unless you need it — usually a ninety percent cut on its own. Draw activity zones that exclude the sidewalk, the street and the neighbor’s driveway. Switch on person or vehicle detection so wind, shadows and cats stop uploading. Shorten the maximum clip length and lengthen the retrigger cooldown. Where the app allows it, drop the recording bitrate a notch — the visual difference is small and the data difference is not. And if the camera takes a microSD card or feeds an NVR, record full quality locally and treat the cloud as off-site backup rather than the primary store.
Choosing between those storage paths is its own question, and resolution feeds directly into it — see what resolution do I need, and buying guides for the full purchase sequence.