Frigate

Media

A complete local network video recorder with real-time AI object detection.

Latest v0.17.2 · by FrigateWebsiteblakeblackshear/frigate

Release activity

Release activity — 10 releases across 10 days since Sep 4, 2025. Each cell is one day; darker means more releases that day. Nothing is recorded before Sep 4, 2025. Older weeks are hidden at this screen width.
MayJunJulAug
SundayNo releases on Apr 26, 2026No releases on May 3, 2026No releases on May 10, 2026No releases on May 17, 2026No releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 20261 release on Jun 28, 2026No releases on Jul 5, 20261 release on Jul 12, 2026No releases on Jul 19, 20261 release on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026
MondayNo releases on Apr 27, 2026No releases on May 4, 2026No releases on May 11, 2026No releases on May 18, 2026No releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 2026
TuesdayNo releases on Apr 28, 2026No releases on May 5, 2026No releases on May 12, 2026No releases on May 19, 2026No releases on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 2026No releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 2026No releases on Jul 21, 2026No releases on Jul 28, 2026No releases on Aug 4, 2026
WednesdayNo releases on Apr 29, 2026No releases on May 6, 2026No releases on May 13, 2026No releases on May 20, 2026No releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026
ThursdayNo releases on Apr 30, 2026No releases on May 7, 2026No releases on May 14, 2026No releases on May 21, 2026No releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026
FridayNo releases on May 1, 2026No releases on May 8, 2026No releases on May 15, 2026No releases on May 22, 2026No releases on May 29, 2026No releases on Jun 5, 2026No releases on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026
SaturdayNo releases on May 2, 2026No releases on May 9, 2026No releases on May 16, 2026No releases on May 23, 2026No releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 20261 release on Aug 8, 2026

10 releases since Sep 4, 2025

Changelog

v0.18.0-beta3Pre-release

0.18.0 Beta 3

Added 2
  • Allow toggling live audio transcription via MQTT
  • Crop motion previews to the selected filter region, with a Crop to filter switch to restore the previous 16:9 tiles
Changed 4
  • Only hide cameras with ui.dashboard disabled from the All Cameras dashboard, not from the camera selector in Settings
  • Improve display of GPU graphs in System Metrics
  • Improve spacing consistency on mobile drawers
  • Preserve frontend function names in production builds
Fixed 12
  • Fix wrong box format passed to cv2.dnn.NMSBoxes
  • Fix the OpenVINO YOLOX detector crashing on every detection
  • Restore fused DetectionOutput in the OpenVINO SSD model conversion
  • Fix manual PTZ relative moves permanently stopping object detection on cameras with autotracking disabled
  • Fix watchdog restarts reverting processes to the boot config
  • Apply persisted runtime and profiles states before workers start
Removed 1
  • Remove the DeGirum detector as the company ceased operations on 1 Aug 2026
Security 3
  • Validate X-Server-Port against a boot-time snapshot of networking.listen.internal instead of the live config, and reject internal and external listening on the same port
  • Verify motion search jobs belong to the requested camera
  • Prevent attacker-controlled recognized_license_plate regex from causing ReDoS attacks on the serialized DB queue thread
Images
Changes since Beta 2
Security
  • GHSA-cch2-w38h-8f44: /auth now validates X-Server-Port against a boot-time snapshot of networking.listen.internal instead of the live config, and config validation rejects internal and external listening on the same port
  • GHSA-vff9-46ww-fjjm: verify motion search jobs belong to the requested camera
  • GHSA-q8jx-q884-jcq9: attacker-controlled recognized_license_plate regex reaches Python re.search on the serialized DB queue thread, letting any authenticated (viewer) user freeze the whole application (ReDoS)
Backend
  • Fix wrong box format passed to cv2.dnn.NMSBoxes
  • Fix the OpenVINO YOLOX detector crashing on every detection (broken since 0.15.0)
  • Restore fused DetectionOutput in the OpenVINO SSD model conversion
  • Fix manual PTZ relative moves permanently stopping object detection on cameras with autotracking disabled
  • Fix watchdog restarts reverting processes to the boot config
  • Apply persisted runtime and profiles states before workers start
  • Fix birdseye camera overrides being clobbered by a global mode change
  • Fix clearing the region grid not surviving a restart
  • Allow toggling live audio transcription via MQTT
  • Reject non-finite numbers in GenAI review descriptions
  • Remove the DeGirum detector, as the company ceased operations on 1 Aug 2026
  • Documentation updates
