> This page is for Firmware, version 3.2.
> For other versions, use one of these documentation indexes:
> - 4.0 (default): https://docs.ouster.com/sensor-docs/firmware/4.0/llms.txt
> - 3.2: https://docs.ouster.com/sensor-docs/firmware/3.2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ouster.com/sensor-docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ouster.com/sensor-docs/_mcp/server.

# Firmware Update

> Upload firmware images through the sensor web UI or HTTP API, and track update status.

Download a firmware file from [Ouster Downloads](https://ouster.com/downloads), navigate to the sensor web UI (for example, `http://os-991900123456.local/`), and upload the file when prompted.

> **Note**
>
> Firmware can also be updated with the [firmware update](/sensor-docs/firmware/api-reference#system) endpoint.

![Uploading a new firmware image onto the sensor](/sensor-docs/_fern-files/_img/4729c82dac420af209f7cf1d6c93d97285ac85d88fb2db4aa46f0b3477fbec91.webp)

Check the current firmware version before updating. Only update to an equal or higher version number.

After the web UI confirms the update, allow about 2 minutes for the sensor to reboot, then refresh the page to access the updated web UI.

## Firmware Update Status

Firmware update status reporting is improved with firmware v3.2. Query the [firmware status](/sensor-docs/firmware/api-reference#system) endpoint during or after an update and inspect `update_status` to confirm progress and completion.

```shell
curl http://os-991234567890.local/api/v1/system/firmware
```

The response includes the installed firmware version and update state. If an update fails or appears stalled, download the diagnostics file and contact [Ouster Support](https://ouster.com/tech-support).