LDAC, aptX Lossless, LHDC and Auracast: What Each One Actually Does

Look at the box of almost any wireless headphone, earbud or Bluetooth dongle sold today and you will find a row of acronyms: SBC, AAC, aptX, aptX Adaptive, aptX Lossless, LDAC, LHDC, LC3, Auracast. The list keeps growing, and it has migrated downmarket fast — Questyle's $99 QCC Dongle Pro2, which we covered in August, arrives with Bluetooth 6.1, LHDC V5 and Auracast, a longer codec roster than plenty of dedicated players carried a few years ago.

The question readers keep asking is narrower than the marketing: which of these differences change what you hear, and which only change the specification sheet? What follows lays out what each one actually does, using the codec owners' own documentation, and flags where the number on the box is a ceiling rather than a promise.

Start here: a codec only exists if both ends support it

This is the most common misunderstanding in the whole subject, and it is worth settling before any discussion of bitrate. A Bluetooth codec is a negotiation between two devices. The transmitter offers what it supports, the receiver offers what it supports, and the link runs on the best codec both have in common. If your headphones support LDAC and your phone does not, you are not listening to LDAC — you are listening to whatever fallback both ends share, typically SBC or AAC.

Platform support differs, and it differs by handset and by operating system version, not just by brand. So the headline codec printed on a pair of headphones is conditional. It describes a capability the headphone brings to the negotiation, not a state your system is guaranteed to reach. Before treating a codec as a reason to choose one product over another, the useful check is whether the source you actually use every day speaks the same language.

LDAC: three steps, chosen for you

Sony introduced LDAC in 2015 and it remains the most visible high-bitrate name in the category. It is a lossy coding technology, despite being marketed in the same breath as high-resolution audio. It operates at three discrete constant-bitrate steps: 330, 660 and 990 kbps at 96 and 48 kHz, and 303, 606 and 909 kbps at 88.2 and 44.1 kHz, with bit depths of 16, 24 or 32.

The detail that matters in practice is the default behaviour. LDAC runs in "Best Effort" mode, moving between those three steps according to how strong the connection is. A device advertising 990 kbps is therefore not necessarily transmitting at 990 kbps at any given moment — on a crowded train platform it may well be sitting on the lowest rung. The rate can be pinned manually on some platforms, including Android developer settings, Sony's own devices, and PipeWire on Linux, but the out-of-the-box state is adaptive.

aptX Lossless: lossless as a best case

Qualcomm's aptX Lossless is a capability of aptX Adaptive within Snapdragon Sound, designed to deliver bit-for-bit 16-bit/44.1 kHz CD-quality audio over Bluetooth at rates up to roughly 1,200 kbps. Qualcomm also states that the link scales down to 140 kbps in congested RF environments to avoid dropouts.

Both figures deserve equal billing. CD PCM is 1,411 kbps, and the ceiling here is 1,200 kbps, so lossless compression is doing genuine work to squeeze the data through the pipe — this is mathematically lossless, not uncompressed. And the 140 kbps floor means "lossless" describes the best case the link can reach, not a state it holds continuously. As with LDAC, supported hardware is required at both ends.

LHDC V5: the high-ceiling outsider

LHDC, developed by Savitech, is lossy and supports bitrates from 160 to 1000 kbps, against SBC's 345 kbps. It handles sample rates up to 192 kHz and bit depths up to 24-bit. Version 5, the latest, adds a 1 MB/s maximum transmission rate and the format's first support for 24-bit/192 kHz.

One point of confusion worth heading off: LLAC is a related low-latency variant running at 400 or 600 kbps, up to 24-bit/48 kHz, with roughly 30 ms latency. Those 400/600 kbps figures belong to LLAC, not to LHDC proper, and they turn up misattributed regularly.

LC3: the codec you will probably end up using

LC3 is the codec with the lowest public profile and quite possibly the widest future footprint, because it is the mandatory codec of Bluetooth LE Audio, which is built on Bluetooth 5.2 and 5.3. Any LE Audio device supports it by definition.

Its interest lies in efficiency rather than a headline bitrate. In the Bluetooth SIG's own characterisation listening tests, LC3 at 160 kbps scored higher than SBC at 345 kbps — better rated quality at under half the data rate. The white paper's summary of intrinsic quality is that LC3 was not worse than SBC at twice the bitrate. Those results come from the SIG, whose codec it is, and should be read with that in mind; but the direction of travel is clear enough, and it undercuts the assumption that a bigger number is automatically the better link.

