Windows 11 Bluetooth codecs break into two camps: SBC is the native baseline, AAC is supported (as an xHE-AAC implementation per RTINGS), and the advanced list, aptX, aptX HD, aptX Adaptive, aptX Lossless and LDAC, is not natively supported and needs special drivers or external solutions. Microsoft's own documentation stops at the profile level without a codec table. The working alternative for aptX-grade links from a PC is a USB transmitter dongle, the route RTINGS itself uses on its bench.
Figures on this page were checked September 2026. Every table row carries its source and access date.
Codec support matrix
| Codec | Status on Windows 11 | Source / as of |
|---|---|---|
| SBC | Native; the mandatory A2DP baseline every stack carries | A2DP 1.3.2, Section 4.2.1, 2026-09-22 |
| AAC | Supported since Windows 11, as an xHE-AAC implementation | RTINGS latency research, 2026-09-22 |
| aptX classic | "Available on some systems but depends on your Bluetooth adapter and drivers", per the same Q&A thread | Microsoft Learn Q&A 5560825, 2026-09-22 |
| aptX HD / Adaptive / LL | Not natively supported; require special drivers or external solutions | Microsoft Learn Q&A 5560825, 2026-09-22 |
| aptX Lossless | Not natively supported; named in the same documented list | Microsoft Learn Q&A 5560825, 2026-09-22 |
| LDAC | Not natively supported; same list | Microsoft Learn Q&A 5560825, 2026-09-22 |
| LC3 (LE Audio) | From Windows 11 22H2, gated on LE Audio-capable drivers from the manufacturer | Microsoft Support LE Audio guidance, 2026-09-22 |
What the documentation does and does not say
Microsoft's own Bluetooth support page is published at the profile level: A2DP 1.3.2 sits in the supported-profiles table, and the page carries no per-codec enumeration. The codec-level statements that do exist in Microsoft's domain come as answers to the driver question, quoted verbatim in the matrix above. The practical reading: a generic Bluetooth headphone on a stock Windows 11 box lands on SBC, with AAC negotiated where the stack takes it.
Two ways around the native ceiling
| Route | What it does | Source / as of |
|---|---|---|
| Third-party codec drivers | The documented path for aptX family and LDAC on Windows: "special drivers or external solutions" | Microsoft Learn Q&A, 2026-09-22 |
| USB transmitter dongle | The dongle owns the Bluetooth chain; the PC feeds it over USB. RTINGS runs aptX Adaptive on its bench exactly this way, via a BT-W5 | RTINGS latency research, 2026-09-22 |
The dongle route has a latency dividend too: RTINGS measured 13 ms over wired USB and 23 ms over a wireless dongle on one headset, against 160 ms for a SBC link on Windows 11 in the AirPods Pro 2 comparison, a product-specific number but a fair picture of the gap. The general fixes live in our Bluetooth audio delay guide.
An aptX- or LDAC-rated headphone does not get those codecs from a stock PC, the ceiling is the PC's native set unless you add drivers or a dongle. The same logic in reverse makes a receiver's wide codec list useful mainly for phone sources like the [Xiaomi](/compatibility/xiaomi) flagships.
FAQ
Not natively. The documented answer names LDAC among the advanced codecs that "are not natively supported in Windows 11" and "require special drivers or external solutions." Third-party drivers exist; without one, a PC-to-headphone LDAC pairing falls back to SBC or AAC.
Because the dongle carries its own transmitter chain. RTINGS measures aptX Adaptive on Windows through a BT-W5 USB dongle and notes it may be more efficient than a smartphone source. The PC sends audio to the dongle over USB; the Bluetooth link and its codecs live inside the dongle.
SBC and AAC. SBC by default, AAC where the stack negotiates it. Microsoft's Bluetooth documentation is published at the profile level, A2DP among supported profiles, without a per-codec table, so the exact pick is not documented first-party and lands in practice on SBC for most generic headphones.
From Windows 11 22H2, with driver requirements attached: the support guidance says devices need LE Audio-capable drivers from the manufacturer. LC3, the LE Audio codec, therefore arrives per-device instead of as a blanket switch.
blafili B3 Bluetooth Receiver
XLR, RCA, optical and coax outputs with an OLED front panel, built on the QCC5125 + ES9018K2M platform. A wired amp or receiver, put on a wireless source.
- Microsoft Learn Q&A, Bluetooth codecs supported in Windows 11, verbatim: "Advanced codecs like aptX HD, aptX Adaptive, aptX Lossless, and LDAC are not natively supported in Windows 11. These require special drivers or external solutions." learn.microsoft.com/en-us/answers/questions/5560825/, accessed 2026-09-22
- Microsoft Learn, General Bluetooth support in Windows: supported-profile table including Advanced Audio Distribution Profile A2DP 1.3.2; the document is profile-level and publishes no codec enumeration. learn.microsoft.com/en-us/windows-hardware/drivers/bluetooth/general-bluetooth-support-in-windows, accessed 2026-09-22
- RTINGS, Test Bench 1.6 latency research: "While Windows 11 introduced support for AAC, it uses xHE-AAC"; AirPods Pro (2nd gen) context "around 45ms on macOS compared to 160ms on SBC/W11"; aptX Adaptive measured via "the newer BT-W5 dongle we use is more efficient than the smartphone." rtings.com/headphones/learn/research/latency, accessed 2026-09-22
- Microsoft Support, check if a Windows 11 device supports Bluetooth LE Audio: Windows 11 22H2 or later with LE Audio capable drivers from the manufacturer (accessed via archived copy; live page intermittently unreachable). support.microsoft.com, accessed 2026-09-22
- Bluetooth SIG, A2DP 1.3.2 Section 4.2.1: SBC mandatory in sources and sinks. bluetooth.com/specifications/specs/advanced-audio-distribution-profile-1-3-2/, accessed 2026-09-22