Security Cameras and Access Control Checklist (2026): Placement, Retention, and Remote Access

Quick summary

Plan cameras in two layers: wide views for context and tighter views at doors, gates, and vehicle choke points for identification. In 2026, size retention before buying storage, keep recorder ports off the public internet, and document exports and access-control events so footage is easy to use later.

• Security & Surveillance services
• Exterior camera positioning guide
• UniFi Protect retention sizing

What should security cameras cover first?

Cover doors, walkways, driveways, gates, and the place where people or vehicles slow down. Those scenes produce the clearest faces, the best vehicle context, and the least wasted storage.

Start with approach paths and entry points, then add overviews. A wide backyard or parking-lot view helps explain what happened, but it rarely replaces a tighter identification shot at a door, gate, lobby, garage apron, or package area. If access control is part of the project, treat readers, intercoms, and strike events as camera design anchors.

• Cover approaches and doors first, then add overviews
• Put identification cameras where people pass within roughly 8 to 15 feet
• Avoid aiming across roads or sidewalks unless that scene is the actual requirement
• Label each camera by location and job before the install is considered done

What lens size do you need at 10, 25, and 50 feet?

Wider lenses show more scene, but they spread detail thinly. Longer lenses narrow the view and keep more pixels on the person or plate you actually need to identify.

What is the best mounting height for security cameras?

Mount entryway cameras at eye level or slightly above it, and reserve higher mounts for overview scenes. Height should protect the camera without turning every clip into a top-of-head recording.

For doors, intercoms, and narrow walkways, the sweet spot is usually 5 to 6 feet with a slight downward angle. For driveways and overviews, 8 to 10 feet is a better starting range because it balances tamper resistance with usable night footage. Roofline and soffit mounts still have a place, but they should usually be the context camera, not the only camera expected to identify a person.

• Entry and vestibule ID views: 5 to 6 feet
• Side gate and walkway ID views: 6 to 8 feet
• Driveway and yard overviews: 8 to 10 feet
• Weather-seal exterior penetrations and route exposed cable in proper conduit

How do you improve night clarity without harsh lighting?

Ambient light and exposure settings matter more than advertised night-vision range. A small lighting change often fixes blur faster than a camera swap.

Use separate day and night profiles. At night, keep shutter speed high enough to freeze walking motion before raising gain, because excess gain adds noise and reduces usable detail. Soft, always-on light near entries and along walkways helps cameras stay in cleaner exposure ranges. Infrared still has value, but it falls apart when the scene includes reflective siding, glass, polished trim, or headlights aimed straight into the lens.

• Start around 15 FPS for most entries and coverage views

• Add low-glare 2700K to 3000K lighting instead of harsh motion floods

• Use WDR for backlit daytime scenes and verify whether it helps or hurts the night profile

• Re-check framing after dark with a walk test and a vehicle test

• UniFi night-lighting guide

What is the safest way to view cameras remotely in 2026?

Do not expose camera or recorder ports to the public internet. Secure relay, private tailnet access, or a Zero Trust tunnel are better defaults than inbound port forwarding.

For everyday viewing, the simplest choice is usually the vendor's remote-access workflow. For administrative access to recorders, controller dashboards, or support tools, use a private-network method such as Tailscale or Cloudflare Tunnel instead of opening inbound NAT rules. That keeps the origin off the public internet while still allowing remote support. If nobody on the project will maintain secure remote administration, keep remote admin disabled and use local-only management.

How much storage does a camera need per day?

Start with bitrate math, not camera marketing. A simple planning rule is 1 Mbps average bitrate equals about 10.8 GB per day.

As a practical baseline, one 2K camera averaging 3 Mbps while recording continuously at 15 FPS uses about 32 GB per day, or roughly 1 TB for 30 days. Busy night scenes, reflective headlights, and higher frame rates push that number up quickly. Use continuous recording where gaps would hurt investigations, and use smart detections or motion-only recording on lower-priority overview views.

• Detailed retention sizing guide

Local storage or cloud subscriptions: why do we often prefer UniFi Protect?

Local storage makes retention, exports, and recurring cost easier to control. It is usually the better fit when the owner wants predictable history and does not want per-camera cloud fees.

UniFi's current documentation says recordings and AI events stay local by default on the console, remote sessions are end-to-end encrypted through Site Manager, and AI processing happens on the local network instead of in the cloud. That is why we often recommend UniFi Protect for cohesive camera-and-access projects. It is not the only workable platform, but it is strong when the goal is local recording, clean exports, straightforward app access, and a single ecosystem for cameras, doorbells, and access events.

The AI story needs nuance. Current G6 and AI-series cameras support broad on-device smart detections, but advanced capabilities such as broader face workflows, license plate recognition, natural-language search, or third-party camera AI often depend on supported models and optional hardware such as AI Port or AI Key. Write that precisely and avoid implying every UniFi camera does every AI function out of the box.

• UniFi camera design guide

How should alerts and smart detections be configured?

High-value alerts come from scene design and tight zones, not from turning on every notification. If an alert cannot drive action, it should probably be off.

Use person detection at doors, gates, and vestibules first. Add vehicle detection where the driveway or lot is operationally relevant. Keep roads, trees, and bright reflective areas outside your active zones whenever possible. Review alert frequency after a week, then remove noisy rules before adding new ones. Detection-only recording is useful only after the scene is quiet enough that detections are trustworthy.

• Person and vehicle alerts belong on identification views first
• Coverage cameras should usually be quieter than entry cameras
• After-hours schedules should notify the right people, not everyone
• Keep at least one known-good export path tested each quarter

How should cameras and access control work together?

Tie every protected door to the nearest useful camera. Door events should narrow the search, not create another system someone has to check separately.

At minimum, label each reader, strike, intercom, and nearby camera with matching names. Keep a short document for schedules, holiday overrides, door groups, and who can export video versus who can unlock doors. On small business jobs, this is often the difference between a five-minute incident review and a 45-minute scavenger hunt.

For homes, the same principle still applies. Smart locks and doorbells are most useful when they support a nearby identification view and a clear export path, not when they operate as isolated gadgets.

• Door schedule and access-policy template

What does a 4-camera small-business install cost in 2026?

Expect a wide range, and be transparent about why. Camera count matters, but cabling difficulty, retention, lighting, conduit, UPS, and integration work move the number more than people expect.

What belongs in the handoff checklist?

The handoff should explain what each camera does, how long footage stays available, and how the team retrieves clips under pressure. If the handoff does not cover those basics, the project is not finished.

References

• Ubiquiti Help Center: UniFi Protect Cameras - AI Detections and Facial Recognition. Checked March 4, 2026.
• Ubiquiti Help Center: How UniFi Protect Protects Your Data. Checked March 4, 2026.
• Axis Communications: Pixel density based on IEC 62676-4:2014. Checked March 9, 2026.
• Cloudflare Docs: Cloudflare Tunnel. Checked March 4, 2026.
• HomeGuide: 2026 Security Camera Installation Cost. Checked March 4, 2026.

Next steps

Need help planning the system? Plan a security project.