Release notes from frigate

0.18.0 Release

2026-09-12T13:20:21Z

Images

Full changelog: v0.17.2...v0.18.0

Major Changes for 0.18.0

Breaking Changes

There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to back up your current config and database before upgrading:

Simply copy your current config file to a new location
Stop Frigate and make a copy of the frigate.db file

GenAI now supports multiple providers. As a result, the global genai config is now a mapping of keys to GenAI provider setups, and a new roles field defines what tasks each provider will be used for (object descriptions, review summaries, embeddings, chat, etc.). Existing configs will be automatically migrated. Documentation
Frigate no longer saves annotated JPEG snapshots (.jpg) to disk. Only a clean, unannotated WebP snapshot (<camera>-<id>-clean.webp) is now stored in /media/frigate/clips/. The clean_copy configuration option has been removed — clean snapshots are always saved when snapshots are enabled. The snapshots.quality default has changed from 70 to 60, reflecting the switch from JPEG to WebP encoding. Users who previously relied on the annotated .jpg files on disk should instead use the /api/events/<id>/snapshot.jpg endpoint, which now honors timestamp, bounding_box, crop, height, and quality query parameters for both in-progress and completed tracked objects. When query parameters are omitted, the camera's snapshots config values are used as defaults. Existing configs containing clean_copy will be automatically migrated. Documentation
The config format for zones and masks has changed to add enabled and friendly_name fields. A config migrator will make the necessary changes, but if migration fails you may need to edit your masks and zones manually.
Intel GPU stats reporting has changed to no longer require intel_gpu_top and now reads directly from the kernel's per-client DRM usage counters. This removes the need for CAP_PERFMON, privileged mode, or perf_event_paranoid tuning, and adds support for newer Intel GPUs (including Battlemage). Reported usage values may differ from previous versions because the measurement method has changed; the underlying GPU workload is unchanged for the same configuration.
- Note that this change will require a Linux kernel version of 6.5 or newer on your host. Kernels older than 6.5 do not expose per-engine counters for GPUs using GuC submission.
FFmpeg has been updated to version 8 (excluding the -rk image), and introduces a known issue with go2rtc streams that transcode video using hardware acceleration. A small change to the go2rtc config is required. Documentation
- FFmpeg 5 is deprecated and will be removed from Frigate in 0.19.
Users running the JinaV2 semantic search model on a GPU will need to run an embeddings reindex due to changes to the CUDA graphs optimization level.
The /api/export DELETE HTTP API endpoint has been removed and refactored to support bulk deletion of exports. A POST to /api/exports should be used instead. Documentation
The sync_recordings config option has been removed and replaced by the new Media Sync pane in Settings.
The timelapse_args export config option has been removed and replaced by custom exporting ffmpeg arguments. Documentation
The ui.date_format and ui.time_format config options have been removed as these fields have been unused since date/time format and handling has been determined by i18n.
The DeGirum detector has been removed as the company has ceased operations effective 1 Aug 2026.
The DeepStack detector is deprecated and will be removed from Frigate in 0.19.

New Features

Frigate 0.18 introduces several major new features.

Full UI Configuration

Frigate 0.18 introduces complete UI-based configuration management. The new Settings experience provides:

A categorized sidebar covering every section of the config (cameras, detectors, motion, recording, review, GenAI, semantic search, face recognition, LPR, classification models, networking, authentication, and more).
Per-field validation, inline descriptions, and links back to the documentation.
A clear distinction between global and camera-level configuration, with the ability to override global values per camera and reset back to defaults at any time.
Highlighting of unsaved changes, a "Save All" button that summarizes pending edits across sections, and a Reset to Default/Global button on each section.
Indicators showing which fields require a restart to take effect, with a one-click restart prompt when a restart-required field is changed.
Most of Frigate's configuration options can now be saved and applied dynamically without restarting, including most enrichment, motion, ONVIF, GenAI, and go2rtc stream settings.
Manual YAML file configuration is still fully supported. Documentation pages now include "Frigate UI" tabs alongside YAML examples to show exactly where each option lives in the new Settings UI.

See the documentation.

Profiles

Profiles let you define named overrides on top of your base camera configuration and switch between them on the fly — without restarting Frigate. Profiles can override a camera's detection, motion, recording, snapshots, review, zones, notifications, objects (including masks and filters), enrichments (face recognition, LPR), audio, and birdseye settings, as well as the camera's enabled state.

