To update UniFi firmware, back up first, then update UniFi OS and the UniFi Network application under Settings > Control Plane > Updates, confirm devices reconnect, and only then update access points, switches and gateways from the UniFi Devices page, one device before the rest. As of September 2026 the current lines are UniFi OS 5.1 and UniFi Network 10.6.
UniFi updates split people into two bad camps: those who click “update all” the moment a badge appears, and those who never update anything for years until something forces them. Both get burned. There’s a defensible middle, and it’s mostly about order and timing, not about chasing or avoiding versions. The version numbers below are a dated snapshot; the strategy is what lasts, because the right version is whatever’s current and stable for your gear, and that moves.
Two different things update, and conflating them causes outages
UniFi has two distinct update tracks, and treating them as one is the root of most update pain:
- Controller / UniFi OS software — the UniFi Network Application (and on a console, UniFi OS itself). This is the management plane, and where it runs — console, self-hosted, or hosted — shapes how you update it, as covered in where to run the UniFi Network Application.
- Device firmware — the software on each access point, switch, and gateway.
They are versioned and released independently, and they have a compatibility relationship: very new device firmware generally expects a reasonably current controller, and a very old controller can struggle to manage devices on much newer firmware (and vice versa). The practical consequence: you don’t update these in a random order. There’s a sequence that keeps them compatible, below. A current example: the UniFi Network 10.6.106 notes add Wi-Fi 7 MLO STR mesh but say it “Requires UAP 8.8 or newer”, while the newest U7/E7 build in the public access point feed on September 27, 2026 was 8.7.11.
Where each piece updates, per Ubiquiti’s UniFi Updates article, with the newest build in each release feed on September 27, 2026:
| What updates | Where you update it | Release channels | Newest in Ubiquiti’s feed |
|---|---|---|---|
| UniFi OS on a console | Settings > Control Plane > Updates, click the console | Official, Early Access | 5.1.33 for Dream Machines (Sept 9) |
| UniFi Network application | Settings > Control Plane > Updates, click the application | Official, Early Access | 10.6.106 (Sept 10); 9.0.120 for UniFi Express only |
| AP, switch and gateway firmware | UniFi Network > UniFi Devices | Official, Release Candidate, Early Access | Per model family (below) |
Update the controller first, devices second
The order that avoids the most trouble:
- Back up first (see controller backups and migration). A pre-update backup is the difference between “roll back” and “rebuild.” Ubiquiti’s self-hosted update guide points to the backup download in UniFi Network’s System Settings.
- Update the controller / UniFi OS to the target version and let it settle. On a console that is Settings > Control Plane > Updates; a self-hosted server older than 8.6 has to be updated by running the installer on its host. Confirm it comes back healthy, all devices still show connected, nothing is stuck provisioning.
- Then update device firmware from the UniFi Devices page (Update Available), ideally not all at once (next section).
The reasoning: the controller is what orchestrates device firmware updates and understands the new firmware. Updating devices to firmware their older controller doesn’t fully understand invites stuck provisioning and odd states. Bring the manager current first, verify it’s stable, then bring the managed devices forward under it.
A self-hosted server update leaves the network running; Ubiquiti says devices stay connected and traffic keeps routing. A console is different. On a Dream Machine or Cloud Gateway the controller host is the gateway, so its UniFi OS update reboots the box that routes your traffic. Give that step the gateway’s maintenance window.
Don’t update every device simultaneously
The tempting button is “update all devices.” The careful path is staged:
- Update one non-critical device first. Confirm it comes back, adopts cleanly, passes traffic, and behaves for a little while.
- Then update the rest in waves, leaving your most critical path (the gateway, the AP your work depends on) for when you’ve seen the firmware behave on similar hardware.
- Update the gateway thoughtfully and with a maintenance window. A gateway firmware update is a routing/firewall and internet-connectivity event. If it goes wrong, everything is down, including your ability to easily fix it remotely. Do it when you can be present and have a way back in.
Why staged rather than all-at-once: if a particular firmware misbehaves on your hardware or with your config, you find out on one expendable device, not on every device at the same time with the whole network down and no known-good reference left.
Where to find UniFi firmware and release notes
Release notes and direct firmware links for every UniFi product are at community.ui.com/releases, with an RSS feed per product line: the Network application, UniFi OS for Dream Machines and access point feeds are the easiest way to read a release before your console badges it.
Ubiquiti’s download page carries the UniFi OS Server installer and a Latest Releases list with separate UniFi and UISP tabs; “Ubiquiti firmware” for UISP-line gear sits under the latter. The page also warns that certain releases are no longer available for security or regulatory reasons, so an old build you plan to fall back on can disappear.
There is no single “latest UniFi firmware” number, because access point firmware is built per model family. On September 27, 2026 the access point feed showed:
- U7 and E7 models (U7-Pro, U7-Pro-Max, U7-Lite, E7 and others): 8.7.11, promoted to Official on July 20, 2026.
- U7-LR: its own track, 8.0.76 (August 31).
- U6-LR, U6-Lite, U6+, nanoHD, FlexHD: 6.7.57 (August 25).
- U6-Pro, U6-Enterprise, U6-Mesh: 6.8.2 (February 3).
Official, Release Candidate or Early Access
Run Official on anything you depend on, and keep pre-release builds to one spare device:
- Official is the default for UniFi OS, applications and device firmware.
- Release Candidate: set the Device Firmware Release Channel in UniFi Network to Release Candidate. RC firmware notes, such as the U6-LR/U6-Lite 6.7.54 release, say to set it back to Official to return.
- Early Access: enable it at account.ui.com under Account Information > Preferences, then through the profile icon in Site Manager, then pick the channel per site under Settings > Updates (Ubiquiti’s Early Access article).
Updating gives you fixes — and occasionally new bugs
Be honest about both directions, because the “always update” and “never update” camps each ignore half of this:
Reasons updates matter:
- Security fixes. Network infrastructure is exactly the kind of thing where known vulnerabilities should not sit unpatched indefinitely. “Never update” is not a security posture; it’s deferred risk.
- Bug fixes and stability. Many “UniFi is flaky” situations on very old firmware are resolved by firmware that fixed exactly that.
- Feature and hardware support. New devices and capabilities often require current software.
The security case is concrete. Security Advisory Bulletin 062 (March 18, 2026) covered CVE-2026-22557, a path traversal in the UniFi Network Application that NVD scores 10.0 (Critical). Fixes shipped as 10.1.89 on Official, 10.2.97 on Release Candidate and UniFi Express firmware 4.0.13 (UniHosted’s summary). On Dream Machines, UniFi OS 5.1.31 (August 20, 2026) fixed the issues in bulletins 067 and 069.
Reasons to not update instantly:
- A brand-new release can introduce regressions. The day-zero version is the least field-tested it will ever be.
- A reasonable strategy is to not be first and not be years-late: let a release accumulate a little real-world mileage, then adopt it deliberately — rather than either the bleeding edge or a frozen ancient install. ShiftCTRL puts “a little” at one to three weeks, reading release notes meanwhile.
The defensible posture is current and deliberate, not bleeding-edge and not frozen. Patch security-relevant updates without unnecessary delay; a critical fix like SAB-062 gets no waiting period. Let feature releases prove themselves briefly before you move.
Automatic updates: convenient, but know what you’re automating
UniFi can apply some updates automatically on a schedule. The settings sit in Settings > Control Plane > Updates; ShiftCTRL notes the default is to install new firmware automatically, with scheduled and notify-only modes available. Update Manager in Site Manager (unifi.ui.com or the mobile app) lists pending updates across every site. This is a genuine convenience for hands-off sites — but understand the trade you’re making:
- For a simple home network, scheduled automatic updates during a low-use window are often a reasonable default: the risk of an unattended hiccup is lower than the risk of never patching a forgotten network.
- For anything you depend on or administer for others, manual, staged, backed-up updates are safer because you control timing, order, and the rollback plan. An automatic gateway update at a bad moment is a self-inflicted outage you weren’t watching.
Decide automation per environment and per device class. Auto-updating a couple of access points at 4 a.m. at home is fine. Auto-updating the gateway of a network people rely on, unattended, is the kind of convenience that eventually costs a bad day.
Manual, offline and SSH firmware updates
Ubiquiti’s Advanced Updating Techniques article treats these as a last resort for when the interface cannot do the job; most users should update automatically or through the UI.
- Pin a version: paste a firmware link from community.ui.com/releases into the address bar in the Settings tab of the device’s properties panel. Ubiquiti lists this for trying Early Access on one device or returning to Official afterwards.
- Cache once, update many: cache device updates in the Network application’s System Settings, then apply them from UniFi Devices > Update Available. The cache is also Ubiquiti’s route for offline updates.
- SSH, only when asked: Ubiquiti says SSH updating is not officially supported and may stop a console from functioning. Device credentials are under UniFi Devices > Device Updates and Settings > Device SSH Authentication, and consoles use
root(Ubiquiti’s SSH guide).
On an access point, the basic SSH method is a single command, upgrade https://<firmware-link>, using the firmware URL for that model. The exact command varies by model and firmware version. The device reboots onto the new image, and info confirms the running version (HostiFi).
When an update goes wrong
The recovery path is exactly why step one was “back up”:
- A bad controller update: restore the pre-update backup (and, if needed, the prior application version), which is why you took it before touching anything.
- A device misbehaving on new firmware: because you staged, only one or a few devices are affected and the rest are a known-good reference. Investigate or roll that device back rather than firefighting the entire network.
- Stuck provisioning after a firmware jump: often a controller/firmware version mismatch — usually resolved by getting the controller to the right version and letting the device re-provision (see adoption troubleshooting).
- A device that stops functioning entirely: Ubiquiti’s last step before an RMA is Recovery Mode, covered in the same advanced updating article.
The thing that turns an update mishap from a scare into a non-event is having backed up first and changed things in an order you can reason about.
The strategy in one place
- Back up before any update. Non-negotiable; it’s your rollback.
- Controller / UniFi OS first, verify healthy, then device firmware.
- Stage device firmware — one expendable device, then waves, gateway last and attended.
- Be current and deliberate, not bleeding-edge, not frozen: patch security promptly, let feature releases season briefly.
- Stay on the Official channel for networks you rely on; try pre-release builds on one spare device.
- Automate updates only where an unattended hiccup is acceptable; keep critical/managed networks manual and staged.
- Treat the gateway as special — its update is a connectivity and routing event; do it in a window with a way back in.
UniFi updates are not scary when they’re ordered, backed up, and staged. They’re scary when they’re “click update all on everything including the gateway and hope.” For the backup workflow this strategy depends on, see controller backups and migration. Staging gets harder the moment you are updating networks you cannot physically reach, which is its own discipline — see managing multiple UniFi sites and remote networks before scheduling an unattended gateway update on a remote site. A new console is the one exception to staging: take the first-boot catch-up update in the Dream Machine setup walkthrough straight away. If Wi-Fi feels worse after an access point update, work through the slow Wi-Fi troubleshooting steps before blaming the firmware. The rest of our UniFi guides cover the surrounding decisions.
Related across the network
- UniFi Adoption Failed: How to Fix Stuck Devices — ubiquitiguide.com
FAQ
does updating unifi take the network down?
Updating a self-hosted UniFi Network application does not: Ubiquiti says devices stay connected and traffic keeps routing during the update. Device firmware is different. Each access point, switch or gateway reboots onto the new image, so its clients drop briefly, and a gateway or console reboot cuts internet access until it returns.
why is my unifi device not updating?
Usually because it cannot reach Ubiquiti’s update servers. Ubiquiti’s checklist is short: the device must be online, DNS should use reliable resolvers such as 1.1.1.1 or 8.8.8.8, and UDP ports 53 and 123 must not be blocked by your gateway or ISP. On a network without internet access, cache the firmware in the Network application first.
how do i downgrade unifi firmware?
Copy the older build’s download link from community.ui.com/releases and paste it into the address bar in the Settings tab of the device’s properties panel, the method Ubiquiti documents for returning to Official after trying Early Access. Pause auto-updates first so it is not moved forward again. Some old releases are withdrawn for security or regulatory reasons.
how often does ubiquiti release unifi updates?
Two or three times a month per product line, on average. Between June 25 and September 10, 2026, Ubiquiti published seven UniFi Network 10.x releases, 10.5.54 through 10.6.106. UniFi OS for Dream Machines shipped five builds between July 22 and September 9, from 5.1.26 to 5.1.33. Access point firmware follows its own schedule per model family.
