From 19e45069c04cabbfc0cd4e1b77c81dfd31f27336 Mon Sep 17 00:00:00 2001 From: Kai Curry Date: Mon, 9 Feb 2026 18:02:55 -0100 Subject: [PATCH] rm note about snapshot file ext change from png to webp --- docs/docs/configuration/snapshots.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/docs/configuration/snapshots.md b/docs/docs/configuration/snapshots.md index 6c19b2132..01c034a04 100644 --- a/docs/docs/configuration/snapshots.md +++ b/docs/docs/configuration/snapshots.md @@ -28,10 +28,6 @@ Frigate can produce up to two snapshot files per event, each used in different p MQTT snapshots are configured separately under `cameras -> your_camera -> mqtt` and are unrelated to the clean copy. -:::note -Clean copies were previously saved as `.png`. Frigate now saves them as `.webp` for smaller file sizes, but the API will still load legacy `.png` clean copies for older events. -::: - The clean copy is required for submitting events to [Frigate+](/plus/first_model) — if you plan to use Frigate+, keep `clean_copy` enabled regardless of your other snapshot settings. If you are not using Frigate+ and `timestamp`, `bounding_box`, and `crop` are all disabled, the regular snapshot is already effectively clean, so `clean_copy` provides no benefit and only uses additional disk space. You can safely set `clean_copy: False` in this case.