Frontend
  • Crop motion previews to the selected filter region, with a "Crop to filter" switch to restore the previous 16:9 tiles
  • Fix the motion region filter grid mapping cells onto a hardcoded 16:9 box, so cells now align with the frame on non-16:9 cameras
  • Fix maximum update depth exceeded when dragging the handlebar quickly in Motion Search
  • Ensure cameras with ui.review disabled don't bump alert/detection badge counts, trigger the "new items to review" button, or appear in the review calendar or Motion Review
  • Only hide cameras with ui.dashboard disabled from the All Cameras dashboard, not from the camera selector in Settings
  • Improve display of GPU graphs in System Metrics
  • Fix stale stream name field when switching cameras
  • Improve spacing consistency on mobile drawers
  • Widen the logger name field in per-process log level settings
  • Preserve frontend function names in production builds

Full changelog: https://github.com/blakeblackshear/frigate/compare/v0.18.0-beta2...v0.18.0-beta3

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:

  1. Simply copy your current config file to a new location
  2. 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.
  • 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.
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.
View originalPermalink
How v0.18.0-beta3 went
v0.18.0-beta2Pre-release

0.18.0 Beta 2

Changed 8
  • GenAI now supports multiple providers with a mapping of keys to provider setups and a new roles field defining what tasks each provider will be used for
  • Frigate no longer saves annotated JPEG snapshots to disk, only clean unannotated WebP snapshots are stored in /media/frigate/clips/
  • The snapshots.quality default has changed from 70 to 60 reflecting the switch from JPEG to WebP encoding
  • The /api/events/<id>/snapshot.jpg endpoint now honors timestamp, bounding_box, crop, height, and quality query parameters for both in-progress and completed tracked objects
  • Expose whether a GenAI provider supports embeddings
  • Clean up llama.cpp and use the API key when configured in GenAI
  • Restrict the semantic search tool to English on JinaV1
  • Runtime camera toggles now persist across config saves and re-apply overrides on save/delete without re-broadcasting
Fixed 9
  • Fix Gemini tool calling and catch an OpenAI error in GenAI
  • Resolve friendly names against the correct camera and render zones with friendly name plus ID in the chat prompt
  • Convert face recognition crops to RGB before embedding and catch faces that become empty after cropping
  • Stop dropping batched add/remove config updates in object processing
  • Always clean up embeddings so they don't outlive their events
  • Prune object filters for unsupported labels when cleaning tracked objects
Removed 1
  • The clean_copy configuration option has been removed as clean snapshots are always saved when snapshots are enabled
Security 2
  • Bound REGEXP evaluation with a per-eval timeout to prevent ReDoS on the database thread
  • Fix JWT exp claim to use max_age per JWT_SESSION_LENGTH and prevent a new token being issued on logout
Images
Changes since Beta 1
Security
  • GHSA-q8jx-q884-jcq9: bound REGEXP evaluation with a per-eval timeout to prevent ReDoS on the database thread
  • Fix JWT exp claim (use max_age per JWT_SESSION_LENGTH) and prevent a new token being issued on logout
Backend
  • GenAI: fix Gemini tool calling, catch an OpenAI error, expose whether a provider supports embeddings, clean up llama.cpp and use the API key when configured, and restrict the semantic search tool to English on JinaV1
  • Zones: resolve friendly names against the correct camera and render zones with friendly name + ID in the chat prompt
  • Face recognition: convert crops to RGB before embedding and catch faces that become empty after cropping
  • Runtime camera toggles: persist across config saves, re-apply overrides on save/delete without re-broadcasting, and stop dropping batched add/remove config updates in object processing
  • Embeddings and event cleanup: always clean up embeddings so they don't outlive their events, and prune object filters for unsupported labels when cleaning tracked objects
  • Various autotracking and ONVIF fixes
  • Add -vaapi_device to the birdseye restream vaapi encode preset so hwupload can init on ffmpeg 8
  • Resolve export hwaccel args global value against the correct config path
  • Don't report auto-populated object/audio filters as camera overrides
  • Derive stale replay cameras from bounded directory listings to avoid scanning all clips at startup
  • Improve error messages for Intel GPU stats
  • Fix notification test button being blocked by websocket auth
  • Replace deprecated openvino-dev with a modern package for OpenVINO model generation
  • Ensure preview and review directories are valid after deleting a camera from the UI
  • Handle indefinite events when a segment needs to forcibly be ended for a camera
  • Bump sqlite-vec to 0.1.9
  • Documentation updates
