Frigate 0.18: the upgrade, GenAI, and the new hardware truth
Frigate 0.18 (September 2026) is the release that changes how the whole system feels: full configuration from the UI, switchable camera profiles, and GenAI that lets you search footage in plain language and chat with your recordings. It also quietly rewrote the hardware advice — including one change that dates every older tutorial, this site's included. Here is the upgrade path and the honest new picture.
Published Nov 18, 2026
What 0.18 changes
- UI configuration — cameras, zones, masks and settings are now editable in the web UI properly, not just viewable. The YAML still exists underneath; the era of config-file-or-nothing is over.
- Camera profiles — switchable Home / Away / Vacation profiles change detection and recording behavior as a set, instead of per-camera surgery.
- GenAI, plural providers — the old single genai block became a provider map with roles: one model can describe events, another power chat, another generate embeddings for search. Local (Ollama) and cloud providers mix freely.
- Semantic search — embeddings (Jina CLIP) let you search 'red truck in the driveway' across history instead of scrubbing timelines.
- Breaking changes — zones/masks format updates, snapshots are WebP-only now, FFmpeg 8 underneath. Your 0.17 config needs a review pass, not just a version bump.
The hardware truth: about the Coral
For years — including in this site's own Frigate guides — the Coral TPU was the default detector recommendation: cheap, fast, sips power. As of the 0.18 era, Frigate's own guidance no longer recommends the Coral for new installs: the EdgeTPU is a dead-end platform (no updates, aging models), and the current detector landscape — OpenVINO on any recent Intel iGPU, Hailo accelerators, NVIDIA, AMD ROCm — delivers more detection performance with a future. If your Coral works, it keeps working; nothing in 0.18 removes it. But nobody should buy one on 2024 advice in late 2026, and any tutorial still leading with it (our older pages are being updated to say this) is showing its age. The detector section of our Coral guide now carries the same note; treat that guide as 'if you own one' documentation.
Already own a Coral? Keep it running and spend nothing. Planning a new build? Put the money toward an Intel-chip host with a real iGPU (OpenVINO) or a Hailo module — the performance ceiling and the model support are both better.
Upgrading from 0.17
- Back up your config file (and your Frigate database if you keep long history) before touching the image tag.
- Read your config against the breaking list: zones/masks format, the genai provider-map restructure, WebP snapshots. The UI config editor will surface most issues as validation errors on first load — that is your checklist.
- Recreate the container on the 0.18 image, open the UI, and work through flagged config items in the editor. Confirm live views, detection and one recorded event per camera before moving on.
- Revisit recording and detection per camera with profiles: set up Home and Away profiles now that they exist — it is the feature that most changes daily life and the one everyone skips.
GenAI and semantic search, set up honestly
The GenAI roles split three ways: descriptions (an event gets a sentence: 'A person in a blue jacket leaves a package on the porch'), chat (ask your footage questions in the UI), and embeddings (the index behind semantic search). Each can point at a different provider. The privacy-honest options: run embeddings and descriptions against a local model via Ollama — Frigate's docs are blunt that local GenAI wants a real GPU (roughly 6–10 GB VRAM) and that CPU inference is not recommended — or send event snapshots (not streams) to a cloud provider and accept that trade with eyes open. Start with semantic search alone: it is the feature that changes how you use the archive, it works on your existing recordings once indexed, and it needs no per-event API spend to feel magical. Our zones & masks guide still applies in full — good zones make GenAI descriptions dramatically more useful, because the model narrates what your geography already framed.
Troubleshooting
- Config validation errors on first load: expected for 0.17 configs — work the list in the UI editor; zones/masks and genai are the usual flags.
- GenAI descriptions time out: the model is too big for your hardware or the provider endpoint is wrong. Local on CPU will feel broken because, for this workload, it is.
- Semantic search returns nothing: the embeddings index builds over time and history; confirm the embeddings role is assigned to a provider and give the indexer a pass over your recordings.
- Detector errors after upgrade: FFmpeg 8 and driver stacks moved together — update your host's GPU drivers before suspecting the config, especially on OpenVINO and ROCm.
Official documentation and references
- Frigate documentation — installation and configuration reference
- Frigate on GitHub — release notes, including the 0.18 series
- Frigate documentation — semantic search configuration
- Frigate documentation — detector hardware and configuration
Frequently asked questions
Should I replace my Coral TPU because of 0.18?
No — if it works, it works, and 0.18 still supports it. The change is buying advice: the Coral is no longer the recommended purchase for new builds, where OpenVINO on an Intel iGPU or a Hailo accelerator is the better spend.
Can GenAI run fully locally?
Yes, via Ollama — with a real GPU (about 6–10 GB VRAM) for usable speed. Frigate's own docs do not recommend CPU inference for GenAI features. Cloud providers are the zero-hardware option, at the cost of sending event snapshots out.
Do my zones and masks survive the upgrade?
The concepts and most geometry carry over, but 0.18 changed parts of the format — expect the UI editor to flag items for review. Our zones & masks guide's approach (mask what never matters, zone what matters differently) is unchanged.
Related guides
- Frigate NVR with Home Assistant
- Frigate zones & masks
- NVR storage calculator
- Frigate config validator & storage planner — paste your config for a 0.18 check

