Two networks, two completely different problems
A camera system sits on two networks at once and they fail in opposite ways. Inside the house, cameras send full-quality streams to a recorder over cable or wireless, and the numbers are small relative to what the hardware can do. Eight cameras at 4 Mbps each is 32 Mbps, plus sub streams, converging on a gigabit link — around three or four percent of it. Local switching is almost never the constraint, and when the local side does fail it is usually wireless cameras on a congested band rather than the switch.
Outside the house is a different story. Watching from anywhere else means the video leaves through your upload, and household upload is not household download. A connection advertised at 300 down might carry 10 or 20 up, sometimes less on older cable and DSL plans. Two people opening a four-camera grid on the main stream is 32 Mbps of upload demand against a 10 Mbps pipe. It does not slow down gracefully; it stalls, freezes tiles, and takes the video call in the next room down with it.
The sub stream is the whole trick
Nearly every IP camera sends two streams at once. The main stream is the high-resolution one that goes to the recorder and to storage. The sub stream is a small, low-resolution version of the same picture, often a twentieth of the bitrate, intended for exactly this: live grid views and phone viewing where a postage-stamp tile does not need four megapixels.
An app configured properly pulls the sub stream for the grid and switches to the main stream only when you tap one camera full screen. An app configured badly, or a camera with no sub stream enabled, pulls main streams for every tile, and the difference is a factor of eight or more on the same view. If remote viewing is unreliable, this is the first thing to check and it usually costs nothing to fix.
| What you are doing | Upload used | Notes |
|---|---|---|
| Watching at home on the LAN | None | Traffic never leaves the local network |
| One camera full screen, sub stream | Under 1 Mbps | Fine on almost any connection |
| Eight-camera grid, sub streams | A few Mbps | Workable on a typical upload |
| Eight-camera grid, main streams | Tens of Mbps | Beyond most household upstream |
| Continuous cloud recording | Full bitrate, all day | A permanent load, not an occasional one |
Cloud recording changes the shape of the load
Local recording is bursty on the upload — nothing goes out until somebody watches. Cloud recording is the opposite. A service that stores everything off-site is uploading whenever the cameras are running, which turns an occasional demand into a permanent one and puts it in direct competition with everything else in the house, forever.
Clip-based services sit between the two, uploading only around detected events, which is why the calculator asks for a duty percentage rather than assuming. The pattern that works well on a constrained connection is local continuous recording for the full record, with short clips pushed off-site around events so that a copy survives if the recorder itself is stolen. That covers the failure that local recording cannot: a thief taking the box the footage is on.
Wireless cameras, and the part that is not about bandwidth
Bandwidth is rarely what breaks a wireless camera. A single 1080p stream is a small load for any modern wireless network. What breaks it is signal quality at the camera, which is usually mounted outside, through a wall, at the far corner of the property, and often on the crowded 2.4 GHz band because that is what reaches. A weak link does not fail cleanly. It retries, and retransmissions consume airtime that every other device on that band has to wait for, so one struggling camera in a far corner degrades the whole network rather than only itself. Cameras carrying continuous video are the devices most worth putting on cable, and if a cable is going out to them anyway, it can carry their power too, which the PoE power budget calculator sizes. The bitrates on this page come out of the resolution decisions in the pixel density calculator and land on the drives in the camera storage and retention calculator, and if you are already short of upstream on this connection the streaming bitrate calculator covers the same ceiling from the broadcasting side.
The security of the system is a network question
A camera system is a set of internet-connected computers with microphones and lenses inside your home, and it deserves to be treated that way. The route by which household footage most commonly ends up in strangers hands is not sophisticated: a recorder with its factory password still set, reachable from the internet because somebody forwarded a port to make the app work from outside. Public search engines index those. Changing default credentials on every camera and the recorder, keeping firmware current, and reaching the system through the manufacturer outbound service or a VPN rather than an open port removes most of the exposure. Putting the cameras on their own network segment removes more. None of that is difficult work, and the reason to do it is plain enough: this is the one part of a house where a configuration mistake gets watched by strangers rather than noticed by nobody.
Questions people ask
How much internet speed do security cameras need?
On the local network, very little relative to what the hardware can do — eight cameras at 4 Mbps each is around 32 Mbps against a gigabit link. The figure that actually constrains you is upload, and only when video leaves the property. Watching at home uses none of it. Watching remotely on sub streams needs a few Mbps for a full grid. Watching remotely on main streams needs tens of Mbps and exceeds most household upstream. Continuous cloud recording needs the full bitrate of every camera, permanently. Work out which of those you are actually doing before worrying about the speed.
Why does remote viewing buffer when my internet is fast?
Because the advertised speed is the download and the cameras are using the upload, which on most residential plans is a small fraction of it. A 300 Mbps connection with 10 Mbps up will show a fast speed test and still stall on a four-camera grid, because sending video out is an upstream job. The two fixes are configuring the app to pull sub streams for grid views rather than main streams, which typically cuts the demand by a factor of eight, and opening fewer cameras at once. If neither is enough, the full grid becomes a home-network view and remote viewing becomes one camera at a time.
What is the difference between the main stream and the sub stream?
They are two simultaneous encodings of the same picture. The main stream is full resolution at full bitrate and is what gets recorded. The sub stream is a much smaller version, often a twentieth of the data, intended for live viewing where the picture is being displayed as a small tile anyway. Recording uses the main stream because that is the copy you may need to examine later. Live grids should use the sub stream because nothing is gained by sending four megapixels to a tile a couple of hundred pixels wide. Most problems with remote viewing come down to something pulling main streams where sub streams would do.
Do wired cameras use less bandwidth than wireless ones?
They produce the same stream — the bitrate is set by the camera, not by how it connects. What differs is reliability and the effect on everything else. A wireless camera with a weak signal retries constantly, and those retransmissions occupy airtime that every other device on the same band has to wait for, so one bad camera in a far corner degrades the whole wireless network rather than just itself. A wired camera has its own dedicated link and cannot do that. For anything sending continuous video, cable is worth the trouble, and the cable that carries the data can carry the power as well.
Is it safe to open a port so I can view cameras from outside?
Forwarding a port to a recorder is the arrangement that most often ends with strangers watching household cameras, and it is worth being blunt about it. Exposed recorders get found automatically, at scale, and the ones still running factory credentials get logged into. Firmware on this class of device is often old and patched slowly. The safer routes are the manufacturer remote-access service, which works over an outbound connection with no inbound port open, or a VPN into your home network so that viewing from outside behaves exactly like viewing from the sofa. Whichever you use, change every default password and keep the firmware current.