Sizing UniFi Protect Storage and Retention (2026 Guide)

Quick summary

Retention is a business decision, not a guess. We capture risk requirements, calculate storage using real scene data, and document the configuration so compliance teams, homeowners, and insurers know exactly what footage exists.

We cover stakeholder interviews, recorder selection, bitrate math, camera tuning, and documentation so audits are straightforward months or years down the line.

• UniFi Protect installation services

Scene bitrate sampling (how to measure)

Pick representative cameras (busy entry, driveway at night, quiet interior). Record average and peak bitrates for each recording mode you plan to use (Always, Detection Only) and at different times of day. This captures real behavior instead of guessing.

Multiply bitrate × hours × days per camera group. Add 20–30% headroom for firmware changes and seasonal variation. Document every assumption next to the spreadsheet.

If you do not have the system installed yet, ask your installer for sample bitrates from similar projects. Use conservative estimates for night scenes, which typically spike due to IR noise and moving headlights.

UNVR sizing examples

Redundancy and power

• UPS for UNVR and PoE switches sized for 15–30 minutes
• RAID strategy with spare on-site; label bays and drives
• Config backups and export SOP stored with the rack

Retention policy examples (by use case)

Retention math example (quick estimate)

Example: 12 cameras average 4 Mbps during business hours and 2 Mbps overnight. That is roughly 3 Mbps average per camera across 24 hours. 12 cameras × 3 Mbps ≈ 36 Mbps total. Over 30 days that can land near 12–15 TB depending on motion settings and codec efficiency.

Use this for initial budgeting, then validate with 24-hour traffic analysis in the Protect dashboard before you buy drives.

If the number feels high, reduce frame rates on coverage cameras before changing retention targets.

Drive selection and replacement plan

Use surveillance-grade drives sized for continuous writes. Create a replacement schedule (for example, every 3–4 years) and keep at least one spare on-site. Label each bay with install dates and record serial numbers in your documentation.

If your retention target is tight, avoid mixing very old and new drives in the same array. A predictable refresh cycle prevents surprises and keeps rebuilds from disrupting footage.

When possible, buy drives from the same batch so performance and wear are consistent across the array.

Export SOP (so you can retrieve evidence fast)

Create a one‑pager: who can export, how to filter by time/camera/event, naming convention, and where files live. Practice the export on a known test clip so anyone can do it under pressure.

If you have multiple sites, standardize export names (site-door-date) so files can be found quickly.

FAQs

Continuous or motion?

Motion saves space, but use continuous on high-value ID views so events are never missed. Mix per camera role.

Do I need LPR cameras?

Dedicated LPR helps on fast roads. For homes and small sites, a correctly placed apron view often suffices.

Clarify retention requirements first

List regulatory mandates, insurance expectations, and practical needs such as slip-and-fall investigations, delivery disputes, or access-control audits. Prioritize cameras where extended retention matters and note which can age off sooner.

Interview stakeholders—owners, safety officers, property managers—so everyone agrees on retention goals before money is spent on storage.

• Security policy checklist

Choose the right recorder platform

Smaller homes often succeed with an UNVR running four drives in RAID 5. RAID 10 is an option on 4-bay arrays, but it halves usable capacity, so use it only when redundancy trumps retention.

Larger estates, campuses, or multi-tenant buildings may require multiple recorders. Whichever path you choose, plan for redundant power, clean rack airflow, and service access.

Bandwidth and motion settings

Retention is tied to both bitrate and detection strategy. In 2026, Smart Detection (person, vehicle, animal) should be the primary filter; motion-only zones catch shadows and trees that burn storage. Use Smart Detection zones for critical areas and keep motion zones tight for coverage views.

If you need 24/7 on ID views, keep them continuous. For coverage views, switch to Detection Only to stretch retention without losing event clips.

Use privacy masks for areas you do not need to record; it reduces storage and improves trust with occupants.

AI-driven retention (G6 / AI series)

Protect AI recording retention now hinges on Smart Detections. G6 and AI series cameras add on-device AI detections (person, vehicle, animal), giving you higher-quality event filtering than motion alone.

Pair Smart Detection zones with Detection Only recording when you want event-only retention, and keep at least one ID view continuous for full context.

Codec and resolution tuning

Use high resolution for identification views and lower resolution for wide coverage where detail is less critical. If a camera supports efficient codecs, compare H.264 vs H.265 (where available) and verify bitrate changes in the Protect dashboard.

If your cameras expose Smart Codec or variable bitrate controls, test static scenes because it can materially reduce storage during quiet hours.

Avoid maxing out every camera just because the hardware can handle it. The best retention plans balance clarity and cost across the whole system.

• ID views: higher resolution, higher frame rate
• Coverage views: moderate resolution, lower frame rate
• Night scenes: watch for bitrate spikes and adjust IR

Calculate retention with real numbers

Record bit rates from representative scenes at different times of day. Note whether cameras record on Smart Detection (Detection Only) or continuously, and build a spreadsheet that multiplies bitrate × hours × days for each camera group.

Round up storage requirements by at least 20 percent to account for firmware changes, additional cameras, or temporary recording spikes. Document every assumption in the calculation so future reviews are transparent.

Tune camera quality per location

Adjust frame rates and resolutions based on use case. Loading docks may need 30 fps for fast-moving forklifts, while storage rooms can live at 15 fps. Keep full resolution for identification views such as entry vestibules or reception desks.

When comparing G6 vs G5 bandwidth, sample real bitrates in Protect (especially at night) before you size storage.

Note these decisions in your documentation so auditors know why certain cameras retain longer or record at different qualities.

Document and audit regularly

Store a snapshot of the UniFi Protect settings, drive health reports, and retention calculations with your security SOP. Schedule quarterly reviews to confirm footage still meets policy.

A five-minute monthly check of drive health and free space prevents silent retention loss.

Keep the latest worksheet export with date and initials for accountability.

• Book a storage and retention audit

Best practices (2026)

• Budget for drive refresh cycles and keep at least one spare on-site so failures do not cut retention
• Align drive purchases with fiscal quarters to avoid long delays when a drive fails
• Keep receipts, warranty dates, and serial numbers with your security documentation

Multi-site and mixed recorder strategy

If you manage multiple buildings, standardize your retention targets by site and keep a shared template for calculations. For large estates or campuses, it can be better to split cameras across multiple UNVRs so a single hardware failure does not take down the entire archive.

Use UniFi Vantage Point to manage multiple NVRs in one interface, and check the current UniFi UNVR stacking limit and constraints if you plan to stack recorders.

Document which doors and cameras live on each recorder so support teams can find footage quickly.