PipeWire is the modern audio and video server for Linux that replaces PulseAudio and JACK, and this guide shows you how to install and configure it on most current distributions. You will learn the exact package names, the key configuration files, and how to set up routing, Bluetooth, and low-latency audio for professional work. By the end, you will have a working PipeWire setup with clear steps for troubleshooting common issues.
What Is PipeWire and Why It Matters
PipeWire was created by Wim Taymans at Red Hat and first released in 2017. It was designed to handle both audio and video streams with low latency, which makes it ideal for screen sharing, video conferencing, and digital audio workstations (DAWs). Unlike its predecessors, PipeWire can run alongside PulseAudio and JACK, and it provides a unified graph that lets you route audio between applications in a flexible way. Most major distributions—Fedora, Ubuntu (since 22.04), Debian (since 12), Arch, and openSUSE—now ship PipeWire as the default audio server, so if you are on a recent system you likely already have it.
The main advantage over PulseAudio is that PipeWire offers per-application volume control, low-latency monitoring, and a JACK-compatible API, so you can run pro-audio tools without needing a separate JACK server. It also handles Bluetooth audio more reliably, including support for the newer LC3 codec in recent versions.
How PipeWire Works: The Core Concepts
PipeWire runs as a system service (pipewire) and a session manager (pipewire-pulse) that emulates the PulseAudio server. It also provides a JACK client library (libjack) that redirects JACK applications to PipeWire. The audio data flows through a graph of nodes and links: each application creates a node that can have input and output ports, and you connect these ports to route audio. The session manager (WirePlumber, since PipeWire 0.3.40) automatically creates links based on your configuration and device priorities.
Configuration files live in /usr/share/pipewire/ (system defaults) and ~/.config/pipewire/ (user overrides). You should never edit the system files directly; instead, copy them to your user directory and edit the copies. The main files are pipewire.conf (server settings), pipewire-pulse.conf (PulseAudio compatibility), and client.conf (client defaults). For advanced routing, you can use tools like pw-cli, pw-link, or graphical interfaces like qpwgraph.
Installing PipeWire on Major Distributions
Here are the commands to install PipeWire on the most common distributions. If you are using a distro that already has it, these commands will simply update it to the latest version.
- Debian/Ubuntu:
sudo apt install pipewire pipewire-pulse wireplumber - Fedora:
sudo dnf install pipewire pipewire-pulse wireplumber - Arch Linux:
sudo pacman -S pipewire pipewire-pulse wireplumber - openSUSE:
sudo zypper install pipewire pipewire-pulse wireplumber - Gentoo:
sudo emerge --ask media-sound/pipewire media-sound/wireplumber
After installation, you may need to enable the user service (if it isn’t already): systemctl --user enable --now pipewire pipewire-pulse wireplumber. On most systems, the package installation automatically replaces PulseAudio, but if you are switching from an existing PulseAudio setup, you might need to remove the pulseaudio package and its user service. A reboot is often the cleanest way to ensure all services start correctly.
Configuring PipeWire: The Essential Steps
Once installed, you can configure PipeWire to suit your needs. The most common tasks are setting the default sample rate, enabling low-latency mode, and adjusting Bluetooth codecs.
- Create your user config directory:
mkdir -p ~/.config/pipewire - Copy the default config files:
cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire/and do the same forpipewire-pulse.confandclient.confif they exist. - Edit
pipewire.conf: Find thecontext.propertiessection. To change the default sample rate, setdefault.clock.rate = 48000(or 44100). For low latency, setdefault.clock.quantum = 256(lower values like 64 or 128 reduce latency but increase CPU usage). - Edit
pipewire-pulse.conf: Undercontext.modules, you can adjust thepulse.cmdmodule options, but most users don’t need to touch this. - Restart PipeWire:
systemctl --user restart pipewire pipewire-pulse wireplumber
For Bluetooth, you can select the codec by editing ~/.config/wireplumber/wireplumber.conf.d/50-bluetooth.conf and setting bluez5.codecs = [sbc sbc_xq aac ldac aptx aptx_hd aptx_ll aptx_ll_duplex]. You can also enable LDAC or AptX if your hardware supports it. Remember to restart WirePlumber after changes.
Choosing Between PipeWire, PulseAudio, and JACK
If you are on a modern Linux system, PipeWire is almost always the best choice because it is a drop-in replacement for PulseAudio and offers JACK compatibility. However, some legacy setups or specialized pro-audio environments still use JACK directly. Here is a quick comparison:
- PipeWire: Best for everyday use, Bluetooth, video conferencing, and light pro-audio. Low latency when configured, but not as low as a dedicated JACK setup.
- PulseAudio: Older, stable, but lacks low-latency features and has issues with Bluetooth and multi-device routing. Still used on older distros.
- JACK: The classic pro-audio server with the lowest latency, but it is not user-friendly and requires manual configuration. PipeWire can emulate it, so you rarely need real JACK anymore.
For most users, the answer is simply: use PipeWire. If you are a musician with a dedicated audio interface and need absolute minimum latency, you can still use JACK, but PipeWire with a quantum of 64 or 128 is often sufficient.
Common Problems and How to Fix Them
Here are the most frequent issues users encounter and their solutions.
- No sound after upgrade: Try
systemctl --user restart pipewire pipewire-pulse wireplumber. If that fails, check if PulseAudio is still running:systemctl --user status pulseaudio. If it is, stop it and disable it. - Bluetooth device connects but no audio: Ensure the device is set as the default sink in your sound settings. You can also use
pactl set-default-sink bluez_output.XX_XX_XX_XX_XX_XX.1. If the codec is the issue, edit the WirePlumber config to enable a different codec. - Applications don’t see PipeWire: Some apps expect PulseAudio. Make sure
pipewire-pulseis running and that thepulseaudiopackage is removed or masked. You can test withpactl info. - High latency in DAWs: Lower the quantum in
pipewire.conf(e.g., set to 128 or 64) and also setdefault.clock.min-quantum = 64. Ensure your CPU governor is set to performance mode. - Microphone not working: Check input levels with
pavucontroland ensure the correct source is selected. If using a USB mic, try a different USB port.
Comparing PipeWire to Alternatives
Besides PulseAudio and JACK, there is also the newer PulseAudio-compatible server from the PipeWire project (which is just PipeWire itself) and the JACK2 implementation. In practice, you are choosing between PipeWire and JACK. PipeWire is more modern, easier to configure, and handles Bluetooth and video streams, while JACK is more mature for ultra-low-latency audio but requires manual setup. There is also ALSA, which is the kernel-level sound system; PipeWire sits on top of ALSA and provides the user-space mixing and routing.
Costs and Safety
PipeWire is completely free and open-source software, licensed under the MIT and Apache 2.0 licenses. There are no costs associated with installing or using it. As for safety, PipeWire is a standard system component and is safe to install from your distribution’s official repositories. The only risk is misconfiguration, which could break your audio, but you can always revert by deleting your user config files or reinstalling the packages. Always back up your configuration before making changes.
Frequently Asked Questions
How do I check if PipeWire is already installed?
Run pactl info and look for “Server Name: PulseAudio (on PipeWire …)”. If you see that, PipeWire is running. You can also run systemctl --user status pipewire to see the service status.
Can I use PipeWire with JACK applications?
Yes. PipeWire provides a JACK compatibility layer. Install pipewire-jack (or libjack-pipewire on some distros) and JACK apps will automatically use PipeWire. You can then route audio with pw-jack or qpwgraph.
Why is my Bluetooth audio stuttering?
Stuttering is often caused by Wi-Fi interference or a poor codec. Try switching to a more stable codec like SBC-XQ or AAC. You can also disable Wi-Fi on the 2.4 GHz band or use a 5 GHz connection if possible.
How do I set the default sample rate to 44100 Hz?
Edit ~/.config/pipewire/pipewire.conf and set default.clock.rate = 44100. Then restart PipeWire. Note that some devices may not support that rate, so you may need to also set default.clock.allowed-rates = [44100 48000].
Does PipeWire support Dolby Atmos or surround sound?
PipeWire supports up to 7.1 surround sound and can pass through compressed formats like Dolby Digital and DTS if your hardware and receiver support them. However, Dolby Atmos object-based audio is not fully supported in Linux due to licensing and implementation complexity.
Can I run PipeWire and PulseAudio at the same time?
No, they would conflict on the same socket. You must choose one. If you want to switch back to PulseAudio, remove the pipewire-pulse package and reinstall pulseaudio. It is not recommended to run both simultaneously.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Windows 11 Calendar Wrong Day? Fix It Here
- How to Use curl Command in Linux
- Install ChromeOS: Convert Laptop to Chromebook
- Fix OneNote App Not Working on Android
- Move Games to SSD Without Reinstalling
- Move Windows 11 Taskbar to Top or Side: Easy Steps