Two weeks after the bicycle disappeared from the side yard, the household pulls up the security camera footage to figure out what happened. The camera is on. It records continuously. The motion-activation log shows a clip from the right time window. The clip plays. It shows the side wall, the gate, and a sliver of driveway. The bicycle isn’t in the frame. The camera was pointed at the gate, not at where the bicycle was leaning, and the moment it actually disappeared happened just outside the camera’s coverage angle.
Three weeks of recorded footage and the household has nothing usable. The camera worked. The recording worked. The cloud retention worked. What didn’t work was the placement decision made the year the camera was installed, when the bicycle wasn’t yet a relevant subject and the camera was aimed at what seemed like the right thing at the time.
No surveillance system is fully protective, and any guidance that promises otherwise is overstating what cameras can do. The realistic question is what specific risks the household wants the cameras to address and what placement, resolution, retention, and review practices serve those risks.
Why placement decides what the camera sees
A security camera records what its lens is pointed at. Everything outside the lens’s angle of view is invisible to the system, regardless of how good the camera is or how long the system retains footage. The household with three cameras pointed in carefully chosen directions has better practical coverage than the household with six cameras pointed where they happened to fit on existing mounts.
The placement question is upstream of every other camera decision. A camera with mediocre resolution placed correctly captures the relevant events. A camera with high resolution placed incorrectly captures the irrelevant ones. The bicycle case at the top of this guide is the placement decision overriding the equipment quality.
Camera types: indoor, outdoor, doorbell
The form factor and intended use dictate environmental rating, lens characteristics, and feature priorities:
- Indoor cameras: optimized for indoor lighting, often smaller and unobtrusive, no weather rating
- Outdoor cameras: weather-rated (typically IP65 or higher), longer-range optics, infrared for night vision
- Doorbell cameras: combine doorbell function with camera and audio, optimized for close-range detection at the front entry
- Floodlight cameras: outdoor cameras integrated with motion-activated lighting, dual-purpose deterrent
- PTZ cameras (pan-tilt-zoom): motorized lens that can be repositioned remotely, useful for large coverage zones
Each type fits specific placement scenarios. A doorbell camera at the front door covers visitors and packages. An outdoor camera at the side yard covers approaches the doorbell can’t see. A floodlight camera at the garage adds deterrent value in a location that doesn’t get casual foot traffic. The household whose camera type matches the placement scenario gets useful footage; the household with mismatched types collects footage that doesn’t show what the household needed.
Resolution, low-light performance, and field of view
The visible camera specifications interact in ways that matter for actual evidence value:
- Resolution: higher resolution preserves detail when zooming into footage; useful for license plates, faces at distance
- Low-light performance: infrared, starlight, or color night vision determines what’s visible after dark
- Field of view: wider FOV covers more area; narrower FOV produces more detail per pixel in the area covered
- Frame rate: standard 15-30 fps captures most events; higher rates serve specific use cases like fast-moving subjects
A wide-angle high-resolution camera covers a large area with reasonable detail throughout. A narrow-angle high-resolution camera covers a small area with high detail. The household’s coverage need determines which trade-off fits. A long driveway approach benefits from narrow-angle cameras at intervals; a small side yard benefits from one wide-angle camera covering the whole space.
How motion detection works
Motion detection is the trigger that distinguishes an active event from continuous quiet recording. The detection methods:
- Pixel-difference detection: compares consecutive frames, flags movement when pixel values change beyond a threshold
- Object detection (AI-assisted): distinguishes people, vehicles, and animals from leaves blowing or shadows moving
- Heat-based detection (PIR): separate sensor detects infrared signatures of warm objects, less prone to false triggers from light changes
- Motion zones: configurable areas within the camera’s view that trigger detection while ignoring others
False triggers are the chronic problem with motion detection. A camera that records every leaf movement produces hundreds of clips per day, none of which the household reviews. The Federal Trade Commission’s connected-device guidance frames this in terms of data minimization: collecting less but more relevant footage produces a more useful system than collecting everything indiscriminately. The configuration that flags relevant motion and ignores routine environmental change is what makes the camera footage actually useful when something happens.
Where storage lives: local versus cloud
Camera footage gets stored somewhere, and the where matters for privacy, reliability, and cost:
- Local recording (NVR/DVR or onboard SD card): footage stays on premises, no monthly fee, but vulnerable to physical theft of the recorder
- Cloud storage: footage uploaded to the manufacturer’s service, accessible remotely, monthly subscription typical
- Hybrid: local primary with cloud backup, redundant against single-point failure
- On-device only (no upload): privacy-preferring approach, requires physical access to retrieve footage
The Electronic Frontier Foundation has documented privacy concerns with cloud-stored camera footage, including law enforcement access through warrants directed at the manufacturer regardless of household preference. A household concerned about footage privacy chooses local-only storage; a household prioritizing remote access accepts cloud storage with the understanding of who can access the footage and under what conditions.
Privacy considerations and data retention
A camera that records produces a continuous record of who comes and goes, what happens in the spaces under coverage, and (depending on placement) potentially of activities the household doesn’t intend to surveil. The privacy considerations:
- Indoor cameras in private spaces: bedrooms and bathrooms are categorically inappropriate; common areas are household-decision territory
- Outdoor cameras with audio recording: subject to one-party-consent or two-party-consent laws by jurisdiction
- Cameras pointed at neighbors’ property: legally permissible in most jurisdictions but creates social friction
- Doorbell cameras and visitor recording: recording of visitors implicit, but transparency about recording is good practice
- Children’s voices and faces: subject to additional considerations under privacy frameworks like COPPA for any cloud-connected processing
The data retention period matters separately from the placement. Footage retained indefinitely on cloud storage is footage available indefinitely to whoever accesses the cloud account. A retention policy that auto-deletes footage after a reasonable period (often 30 to 90 days for most household needs) reduces the surveillance footprint without compromising the camera’s day-to-day utility.
Coverage geometry: blind spots and overlap
A single camera produces a single coverage angle. Real properties have blind spots: behind structures, around corners, in shadows the camera can’t see into. Effective coverage requires either multiple cameras whose coverage zones overlap, or carefully chosen single-camera positions that minimize blind spots for the specific risks the household is concerned about.
The coverage analysis:
| Coverage need | Approach |
|---|---|
| Front entry (deliveries, visitors) | Doorbell camera + supplementary camera if entry is set back |
| Vehicle approach (driveway) | Camera at house facing approach + license-plate-capable resolution at distance |
| Side yard (typical entry vector) | Outdoor camera with clear line to ground beneath gates |
| Backyard | One camera per logical zone, overlap at access points |
| Garage interior | Indoor camera with low-light capability |
| Inside main living area | Optional, often skipped for privacy reasons |
The bicycle case at the top of this guide showed a camera placed at the gate, which covered visitors entering through the gate but missed the side wall where bicycles were stored. Adding a second camera, or repositioning the existing one to cover both the gate and the storage area, addresses the gap. The decision is whose use case the camera is sized to: visitors at the gate or property in the side yard.
When network bandwidth becomes the bottleneck
Multiple cameras streaming continuously to the network or to the cloud consume bandwidth. The household’s internet upload speed determines how many cameras can stream simultaneously without degradation. A camera at 4 megabits per second uploads 30 gigabytes of footage per day if streaming continuously. Five cameras quintuple that figure. Cloud-based systems either compress aggressively, record only on motion, or require substantial upload bandwidth.
The mitigations:
- Use motion-triggered recording rather than continuous to reduce bandwidth load
- Compress on-device before upload where the camera supports it
- Keep cameras on the IoT network segment covered in a separate guide on Wi-Fi networks for smart homes, which isolates camera traffic from other household uses
- Local recording with cloud-only-on-event reduces bandwidth substantially
- Wired (PoE) cameras avoid wireless contention, reduce bandwidth interference
The National Institute of Standards and Technology’s IoT cybersecurity baseline frames camera traffic as a category that benefits from segmentation, both for performance and for security; the bandwidth consideration reinforces that framing.
Failure modes the household sees
Camera systems fail in characteristic ways:
| Symptom | Likely cause |
|---|---|
| Recorded footage missing key event | Camera placement, motion zone exclusion, retention expired |
| Camera offline at critical moment | Network outage, power loss, IP conflict |
| Cloud account compromised | Account credential breach, often password reuse |
| Footage quality poor at distance | Resolution and field-of-view mismatch with use case |
| Night vision unusable | Infrared illuminator failure, lighting interference |
| Motion alerts overwhelming | False-trigger configuration, lack of motion zones or AI filtering |
| Storage full | Retention policy too long, motion-trigger-everything filling capacity |
| Audio recording legally questionable | One-party vs two-party consent jurisdiction issue |
Each maps to a configuration or placement decision, and most are recoverable without replacing equipment. The bicycle case is the placement-decision category, which often requires camera repositioning rather than additional equipment.
The bicycle two weeks later
The footage that didn’t show the bicycle leaving wasn’t a camera failure. It was a placement that addressed a different concern from the one the household later needed addressed. The household with one camera at the gate had a coverage profile optimized for visitors. The household with cameras placed for property-in-the-yard concerns has a different coverage profile. The system worked, but the system was set up for a different question than the one that came up.
The realistic surveillance posture for most households accepts that placement reflects the risks the household actually expects, and that unexpected risks may not be covered. A household reviewing its coverage periodically (after each significant change in property use, after each instance where coverage missed something) catches placement gaps before they become bicycle gaps. A household that sets up cameras once and never revisits the placement gets the coverage that was relevant the year of installation, regardless of what’s happened since. The two weeks the household spent reviewing footage that didn’t help is the visible cost of placement that hadn’t been revisited.
