Resolve backup and timelapse dependencies before enabling Verkada Low Bandwidth Mode

Obtain an explicit decision on dependent backup and timelapse workflows before reducing camera bandwidth.

Source facts

Verkada Low Bandwidth Mode changes more than live-stream bitrate. The documentation says cloud backup and timelapse cannot be used while the camera operates in this mode. It reduces non-motion thumbnail frequency and thumbnail size and quality, while motion thumbnails follow a different interval. Enabling the mode removes older cached thumbnails on the camera and uploads new ones from that point. Org Admins and Site Admins can apply it to an individual camera or multiple selected cameras.

Source: Verkada Help — Optimize Low Bandwidth Mode.

Applicability

Applies to the Low Bandwidth Mode feature and dependencies documented for Verkada cameras. This article does not promise a particular percentage reduction, image quality, or storage-retention outcome.

DSE recommendation

DSE recommends checking backup and investigation requirements before approving this toggle at a constrained site. Have the footage owner explicitly accept any loss of cloud backup or timelapse and identify an alternative preservation approach if required. Change a limited pilot first and record when the thumbnail behavior changes. Keep the bandwidth objective separate from recording and backup acceptance; a quieter uplink alone does not demonstrate that the required incident workflow still works.

Verification

Compare the camera’s backup, timelapse, and thumbnail behavior before and after an approved pilot change. Run a representative history search and inspect the resulting views with an investigator. Measure the site’s actual network impact and document the accepted feature tradeoffs before applying the setting to more cameras.

Official reference

Verkada Help — Optimize Low Bandwidth Mode. Reviewed October 15, 2026.