How to Switch Bluetooth Audio to a High-Quality Codec (LDAC/AAC) on Linux

Your headphones support LDAC or AAC, the box promises high-resolution audio, but on Linux they quietly connect with the basic SBC codec. Music sounds flat, and you have no idea whether you are getting the quality you paid for. The frustrating part is that nothing looks broken.

Linux can absolutely use high-quality Bluetooth codecs. PipeWire supports LDAC, AAC, aptX, and improved SBC modes on most modern systems, but support depends on your headphones, your Bluetooth adapter, and a few settings. This guide shows you how to check the codec you are using now, switch to a better one, make the change stick, and understand the honest limits of Bluetooth audio quality.

Quick Answer

Check your current codec with pw-dump or in the headphone settings shown by your desktop, then select LDAC or AAC from the profile or codec menu in Sound settings or pavucontrol if your headphones support it. On PipeWire systems the option appears automatically when both sides support the codec. If it is missing, install the full PipeWire Bluetooth support and restart the audio services.

Bluetooth Codecs Explained in Plain English

A codec is the method used to compress music for the trip from your computer to your headphones, and to unpack it at the other end. Better codecs waste less of the music.

The Main Codecs You Will See

• SBC: The universal fallback every Bluetooth audio device supports. Basic SBC sounds acceptable, but it is the lowest common denominator.
• AAC: Common on Apple-style devices and many modern headphones. On Linux it can sound very good, and it is often the best option for headphones designed around AAC.
• aptX and aptX HD: Qualcomm codecs found on many Android-focused headphones. aptX HD carries more data than standard aptX.
• LDAC: Sony’s high-bitrate codec, capable of up to 990 kbps. When it works at its top rate, it is the closest Bluetooth gets to wired quality.
• SBC XQ: An improved high-bitrate SBC mode in PipeWire that squeezes much better sound from ordinary headphones that lack fancy codecs.

Both Ends Must Agree

Your headphones and your computer negotiate the best codec they both support. If the headphones only offer SBC and AAC, LDAC will never appear, whatever you install. Check the headphone specifications first, and remember that many models switch to a basic mode whenever the microphone is used.

Step 1: Check Which Codec You Are Using Now

1. Connect your headphones and play some music, so the audio connection is fully active.
2. Open a terminal and run wpctl status to confirm the headphones are the active output.
3. Run pw-dump | grep -A5 bluez and look for the codec name in the output, or use pw-cli list-objects for a fuller view.
4. On GNOME, some versions show the codec in Settings > Sound after selecting the device, or in the quick settings audio panel.
5. In pavucontrol, the Configuration tab shows the active profile, which often includes the codec name.

Write down what you find before changing anything. If it already says LDAC or AAC, your system was working correctly and any sound problem lies elsewhere, such as bitrate drops caused by interference.

Step 2: Make Sure PipeWire Has Full Codec Support

Most current Ubuntu, Fedora, and Arch-based systems include the codecs by default. Problems usually come from partial installs or older setups.

1. Confirm you are running PipeWire with pactl info. The server name should mention PipeWire.
2. On Ubuntu and Debian-based systems, install the Bluetooth audio support with sudo apt install pipewire pipewire-audio-client-libraries libspa-0.2-bluetooth.
3. On Fedora, the equivalent support is normally present, and you can verify the package with rpm -q pipewire-codec-aptx on systems where aptX support is packaged separately.
4. Restart the audio stack with systemctl --user restart pipewire wireplumber.
5. Disconnect and reconnect the headphones so they renegotiate codecs with the updated stack.

Legal and packaging rules mean a few distributions ship some codecs in separate repositories. If a codec is genuinely missing after these steps, check your distribution’s multimedia documentation rather than downloading random packages. The configuration examples in the PipeWire project wiki show how WirePlumber exposes Bluetooth codec choices on modern systems.

Step 3: Switch the Codec

On a healthy PipeWire system, switching takes less than a minute.

1. Connect the headphones and make sure no call app is using the microphone, because headset mode blocks high-quality codecs.
2. Open Settings > Sound, select the headphones, and look for a codec or profile choice.
3. Choose LDAC if offered and your headphones support it, or AAC for AAC-focused models.
4. If Settings shows no codec choice, open pavucontrol, go to the Configuration tab, and select the profile that names your preferred codec.
5. Stop and restart playback, then verify the new codec with pw-dump again.
6. Listen to a familiar, well-produced track and compare. The difference is clearest in cymbals, voices, and busy passages.

