Frigate config validator & storage planner

Two of Frigate's most common headaches are arithmetic, not mysteries: a shm_size that's too small (the classic "Bus error" crash) and a drive that fills up weeks before the retention you expected. This tool does the arithmetic with the formula from Frigate's own installation docs, plans storage the way Frigate actually records — continuous, motion and alerts on separate clocks — and checks a pasted config for the things that changed in Frigate 0.18.

Private by design. Everything on this page runs locally in your browser. Your config, camera names and IP addresses are never uploaded or sent anywhere. The checks target Frigate 0.18.x.

1 — Size it: SHM, storage and detector load

Add your cameras with the resolution and frame rate of each camera's detect stream (usually the low-resolution substream) and the bitrate of the stream Frigate records. Storage follows each camera's record mode: continuous footage is kept for the record retention, motion and alerts footage for the events retention.

CameraDetect widthDetect heightDetect fpsRecord bitrate (Mbps)Record modeSHM / camera

Detector inference times are typical published figures — treat the load bar below as a band, not a precise measurement.

Recommended shm_size

—

Recording storage

—

CameraModeGB / dayRetentionStorage

Detector load

Starting config

Generate a clean Frigate 0.18-format config skeleton from the camera table above — detector block, go2rtc restreams, per-camera detect and record settings. Placeholders for IPs and passwords; review before use.

2 — Check it: 0.18 config validator

Paste your existing config.yml below. The validator runs structural checks — a tolerant line-and-indentation scan, not a full YAML parser — for the 0.18 breaking changes and the setup mistakes that surface later as silent problems: a removed detector, the old flat genai layout, a missing MQTT block, detection frame rates no camera can feed.

How this works / sources

The SHM formula is the one Frigate's own installation docs publish: each camera needs (detect width × detect height × 1.5 + 270,480) ÷ 1,048,576 MB per buffered frame. The planner multiplies by 25 frames (the standard figure), adds headroom for two more cameras — Frigate sizes for cameras you might add at runtime — plus 50 MB for logs and the nginx cache, and 8 MB when the birdseye restream is on. It also shows the 50-frame figure, which is the next step up if warnings persist. Sanity check from the docs: two 720p cameras work out to roughly 210 MB; this planner says 208 MB.

The storage model mirrors how Frigate records. A continuously recording camera writes its record bitrate around the clock (1 Mbps ≈ 10.8 GB/day). Motion and alerts modes only keep footage while something is happening, so those rows are scaled by the activity percentages you set — honest estimates, not promises: a busy street can double the motion figure, a quiet hallway can halve it. Events retention applies to the motion and alerts rows, record retention to the continuous rows.

The validator's rules come from the 0.18 release notes and configuration docs: DeGirum removed, DeepStack deprecated, the genai providers-map-plus-roles layout, and MQTT being required for the Home Assistant integration.

Frequently asked questions

Why does Frigate crash with 'Bus error' or warn that SHM is too small?

Frigate keeps decoded frames in shared memory (/dev/shm). Docker's default shm size is far too small for more than a camera or two, so the frame buffer fills up and the process dies with a bus error, or Frigate logs a warning that the current SHM size is too small. The fix is a shm_size in your Compose file sized from your detect resolutions — the planner above computes it with the same formula Frigate's installation docs publish.

How is the shm_size figure calculated?

Per camera it is (detect width x detect height x 1.5 + 270,480 bytes) converted to MB, multiplied by the number of frames kept in the buffer — 25 frames is the standard figure, 50 if you see warnings under load. The totals add headroom for two more cameras plus about 50 MB for logs and the nginx cache, and 8 MB more when the birdseye restream is on.

Does my config get uploaded anywhere?

No. The validator and planner run entirely in your browser with JavaScript — your config, camera names and network details never leave your device, and nothing is sent to a server.

What changed in Frigate 0.18 that breaks older configs?

Three things trip people up: the DeGirum detector was removed entirely (a config that references it will not start), DeepStack is deprecated and leaves in 0.19, and the genai block changed shape — providers are now a named map with a separate roles block, so a flat pre-0.18 genai section needs rewriting. The validator above checks for all three.

Related guides