Security Camera Bitrate & Bandwidth Chart
Bitrate is how much data a camera produces per second — it drives both the network load and how much storage you burn. Higher resolution, higher frame rate, and the older H.264 codec all raise it. Use this chart to plan your NVR throughput and network. Figures are typical per-camera bitrates; your camera’s settings may vary.
| Resolution | 15 fps | 30 fps | 8 cameras @ 30 fps |
|---|---|---|---|
| 2MP (1080p) | 2 Mbps | 3.2 Mbps | ~26 Mbps |
| 4MP | 4 Mbps | 6.4 Mbps | ~51 Mbps |
| 5MP | 5 Mbps | 8 Mbps | ~64 Mbps |
| 8MP (4K) | 8 Mbps | 12.8 Mbps | ~102 Mbps |
| Resolution | 15 fps | 30 fps | 8 cameras @ 30 fps |
|---|---|---|---|
| 2MP (1080p) | 4 Mbps | 6.4 Mbps | ~51 Mbps |
| 4MP | 8 Mbps | 12.8 Mbps | ~102 Mbps |
| 5MP | 10 Mbps | 16 Mbps | ~128 Mbps |
| 8MP (4K) | 16 Mbps | 25.6 Mbps | ~205 Mbps |
A standard gigabit (1000 Mbps) network and NVR handle even eight 4K cameras comfortably — the more common limit is the NVR’s rated incoming bandwidth (often 80–320 Mbps on home models), so check that spec before maxing out resolution and frame rate. Switching cameras from H.264 to H.265 roughly halves both bandwidth and storage with no visible quality loss — the single biggest efficiency win if your gear supports it.
Source: Guard Source HQ — guardsourcehq.com/camera-bitrate-bandwidth. Free to cite with attribution and a link back.
How to Use This Chart
Read the chart by finding your camera’s resolution down the left column, then the frame rate across the top; the cell is the typical bitrate for one camera. The right-hand column shows the combined load of eight cameras so you can size a whole system at a glance. Use the H.265 table if your cameras and NVR support the modern codec (most made in the last few years do) and the H.264 table if they don’t.
The bitrate you land on is what you’ll plan two things around: your NVR’s rated incoming bandwidth (often 80–320 Mbps on home recorders) and your network. Multiply the per-camera figure by your camera count and keep the total comfortably under the NVR’s cap. For storage, feed the same numbers into the NVR Storage Calculator, and for a high-motion scene, size up — a busy view runs above these typical figures.
When This Tool Is Most Useful
This chart is most useful when you’re:
- Choosing resolution and frame rate for a new system without overloading the NVR
- Checking whether your NVR’s incoming-bandwidth cap can handle the cameras you want
- Deciding whether to switch cameras from H.264 to H.265
- Planning remote viewing over a limited home upload connection
- Diagnosing lag, dropped frames, or an NVR that can’t keep up
Worked Example
Say a homeowner runs eight 4MP cameras and wants smooth, clear footage. Walk it through the chart:
- H.264 at 30 fps: 4MP is 12.8 Mbps per camera — about 102 Mbps for all eight. Fine for a gigabit network, but already brushing the incoming-bandwidth cap of many home NVRs (often 120–160 Mbps), and it fills a hard drive fast.
- Switch to H.265: the same 4MP/30 fps drops to 6.4 Mbps each — about 51 Mbps total. That one change roughly halves both bandwidth and storage with no visible quality loss.
- Drop 30 fps to 15 fps: it halves again to about 26 Mbps for all eight. For most surveillance, 15 fps looks perfectly smooth, so this is nearly free.
Bitrate touches four things at once, which is why it’s the setting worth getting right:
- Image quality — more bitrate means less compression and cleaner detail on fast motion, but only up to a point; past the camera’s efficient range, extra bits don’t visibly improve a clear scene.
- Storage — bitrate maps almost directly to drive space. Double the bitrate, double the terabytes for the same retention.
- Network bandwidth — every stream shares the NVR’s incoming cap and your LAN; overshoot and you get dropped frames or a recorder that can’t keep up.
- Remote viewing — watching away from home is limited by your internet upload speed (often just 10–35 Mbps at home). A full-bitrate 4K stream can exceed that and stutter, which is why apps use a lower-bitrate substream for remote view while the NVR still records the high-bitrate main stream.
So the instinct to crank bitrate for “better quality” usually backfires: you pay in storage and bandwidth, risk overloading the NVR and your upload, and often see no real improvement. The better levers are H.265 (halves the data for free), 15 fps where you don’t need to read fast-moving plates, and letting the camera use variable bitrate so it spends data only when the scene is busy. Save the high bitrate for the one or two cameras that truly need it — a gate or driveway watching for license plates.
Common Mistakes
- Leaving cameras on H.264. If both the camera and NVR support H.265, staying on H.264 doubles your bandwidth and storage for nothing. Switch and reclaim it.
- Recording everything at 30 fps. 15 fps is smooth for surveillance and halves the load; reserve 30 fps for a plate-catching camera.
- Ignoring the NVR’s incoming-bandwidth cap. It’s a separate, smaller limit than your gigabit network — check the spec (often 80–320 Mbps) before maxing resolution.
- Assuming higher bitrate always means better footage. Past the efficient range it just costs storage; scene, lens, and lighting matter more.
- Forgetting upload for remote viewing. Great local footage can still stutter on your phone if your upload is thin — use the substream for remote view.
Accuracy & Assumptions
The chart lists typical per-camera bitrates for average scenes. Your real numbers move with:
- Scene motion and complexity — a busy street or wind-blown foliage runs well above these figures; a quiet room runs below
- Variable vs constant bitrate — most cameras use VBR and only hit the listed rate during activity
- Camera and codec tuning — manufacturers implement H.264/H.265 differently, and “smart” codecs (H.265+) cut idle bitrate further
- Night and IR — low light and infrared can raise bitrate as the sensor adds noise the codec has to encode
- Audio and overlays — enabling audio or timestamps adds a little on top
Treat the chart as planning figures, size up for busy scenes, and confirm against your NVR’s live bandwidth readout once the cameras are running.
Next Steps
Turn these bitrates into a drive size with the NVR Storage Calculator, or scan the NVR Storage Size Chart for a quick read. Sizing the whole system? Match coverage with the Camera FOV & Coverage Calculator and power with the PoE Budget Calculator. For the reasoning behind the storage math, read how much NVR storage you need.
Related Resources
Related calculators & charts
- NVR Storage Calculator — turn a bitrate into a hard-drive size
- NVR Storage Size Chart — drive sizes at a glance by camera count and resolution
- Camera FOV & Coverage Calculator — match resolution to the area you need to cover
Related guides
- How Much NVR Storage Do You Need? — the full sizing walkthrough
- How to Choose an NVR — pick a recorder with enough bandwidth and drive bays
Browse all free security camera & NVR tools.
Frequently Asked Questions
How much bandwidth does a 4K security camera use?
A 4K (8MP) camera typically runs somewhere around 8 to 16 Mbps on H.264, or roughly half that on H.265, depending on frame rate and scene complexity. Busy scenes with lots of motion push toward the high end. Use the chart above to match your exact resolution and codec.
What is the difference between H.264 and H.265?
H.265, also called HEVC, is the newer codec and compresses video far more efficiently, about half the bitrate of H.264 for the same visual quality. That means less bandwidth and less storage, at the cost of slightly more processing power. Most modern NVRs and cameras support it, and it is the better choice when both ends are compatible.
Does a higher frame rate use more bandwidth?
Yes. Doubling the frame rate, for example 15 fps to 30 fps, increases the data the camera produces and therefore its bandwidth and storage needs. For most surveillance, 15 fps is plenty smooth, so dropping from 30 fps can roughly halve usage without meaningfully hurting the footage.
How much bandwidth do 8 security cameras use?
On H.265 at 30 fps, eight 4MP cameras total about 51 Mbps and eight 4K cameras about 102 Mbps; on H.264 those roughly double. A gigabit network handles it easily, but check your NVR rated incoming bandwidth, often 80 to 320 Mbps on home models, since that is the real limit.
Does a higher bitrate mean better video quality?
Only up to a point. More bitrate reduces compression and helps with fast motion, but past a camera efficient range the extra data does not visibly improve the image while still costing storage and bandwidth. Scene lighting, lens, and resolution usually matter more than pushing bitrate higher.
Why do my cameras lag or stutter when I view them remotely?
Remote viewing is limited by your internet upload speed, often just 10 to 35 Mbps at home, so a full-bitrate 4K stream can exceed it and stutter. Most apps offer a lower-bitrate substream for remote viewing while the NVR keeps recording the high-quality main stream locally.
What bitrate should I use for a security camera?
Start with the typical figures in the chart for your resolution and frame rate on H.265, then adjust for the scene. A quiet indoor camera can run lower, while a driveway watching for license plates may need a higher bitrate and 30 fps. Use variable bitrate so the camera spends data only when something is happening.
About Guard Source HQ — Guard Source HQ is built on 30 years in the construction trades — real-world experience installing equipment, keeping systems running, and protecting them from the elements. Every guide here follows the same rule: practical, field-tested advice on security cameras and the networks behind them, without the scare tactics or the hard sell.
Guard Source HQ exists to give homeowners practical, experience-based troubleshooting and clear educational resources — tools and guides that help you plan, install, and maintain your own security setup with confidence, and make an informed decision before you buy.
July 2026
- Added a worked read-through of the chart
- Added guidance on quality, storage, bandwidth, and remote-viewing trade-offs
- Added chart assumptions
- Expanded the FAQ
Last updated: July 2026