Profiles are defined at the top level of the config with optional friendly names, and per-camera overrides are defined under each camera.
The active profile is persisted across restarts and can be changed from the UI or via the frigate/profile/set MQTT topic.
The current profile state and the list of available profiles are published over MQTT.
The Settings UI shows which fields are overridden by the active profile, supports editing the base config independently from any profile, and provides per-profile camera enable/disable from the camera management view.
A dedicated Profiles page in the main menu shows a card-based summary of all configured profiles and their overrides.

See the documentation.

GenAI

Frigate 0.18 includes a major expansion of GenAI capabilities. In addition to multi-provider support (see Breaking Changes), there is a new dedicated llama.cpp provider with automatic model probing and context sizing, and GenAI configuration can now be updated dynamically without restarting Frigate.

See the documentation.

Chat

Frigate 0.18 introduces a Chat interface for talking to your configured GenAI provider directly from the Frigate UI. Chat is implemented as a tool-calling LLM agent with access to Frigate-specific tools, so you can ask natural language questions about your cameras, tracked objects, and review activity.

Streaming responses with markdown support (including tables), per-message copy buttons, message editing, and the ability to stop a streaming response.
Tool calls are grouped and displayed inline as the agent works, with quick links to relevant tracked objects and review items.
Tools include searching tracked objects, finding similar objects via semantic search, inspecting live camera context, toggling camera features, starting VLM monitoring on a camera, and a recap tool for summarizing recent activity.
Tracked object thumbnails and similarity results render as cards in the chat, and any event can be attached to a chat message via the paperclip button or by clicking a thumbnail.
A persistent quick-replies row makes it easy to start common queries from a fresh chat.

Remote Embeddings

Semantic Search embeddings can now be generated by an external GenAI provider instead of running locally. This is especially useful when you would prefer to offload embedding work to another machine or to a hosted provider.

Any configured GenAI provider that supports an embeddings endpoint can be selected as the embedding provider for Semantic Search.
The semantic search settings UI includes a dropdown for choosing which configured GenAI provider should produce embeddings.

See the documentation.

Motion Review and Motion Search

Frigate 0.18 introduces a redesigned Motion Review experience along with a new Motion Search feature.

Motion Search. A new motion search workflow lets you draw or select a region on a camera image and find time periods where motion occurred in that area, similar to a motion-based version of object review.
Motion previews. Motion preview clips are generated and shown directly in the review pane, quickly highlighting areas of motion in the frame where Frigate did not detect and track any objects.
Heatmap filter. A heatmap-grid filter on the motion review page lets you constrain motion previews to specific regions of the camera image.

See the documentation.

Debug Replay

Debug Replay is a new tool that lets you replay recorded video through Frigate's detection and motion pipelines as if it were a live camera. This makes it dramatically easier to tune motion settings and object filters against real footage rather than waiting for live activity to reproduce an issue.

Configure the debug replay camera directly in the UI without manually editing your configuration.
Adjust motion and object detection configuration on the replay camera and see the effect on detections in real time.
The Debug view's overlays (regions, motion, paths, zones) are fully supported during replay.

See the documentation.

Exports

Frigate 0.18 brings substantial improvements to exports, including fast multi-camera exporting from History, single-click exporting of multiple review items in Review, and more.

See the exports documentation.

Case Management

Exports can now be organized into named cases, making it much easier to manage exports related to a single incident or investigation.

Cases are displayed separately from individual exports in the UI and can be filtered, edited, and deleted.
Exports can be assigned to a case at creation time (including from the single-camera and mobile review export dialogs) or moved between cases later.
Bulk selection (similar to the Review page) supports reassigning or deleting multiple exports across cases at once, with admin-only actions properly gated.
New cases can be created directly from any export dialog, and exports can be removed from a case without deleting them.
Stale or interrupted in-progress exports are reaped automatically on startup.

Custom Exports

Frigate 0.18 provides a dedicated exports API that accepts arbitrary ffmpeg arguments, allowing for fully custom export pipelines (custom filters, encoders, output formats, and so on). A CPU fallback path is automatically used if hardware-accelerated encoding fails. For security, custom ffmpeg arguments are restricted for non-admin users and a number of dangerous flags (such as -filter_complex, -vf, and -attach) are blocklisted to prevent arbitrary file reads via filter sources.

