Retention of security camera footage matters. Whether it's evidence for an insurance claim, material for a police investigation, or proof for regulatory compliance, having the correct retention period can make or break an outcome. Most systems retain footage for 7 to 90 days; the exact retention time depends on storage type, camera settings, and legal or industry rules. Let's take a look at typical retention windows, where footage is stored, what affects retention, practical storage examples, and how to extend your archive.
Retention periods for security camera footage
Typical retention ranges are as follows:
- Home/small property: 7–30 days
- Small/medium business: 30–90 days
- High‑security/regulated sites (banks): 6–12 months or more (depending on policy or law)
- Healthcare: 30–90 days (depending on jurisdiction)
- Retail/hospitality: 30–90 days
- Law enforcement/government: 180 days–18 months (depending on policy)
Why does retention vary? Most systems use loop (overwrite) recording: when storage is full, the oldest footage is erased to make room for new recordings. Retention is affected by recording mode (continuous vs motion), resolution, bitrate/frame rate, number of cameras, compression codec, and any legal or internal retention requirements. Retention should also be driven by the estimated time-to-detect incidents relevant to the site (e.g., warehouse archive depth > product turnover time; a cafe's kitchen camera should cover product shelf life + 14 days).
Where is security camera footage stored?
Cloud storage
- Footage uploaded to remote servers; retention set by subscription (standard tiers: 7, 14, 30, 60, 90 days; premium/custom tiers for longer). Pros: true off‑site backup and continued access even if the device is lost; remote viewing is also possible with local NVRs or SD cards but depends on the network/configuration. Cons: ongoing fees and upload bandwidth required.
NVR/DVR (on‑site)
- NVRs (IP cameras) and DVRs (analog) store video on local HDDs. Retention depends on drive size, number of drives/bays, recording settings, and codecs. Local storage is cost‑effective and fast to access; it doesn’t rely on the internet.
SD card (edge)
- Onboard SD is cheap and straightforward but capacity‑limited — typically days to a few weeks depending on settings and motion. SD cards are overwritten when full.
Hybrid (local + cloud)
- Keep recent footage on local HDDs/NVRs for full‑capacity archives and fast access; use the cloud as a complementary backup for recent or flagged clips (shorter retention due to cost). Hybrid setups let you store the bulk archive locally (cost‑efficient, one‑time HDD purchase) while keeping a smaller cloud copy for off‑site redundancy and quick remote access.

Use the Video storage calculator to estimate exactly how much space your setup needs: enter camera count, resolution or bitrate, codec (H.264/H.265), frame rate, and recording mode (continuous or motion). The tool returns required storage (GB/TB), expected retention days, and recommended NVR/HDD or cloud sizing so you can compare local, cloud, and hybrid options.
Factors that affect CCTV storage capacity
Several technical and operational choices determine how much video your system stores and for how long:
- Resolution (measured in megapixels): 4K (≈ 8 MP) vs 1080p (≈2 MP) dramatically increases file size.
- Bitrate: primary determinant of file size; higher bitrate = bigger files.
- Codec/compression: H.265 (HEVC) typically saves ≈30–50% of storage space vs H.264 at similar quality.
- A 30 fps frame rate generally requires more data than 15 fps; the exact increase depends on codec, bitrate, and scene complexity.
- Number of cameras: storage needs scale with camera count.
- Recording mode: continuous recording consumes far more space than motion‑triggered recording.
- Retention period & overwrite policy: longer retention periods require more storage and a more robust strategy.
Storage calculation (simple baseline)
Storage (GB) ≈ bitrate (Mbps) × 0.45 × 24 × days × cameras
Notes: Bitrate in Mbps (megabits per second). The 0.45 factor converts Mbps → GB/hour.
- For motion recording, multiply by the duty cycle fraction (e.g., 25% → × 0.25).
- Bitrate — not megapixels — drives file size: two 8 MP cameras can have very different bitrates depending on codec, scene complexity, and settings.
Storage calculator examples with Ajax hardware (consistent units)
Example A — motion‑focused home setup
- Cameras: 2 × Ajax Superior BulletCam HLVF (8 Mp), H.265, average bitrate 2 Mbps each; duty cycle 25%.
- Per camera: 2 Mbps × 0.45 × 24 ≈ 21.6 GB/day. Two cameras continuous = 43.2 GB/day. With 25% duty → 43.2 × 0.25 = 10.8 GB/day.
- Storage: 2 TB (≈2,000 GB) → 2,000 / 10.8 ≈ 185 days retained.
Example B — 24/7 multi‑camera business setup
- Cameras: 4 × BulletCam HL (8 Mp/2.8 mm), H.265, average bitrate 8 Mbps each; continuous recording.
- Per camera: 8 Mbps × 0.45 × 24 ≈ 86.4 GB/day. Four cameras = 345.6 GB/day.
- Storage: Ajax Superior NVR H2DAI8PAC (8-ch) with two 6 TB drives (≈12,000 GB total) → 12,000 / 345.6 ≈ 34 days retained.
Both examples use 8 MP sensors, but the bitrates differ (2 Mbps vs 8 Mbps). Bitrate choices (codec, scene, motion, and quality settings) cause the storage difference. Use Video storage calculator with your actual average Mbps to get precise results.
Extend your security camera footage retention
- Prefer motion/AI detection: record only relevant events and tune sensitivity to reduce false triggers.
- Use H.265 compression: it reduces storage needs substantially compared to H.264.
- Lower resolution/frame rate where ultra‑detail isn't required.
- Expand local storage: add larger HDDs and pick a RAID that fits your needs: RAID 1 — for mirroring, RAID 5/6 — for capacity + redundancy; always keep external backups.
- Hybrid archiving: keep recent footage locally; offload older/flagged clips to cloud.
- Export and archive evidence immediately to an external HDD/cloud storage to prevent overwriting.
- Automate backups and retention policies to ensure preservation of key footage.
Quick checklist
- Run the video storage calculator for your exact setup.
- Use H.265‑capable cameras and NVRs.
- Enable AI/motion detection and tune it.
- Choose NVRs with hot‑swappable HDDs (e.g., Ajax Superior NVR H2DAI8PAC (8-ch)) for easy capacity upgrades.
- Define retention policy and export critical clips.
Recommended Ajax hardware for longer footage retention
For longer retention, consider these Ajax hardware options for clearer footage and scalable local storage:
- Ajax Superior BulletCam HLVF (8 Mp) — high resolution, 2.8–12 mm motorized varifocal P‑Iris lens, hybrid illumination, True WDR, built‑in microphone/speaker, audio & alarm I/O, PoE/12 V. Ideal for targeted framing, evidence capture, and reliable PoE operation.
- BulletCam HL (8 Mp/2.8 mm) — wide 110° viewing angle, hybrid illumination, True WDR, microphone, PoE/12 V. Good for continuous area coverage with fewer cameras.
- Ajax Superior NVR H2DAI8PAC (8-ch) — 8‑channel AI‑powered NVR with 4K HDMI output, Gigabit Ethernet interface, eight PoE ports, and support for two hot‑swappable HDDs. Tip: don't size a recorder to the exact current camera count — buy extra channels (e.g., a 16‑ch unit for an 8‑camera system) and leave HDD headroom so you can add cameras or increase retention without replacing the recorder.
Pairing suggestions
- Best continuous 24/7 system: BulletCam HL (8 Mp/2.8 mm) + Ajax Superior NVR H2DAI8PAC (8-ch) with two large HDDs (e.g., 2 × 6 TB or 2 × 8 TB). It is better to use surveillance‑grade drives or NAS‑rated HDDs — they're built for 24/7 operation, high rewrite workloads, vibration tolerance, and longer warranty/support than desktop drives.
- Best storage‑efficient system: Ajax Superior BulletCam HLVF (8 Mp) + Ajax Superior NVR H2DAI8PAC (8-ch) with AI/motion detection enabled to reduce duty cycle.
Explore Ajax video surveillance products to match your storage and retention plan. Compare specs, recommended pairings, and expandable storage options to pick the right system for your needs.
FAQ
Do home security cameras delete footage?
Yes. Most systems use loop recording and overwrite the oldest files when storage is full unless you archive or export clips. That's why choosing the right disk/storage capacity (and NVR HDD sizing or cloud tier) is essential to meet your retention goals.
How far back can a security camera go?
From 24 hours to months or years, depending on storage capacity, resolution, bitrate, frame rate, camera count, and recording mode.
Do security cameras keep all footage?
No. Retention is limited by storage and settings; important clips must be exported or archived to avoid deletion.
Can deleted footage be recovered?
Overwritten footage is usually unrecoverable — whether local or cloud. Backups and separate long‑term archives (off‑site HDDs or dedicated cloud retention tiers) are the only reliable way to ensure recovery if the primary store is overwritten.
How can I check retention on my camera?
Open the camera/NVR app or software to view storage settings and available capacity, consult the manual, or run your config in the video storage calculator.
Can I extend retention without replacing cameras?
Yes. Upgrade NVR/HDD capacity: use hot‑swappable bays where near‑zero downtime is critical, or rely on planned short reboots and cold‑spare drives for typical installations; and/or add a cloud plan, enable motion/AI detection, or adjust resolution/bitrate.
Protecting your surveillance footage
Start by picking a retention target that fits your risk, budget, and any legal rules. Then, let that goal drive your camera settings and storage choices. Use efficient codecs (e.g., H.265), reasonable resolutions and frame rates, and smart recording (motion/AI) to cut unnecessary footage. Choose NVRs with hot‑swappable HDDs or a hybrid local+cloud approach to grow capacity and archive important clips. Document a clear retention policy, automate backups/exports for critical events, enable health alerts and scheduled integrity tests, and perform brief quarterly verification to ensure archives are recoverable without constant manual oversight. Do this, and your video archive will be leaner, more reliable, and ready when you need it.
Roman Konchakivskiy
Head of Ajax Academy