If you prefer the terminal, WirePlumber settings can prioritise codecs through its configuration. Our guide to configuring PipeWire audio on Linux covers where those user settings live and how to edit them safely.

Step 4: Force a Preferred Codec Order in WirePlumber

When the system keeps choosing SBC even though better codecs exist, you can set a preference order.

1. Create the user config folder with mkdir -p ~/.config/wireplumber/wireplumber.conf.d.
2. Create a file such as ~/.config/wireplumber/wireplumber.conf.d/51-bluez.conf using nano.
3. Add a monitor.bluez.properties section listing your preferred codecs in order, following the exact syntax shown in the WirePlumber documentation for your version, for example putting ldac first, then aac, then sbc_xq, then sbc.
4. Save the file and restart with systemctl --user restart wireplumber pipewire.
5. Reconnect the headphones and verify the negotiated codec again.

Treat this as a preference, not magic. The headphones still decide what they accept, and a badly written config file can stop WirePlumber from starting. If audio disappears after editing, delete the new file and restart the services to return to defaults. The official WirePlumber documentation is the safest reference for the current config format, which changed between WirePlumber generations.

Step 5: Fix LDAC Dropping to Low Bitrate

LDAC adapts its bitrate to connection quality. In a crowded radio environment it may fall from 990 kbps to 330 kbps, which can sound worse than a stable AAC connection.

• Reduce interference: Move away from USB 3 hubs, unshielded cables, and microwave ovens, all of which disturb the 2.4 GHz band.
• Keep line of sight: LDAC at its top rate needs a strong signal. A laptop in another room is asking too much.
• Choose stability in the headphone app: Many LDAC headphones offer a sound quality versus connection stability setting in their phone app. That setting is stored on the headphones and affects Linux too.
• Accept AAC when it sounds better: A rock-solid AAC stream beats a struggling LDAC stream. Trust your ears over the spec sheet.
• Update firmware: Check for headphone and Bluetooth adapter firmware updates, which often improve codec negotiation.

Common Mistakes and Honest Tips

• Expecting LDAC with the microphone on: Headset mode uses a completely different profile. High-quality stereo codecs are for listening only.
• Buying a codec your headphones lack: No setting can add LDAC to SBC-only headphones. Check the specifications first.
• Judging by the label, not the sound: Codec names in menus show what was negotiated at connection time. Verify after playback starts.
• Editing system files instead of user files: Put WirePlumber overrides in your home config folder so updates do not erase them and mistakes are easy to undo.
• Chasing numbers: At the top rates, room noise and headphone quality matter more than the difference between good AAC and LDAC.
• Forgetting other connected devices: If the headphones are also connected to a phone, the phone may hold the high-quality profile. Disconnect the phone while testing.

Conclusion

Switching to LDAC or AAC on Linux is mostly about checking what you already have. Verify the active codec, confirm PipeWire has full Bluetooth support, pick the best codec your headphones genuinely offer, and set a preference order in WirePlumber only if the automatic choice disappoints you. Keep the signal strong, keep the microphone off while listening, and your headphones will finally deliver the sound quality you bought them for.

Frequently Asked Questions

Why is LDAC not showing as an option for my headphones?

Either the headphones do not support LDAC, the headset profile is active because an app is using the microphone, or your PipeWire install lacks the Bluetooth codec support package. Check the specifications and install the support packages first.

Is LDAC always better than AAC?

At its highest bitrate with a strong signal, LDAC carries more detail. In real rooms with interference, LDAC often drops its rate, and a stable AAC connection can sound better. Test both with music you know well.

What is SBC XQ and should I use it?

SBC XQ is PipeWire’s high-bitrate version of the universal SBC codec. If your headphones only support SBC, enabling SBC XQ is the easiest real quality upgrade available to you.

Why does the codec change back after every reboot?

The negotiation happens fresh at each connection. A WirePlumber preference file makes your choice the default order, but a phone connection or a call profile can still override it for that session.

Can I use LDAC and the headphone microphone at the same time?

No. Stereo music profiles and headset call profiles are separate in classic Bluetooth audio. When the microphone opens, the system switches to the headset profile and quality drops until the call ends.