How much security camera storage do you need? Use this practical planning guide to estimate retention for microSD cards, NVR hard drives, NAS systems, and cloud recording before you buy equipment or change recording settings.
Overview
Storage planning is less about choosing the biggest drive and more about matching capacity to how your cameras record. The main variables are camera count, resolution, frame rate, video bitrate, recording mode, retention target, and whether audio is included. A single battery-powered camera recording motion clips has very different requirements from four PoE cameras recording continuously in 4K.
The useful question is not simply “How many gigabytes does a camera use?” It is: How many cameras must preserve how much footage, at what quality, for how many days? Start with the retention period you actually need. Many households may want several days of recent footage, while a small business, rental property, or site with infrequent visits may need a longer window. Your target should also account for the time needed to notice an event, export a clip, and replace a failed storage device.
Storage is normally managed with an overwrite cycle. When the card, NVR drive, or NAS allocation fills, the system deletes the oldest eligible footage to make room for new recordings. Confirm that overwrite is enabled, and do not assume that an advertised capacity equals usable recording space. Formatting, system data, event protection, and reserved capacity can reduce the space available for ordinary footage.
How to estimate security camera storage
The most dependable method is to use the camera or recorder’s stated bitrate. If that information is unavailable, use the following planning formula:
Storage per camera per day in decimal gigabytes = bitrate in Mbps × 10.8
Then apply the rest of the system:
Total storage = cameras × storage per camera per day × retention days × recording factor
The recording factor is 1 for continuous recording. For motion-only recording, it represents the share of the day during which the camera is actually saving video. For example, a planning assumption of 0.25 means the camera records motion for an estimated quarter of the day. This is only an estimate: a busy entrance, active pets, rain, moving foliage, headlights, and poorly adjusted motion zones can raise recording time substantially.
Finally, add a capacity buffer. A practical planning buffer is often 10% to 20% above the calculated result, but the right margin depends on how critical the footage is and how closely you can monitor the system.
| Input | What to record | Why it matters |
|---|---|---|
| Camera count | Number recording to the same destination | Every additional stream adds storage demand |
| Resolution | For example, 1080p, 2K, or 4K | Higher detail commonly requires a higher bitrate |
| Frame rate | Frames per second | More frames can increase bitrate and storage use |
| Bitrate | Constant or average Mbps | The most useful input for a precise estimate |
| Recording mode | Continuous, scheduled, or motion-only | Determines how much of each day is saved |
| Retention | Number of days to preserve | Sets the required recording window |
Inputs and assumptions
Resolution, codec, and bitrate
Resolution alone does not determine storage use. A 4K security camera can use different amounts of space depending on its codec, frame rate, image complexity, and bitrate settings. Newer compression may reduce storage compared with an older codec at similar visual quality, but compatibility matters if you are recording to an NVR, NAS, or third-party application.
Use the manufacturer’s storage calculator or the recorder’s displayed bitrate when possible. If the camera offers a bitrate range, calculate with the higher value for a conservative estimate. Night scenes, foliage, rain, and busy movement can produce more complex video than a quiet indoor scene.
Continuous versus motion-only recording
Continuous recording is easier to calculate and provides a complete timeline, but it requires much more capacity. Motion-only recording saves space, yet it can miss activity outside detection zones or create gaps around an event. Check whether the system records a short period before and after an alert, and whether protected event clips are excluded from automatic deletion.
MicroSD cards
For a local storage security camera, check the exact supported card type and maximum capacity in the current manual or app. Capacity is only one consideration. Cameras that record frequently can write heavily to a card, so choose a card intended for continuous or surveillance use when the manufacturer recommends one. Format the card in the camera if instructed, enable health or error notifications, and test playback before relying on it.
NVR, NAS, and cloud storage
For an NVR hard drive storage requirement, calculate the streams together, then verify the recorder’s supported drive size, bay count, file system, and camera compatibility. A NAS may provide more flexible capacity, but confirm that the cameras support the required protocol or application. RTSP and ONVIF support can help with compatibility, but they do not guarantee that every recording feature will work.
Cloud plans require a different check. Review the number of included cameras, video quality, event retention, continuous recording availability, download limits, and what happens when a subscription ends. Cloud retention is governed by the provider’s plan rather than by a drive you control.
Worked examples
Example 1: One indoor camera using motion recording
Assume one camera averages 2 Mbps, records motion for an estimated 25% of the day, and should retain 14 days. Continuous storage would be 2 × 10.8, or about 21.6 GB per day. Applying the motion factor gives 21.6 × 0.25 = 5.4 GB per day. Over 14 days, the estimate is 75.6 GB. Add a buffer and check the camera’s supported card capacity before choosing a microSD card.
Example 2: Four outdoor cameras recording continuously
Assume four cameras each average 4 Mbps and the target is 14 days. One camera uses about 43.2 GB per day. Four cameras use approximately 172.8 GB per day, or 2,419.2 GB for 14 days. With a 15% planning buffer, the target becomes roughly 2,782 GB before accounting for the recorder’s reserved space and any protected clips. In this scenario, select the next practical NVR capacity above the estimate rather than matching it exactly.
Example 3: Compare a quality change
If changing a camera from a lower setting to a higher setting increases its average bitrate from 2 Mbps to 4 Mbps, the storage estimate for that stream approximately doubles. Recalculate after changing resolution, frame rate, codec, or bitrate rather than relying on the old retention estimate.
A reusable worksheet
For each camera, write down: camera name, bitrate in Mbps, recording factor, retention days, and storage destination. Calculate bitrate × 10.8 × recording factor × retention days. Add the cameras together, then add your buffer. Record the result next to the actual capacity and the system’s overwrite setting. This makes it easier to identify which camera is consuming the most space.
When to recalculate your security camera retention
Revisit your estimate whenever you add or remove a camera, change resolution or frame rate, enable continuous recording, alter motion sensitivity, replace a microSD card or NVR drive, or move cameras to a busier area. Also check after firmware changes because recording options, codecs, or storage limits can change.
At least twice a year, review the current camera manual, recorder specifications, supported card and drive capacities, and cloud retention terms. Product limits and app features can change, and a storage plan that worked during a quiet season may fail when activity increases. Check actual usage in the app or NVR: compare the oldest available footage with your intended retention period, confirm playback at different times of day, and verify that important clips can be exported.
Before finalizing a system, follow this checklist:
- Use the actual or manufacturer-stated bitrate where available.
- Calculate each camera separately before combining totals.
- State whether the estimate assumes continuous or motion-only recording.
- Add capacity for overhead, protected clips, and normal variation.
- Confirm supported microSD, NVR, NAS, or cloud limits.
- Test overwrite behavior and storage-health alerts.
- Recalculate after every major recording-setting or hardware change.
For related planning, see our security camera total cost of ownership guide, and use the smart camera maintenance checklist to include storage checks in your regular maintenance routine.
