Formula Used
Video Mbps per camera = width × height × FPS × bits per pixel × codec factor × scene factor ÷ 1,000,000.
Stream Mbps per camera = video Mbps per camera + audio Mbps per camera.
Live network Mbps = stream Mbps per camera × camera count × overhead factor.
Recording Mbps = live stream demand × recording factor.
For continuous recording, the factor is 1.
For motion recording, the factor equals motion activity percentage divided by 100.
Storage GB per day = recording Mbps × 3,600 × recording hours ÷ 8 ÷ 1,000.
Final storage TB = raw retention TB × redundancy factor × spare growth factor.
How to Use This Calculator
Enter the camera count, resolution, frame rate, codec, and quality value.
Select a scene type that matches the real camera location.
Choose continuous or motion based recording.
Add audio, overhead, retention, storage margin, and remote viewing details.
Press the calculate button.
The result appears above the form and below the header.
Use the export buttons to save the current result.
Example Data Table
| Cameras |
Resolution |
FPS |
Codec |
Mode |
Estimated Use |
| 8 |
1920 x 1080 |
15 |
H.265 |
Continuous |
Small office or shop |
| 16 |
2560 x 1440 |
20 |
H.264 |
Motion based |
Warehouse with mixed activity |
| 32 |
3840 x 2160 |
15 |
H.265 |
Continuous |
Campus or large facility |
Security Camera Bandwidth Planning
A security camera bandwidth calculator helps plan a stable video system. It estimates how much network capacity cameras need. It also estimates storage for recorded footage. These numbers matter before cameras are installed. They help avoid dropped frames, slow viewing, and weak remote access.
Why Bandwidth Matters
Each camera sends video as data. Higher resolution uses more data. Higher frame rate also increases data. A busy scene can need more bitrate than a quiet hallway. Compression reduces the stream, but each codec behaves differently. H.265 often saves more bandwidth than H.264. MJPEG can use much more bandwidth. Audio also adds a small constant load.
Good planning includes overhead. Switches, routers, wireless bridges, and recorders do not work at perfect efficiency. A safety margin helps when scenes get busy. It also helps when cameras update, reboot, or change quality settings.
Using the Results
Start with the number of cameras. Then enter resolution, frames per second, codec, quality, and scene complexity. Choose continuous recording when every camera records all the time. Choose motion recording when footage is saved only during activity. Enter the expected motion percentage with care. A street camera may record most of the day. A storage room may record very little.
The calculator separates live bandwidth from recording bandwidth. Live bandwidth shows the network load when streams are active. Recording bandwidth shows the amount used for saved video. Daily storage converts recorded megabits into gigabytes. Retention storage multiplies daily storage by the number of days kept.
Practical Tips
Do not size a system at the exact calculated value. Add spare capacity for future cameras. Add more margin for public areas, weather, trees, traffic, or night noise. Test one camera at real settings when possible. Vendor bitrate tables are useful, but real scenes can vary.
For best performance, keep camera traffic on a dedicated network. Use wired links when possible. Check switch port speed and uplink speed. Confirm that the recorder can write the required data rate. A balanced design gives smoother playback, safer retention, and easier expansion. Review remote viewing needs too. Multiple users can double live demand. Mobile apps may use sub streams, but desktop clients may request full quality video during reviews often.
FAQs
1. What is camera bandwidth?
Camera bandwidth is the amount of network data a camera stream uses. It depends on resolution, frame rate, compression, scene detail, audio, and overhead.
2. Does H.265 always use less bandwidth?
H.265 usually needs less bandwidth than H.264 at similar quality. Actual savings depend on the camera, scene movement, lighting, and encoder settings.
3. Why does motion recording reduce storage?
Motion recording saves footage only when activity is detected. This reduces recorded hours, so it can lower daily storage and retention storage.
4. Should I include network overhead?
Yes. Network overhead covers protocol traffic, switching loss, bursts, and system inefficiency. A margin helps keep video stable during busy scenes.
5. What bits per pixel value should I use?
Use a lower value for basic quality and a higher value for sharper evidence footage. Common planning values range from 0.05 to 0.15.
6. Does audio affect storage?
Yes. Audio adds a small constant bitrate per camera. It may be minor for one camera, but it becomes important across many cameras.
7. Is final storage the same as raw storage?
No. Raw storage is the direct recording estimate. Final storage adds redundancy and spare growth margin for safer long term planning.
8. Can this calculator size internet upload speed?
Yes. Enter remote viewers and stream Mbps per viewer. The calculator estimates remote demand and adds an uplink safety margin.