Frontend
  • Zone editing: disable the ID field when a zone is referenced in any required_zones, and delete all required_zones references when the zone is deleted
  • Exports: center the multi-camera export range on the current playback position and fix a crash when camera group icons are invalid
  • Motion search/preview: fix motion-preview playback rate and don't stay on the page when the flow is cancelled
  • Improve the classification model edit dialog (edit enabled/save_attempts, plus state/motion/interval configs)
  • Show a numeric keyboard on mobile for number-specific fields in Settings
  • Fix the birdseye reordering widget in Settings
  • Update several object icons for Frigate+ 2026.2
  • Pin react-zoom-pan-pinch to fix History zooming reset
  • Fix minor export/review activity calendar timezone handling bug
  • Various frontend tweaks and fixes (logger i18n, scrollbar, overflowing text, etc.)

Full changelog: https://github.com/blakeblackshear/frigate/compare/v0.18.0-beta1...v0.18.0-beta2

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:

  1. Simply copy your current config file to a new location
  2. 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.
    • FFmpeg 5 is deprecated and will be removed from Frigate in 0.19.
    • FFmpeg 8 introduces a known issue with go2rtc streams that transcode video using hardware acceleration. A small change to the go2rtc config is required. Documentation
  • 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.
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.
View originalPermalink
How v0.18.0-beta2 went
v0.18.0-beta1Pre-release

0.18.0 Beta 1

Added 2
  • API endpoint /api/events/<id>/snapshot.jpg now honors timestamp, bounding_box, crop, height, and quality query parameters for both in-progress and completed tracked objects
  • Introduce complete UI-based configuration management with a categorized sidebar covering every section of the config
Changed 5
  • GenAI now supports multiple providers with a mapping of keys to GenAI provider setups and a new roles field that defines what tasks each provider will be used for
  • Snapshots quality default changed from 70 to 60 to reflect the switch from JPEG to WebP encoding
  • Config format for zones and masks has changed to add enabled and friendly_name fields
  • Intel GPU stats reporting no longer requires intel_gpu_top and now reads directly from the kernel's per-client DRM usage counters
  • FFmpeg has been updated to version 8
Removed 6
  • Frigate no longer saves annotated JPEG snapshots to disk, only clean unannotated WebP snapshots are stored
  • Remove clean_copy configuration option as clean snapshots are always saved when snapshots are enabled
  • The /api/export DELETE HTTP API endpoint has been removed and refactored to support bulk deletion of exports using POST to /api/exports
  • Remove sync_recordings config option and replace it with the new Media Sync pane in Settings
  • Remove timelapse_args export config option and replace it with custom exporting ffmpeg arguments
  • Remove ui.date_format and ui.time_format config options as these fields have been unused since date and time format handling is determined by i18n
Deprecated 1
  • FFmpeg 5 is deprecated and will be removed from Frigate in 0.19
Images

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:

  1. Simply copy your current config file to a new location
  2. 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.
  • FFmpeg has been updated to version 8.
    • FFmpeg 5 is deprecated and will be removed from Frigate in 0.19.
    • FFmpeg 8 introduces a known issue with go2rtc streams that transcode video using hardware acceleration. A small change to the go2rtc config is required. Documentation
  • 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.
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.
View originalPermalink
How v0.18.0-beta1 went
v0.17.2

0.17.2 Release

Added 1
  • Exports can optionally include recording segment information as chapters in mp4 metadata
Changed 3
  • Performance improvements when displaying previews in the live page
  • Offload preview encoding and Plus upload off the API event loop
  • Allow non-admin users to use PTZ controls for cameras they have access to
Fixed 2
  • Filter motion review by allowed cameras
  • Fix cache control header for current hour preview mp4s
Security 6
  • Fixed go2rtc WebSocket live stream camera access bypass for role-restricted users
  • Fixed incomplete patch of CVE-2025-62382 regarding image_path backslash-separator bypass and arbitrary host-file read
  • Fixed incomplete patch of CVE-2026-25643 regarding go2rtc exec:/echo:/expr: prefix block bypass allowing RCE and container escape
  • Fixed RTSP credentials leak to viewer role via nginx proxy_cache
  • Fixed authenticated admin RCE via go2rtc Stream API by enforcing exec: filter at API layer
  • Fixed WebSocket missing authorization allowing viewer to execute admin-only operations

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
New Contributors

Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.17.1...v0.17.2

View originalPermalink
How v0.17.2 went
v0.17.1

0.17.1 Release

Changed 6
  • Save detect dimensions to config on add camera wizard save
  • Filter push notifications by user role camera access
  • Keep Tracked Object Details nav buttons visible
  • Consistently sort class names
  • Hide set password menu option when native auth is disabled
  • Disable pip for animated event cards
