Frigate zones & masks: detect everywhere, alert where it matters
Out of the box, Frigate notices everything — including the tree that waves all day and the road where a hundred cars pass. The fix is not a smarter model; it is geography. Masks tell Frigate what to ignore, zones tell it what deserves your phone's attention, and required-zone rules turn a noisy camera into a precise one. This is the tuning pass that turns Frigate from interesting into trustworthy.
Published Nov 17, 2026
Three different tools, often confused
- Motion masks blind Frigate to movement in part of the frame — the swaying tree, the busy road, the flag. Masked motion never triggers detection at all. This is your CPU saver and false-positive killer.
- Object (filter) masks ignore detected objects whose feet land in a region — useful when a neighbor's driveway keeps producing 'person' events you cannot mask without blinding your own yard.
- Zones do the opposite of masking: they label regions ('driveway', 'porch') so events know where they happened. Zones drive notifications, required-zone rules and zone-specific sensitivity — detection still runs everywhere.
Rule of thumb: mask what should never matter, zone what should matter differently. If you find yourself masking your own porch to stop alerts, you wanted a zone rule instead.
Draw them in the UI, keep the YAML
Frigate's web UI has a mask & zone editor (camera settings → Masks & Zones) that lets you draw polygons on the actual frame and shows the resulting coordinates. Use it — hand-computing polygon coordinates from percentages is nobody's idea of fun. The editor writes into your config, which ends up looking like this:
cameras:
front_door:
motion:
mask:
- 0.02,0.55, 0.30,0.55, 0.30,0.95, 0.02,0.95 # the road strip
zones:
driveway:
coordinates: 0.25,0.45, 0.85,0.45, 0.95,1.0, 0.30,1.0
inertia: 3
porch:
coordinates: 0.55,0.30, 0.90,0.30, 0.90,0.60, 0.55,0.60
loitering_time: 10 # seconds in-zone before it counts as loitering
Coordinates are fractions of the frame (0–1), listed as x,y pairs around the polygon. inertia demands an object stay in the zone for a few consecutive frames before the zone counts it — the difference between 'walked past the driveway's edge' and 'is in the driveway.' loitering_time exists for the porch problem: a delivery driver crosses it in seconds; someone standing there for ten seconds is information.
Required zones: the notification upgrade
The single highest-value line in a Frigate config ties recording and alerts to zones. In Home Assistant, the matching move is filtering your notification automation on the event's zones — Frigate reports exactly which zones each tracked object entered:
# Frigate side: keep snapshots/recordings meaningful per camera
cameras:
front_door:
record:
retain:
days: 3
snapshots:
required_zones:
- driveway
- porch
- With
required_zoneson snapshots, the hundred daily detections on the sidewalk produce no snapshots at all — only driveway and porch events exist as far as your review queue is concerned. - In the Home Assistant notification automation, trigger on Frigate events and condition on the zone list containing your zone — the pattern from our Frigate guide's notification setup, with one extra condition doing all the work.
- Keep one camera (a wide overview, if you have it) unfiltered as the household's memory; make the doorbell and driveway cameras strict. Different jobs, different tuning.
A tuning workflow that converges
- Run a full day unfiltered and review what Frigate found. Your false positives will introduce themselves — note WHERE they happen, not just what they are.
- Mask the repeat offenders' territory (tree canopy, road, the neighbor's flag). Re-check the next day: CPU load and event count should both drop visibly.
- Draw zones for the places you would act on: driveway, porch, gate, the car. Set inertia 3 as a starting point.
- Add required-zone rules to snapshots and notification automations. Live with it for two days, then adjust one variable at a time — tuning by vibes in hour one is how configs become folklore.
Troubleshooting
- Real events stopped too: a mask crept over a walkway, or the zone polygon misses where people's feet actually land — Frigate judges zone membership by the object's bottom-center point, not its whole box. Shrink masks from the ground up.
- Zone triggers as people pass on the sidewalk: the polygon's top edge reaches too far up-frame; distant objects' feet land higher in the image than intuition says. Pull the far edge down toward the camera.
- Notifications still noisy: the automation is not filtering on zones, or the camera's snapshots lack required_zones — both layers exist; use both.
- CPU still high despite masks: masks cut detection triggers, but a very busy scene still decodes and analyzes constantly. The other half of the fix is a Coral — see the Coral guide.
Zones as a household language
The sleeper benefit of zones is not fewer alerts — it is that zones give your automations a vocabulary. Once Frigate reports the world in zones, Home Assistant can speak in them too: announce 'person on the porch' instead of 'motion at front door,' record the driveway at high retention while the garden camera keeps two days, light the path only when someone is in the yard zone after midnight rather than for every passing cat. Presence gets sharper as well — a person event in the porch zone at 3 a.m. is a notification; the same event in the street-adjacent zone is a log line. This is the general pattern of a maturing smart home: the first pass makes things work, the second pass — the one this guide is part of — makes them mean something. Tune for meaning, and the noise takes care of itself.
Planning or upgrading a Frigate setup? The Frigate config validator & storage planner checks a pasted config against the 0.18 rules, computes your shm_size and tiered storage, and generates a valid 0.18 skeleton.
Official documentation and references
- Frigate documentation — zones configuration
- Frigate documentation — object and motion masks
- Frigate documentation — stationary objects
- Frigate documentation — review segments and alerts
Frequently asked questions
Do masks reduce Frigate's CPU use?
Yes — masked regions never trigger motion detection, so a masked busy road removes all the detection runs it would have caused. On street-facing cameras it is often the single biggest CPU saving available, before any hardware.
Can zones have different sensitivity?
Effectively, yes: zones support their own thresholds via inertia and loitering, and you can pair them with per-zone notification rules. A common setup is a hair-trigger porch and a skeptical street-adjacent driveway.
I drew a zone in the UI but events ignore it — why?
Zone membership uses the object's bottom-center point (roughly, its feet). If your polygon covers where heads appear but not where feet land, crossings will not register. Extend the polygon to the ground line where people actually stand.

