Apple has released beta firmware build 9B5045a for a broad portion of its current AirPods range. The update is being made available to developers and public beta testers using AirPods Pro 2, AirPods Pro 3, AirPods 4, AirPods 5 and AirPods Max 2.
There is an important limitation for anyone deciding whether to enable it: no release notes have been published for this AirPods beta. That means the build number confirms a new test version exists, but it does not establish which bugs, behaviors or features may have changed.
For beta participants, the update can be enabled from the AirPods settings interface when the headphones are connected to an iPhone, iPad or Mac running iOS 26, iPadOS 26 or macOS 26 or later. Once the beta-update control is switched on, the firmware is eligible to download.
Which AirPods are included
The 9B5045a beta applies to the following models:
- AirPods Pro 2
- AirPods Pro 3
- AirPods 4
- AirPods 5
- AirPods Max 2
That is a notably wide device list, spanning in-ear AirPods, Pro-branded models and the over-ear Max line. Still, a shared build number should not be treated as confirmation that every model receives the same visible change. Without model-specific notes, there is no supported basis for claiming a particular capability, audio adjustment or fix has arrived on one set versus another.
What beta firmware means here
Firmware is the software that runs directly on a device’s hardware. In this case, it is distinct from iOS, iPadOS and macOS, which are operating systems on the iPhone, iPad and Mac used to manage the AirPods. Updating an iPhone does not automatically explain what has changed inside the earbuds or headphones themselves; the AirPods firmware has its own build number and installation process.
Beta denotes a pre-release version intended for testing before a wider stable rollout. Developers and public beta testers can choose to receive it, but Apple has not supplied a change list for this particular build. The practical result is simple: participants can verify that their AirPods have moved to 9B5045a, yet they may not be able to tie that update to a documented user-facing improvement.
That uncertainty is worth taking seriously. A beta build can be useful to people testing Apple’s wider pre-release software environment, but users who depend on their AirPods for everyday calls, work or listening have little information here with which to judge the benefit of installing early. The available facts support the update’s availability and setup route, not a promise of any specific new function.
How the update is delivered
Unlike many updates on phones, tablets and computers, AirPods firmware does not provide a conventional button that immediately downloads and installs a selected release. The process is more hands-off.
- Connect the supported AirPods to an iPhone, iPad or Mac running iOS 26, iPadOS 26 or macOS 26, or a later version.
- Open the AirPods settings interface and turn on beta updates.
- Connect the AirPods to power while they remain associated with the Apple device.
- Allow time for the firmware to download and install.
Apple’s approach means patience is part of the procedure. Installation can take several hours, rather than occurring immediately after the setting is enabled. A missing on-demand update control is especially relevant for anyone trying to prepare a device for a test session: toggling the beta option does not guarantee that 9B5045a will appear at once.
Keeping the AirPods connected to the relevant Apple device and connected to power is therefore the practical requirement supplied for receiving the build. It also makes sense not to read a delay as proof that an update has failed, given that the process is explicitly capable of taking hours.
The absence of release notes is the real story
Build 9B5045a’s lack of published notes creates a clear boundary between reporting and speculation. It would be easy to assume that a firmware update concerns sound quality, pairing, battery behavior, noise management or another familiar headphone topic. None of those possibilities has been identified for this release.
For users, the useful takeaway is not a rumored feature list but an expectation of opacity. The version number is the reliable identifier. If a tester encounters a difference after updating, that observation may be personally useful, but it is not the same as an officially documented change or proof that the behavior applies across every supported AirPods model.
This is also why the beta setting matters more than it might for a fully described release. Opting in is a deliberate choice to accept a pre-release firmware build without a published account of what it contains. Users who have not opted in should not expect a manual path to force-install this specific beta.
What to do before enabling the beta
The supplied installation requirements point to a short, sensible checklist. First, confirm that the AirPods model is among the five named devices. Then make sure the paired iPhone, iPad or Mac is on the required generation of system software: iOS 26, iPadOS 26 or macOS 26, or later. Finally, expect the hardware to need power and time rather than a quick tap-to-update experience.
It is also helpful to separate the status of the companion device from the status of the AirPods. The iPhone, iPad or Mac provides the settings path and connection required for the download, while the AirPods themselves receive the firmware. In other words, installing an operating-system beta on a companion device is not presented as the final AirPods update step; beta updates must also be enabled in the AirPods settings interface.
For people already operating inside Apple’s beta ecosystem, that setup may be familiar. For everyone else, it is a reminder that accessory software can follow a less visible maintenance cycle than apps and operating systems. A version number may change in the background, and the wait is expected rather than exceptional.
How this fits Apple’s broader beta cycle
The timing also places the AirPods build alongside Apple’s current platform betas, since eligibility depends on iOS 26, iPadOS 26 or macOS 26 and later. The connection does not tell us what 9B5045a changes, but it does show that Apple is using the companion platforms’ AirPods settings to manage access to the pre-release firmware.
That broader ecosystem approach is visible elsewhere in Apple software coverage, including the company’s iOS-linked Fitness+ changes. The important distinction is that the AirPods release currently comes without a comparable feature description. The software version and supported hardware are known; the payload is not.
For now, 9B5045a is best understood as an opt-in test firmware rollout for the five supported AirPods products. Enable the beta setting only if participating in that testing track makes sense, keep the AirPods connected to a qualifying Apple device and power, and allow several hours for the update process to complete.
