AXIS OS 13 is scheduled for September 2026, and it is the most disruptive Axis firmware release in years. That is deliberate. A preview build carrying every breaking change has been downloadable since April so integrators can find out what fails before it fails on a customer site. The current shipping version is 12.11.77, released July 13, and when 13 arrives the 12 line becomes LTS 2026.
The short version: cameras that upgrade cleanly will be more secure by default, and any site running custom or third-party edge applications needs to be checked before the upgrade goes anywhere near it.
The 2038 rebuild is the reason for the disruption
Axis is moving AXIS OS to 64-bit time_t and 64-bit time APIs. Thirty-two-bit time counters overflow in January 2038, and for hardware being specified today with ten to fifteen year service lives, that is inside the deployment window rather than a distant curiosity.
The practical consequence is that every ACAP application has to be recompiled against the new time interface. An application that has not been rebuilt is not merely degraded, it is incompatible, and the device will roll the upgrade back automatically rather than boot into a broken state. The rollback behaviour is the important detail for anyone planning a fleet upgrade: a camera running an unmigrated analytics app will refuse to move to 13 and quietly stay where it is. Plan on auditing what is actually installed on your estate rather than assuming a firmware push took.
Roughly fifty older 32-bit models across the C, M, P, and Q series are in scope. Current 64-bit products cross over without the time-handling complications.
Security defaults that will change how installs behave
Several things that used to be configuration choices become the default:
- HTTPS only. Plain HTTP is disabled, and all network communication requires a secure connection. Any workflow still pulling snapshots or posting VAPIX calls over HTTP breaks here, and that includes a lot of quietly working integrations glued together years ago.
- Strong password enforcement on new or edited accounts, at fifteen characters, or twelve with complexity rules. Existing passwords are grandfathered, so this bites at the moment someone edits an account, not at upgrade.
- Signed video on by default. Footage is cryptographically signed so it can be shown to be unaltered. For anyone whose recordings might end up in a labour dispute, an insurance claim, or a courtroom, this is the most useful thing in the release.
- UPnP Discovery removed in favour of Bonjour. Discovery tooling that leans on UPnP stops finding cameras.
Axis ties these changes to regulatory pressure from the EU Cyber Resilience Act, France’s ANSSI requirements, and Japan’s JC-Star scheme. That direction of travel is worth noting even if you never sell into those markets, because it sets the baseline every manufacturer will eventually be measured against.
The API cull
More than fifty VAPIX APIs are removed, including legacy PTZ endpoints, older streaming parameters, SNMP configuration options, and file upload functionality. Deprecated VDO functions and a long list of obsolete parameters go with them.
ACAP requirements tighten at the same time. Signing through the ACAP Portal becomes mandatory for production, manifest schema v2 is required, legacy package.conf support is gone, and the old .larod model format for deep learning applications is dropped.
Motion Guard, Fence Guard, and Loitering Guard are discontinued, with AXIS Object Analytics as the replacement. If any of those three are earning their keep on a live site, that is a migration with a customer conversation attached, not a firmware update.
What this means for a Canadian estate
Axis publishes its support model clearly, which makes planning easier than it is with most manufacturers. The active track ships every two to three months and only the newest version is supported, so following it means committing to a genuine update cadence. LTS tracks appear every two years and carry roughly five years of maintenance. Sites that cannot absorb frequent firmware changes belong on LTS 2026, and that decision is worth making explicitly rather than by drift.
For integrators, the work between now and September is unglamorous and worth doing: inventory which cameras run ACAP applications and which are third party, confirm whether those vendors have shipped recompiled versions, find the integrations still talking HTTP, and check whether anything in the estate depends on the VAPIX calls being removed. The preview build exists precisely so this can be answered on a bench instead of during a maintenance window.
The read
This release is a manufacturer choosing correctness over convenience, and the industry is better for it. Signed video by default and HTTPS everywhere are the settings most of us have been recommending for years and watching get skipped. Solving the 2038 problem now, on hardware that will still be recording in 2038, is the kind of thing that never generates a sales sheet but prevents a genuine mess.
The cost is real, and it lands on integrators rather than on Axis. A fleet upgrade that would once have been a scheduled push is now an audit first. Do that audit in August on the preview build. The alternative is discovering in September that a customer’s analytics stopped and the camera rolled itself back without telling anyone.