In addition, exports now use Frigate's Job infrastructure end-to-end, providing more reliable progress reporting and better cleanup of interrupted jobs. Per-camera record.export.hwaccel_args settings cascade up through camera and global configuration, allowing per-camera tuning of export hardware acceleration. See the recording documentation for export configuration details.

Other Improvements

There are many other improvements to highlight in this release.

Backend

Masks and zones can now be dynamically enabled and disabled via MQTT. Documentation
Camera enabled, detect, record, snapshots, and audio toggles now persist across Frigate restarts.
Added support for the AXERA AI accelerator. Documentation
Nvidia 50 series GPUs are now supported following an upgrade of CUDA and ONNX Runtime dependencies. As part of this change, the CUDA version was tuned to avoid overaggressive BFC behavior on these cards.
The Intel drivers have been updated to support Battlemage GPUs.
There is now a dedicated llama.cpp GenAI provider with automatic model probing and context sizing. Documentation
Custom (API-created) events can now be configured as detections or alerts based on the event label, can run indefinitely until explicitly ended, and support a configurable pre_capture value when created.
ROCm has been updated to 7.2.0 and now supports RDNA4 AMD GPUs. JinaV1 also works correctly under the new ROCm. Documentation
Added VLM monitoring, which runs a configured GenAI provider in a loop against a camera's live view to power chat-driven workflows.
ONVIF support has been refactored to add profile selection, decouple relative move from autotracking, and dynamically update ONVIF configuration without a restart. Documentation
A new generic process watchdog auto-restarts subprocesses that crash or stall.
The license plate detection box coordinates are now published in tracked_object_update MQTT messages. Documentation
A new frigate/<camera>/<role>/status topic and a stopped value on the LWT topic make it easier to monitor camera health and Frigate availability. Documentation
Configurable listening ports via the networking config section for advanced use cases. Documentation
New /api/recordings endpoints for deleting recordings, syncing media (replacing the old scheduled sync_recordings cleanup), and pulling review clips by review item ID.
Snapshot responses now include an X-Frame-Time header.
Frigate+ API calls now run in a thread pool to avoid blocking the event loop.
API performance improvements for several recording related endpoints.
ffmpeg has been updated to 8.1.1, and go2rtc to v1.9.14.
HTTP/2 support has been enabled in nginx. Users who access Frigate over port 8971 instead of port 5000 may see a significant performance improvement in Live and History view, especially if their installation has more than a couple of cameras.
Face recognition optimizations to increase accuracy and reject poor candidates.
Many internal type-safety improvements and a significant increase in mypy coverage across the codebase.
A number of security hardening fixes around authentication, role enforcement, custom export ffmpeg arguments, and SQL parameterization.

Frontend

There is a new Media Sync function which allows checking for orphaned files which can be deleted directly from the UI. A verbose mode writes a per-media-type report of orphaned paths to /config/media_sync. Documentation
A new camera connection quality indicator is shown on the camera metrics page, making it easy to see when cameras are having connection issues.
Greatly improved the efficiency of metrics loading and rendering, including hiding rather than unmounting graphs when switching tabs.
The Classification Wizard now allows regenerating examples in cases where the images are not representative of all scenarios, and supports reclassifying both images and faces after training.
The system metrics page now shows GPU and NPU temperatures (Nvidia, Rockchip, Hailo, and others where available).
A new Messages tab in the Logs section and Debug Replay shows the messages exchanged between Frigate's backend and the frontend/MQTT.
Preview generation has improved, with smoother transitions between hours and a new qmax parameter for higher-quality previews at high and very_high settings.
Cameras can now be deleted directly from the UI, with full cleanup of associated media.
Instant snapshots can now be downloaded directly from the controls in History view.
The Tracking Details pane now shows additional scoring information including computed and top scores per timeline entry.
The motion and object debug overlays now match between Debug view and Replay objects lists, and area is shown as a proper percentage.
Camera group and streaming settings are now saved to the browser local storage separately for each user.
The frontend has been migrated to React 19, with corresponding upgrades across the dependency tree (framer-motion, react-konva, react-grid-layout, vaul, sonner, and others).
The WebSocket layer has been rewritten on top of useSyncExternalStore for finer-grained, per-topic subscriptions and significantly fewer unnecessary re-renders.
Many fixes around mobile usability, including export crash fixes on iOS, viewport scaling tweaks, and improved drawer/dialog behavior.
New translations and substantial improvements to existing translations across many languages, including a new i18n key check in CI to keep translations in sync.
Many small UX improvements and tweaks.

