Planning UniFi Protect Storage and Recording Without Guesswork

UniFi Protect is easy to get running and easy to get wrong in two specific ways: undersizing storage so footage rolls off before you need it, and exposing the console to the internet to “check cameras remotely.” Both are avoidable with a little upfront planning. This guide is the reasoning, not specific capacity numbers — because the right number depends entirely on your cameras and settings, and any single figure quoted as universal would be fiction.

What actually consumes storage

Recorded video size is driven by a handful of factors, and they multiply:

• Number of cameras. Linear: ten cameras is roughly ten times one camera at the same settings.
• Resolution and frame rate. Higher resolution and higher FPS mean more data per second, substantially.
• Recording mode. Continuous (always recording) consumes far more than detection-based recording (records on motion/smart events with some pre/post buffer). This is usually the biggest lever.
• Scene activity. Modern codecs compress static scenes efficiently and busy scenes poorly. A camera staring at a quiet hallway stores far less than one watching a windy tree-lined street, even at identical settings.
• Retention. How many days you keep footage before it overwrites. Double the retention, roughly double the storage, all else equal.

Because these multiply, you size by reasoning about your combination, not by copying someone else’s “X cameras needs Y TB” claim. Their cameras, scenes, and settings aren’t yours.

A sizing method that doesn’t require fake numbers

Rather than trust a universal figure, derive yours:

1. List cameras and their intended settings (resolution, frame rate, and recording mode per camera). Be honest about which truly need continuous recording — usually fewer than you’d first say.
2. Use the storage estimate UniFi Protect itself provides. The application estimates expected retention for your actual configured cameras and storage. This is far more trustworthy than any external rule of thumb because it reflects your codecs, settings, and disk.
3. Watch real retention after a week of real footage. Activity-based compression means estimates firm up only once your scenes have been recording. Adjust resolution, FPS, mode, or storage based on observed roll-off, not predictions.
4. Decide retention by need, not by “as long as possible.” If you need 14 days for an insurance/incident window, size for that with margin; don’t chase 90 days of continuous 4K across a dozen cameras and then act surprised at the disk requirement.

The honest answer to “how much storage do I need” is: configure your real cameras, read Protect’s own estimate, verify against a week of real recording, and tune. Anyone giving you a flat number without your camera list is guessing.

Recording mode is the highest-impact decision

The single biggest storage lever is usually continuous vs detection-based recording:

• Continuous guarantees you never miss anything between events, at the highest storage cost. Justified for a few critical views (a main entrance, a register, a driveway you must have unbroken coverage of).
• Detection / smart-event recording stores clips around motion or recognized events with pre- and post-roll. Dramatically lower storage for cameras watching areas that are quiet most of the time. Appropriate for the majority of cameras in most deployments.

A common, expensive default is leaving every camera on continuous because it’s the safe-feeling option. Reserve continuous for the views that genuinely require gap-free footage and let the rest record on detection. This one decision often changes storage needs by a large multiple.

Keep the console off the public internet

The second classic mistake: wanting to view cameras away from home, so port-forwarding the UniFi Protect / UniFi OS console to the internet. Don’t. That exposes an admin surface and a video system directly to the world.

Reach Protect remotely the safe way:

• Use the official remote-access that UniFi OS consoles provide through Ubiquiti’s portal. It does not require you to open inbound ports.
• Or VPN into your network and view Protect as if you were local.
• Isolate cameras on their own VLAN (see our VLAN segmentation guide) so a compromised camera can’t roam your network, and only the NVR/console UI is reachable from your trusted segment.

Convenience of remote viewing and exposure of the console are not the same thing. Get remote viewing from official remote access or a VPN, never from a port forward.

A pragmatic Protect plan

1. List cameras and settings; mark the few that truly need continuous recording.
2. Configure them for real, read Protect’s own retention estimate, then verify against a week of real footage and tune.
3. Default most cameras to detection-based recording; reserve continuous for critical views only.
4. Isolate cameras on their own VLAN with only the NVR UI reachable from Trusted.
5. Never port-forward the console. Use official remote access or a VPN.

Plan storage from your actual cameras and Protect’s own estimate, lean on detection recording, and keep the system off the open internet. That’s the difference between a Protect deployment that quietly works and one you fight. For the groundwork this builds on, see VLAN segmentation for camera isolation, switch PoE budgeting for powering cameras, controller backups, and the rest of our UniFi guides.