Auracast is not a codec

This is the category error the whole comparison exists to correct. Auracast does not compete with LDAC or aptX Lossless on fidelity, because it is not a codec at all — it is a broadcast topology. The Bluetooth SIG describes it as a capability that lets audio be shared from a single transmitter to an unlimited number of receivers, without pairing.

Its stated use cases are social and public rather than audiophile: sharing audio with other people, unmuting silent televisions in gyms, bars and waiting areas, and next-generation assistive listening positioned as a successor to inductive loop systems. Multiple receivers join one transmitter without going through Bluetooth pairing first, which opens up museum guides, simultaneous translation, and announcements in airports and transport hubs.

Auracast changes how many people can receive one stream. It does not change the fidelity of the stream, and seeing it listed alongside three codecs on a spec sheet is exactly how the confusion starts.

Ceilings, not operating points

If there is one habit to carry away from this, it is reading advertised bitrates as ceilings. LDAC's Best Effort mode steps down as the connection weakens. aptX Lossless drops as far as 140 kbps under RF congestion. Both are documented by the people who make them. A codec's peak rate describes what the link can do in good conditions with a cooperative source at the other end — a commuter train, a busy office and a quiet room at home are not the same radio environment, and the same headphones will behave differently in each.

The other half of the honest answer is the part codec tables never show: the wireless link is one link in a chain that also includes the recording, the file you are streaming, the transducer, and — for in-ears especially — whether you have a proper seal. A poor tip fit will alter the sound more dramatically and more reproducibly than any difference between two high-bitrate codecs, and it costs nothing to correct. Independent blind listening evidence comparing codecs at matched levels is thinner than the marketing implies, and mostly small-sample, so anyone claiming a settled hierarchy is going beyond the published record.

None of that makes codec support irrelevant. Latency matters for video and games. Connection stability matters on a commute. Auracast matters if you want shared or assistive listening. LC3 matters because LE Audio devices will use it whether you asked for it or not. Those are concrete, checkable capabilities. Just be clear about which column a given acronym belongs in — and check that the phone in your pocket supports it before the number on the box means anything at all.

Frequently asked questions

Does the Bluetooth codec matter more than the headphones themselves?

The Bluetooth codec is one link in a chain that also includes the recording, the source file, the transducer and, for in-ears, the seal of the eartips. A poor fit changes the sound more dramatically and more repeatably than the difference between two high-bitrate codecs. Independent blind listening evidence comparing codecs at matched levels remains thin and mostly small-sample.

Why doesn't my phone use the codec my headphones support?

A Bluetooth codec is negotiated between two devices: the link runs on the best codec both the source and the receiver support. If headphones support LDAC or LHDC but the phone does not, the connection falls back to a shared codec such as SBC or AAC. Platform support varies by handset and operating system version.

Is Auracast a sound quality feature?

Auracast is not a codec and does not affect fidelity. The Bluetooth SIG describes it as a broadcast capability that shares audio from one transmitter to an unlimited number of receivers without pairing. Stated uses include sharing audio with others, unmuting silent TVs in public spaces, assistive listening, museum guides, translation and transport announcements.

Does LDAC always transmit at 990 kbps?

No. LDAC operates at three discrete steps — 330, 660 and 990 kbps at 96/48 kHz, or 303, 606 and 909 kbps at 88.2/44.1 kHz — and by default runs in Best Effort mode, switching between them according to connection strength. The rate can be pinned manually on Android developer settings, Sony devices and PipeWire on Linux.

Is aptX Lossless genuinely lossless over Bluetooth?

Qualcomm designed aptX Lossless to deliver bit-for-bit 16-bit/44.1 kHz CD-quality audio at up to roughly 1,200 kbps. CD PCM is 1,411 kbps, so the result is mathematically lossless rather than uncompressed. Qualcomm also states the link scales down to 140 kbps in congested RF environments, making lossless the best case rather than a constant state.

This article was written by an AI system from Into The HiFi AI Desk, generated from the following sources, with no human editing pass before publication: LDAC (codec) — Wikipedia, Qualcomm says aptX Lossless can deliver lossless CD-quality audio over Bluetooth — What Hi-Fi?, LHDC (codec) — Wikipedia, A Technical Overview of LC3 — Bluetooth SIG, LC3 Characterization White Paper — Bluetooth SIG, LE Audio — Wikipedia, Auracast Broadcast Audio — Bluetooth SIG.