Security Camera Bandwidth Requirements

Security camera bandwidth requirements tell you how much video a system can move at the same time. A warehouse can have plenty of hard-drive space and still drop live views if the switch, the recorder, or the internet upload cannot carry the streams. Local recording and remote viewing are two different loads. The first stays on the property. The second leaves the building.
Bitrate is the practical unit. It is the video a camera sends each second, usually shown in megabits per second (Mbps). Add the streams that actually run together, then leave room above that total. A quoted internet plan is not that total. Most commercial security camera systems record on the local network even when the internet is down.
Request a free security assessment
Call 773-733-0970 to review your camera network load
What Security Camera Bandwidth Requirements Measure
Bandwidth here means simultaneous video, not how many days the recorder can keep. Days of video belong in a storage plan. The network question is simpler: which streams are moving right now, and through which piece of equipment?
A camera usually creates two streams:
- Main stream. This is the higher-quality stream the recorder stores and the one a manager uses when a face, a plate, or a package label matters.
- Substream. This is a smaller stream for phone grids, guard monitors, and quick checks. It is often the stream that leaves the building.
Those streams do not always travel the same path. On a typical business PoE camera setup, the main stream goes from the camera to a switch and then to the recorder. Remote viewing adds a second path from the recorder, or from a cloud service, out through the internet. Counting only one of those paths is how a design looks fine on paper and stalls on opening day.
Resolution, frames per second, compression, and scene motion set the bitrate. A quiet hallway can sit near the low end. A dock with constant forklift traffic sits near the high end, even at the same resolution. H.265 is commonly more efficient than H.264. It does not erase the need to add the streams up.
Published ranges are planning bands, not a quote. One installer guide puts 1080p around 2 to 5 Mbps per camera and 4K around 15 to 20 Mbps, before you multiply by camera count. Use the camera maker’s calculator for the final number. Hikvision’s bitrate guidance tells installers to enter resolution, frame rate, scene complexity, and codec into its network and storage calculator rather than guess a single bitrate.
How to Estimate the Load on the Building Network
Start with the main streams. Those are what the recorder must accept while the building is open. Use one worksheet row per camera group, not one row per camera model. Read each row as its own case.
| Camera group. | Main stream. | Substream. | What to multiply. |
|---|---|---|---|
| Entrances and cash wraps. | Higher bitrate, often continuous. | Small grid view. | Camera count times main-stream bitrate. |
| Offices and back halls. | Lower bitrate or motion-based. | Rarely viewed live. | Peak cameras that record at once. |
| Docks, yards, and sales lots. | Busy scenes, higher bitrate. | Used by remote managers. | Main stream on site, plus viewers off site. |
| Phone and guard monitors. | Not the stored stream. | One stream per tile. | Tiles on screen times substream bitrate. |
The arithmetic is ordinary. Ten 1080p cameras at 4 Mbps need about 40 Mbps of recorder intake if they all send the main stream at once. The same ten cameras at a 1 Mbps substream need about 10 Mbps if someone opens every tile remotely. A 16-camera view is a different number from a single-camera playback.
Three devices can each be the limit:
- The switch uplink. Camera ports can be fine while the single link back to the recorder is full. A 1-gigabit uplink has a hard ceiling, and other building traffic shares it if cameras are not separated.
- The recorder’s incoming bitrate. An NVR publishes a maximum incoming throughput. Older Hikvision guidance for one 32-channel model put the ceiling at 80 Mbps and recommended staying near 74 Mbps so remote viewing still had room. Your recorder’s sheet will differ. Read that number before you add cameras.
- The viewing station. A wall monitor that decodes 16 main streams needs more than a phone that opens one substream. The network is not the only bottleneck.
Leave headroom. Thirty percent is a reasonable planning cushion for a busier season, a firmware change, or two extra cameras. If the math already fills the recorder or the uplink, lower the frame rate on low-risk scenes before you buy a larger internet plan. The internet plan does not carry local recording.
Which recorder family you use is a separate choice. NVR and DVR system choices decide how the cameras connect. This estimate starts after that choice and asks only what those cameras put on the network.
When the Internet Plan Matters, and When It Does Not
Local recording does not use your upload speed. The cameras and the recorder are on the same side of the router. A site can keep recording through an internet outage. People off site cannot watch that live view until the connection returns.
Upload speed matters in three cases:
- An owner or manager watches live video away from the building.
- Selected cameras send a continuous or event stream to a cloud service.
- A second site pulls playback across the connection instead of copying a clip first.
A 300 Mbps internet plan is usually a download number. Camera viewing the other way uses upload. One remote viewer on a substream may be fine on a modest upload. Eight full-quality main streams are not. Ask the provider for the upload figure, then compare it with the substreams you expect to open at once, not with the whole camera count.
Cloud review changes the math again. If every camera uploads full time, the upload must cover those main streams. If the cloud only receives events or bookmarks, the everyday load is much smaller. Cloud video surveillance systems cover when a hosted platform is the right product. Use this page to decide which streams are allowed to leave.
Wi-Fi adds a further limit that a speed test will not show. Interference, distance, and other devices share the same air. A wired camera path is the predictable choice for a fixed commercial view. Cameras that record without Wi-Fi stay on the local recorder when the wireless network is busy or down.
How to Keep Quality Without Flooding the Network
You rarely need every camera at maximum settings. Match the stream to the job, then check the total again.
- Set resolution where detail pays off. Use a higher resolution at entrances, transaction counters, and plates. A back hallway can stay at 1080p. 1080p versus 4K resolution is a detail decision, and it is also a bitrate decision.
- Drop frames on calm scenes. Fifteen frames per second is enough for many overview cameras. Save 30 frames for fast motion you may need to identify.
- Use the efficient codec the recorder supports. Turn on H.265 only when every viewer and the recorder can decode it. A camera set to a codec the phone app cannot open will look like a bandwidth failure.
- Send the small stream to phones. Keep the main stream for recording and for single-camera investigation. A four-tile phone view should use substreams.
- Record on motion where the scene allows it. Continuous recording is still right for docks and cash wraps. Motion recording cuts traffic only while the scene is actually quiet.
- Separate camera traffic from checkout and guest Wi-Fi. A dedicated switch, or a dedicated VLAN, keeps a busy register from competing with video. Cable category and PoE power are part of that build, and they are covered in the PoE guide rather than here.
After the changes, add the rows again. If the recorder intake is still above its published limit, you need fewer main streams or a recorder with a higher incoming rating. A larger hard drive will not fix that. Drive size answers how long video lasts, which is the job of commercial camera storage options.
What to Check Before You Approve a Camera Quote
Ask for the bitrate worksheet before you approve camera counts. A quote that lists 16 cameras and a recorder model, with no per-stream bitrate, has not answered the network question.
Five checks cover most Chicago-area plants, dealerships, and retail floors.
- Each camera group has a main-stream bitrate and a substream bitrate, taken from the maker’s calculator or a measured test, not from a single blog average.
- The sum of the main streams, plus headroom, fits the recorder’s incoming throughput.
- The switch path from the cameras to the recorder is shown, including the uplink, and camera traffic is not assumed to share a full checkout network.
- The internet upload is compared only with remote and cloud streams. Local recording is not charged against that upload.
- The viewing habit is named: one phone, a guard watching nine tiles, or a manager pulling four sites at once. Each habit is a different load.
InVision Systems designs that load as part of the camera system, not as an add-on after the cameras are on the wall. A site survey checks scene activity, the switch closet, and the real upload speed together. Retention rules, evidence holds, and who may export a clip stay in security footage retention planning. They do not change the live bitrate.
A Worked Example for a Mixed Commercial Site
Numbers make the split easier to see. Take a mid-size dealership or light industrial site in the Chicago area. It has 20 cameras, one recorder in the office closet, and a manager who checks the lot from a phone after hours. Nothing here is a bid. It is the worksheet a buyer can ask the installer to fill in.
Group the cameras before you multiply:
- Eight overview cameras on the lot and the dock, 4 Mbps each on the main stream, recorded all day because the scene keeps moving.
- Eight interior cameras on the showroom, the parts counter, and the shop floor, 3 Mbps each.
- Four quiet cameras in offices and a back hall, 2 Mbps each, with motion recording after hours.
The local total is about 68 Mbps before headroom: 32 plus 24 plus 8. Add about 30 percent and the recorder should accept roughly 90 Mbps of incoming video. A recorder rated at 80 Mbps incoming is already short, even if its hard drives could store a month. That is a recorder-throughput problem, not a disk-size problem.
The internet number is smaller if remote viewing uses substreams. Suppose the manager opens four lot cameras at once at 0.75 Mbps each. That is about 3 Mbps of upload, plus a little for the app itself. A 300 Mbps download plan with a 10 Mbps upload can handle that habit. It cannot handle someone pulling all 20 main streams from home. Write the viewing habit into the quote so the upload is sized for a real person, not for every camera at full quality.
The switch path needs the same honesty. If all 20 cameras home-run to one switch, the link from that switch to the recorder must carry the 68 Mbps. And more when someone plays recorded video at the desk. A gigabit link can do that. A busy office network that also moves large files on the same link is a weaker bet. Put the cameras on their own switch, or their own VLAN, and the video stops competing with the front office.
Busy season changes the lot cameras more than the offices. A Saturday rush does not add cameras, but it adds motion, which pushes variable-bitrate cameras toward the top of their range. If the worksheet used a quiet-night bitrate, rerun it with the busy profile before you buy. The warehouse camera system planning guide covers where to put cameras in a distribution building. This example only covers what those cameras will put on the wire.
Two failures show up after install when this sheet was skipped. Live views freeze at shift change, because that is when the most people open the app. Or the recorder shows a throughput warning while the drives still have free space. Both point back to simultaneous video, not to retention days.
Schedule your free security assessment today
Call 773-733-0970 to schedule your camera assessment
Frequently Asked Questions
Is 100 Mbps enough for security cameras?
It can be enough for local recording of a modest 1080p system. If 100 Mbps is the recorder and switch capacity and the main streams add up to less than that with headroom. It is not automatically enough when the 100 Mbps figure is an internet download speed, or when several people watch full-quality video remotely.
Is 300 Mbps fast enough for security cameras?
Three hundred Mbps of internet download does not tell you the camera load. Local recording depends on the switch and recorder. Remote viewing depends on upload. A 300 Mbps plan can still have a much smaller upload, which is the direction live viewing uses.
How much bandwidth does a 4MP camera require?
There is no single number. A 4MP camera uses more than a typical 1080p camera and less than a maxed 4K camera, and motion, frame rate, and codec move it inside that range. Look up the exact bitrate in the manufacturer’s calculator, then multiply by the number of 4MP cameras recording at once.
Does a security camera use upload or download?
On site, a camera uses the local network between the camera and the recorder, which is neither your internet upload nor your download. Off site, watching that camera uses internet upload at the building and download on the viewer’s connection.
Will a bigger hard drive lower bandwidth use?
No. A larger drive stores more days of video. It does not reduce the live stream. Lower the resolution or the frame rate. Send substreams to remote viewers. Or record on motion where that still meets the job.