diff --git a/assets/_/2025/construction-site-surveillance/frigate-config.png b/assets/_/2025/construction-site-surveillance/frigate-config.png
new file mode 100644
index 0000000..a6fbbfd
Binary files /dev/null and b/assets/_/2025/construction-site-surveillance/frigate-config.png differ
diff --git a/assets/_/2025/construction-site-surveillance/grafana-traffic.png b/assets/_/2025/construction-site-surveillance/grafana-traffic.png
new file mode 100644
index 0000000..40ac28b
Binary files /dev/null and b/assets/_/2025/construction-site-surveillance/grafana-traffic.png differ
diff --git a/content/log/2025/construction-site-surveillance.md b/content/log/2025/construction-site-surveillance.md
index f13bde8..aa1c912 100644
--- a/content/log/2025/construction-site-surveillance.md
+++ b/content/log/2025/construction-site-surveillance.md
@@ -142,9 +142,12 @@ a yet another tailscale+headscale recommendation.
 
 ## Bandwidth and codec considerations
 
-I am pushing two camera streams, encoded in h.265 (resolutions TBD) using a
-constant 4.1Mb/s. Both streams are transcoded to h.264 via go2rtc and then sent
-over to Frigate and live view.
+Two camera streams (`2688x752` and `1920x1080`), encoded in h.265 consume
+around 1.8Mb/s 24/7. Both streams are transcoded to h.264 via go2rtc and then
+sent over to Frigate and live view. and
+
+Every 5 minutes a separate process captures a full-resolution picture of both
+cameras: `5376x1520` and `2560x1440`.
 
 Using exactly the same parameters (resolution, fps), but with h.264, the
 bandwidth grows to 11 Mb/s. Which may not sound like a lot with today's fiber