Storage
How Long Do Security Cameras Keep Footage?
Translate your disk capacity into an estimated retention window.
Read guideStorage
Estimate security-camera disk space from bitrate, camera count, recording hours and retention days instead of guessing from resolution alone.
For a continuously recorded stream:
Storage (GB) ≈ bitrate (Mbps) × 10.8 × cameras × days.
The constant comes from converting megabits per second into bytes over 86,400 seconds in a day. It is a planning approximation using decimal gigabytes.
Example: four cameras averaging 4 Mbps for 30 days:
4 × 10.8 × 4 × 30 ≈ 5,184 GB, or about 5.2 TB of video before adding safety margin and filesystem/other usage.
| Average bitrate | Per day | 7 days | 30 days |
|---|---|---|---|
| 1 Mbps | 10.8 GB | 75.6 GB | 324 GB |
| 2 Mbps | 21.6 GB | 151.2 GB | 648 GB |
| 4 Mbps | 43.2 GB | 302.4 GB | 1.30 TB |
| 8 Mbps | 86.4 GB | 604.8 GB | 2.59 TB |
| 12 Mbps | 129.6 GB | 907.2 GB | 3.89 TB |
These values are for one camera recording all day at the stated average bitrate. Variable-bitrate cameras can rise sharply in busy or noisy scenes, so size storage from measured behavior when possible.
A 4K camera does not consume one fixed number of gigabytes. Two 4K cameras can use very different bitrates because of:
Use the bitrate reported/configured by the camera or measure the actual recording files. Resolution is important for image detail, but bitrate is the direct storage input.
At an average 4 Mbps per camera, four continuous cameras use about 172.8 GB/day. Approximate video storage would be:
A nominal 6 TB drive may therefore be a reasonable starting capacity for that simplified 30-day example, but do not treat nominal capacity as fully usable. Leave room for formatting, system files, bitrate variation and operational headroom.
At the same 4 Mbps average, eight continuous cameras use about 345.6 GB/day:
This is why camera count and retention should be planned together. Doubling the camera count approximately doubles storage use when everything else stays equal.
If recording is event-triggered, multiply the continuous estimate by the approximate recording duty cycle. A camera that records 20% of the time may use around 20% of the continuous space at the same bitrate.
But do not assume a duty cycle before testing. A view with moving trees, street traffic, insects at night or poor motion tuning can record for most of the day. Measure several normal days before buying storage for a long retention target.
If you record 12 hours per day instead of 24, the time-based portion of the estimate is roughly halved. For a small office that only needs after-hours coverage, scheduling can reduce storage without lowering image quality.
Schedules also make retention more predictable than motion-only recording in scenes where activity varies widely.
For evidence, the main stream normally provides the useful detail. A substream is often designed for low-bandwidth live viewing and may have lower resolution, frame rate or bitrate. Recording only the substream saves space but can reduce the detail available when you zoom into an incident later.
A common design is to record the main stream locally and use a lower-bitrate stream for remote live view.
Do not plan to consume every advertised gigabyte. The recording drive needs operational headroom, and Windows needs free space for updates, logs and temporary files. If recordings share the system drive, be even more conservative.
For an important multi-camera installation, consider a dedicated recording drive so normal Windows/app activity does not compete with surveillance files.
This real measurement automatically captures the effect of your actual codecs, motion activity and camera settings, so it is more reliable than a generic “1080p needs X GB” chart.
Security Eye is video surveillance software for Windows with IP camera and webcam monitoring, recording, motion detection, scheduling, notifications, and remote web access.