iOS 27's AirPods Custom EQ Explained: What It Does, Which Models Get It, and What Apple Left Out
iOS 27 brings native Custom EQ to AirPods for the first time. Here's how it works, which H2 models are supported, and where Apple's three-band implementation still leaves room to grow.
For years, the polite answer to "can I adjust the EQ on my AirPods?" was: sort of. You could nudge treble through Headphone Accommodations, an accessibility feature that was never designed for audio preference tuning. You could use the EQ setting buried in Apple Music, which only applied inside that app. Or you could install a third party audio app that routed system audio through its own equalizer, an inelegant workaround that Apple tolerated without ever acknowledging it as the gap it obviously was.
At WWDC 2026 on June 8, Apple acknowledged the gap. iOS 27 is bringing a native custom EQ to AirPods, system wide, with no workarounds required. It is one of the more straightforward quality of life additions Apple has made to the AirPods platform in years, and it arrived with almost no fanfare in a keynote that was almost entirely focused on Siri AI. If you missed it, here is what it actually does, which pairs are supported, and where Apple's implementation still falls short.
What the AirPods Custom EQ Actually Does
The new Custom EQ lives inside Settings, not inside any specific app. When your supported AirPods are connected, you navigate to Settings, tap your AirPods at the top, select Audio and Routing, then Equalizer. From there you have two options: Recommended, which is Apple's default sound profile, or Custom, which hands you a three band equalizer with adjustable points for low, mid, and high frequencies.
The implementation is straightforward. A blue line overlays a frequency graph, and you drag it up or down across the three bands to shape the sound. Apple includes an interactive preview so you can hear changes in real time before committing, along with a one tap return to the Recommended profile if you want to go back to Apple's defaults.
A few things are worth understanding about how this works at a technical level. The EQ setting is attached to the AirPods hardware itself, not to the iPhone or the app you're listening in. That means your custom setting follows your AirPods across devices: if you pair them with your iPad or Mac, the same EQ profile applies. This is meaningfully different from app level EQ settings, which only work inside that specific app and disappear the moment you switch to something else. It is also different from the old Headphone Accommodations approach, which was a system level setting but one calibrated around speech clarity rather than music preference. Engadget confirmed Apple is extending the feature across iPadOS 27 and macOS 27, making it genuinely cross platform from day one.
For current beta testers, the EQ is already functional with AirPods beta firmware build 9A5292e. You need both the iOS 27 developer beta on your iPhone and the AirPods beta firmware active; the feature does not appear without both sides of that equation in place.
Which AirPods Get It, and Which Don't
The feature is tied to Apple's H2 audio chip. The supported models are AirPods Pro 2 (USB-C), AirPods Pro 3, AirPods 4, and AirPods Max 2. If your AirPods contain H2 silicon, you are getting Custom EQ. If they don't, you aren't.
There is one notable nuance in how Apple communicated this. The post keynote briefings listed AirPods Max 2, AirPods Pro 3, and AirPods 4 as the supported models, conspicuously omitting AirPods Pro 2, the pair that first introduced the H2 chip. Beta testing has since confirmed that AirPods Pro 2 does receive the feature; Apple appears to have simply overlooked it in official communications given that the Pro 2 is no longer a current product.
The original AirPods Max, including its USB-C refresh, is not getting Custom EQ. This is going to frustrate anyone who bought into Apple's premium headphone lineup expecting long term feature parity. The original Max still supports Adaptive Audio, Spatial Audio, and Transparency mode, so it is not being abandoned entirely, but the EQ feature is off the table. AirPods Max 2 support is also arriving slightly later than the rest: it was absent from iOS 27 Beta 1 and is expected with Beta 2.
For anyone on first generation AirPods Pro, the answer is the same. No H2, no Custom EQ.
What Apple Left Out
The three band implementation has already drawn criticism from audio enthusiasts who were hoping for something more granular, and the criticism is fair. Competitors like Sony, Bose, and Samsung have offered multi band graphic EQs in their companion apps for years, some with ten or more adjustable frequency points and the ability to save multiple named presets. Apple's three band approach covers the basics: less bass, more treble, pull back the mids, but it does not give you the kind of precision that serious listeners or content creators actually want.
The single profile limitation is the other gap worth naming. Right now, you can only maintain one Custom EQ setting. There is no way to save a "podcasts" profile alongside a "music" profile and switch between them based on what you're listening to. 9to5Mac flagged this in their hands on, noting the hope that Apple adds multi profile support before iOS 27 ships publicly in the fall. It is a reasonable feature request, and given that the beta cycle still has months to run, there is time for it to arrive.
Both of those gaps matter less if you consider who Custom EQ is actually for. The audio enthusiast who wants parametric EQ control is probably not using AirPods as their primary listening tool anyway. The much larger audience, the person who has always wanted a bit less treble, or a bit more bass, or a warmer overall sound than Apple's default profile provides, gets exactly what they need from three bands and a live preview. That is most AirPods users. Apple built for the majority, not the edge case, which is entirely consistent with how it approaches every hardware software decision.
The more interesting context here is competitive. Apple has spent years defending its position that it tunes AirPods to sound correct, and that letting users apply their own EQ settings risks making them sound worse. Every Android earbud competitor with a companion app has been quietly eroding that position, making the absence of any EQ control feel less like a principled design choice and more like a gap. iOS 27 closes it, even if not to the satisfaction of everyone who wanted it closed.
The feature ships publicly with iOS 27 this fall. For now it is beta only, requiring both the iOS 27 developer beta and compatible AirPods firmware. If you are not running the developer beta, you will get it at the same time as everyone else, when iOS 27 goes public alongside the new iPhone lineup later this year.