UniFi Protect Retention Planning Playbook for Homes and Small Offices

Most retention problems in UniFi Protect systems stem from policy decisions rather than hardware limitations. Organizations typically purchase an NVR, connect cameras, and maintain default settings. Months later, critical footage has already been deleted.

Start with incident timelines, not terabytes

Before calculating storage needs, establish what questions your footage must answer:

1. How far back must critical evidence exist? (7, 14, 30, 90 days)
2. Which zones are legally or operationally sensitive?
3. How long does your team usually take to notice and review incidents?

Different zones require different retention windows. A package room might need 30 days, while a low-risk side yard could function with 7-14 days. Retention targets should vary by location rather than apply uniformly.

Segment cameras into policy tiers

Three policy tiers work well for most deployments:

• Tier A (critical): entrances, cash handling, medicine storage, loading docks
• Tier B (important): hallways, shared spaces, parking lanes
• Tier C (context): perimeter corners, low-risk exterior coverage

Recording modes align with tier importance:

• Tier A: continuous + smart detections
• Tier B: motion-indexed with tuned sensitivity
• Tier C: smart detections only, lower bitrate

This structured approach significantly improves retention effectiveness without hardware replacement.

Sizing formula (quick estimate)

Total daily GB = sum(camera bitrate Mbps × 10.8)

Multiply this by retention days and add 20-30% overhead for traffic spikes and operational buffer. Refine calculations with actual deployment data.

Common mistakes that collapse retention

1) High bitrate everywhere Not all zones require maximum detail continuously. Reserve high bitrate for critical areas.

2) No scene-specific frame rates Different environments need different frame rates. A hallway differs significantly from a point-of-sale counter.

3) No monthly retention audit Storage patterns shift after camera additions or firmware updates. Monthly reviews are essential.

4) No written policy Unexplained retention settings indicate defaults rather than intentional policy.

What to document for reliability

Operational runbooks should include:

• Camera list and tier assignment
• Retention target by tier
• Recording mode by camera
• Expected days on disk (baseline)
• Procedure for exporting and preserving clips

Without documentation, teams repeat investigations and lose system confidence.

Final recommendation

Treat retention as an ongoing operational control rather than a single setup task. Explicit, tiered policies reviewed monthly make UniFi Protect significantly more dependable during actual incidents.

Detailed sizing workflow

After initial estimates, conduct a seven-day observation period under production conditions. Measure per-camera average bitrate, motion density, and peak-hour traffic. Use these metrics to recalculate retention with realistic buffers.

A practical worksheet captures:

• camera ID and zone tier
• target frame rate and resolution
• average and peak bitrate
• recording mode (continuous, motion, smart)
• expected days retained

This foundation supports capacity planning and future expansion decisions.

Zone-specific quality profiles

Cameras should not run identical quality settings. Define distinct profiles:

• Investigative profile: high detail for identification-critical zones
• Operational profile: medium detail for workflow visibility
• Context profile: efficient settings for situational awareness

Assign each camera to a profile and review quarterly.

Alert strategy tied to retention policy

Retention and alerting should reinforce each other. Critical zones warrant both extended retention and higher-priority alert routing. Lower-priority areas can use summary notifications to prevent alert fatigue.

Export and legal readiness

Even without regulatory requirements, evidence handling demands discipline. Standardize export naming, include padding before and after trigger events, and maintain controlled repositories with access documentation.

Capacity forecasting for growth

Before installing additional cameras, estimate storage impact. Model worst-case motion density and maintain headroom to prevent retention collapse after expansion.

Monthly governance review

A lightweight monthly meeting maintains policy health:

• compare expected versus actual retention days
• review top incident retrieval times
• evaluate false positives by zone
• approve tuning changes and document reasoning

Field checklist you can apply this week

Execute a one-week stabilization sprint for immediate progress:

Day one: Verify inventory accuracy—list every gateway, switch, AP, camera, controller, and automation hub with firmware versions and owners.

Day two: Validate security controls—check admin MFA, role separation, remote access paths, and inter-network policy intent.

Day three: Review reliability controls—assess backup freshness, restore viability, and leading noisy alerts.

Day four: Execute one failure simulation relevant to your environment (WAN outage, camera failure, automation controller restart, or identity-provider disruption).

Day five: Close the loop with documentation updates and stakeholder communication.

The sprint replaces assumptions with tested facts. Most teams discover that undocumented dependencies and unowned operational tasks pose greater risks than unfamiliar technologies.

When reviewing results, sort findings into three categories: immediate fixes (high risk, low effort), planned engineering work (high impact, medium effort), and deferred optimizations (lower impact or high complexity). This classification maintains focus and prevents scattered initiatives.