Fixed 12
  • Fix RKNN arcface input format
  • Don't try to run storage cleanup if frigate is in safe mode
  • Fix go2rtc stream alias auth
  • Fix birdseye functionality
  • Fix genai
  • Fix menu display conditions
Security 2
  • Restrict raw config endpoint to admin role
  • Fix cross-camera auth in timeline and media endpoints

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

Images
What's Changed
Security Fixes
Notable Changes
Other Changes
New Contributors

Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.17.0...v0.17.1

View originalPermalink
How v0.17.1 went
v0.17.0

0.17.0 Release

Added 5
  • Support for classification models including state classification to determine regions with multiple states and object classification to classify specific object instances
  • Custom viewer roles allowing users to create additional roles with limited access to specific cameras
  • Review item summary with GenAI to generate structured summaries with title, description, and activity classification
  • Object descriptions as a searchable feature from GenAI
  • Ability to assign cameras to custom viewer roles with guarded API access and limited frontend access
Changed 4
  • GenAI configuration now only configures the provider at the global level, with other fields moved under objects -> genai
  • Recordings retention is now fully tiered with record -> continuous and record -> motion as separate config fields
  • LPR models have been updated and users should manually switch to the small model, with the large model remaining unchanged from 0.16
  • Auto detection logic for camera resolution has changed and may require explicit definition of detect resolution width and height for some cameras
Removed 3
  • strftime_fmt configuration that was deprecated in 0.16 must now be fully removed from the config
  • The exec, expr, and echo sources for go2rtc are now removed by default to reduce security risk, controllable via GO2RTC_ALLOW_ARBITRARY_EXEC environment variable
  • Nvidia GTX 900 series GPUs are no longer supported due to updates to ONNX Runtime
Images
Changes since RC3
  • None

Major Changes for 0.17.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:

  1. Simply copy your current config file to a new location
  2. 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:

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
View originalPermalink
How v0.17.0 went
v0.16.4

0.16.4 Release

Security 1
  • Address authenticated remote command execution (RCE) and container escape vulnerability
Images
Security Advisory

A security vulnerability was reported and addressed with this release. Exploiting this vulnerability requires authenticated access to Frigate.

What's Changed
New Contributors

Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.16.3...v0.16.4

View originalPermalink
How v0.16.4 went
v0.16.3

0.16.3 Release

Changed 1
  • Improve recording playback efficiency
Fixed 4
  • Fix certificate generation crash when using webpush notifications
  • Fix YOLOv9 export script
  • Fix model exports
  • Fix jetson build
Security 1
  • Fix broken access control vulnerability that allowed viewer users to delete admin and other user accounts
Images
Security Advisory

A security vulnerability was reported and addressed with this release.

Exploiting this vulnerability requires authenticated access to Frigate.

Improvements
  • Improve recording playback efficiency
  • Fix certificate generation crash when using webpush notifications
What's Changed
New Contributors

Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.16.2...v0.16.3

View originalPermalink
How v0.16.3 went
v0.16.2

0.16.2 Release

Added 2
  • Add GitHub mirror download endpoint
  • Add robots.txt
Changed 3
  • Improve live loading by not blocking UI
  • Improve rf-detr export
  • Ensure that a user must provide an image in an expected location
Fixed 2
  • Fix best thumbnail endpoint
  • Fix model selection type in Frigate+ settings pane
Security 1
  • Fix arbitrary file read vulnerability via Export Thumbnail image_path parameter
Images
Security Advisory

A security vulnerability was reported and addressed with this release.

Exploiting this vulnerability requires authenticated access to Frigate.

What's Changed
New Contributors

Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.16.1...v0.16.2

View originalPermalink
How v0.16.2 went
v0.16.1

0.16.1 Release

Changed 5
  • Improve recording playback startup time on slow connections
  • Allow users with the viewer role to register for webpush notifications
  • Remind users to restart after enabling face recognition
  • Always allow sorting by score in Explore page
  • Cleanup vod clip handling and add padding arg
Fixed 15
  • Fix export dialog overflowing due to i18n time lengths
  • Ensure audio support is correctly queried from go2rtc streams
  • Fix video dimension layout for Chrome
  • Fix recognized license plate filter being incorrectly hidden in Explore filters in certain circumstances
  • Fix unscrollable languages menu on small mobile devices
  • Fix label in streaming stats
Deprecated 1
  • Deprecate include_thumbnails field in events API

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

Images
What's Changed
Frontend Changes
Backend Changes
View originalPermalink
How v0.16.1 went
View all

Discussion