Does Bluetooth Ruin Lossless Audio?
9 Eylül 2026
Every Bluetooth codec re-encodes your file on the way to your headphones. Here's what each one carries, which ones you can actually hear, and how to check what your phone is doing.
Yeah, pretty much. Bluetooth decodes your file and squashes it again before sending it, so a FLAC played over SBC, AAC, aptX or LDAC lands in your ears lossy. aptX Lossless is the one exception, and only on matching hardware with a clean connection. The good news is the loss stops mattering somewhere around aptX HD.
What actually happens between your phone and your earbuds
There is no version of this where the file goes over the air untouched. Your player decodes the FLAC or MP3 into raw audio, hands it to the phone's Bluetooth stack, and the stack re-encodes it with whatever codec the two devices shook hands on when they paired. The earbuds decode that second copy and push it to their amp.
So your file format sets one ceiling and the Bluetooth codec sets a second, lower one. That second encode is where the whole "lossless over Bluetooth" pitch quietly dies. You're not streaming a file. You're streaming a fresh compression of it, made in real time by a chip running on a battery the size of a coin.
The reason is bandwidth, and the math is not close. A2DP, the profile every wireless headphone uses for music, gets you somewhere under 1Mbps of usable throughput once retransmissions and everything else on the radio take their cut. CD audio uncompressed is 1,411kbps. It was never going to fit, which is why every codec below is an argument about where to spend the bits you do have.
Worth saying out loud before the spec tables start: if your source file is already a 256kbps AAC, the Bluetooth encode is lossy compression stacked on lossy compression. That's your actual quality problem, and it's a bigger one than any codec choice.
The Bluetooth codecs, and what each one carries
| Codec | Max bitrate | Max resolution | Lossless | Support |
|---|---|---|---|---|
| SBC | ~328 kbps typical | 16-bit/48kHz | No | Mandatory, every device |
| SBC XQ | ~452-576 kbps | 16-bit/44.1kHz | No | Unofficial, patchy |
| AAC | ~250-320 kbps | 16-bit/48kHz | No | Apple, most Android, most earbuds |
| aptX | 352 kbps | 16-bit/48kHz | No | Qualcomm phones and headphones |
| aptX HD | 576 kbps | 24-bit/48kHz | No | Qualcomm, mid-range and up |
| aptX Adaptive | 279-420 kbps, up to 620 kbps | 24-bit/96kHz | No | Newer Qualcomm hardware |
| aptX Lossless | up to 1.2 Mbps | 16-bit/44.1kHz | Yes, when the link holds | Snapdragon Sound devices only |
| LDAC | 330 / 660 / 990 kbps | 24-bit/96kHz | No | Sony, and all Android 8.0+ |
| LHDC / LHDC 5 | up to 900 kbps / 1 Mbps | 24-bit/192kHz | No | Some Android phones, few earbuds |
| LC3 | ~160-345 kbps | 24-bit/48kHz | No | Bluetooth LE Audio devices |
Numbers are the codec vendors' own. The aptX Adaptive and LHDC 5 ceilings, both have moved across versions.
Some of those rows need a translation.
SBC is the one every Bluetooth audio device is required by law to support, and the thing you fall back to when two devices can't agree on anything nicer. Its terrible reputation is about half earned. Default configurations really are mediocre, but the codec scales up fine, and a well-tuned SBC link gets much closer to the fancy codecs than anyone selling a fancy codec wants to tell you. The catch is that you don't pick the tuning. The pairing does, and it doesn't ask.
AAC is where it gets political. On Apple hardware it's genuinely good, because Apple owns the encoder on both ends and has spent years tuning it. On Android it's been a lottery for years, with some manufacturers shipping encoders that ran well below what the codec can do. Newer Android versions handle it better, but "AAC on Android" still doesn't mean one specific thing the way "aptX HD" does.
LDAC is Sony's, and most people have it because Google folded it into Android 8.0 and up. The part that matters is those three rates. 990kbps is the number on the box, it needs a clean and close connection to hold, and your phone will quietly slide down to 660 or 330 the second the link gets rough. Left on adaptive it'll change rate mid-song and never mention it. LDAC at 330kbps is not obviously beating a decent AAC connection.
aptX Lossless is the only real lossless option here, and the asterisks are doing heavy lifting. It tops out at CD resolution, 16-bit/44.1kHz, so not hi-res. It wants Snapdragon Sound certification on the phone and the headphones, which is a far shorter list than "supports aptX." And it bails out of lossless mode when the airwaves get busy, which on a train or in an office is most of the time.
LC3 is the codec for LE Audio. Its whole trick is efficiency instead of a big number: it aims to beat SBC at roughly half the bitrate, which buys you battery life and streaming to multiple devices, not fidelity headroom. Good codec. Not the one to chase for sound.
So can you actually hear any of this?
Below about 300kbps, yes, and you won't have to concentrate. A badly configured SBC connection smears cymbals and reverb tails the same way a 128kbps MP3 does.
Above that it gets small fast and then it stops. The gap between aptX HD at 576kbps and LDAC at 990kbps is not something most people pick out reliably on earbuds, and the reasons have nothing to do with codecs. Wireless earbuds have tiny drivers, tiny amps, and a fit that leaks bass differently depending on how you shoved them in this morning. That last one moves the sound more than a codec swap does.
Then there's where you're listening, which is the part everyone skips. Bluetooth is a commute format. Bus noise, traffic, an air conditioner, a gym's awful ceiling speakers, all of it eats exactly the quiet detail those extra bits were protecting. It's the same reason the useful ceiling for lossy files sits around 256kbps AAC. Past a point you're paying for data the situation destroys on arrival.
So: codec choice matters up to a threshold and then turns into a spec-sheet argument. If your phone and headphones agree on LDAC, aptX HD, aptX Adaptive, or a properly built AAC, you already have basically all the quality that's available to you. Chasing the next codec tier is worth less than buying better earbuds or getting the eartips to seal.
What Bluetooth actually costs you
Latency is the real one. Every codec buffers, encodes, transmits and decodes, and all of that is delay. It's why video drifts out of sync and why nobody sane plays a rhythm game on wireless earbuds. aptX Adaptive and LC3 handle it better than SBC and LDAC, and LDAC at 990kbps is the worst of the lot.
Battery is the other. Higher bitrate means more radio time and more encoding work on both ends, and LDAC at full rate noticeably shortens earbud runtime next to AAC or SBC.
And stability. High-rate LDAC in a crowded 2.4GHz environment, meaning any city, drops rate constantly. A steady 660kbps beats a 990kbps that keeps hiccuping every time someone walks past with a microwave.
How to check which codec you're actually on
On Android it's hiding in developer options.
- →Settings > About phone, tap Build number seven times.
- →Settings > System > Developer options.
- →Connect your headphones and start playing something. The codec settings do nothing unless audio is running.
- →Bluetooth audio codec shows the active one and lets you force a different one, from the list both devices support.
- →Bluetooth audio LDAC codec playback preference picks LDAC's target: connection priority (330kbps), sound quality priority (990kbps), or adaptive.
If a codec is greyed out, one of the two devices doesn't support it and there is no clever workaround. Codec support is negotiated at connection time between the phone's Bluetooth chip and the headphones', not chosen by the music app.
Which catches a lot of people out, so: switching music apps will not change your Bluetooth codec. Any app advertising better Bluetooth sound quality is doing something else, and that something else is usually an equalizer.
What to do about it
Keep your library in FLAC or high-bitrate lossy and stop worrying about the wireless leg. The file is the thing you keep for years and re-encode from. The Bluetooth copy is thrown away and rebuilt every time you hit play. Downgrading your library to match your earbuds is optimizing the wrong end, and the day you plug in wired headphones or move the files somewhere better, you'll want the good version back. Same argument as buying DRM-free files instead of renting a stream.
Match your hardware if you're buying new. Sony phone plus Sony earbuds gets you LDAC working properly. A Qualcomm phone plus Snapdragon Sound earbuds gets you aptX working properly. Mixing brands usually dumps you on AAC or SBC, which is fine, just a lower ceiling than the box implied.
And if you actually care about a specific album, plug in. A cheap USB-C DAC dongle skips the whole Bluetooth conversation, and it's the only way your lossless files reach your ears as files instead of as a re-encode.
Key takeaways
- →Every mainstream Bluetooth codec re-encodes your audio. Playing a FLAC over Bluetooth does not send a lossless signal to your headphones.
- →aptX Lossless is the only true lossless option, caps at CD quality, and needs Snapdragon Sound on both ends plus a clean connection.
- →LDAC's 990kbps is a best case. It slides to 660 or 330kbps on a busy link, usually without telling you.
- →Codec differences are obvious below roughly 300kbps and very hard to hear above it. Earbud fit and background noise matter more than which tier you're on.
- →Higher-rate codecs cost you latency and battery, and drop out more in crowded radio environments.
- →Check the active codec in Android developer options. No music app can change it.
FAQ
Is LDAC actually lossless?
No. Sony markets it around hi-res support, and it does carry 24-bit/96kHz audio, but it's lossy at all three of its bitrates. It throws data away on the way out and can't put it back on the way in.
Should I convert my FLAC files to MP3 if I only use Bluetooth?
Only if you're out of storage. Converting doesn't improve the Bluetooth encode one bit, and it permanently limits what you can do with those files later. If you do need the space, go 256kbps AAC or 320kbps MP3 and keep the FLACs somewhere else. More on that in FLAC vs MP3 vs AAC.
Why does my phone say LDAC but my old wired headphones sound better?
Because the codec is one link in a chain that also includes drivers, an amplifier, tuning, and how well the things seal in your ear. Wired headphones skip the wireless encode entirely and usually have room for better hardware. A high-end codec on mediocre earbuds still sounds like mediocre earbuds.
Does the music app I use affect Bluetooth sound quality?
Not the codec. That's settled between the phone's Bluetooth stack and the headphones. An app can affect what it feeds the stack, through resampling, EQ, or gain, but it cannot pick or override the codec.
Is aptX better than AAC?
On Android, usually, because AAC encoder quality varies by manufacturer while aptX is a fixed Qualcomm implementation. On Apple hardware AAC is done properly and the gap basically vanishes. Neither is far enough ahead to pick your headphones over.
Does Bluetooth 5.3 or 6.0 improve audio quality?
Not directly. The Bluetooth version affects range, power use, and whether you get LE Audio and LC3. It does nothing to the bitrate available to the classic A2DP codecs. A newer number on the box changes nothing about how your music sounds.
Bluetooth caps what leaves your phone, so the only part still worth controlling is what's sitting on it. NeoMusic plays FLAC and every common lossy format through Media3/ExoPlayer, with a real 16-band spectrum visualizer and a built-in EQ, free, no account, no ads, about 5MB installed. If your FLAC files won't open at all, how to play FLAC on Android covers the usual suspects, and the roundup of offline Android players compares eight of them.