> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/configuration/view-and-edit-camera-settings/schedule-camera-firmware-updates.md).

# Schedule Camera Firmware Updates

Configure when your cameras will perform firmware updates

Verkada releases regular camera firmware updates. These updates enhance security and functionality and are included at no additional cost as part of your cloud license.

Firmware updates are pushed automatically. However, you can schedule firmware updates to happen during a configured window.

## Schedule firmware updates

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**Select the camera you want to schedule.**
{% endstep %}

{% step %}
**At the bottom right, click Settings.**
{% endstep %}

{% step %}
**Under General, toggle on Schedule Firmware Updates.**
{% endstep %}

{% step %}
**Set the window for updates to occur.**

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-6a92dca187cf9ccd43acf4bdeb893b5326b2ebe2%2F1cc7e874023350b04f86cc05653528d2863915e7.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
The update window needs to be a minimum of 2 hours. Cameras may reboot during this time.
{% endhint %}

***

## Firmware updates and versioning

### Update Now

If a new update is available, **Update Now** will appear below your firmware version. Click **Update Now** to start the update. The process may take up to 20 minutes to initiate and complete.

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-bcb7c2ebc3fb365b02ae9c5a063c310666c43611%2F5d705cf02d030e500047148e1a70aa34350a51ce.png?alt=media" alt=""></div>

### Firmware Versioning

The camera firmware version is listed on the camera settings page under **Firmware**.

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-944cca6c1ce60980256c946df4e57076fa8b3cff%2F1fe390b7020bfba17161097f0f6c6e6286c94e3a.png?alt=media" alt=""></div>

Firmware release notes for the associated version are available on [Verkada’s Updates page](https://www.verkada.com/updates/?category=release-notes\&page=1), starting with C.29.0.6.

### Automatic failover

Each Verkada camera has a dual-partition firmware bank to ensure reliable updates. In the rare case of a failed firmware update, the device automatically reverts to the previous version and retries the update later.

### Does my camera stop recording during firmware updates?

We prioritize failsafe firmware updates to minimize service interruptions. While your camera may briefly go offline during the final stage of the update process, these updates are scheduled during regular maintenance windows to ensure minimal disruption.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/verkada-cameras/configuration/view-and-edit-camera-settings/schedule-camera-firmware-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.