v0.18.0-rc2

2026-09-06T19:32:44Z

Fix Content-Type for webp, png, and jpeg files in /clips/ (#24208)

v0.18.0-rc1

2026-08-28T12:08:54Z

proper belarusian locale support (#24112)

v0.18.0-beta3: Miscellaneous fixes (0.18 beta) (#23934)

2026-08-08T13:20:09Z

add host npu requirements to docs
allow toggling live audio transcription via mqtt
improve spacing consistency on mobile drawers
fix clearing the region grid not surviving a restart

v0.18.0-beta2

2026-07-26T00:50:41Z

pin react-zoom-pan-pinch to 3.4.4 (same as 0.17.x) (#23818)

v0.18.0-beta1: Fix enabled flag for custom classification models (#23681)

2026-07-12T11:48:14Z

honor enabled flag for custom classification models

for both startup and dynamically, even though the UI doesn't currently have a way to toggle dynamically

add test

0.17.2 Release

2026-07-01T04:54:27Z

This is a maintenance release for Frigate 0.17 that includes fixes and minor changes.

Images

What's Changed

Security Advisories

These advisories impact users with publicly exposed instances with no authentication and users with viewer roles where it is important to restrict access to some cameras.

Addressed in this release:

To be addressed in future versions:

Notable Changes

Exports can optionally include recording segment information as chapters in mp4 metadata
Performance improvements when displaying previews in the live page

All Commits

Update docs for DEIMv2 support by @NickM-27 in #22598
Add role-based auth to websocket message handler by @hawkeye217 in #22710
Update MemryX section documentation by @abinila4 in #22712
Memryx docs update by @abinila4 in #22746
Docs update by @hawkeye217 in #22864
Update restream.md docs and clarify output config by @Feni85 in #22860
Fix broken docs links with hash fragments that resolve wrong on reload by @hawkeye217 in #22925
Fix yolonas colab notebook by @hawkeye217 in #22936
Fixes by @hawkeye217 in #23235
Add metadata for creation time in recordings / exports by @NickM-27 in #23239
Fix admin response cache leak to non-admin users via nginx proxy_cache by @hawkeye217 in #23261
Docs update by @hawkeye217 in #23280
Docs update by @hawkeye217 in #23282
Filter motion review by allowed cameras by @hawkeye217 in #23294
Add ability to control chapters set on MP4 Export by @NickM-27 in #23310
Chapter tweaks by @NickM-27 in #23440
Catch edge cases in security protections by @NickM-27 in #23493
Offload preview encoding and Plus upload off the API event loop by @hawkeye217 in #23552
Fix cache control header for current hour preview mp4s by @hawkeye217 in #23553
Allow non-admin users to use PTZ controls for cameras they have access to by @hawkeye217 in #23578

New Contributors

@Feni85 made their first contribution in #22860

Full Changelog: v0.17.1...v0.17.2

0.17.1 Release

2026-03-22T20:33:17Z

This is a maintenance release for Frigate 0.17 that includes bugfixes and minor changes.

Images

What's Changed

Security Fixes

Restrict raw config endpoint to admin role by @hawkeye217 in #22523
Fix cross-camera auth in timeline and media endpoints by @hawkeye217 in #22522

Notable Changes

Fix/rknn arcface input format master by @begetan in #22319
Don't try to run storage cleanup if frigate is in safe mode by @hawkeye217 in #22492

Other Changes

docs: fix image address by @ZhaiSoul in #22067
docs: fix hailo setup numbering error by @ZhaiSoul in #22066
Fix script for downloading RF-DETR by @f0ff886f in #22083
docs: Add frame selection and clean copy details to snapshots docs by @webmasterkai in #21946
Update line breaks in video_pipeline.md diagram by @GrumpyMeow in #21919
docs: Add detail to face recognition MQTT update docs by @webmasterkai in #21942
Update HA docs with MQTT example by @hawkeye217 in #22098
Docs: fix YOLOv9 onnx export by @tremby in #22107
Docs updates by @hawkeye217 in #22131
updates for yolov9 coral support by @blakeblackshear in #22136
0.17 Release by @blakeblackshear in #19787
Fix link to Coral YOLOv9 Frigate+ models by @hawkeye217 in #22164
Fix go2rtc stream alias auth by @hawkeye217 in #22097
Birdseye fixes by @hawkeye217 in #22166
Fix genai by @NickM-27 in #22203
Docs updates by @hawkeye217 in #22222
Fix menu display conditions by @hawkeye217 in #22237
docs: updated the guides detectors section by @ZhaiSoul in #22241
Docs update by @hawkeye217 in #22251
Update docs for new HA language by @hawkeye217 in #22258
Update docs for AVX2 CPU requirement by @hawkeye217 in #22305
Improve playback of videos in Tracking Details by @hawkeye217 in #22301
Fix broken link to Home Assistant apps page by @ARandomGitHubUser in #22320
Fix preview retrieval to handle missing previews gracefully by @hawkeye217 in #22331
Fix thumbnail encoding logic by @hawkeye217 in #22329
Environment variable fixes by @hawkeye217 in #22335
Fix go2rtc config handling by @hawkeye217 in #22346
Save detect dimensions to config on add camera wizard save by @hawkeye217 in #22349
docs: add highlight magic comments by @ZhaiSoul in #22367
Various Fixes by @NickM-27 in #22376
Filter push notifications by user role camera access by @hawkeye217 in #22385
Keep Tracked Object Details nav buttons visible by @hawkeye217 in #22384
Add handler for license plate which is not expected to be stationary by @NickM-27 in #22416
Consistently sort class names by @hawkeye217 in #22415
Update dev contrib docs with Python checks by @leccelecce in #22419
UI tweak by @hawkeye217 in #22420
Hide set password menu option when native auth is disabled by @hawkeye217 in #22439
Disable pip for animated event cards by @hawkeye217 in #22438
Sync Tracking Details timeline with keyframe-snapped vod clip start by @hawkeye217 in #22454
Add Strix to third party extensions by @eduard256 in #22488
Fix audio event maintainer by @hawkeye217 in #22495
docs: remove onvif host environment variable by @ZhaiSoul in #22517
Validate preview filename and camera access by @hawkeye217 in #22530

New Contributors

@f0ff886f made their first contribution in #22083
@webmasterkai made their first contribution in #21946
@tremby made their first contribution in #22107
@begetan made their first contribution in #22319
@ARandomGitHubUser made their first contribution in #22320
@eduard256 made their first contribution in #22488

Full Changelog: v0.17.0...v0.17.1

0.17.0 Release

2026-02-27T03:07:35Z

Images

Changes since RC3

None

Major Changes for 0.17.0

Breaking Changes

Simply copy your current config file to a new location
Stop Frigate and make a copy of the frigate.db file

GenAI now supports reviews and object descriptions. As a result, the global genai config now only configures the provider. Other fields have moved under objects -> genai. See the new GenAI documentation.
Recordings retention is now fully tiered. This means that record -> continuous and record -> motion are separate config fields. See the examples in the documentation.
Some of the LPR models have been updated, and most users should manually switch to the small model, which performs well on both CPU and GPU. The large model is the same as 0.16's and is not as accurate as the upgraded small model in 0.17. Use large only if you live in a region with multi-line plates and you are having issues detecting text on them with the small model.
strftime_fmt was deprecated in 0.16, and should now be fully removed from the config in 0.17. Date/time formatting is based on the language selected in the UI.
The auto detection logic for camera resolution has changed. Some cameras fail to correctly advertise their resolution, and in previous versions, a default value was assumed that was not always correct. You may need to explicitly define detect resolution width and height for cameras in your config if Frigate hangs on startup.
The exec, expr, and echo sources for go2rtc are now removed by default to reduce the security risk if an attacker has access to the configuration. This can be disabled using an environment variable GO2RTC_ALLOW_ARBITRARY_EXEC A separate configuration for this for HA addon users will come in a later beta. See the documentation.
Nvidia GTX 900 series GPUs are no longer supported due to updates to ONNX Runtime

New Features

Frigate 0.17 introduces several major new features.

Classification Model Training

Frigate 0.17 supports classification models in two separate types: state classification and object classification. These models are trained locally on your machine using ImageNet via MobileNetV2.

State Classification

State classification allows you to choose a certain region of camera(s) with multiple states, and train on images showing these states. For example, you could create a state classification model to determine if a gate is currently open or closed.

See the documentation.

Object Classification

Object classification allows you to choose an object type, like dog, and classify specific dogs. For example, you can train the model to classify your dog Fido and add a sub label, while not labeling unknown dogs. Another example would be classifying if a person in a construction site is wearing a helmet or not.

See the documentation.

Custom Viewer Roles

Frigate 0.17 now has the ability to create additional viewer user roles to limit access to specific cameras. Users with the admin role can create a uniquely named role from the UI (or auth --> roles in the config) and assign at least one camera to it. Users assigned to the new role will have:

Guarded API access
Limited frontend access, following what the viewer role has access to (Live, Review/History, Explore, Exports), but only to the assigned cameras

See the documentation.

Review Item Summary with GenAI

Frigate 0.17 supports using GenAI to summarize review items. Unlike object descriptions which add a searchable description, review summaries have a structured output that instruct the AI provider to generate a title, description, and classify the activity as dangerous, suspicious, or normal.

This information is displayed in the UI automatically making it easier to see when activity requires further review and easier to understand what is happening during a particular video segment.

See the documentation.

Semantic Search Triggers

Triggers utilize Semantic Search to automate actions when a tracked object matches a specified image or description. Triggers can be configured so that Frigate executes a specific actions when a tracked object's image or description matches a predefined image or text, based on a similarity threshold. Triggers are managed per camera and can be configured via the Frigate UI in the Settings page under the Triggers tab.

See the documentation.

Object Detector Improvements

Frigate 0.17 brings performance increases for many detectors as well as support for new object detection hardware.

Nvidia GPU Performance

Support for Nvidia GPUs has been enhanced by implementing CUDA Graphs. CUDA Graphs work to reduce the involvement of the CPU for each inference, leading to faster inference times and lower CPU usage. CUDA graphs do have some limitations based on the complexity of the model, which means that YOLO-NAS, Semantic Search, and LPR models are not accelerated with CUDA Graphs. They will still continue to run on GPU as they did before.

Intel OpenVINO

Frigate 0.17 supports running models on Intel NPUs, for many models performance on NPU is similar to GPU but more efficient, leaving room to run more enrichment features on the GPU.

OpenVINO has also had many optimizations put in place to reduce memory and CPU utilization for object detection.

RKNN

Frigate 0.17 brings several improvements to RKNN platform including:

Automatic Model Conversion: automatically convert ONNX models to RKNN format. This allows Frigate+ and other models to be seamlessly configured and converted on startup.
Accelerated Enrichment Support: convert and run Semantic Search and Face Recognition models using the NPU. This greatly enhances performance while maintaining high accuracy with large model sizes.

Apple Silicon

Frigate 0.17 supports running object detection on Apple Silicon NPU. This is provided through the Apple Silicon Detector which runs on the host and connects via IPC proxy to Frigate, providing fast and efficient inferences when run within the same Apple device.

See the documentation.

YOLOv9 on Google Coral

Frigate 0.17 supports running a quantized version of YOLOv9 on Coral devices, bringing improved accuracy over the default mobiledet model. Note that due to hardware limitations, only a subset of the objects on the standard COCO labelmap is included. Frigate+ has also added support for YOLOv9 models on the Google Coral and includes support for all 41 Frigate+ labels.

See the documentation.

New Community Supported Detectors

Frigate 0.17 has community support for several new object detectors:

MemryX: MemryX MX3 M.2 module. Documentation
Degirum SDK: a proxy for inference with a variety of models. Documentation
Synaptics: Synaptics SL1680 NPU. Documentation

Frontend Improvements

In addition to supporting the new features, the frontend has many improvements.

Detail Stream

History view in 0.17 supports an additional view mode, Detail. This mode shows a card for each review item, and expanding a card reveals all tracked objects and their lifecycle events. Selecting any lifecycle event seeks the video to that exact timestamp. You can also overlay a tracked object's path on the video to help with debugging.

Redesigned Tracked Object Details pane

The Tracked Object Details pane in Explore has been redesigned to streamline the layout and consolidate related information. The Object Lifecycle tab is now the Tracking Details tab, which displays video overlays of the tracked object instead of static images, giving a clearer and more intuitive view of its activity.

Revamped Settings

Frigate 0.17 has a revamped Settings menu with a sidebar that categorizes the available options. This brings more scalability which will make it easier to support full UI configuration in a future version.

NOTE: The Debug view has been moved to the single camera Live view instead of Settings. Access the Debug view by enabling the switch under the Live view settings (cog icon) menu.

Add Camera Wizard

Frigate 0.17 supports adding camera via the UI without manually modifying your configuration file. When installing and starting Frigate for the first time, the main dashboard will include a button to start adding cameras via the Wizard.

Access the Wizard from the Cameras --> Management page in Settings.

Update Without Restarting

Frigate 0.17 supports saving many more features dynamically. Cameras, zones, and masks will not require a restart to take effect when saved through the UI. More will come in future versions.

Configuration Safe Mode

If an invalid configuration is detected, Frigate will enter safe mode and highlight the location of the issue. While in safe mode, the frontend is limited to the configuration editor, making it easy to correct the problem directly in the UI without needing an external file editor.

Other Notable Frontend Improvements

No recordings indicator on the History timeline. When no recordings are available, the timeline now displays a blank background to make this clear at a glance.
Clickable Birdseye view. When using the Frigate UI, you can now click a camera within Birdseye to jump directly to its individual Live view.
Object paths in Debug view. The Debug view can now display each tracked object's path — just enable the Paths toggle.
Audio debugging support. When audio detection is enabled, the Debug view includes an Audio tab showing live dbFS and RMS values from the camera’s microphone.

Other Backend Features and Improvements

Audio Transcription and Analysis

Frigate 0.17 supports fully local audio transcription using either sherpa-onnx or faster-whisper. The single camera Live view in the Frigate UI supports live transcription of audio for streams defined with the audio role, and any speech events in Explore can be transcribed and/or translated through the Transcribe button in the Tracked Object Details pane.

See the documentation.

Process and Efficiency Improvements

Frigate 0.17 uses the forkserver spawn method, this allows for better segmented memory control and better process management. Some processes are also started with lower priority, allowing the most important processes to have more CPU time when it is required.

Review Item Improvements

Review items have been refined to behave more intuitively:

Revamped stationary object tracking. Stationary object tracking has been enhanced to use new features to reduce incorrectly marking objects as active:
- Tracking now uses a history of the object's positions to better avoid inaccurate bounding boxes making the object be considered active.
- If an object is marked as having moved, Frigate will use image heuristics to compare the object from when it was known to be stationary to double-check if the object has moved from its original position.
Smarter handling of loitering objects. Stationary behavior is now dynamic based on object type. Objects that are normally stationary for long periods (e.g., cars) will no longer keep a review item active indefinitely when stopped inside a loitering zone. Objects that are not expected to remain still (e.g., people) will continue the review item as long as they stay within the zone.
Severity-based review item cutoff. Review items now end when a higher-severity event (such as an alert for arriving home) finishes. Ongoing lower-severity motion (e.g., passing cars) will no longer keep the higher-severity review item alive. In these cases, the alert ends and a new detection review item begins immediately.

Enrichment Improvements

LPR now includes a normalization configuration, this allows removing some commonly confused characters such as -, , etc. to ensure that plates are more consistently recognized as the same plate. Documentation
LPR now uses newer PaddleOCR models with support for Chinese characters.
All enrichments can now be assigned a specific device with the device config option. This is useful in cases when multiple GPUs are available. Documentation

Other Improvements

IPv6 can be toggled via the config with networking -> ipv6 -> enabled. Documentation
There is now config support for mapping Frigate roles to arbitrary values used in proxy headers. Documentation
MQTT now has a dedicated topic for camera health / status. Documentation
go2rtc support for HomeKit has now been improved, including persistent configuration being saved automatically when a camera is shared with HomeKit. Documentation
Add a toggle in the UI Settings to always overlay camera names on the Live dashboard
Add browser console logging to help debug Live view issues Documentation
Add a fallback timeout value to the UI Settings pane to configure the amount of time to wait to fall back to jsmpeg after the MSE player fails
Add the ability to download an instant snapshot from single camera Live view
Recording playback bugfixes and efficiency improvements should cause playback to start more quickly
User account passwords have a stricter password policy (minimum length and special characters) for improved security
Add the ability to dynamically toggle GenAI per camera via MQTT

v0.17.0-rc3: Translated using Weblate (Cantonese (Traditional Han script))

2026-02-21T16:22:26Z

Currently translated at 100.0% (56 of 56 strings)