foundations

PulseAudio or PipeWire? The two-minute check that decides everything

~/pulseaudio-vs-pipewire

By the TuxTone crew · Updated 2026-09-20 · PipeWire stable was 1.6.9 (released 2026-09-17) when we checked.

Every recommendation on this site forks on one question, and most people can't answer it about their own machine. That's not ignorance — it's a compliment to the engineering. The transition from PulseAudio to PipeWire was designed to be invisible, and it largely was. But "invisible" is exactly what makes stale advice so sticky: a 2021 tutorial and a 2026 desktop can look identical and need completely different software.

Run this

~$ pactl info | grep "Server Name"

Two possible answers, and they're unambiguous:

• Server Name: PulseAudio (on PipeWire 1.6.9) — you're on PipeWire. The parenthetical is the giveaway. PipeWire is answering, wearing PulseAudio's name so that older software keeps working.
• Server Name: pulseaudio — you're on genuine PulseAudio. No parenthetical, no PipeWire.

If pactl isn't installed, or you'd like a second opinion:

~$ # is the PipeWire user service running?
~$ systemctl --user status pipewire

~$ # PipeWire's own inventory — only exists on PipeWire
~$ wpctl status

~$ # what version, precisely
~$ pipewire --version

If wpctl returns a tree of devices and streams, the question is settled. If the command doesn't exist, you're almost certainly on PulseAudio.

What you're probably running, by distro

Mainstream desktop distributions moved years ago. Fedora led, switching to PipeWire for audio by default in Fedora 34; Ubuntu followed in 22.10; current Debian and Arch desktop installs land on PipeWire too, and the mainstream derivatives inherit that choice. Unless you're on a long-lived LTS install from the early 2020s, a deliberately minimal system, or a distro that made a point of staying put, PipeWire is the answer.

The interesting exceptions in 2026 are servers and long-uptime workstations — machines installed once, upgraded conservatively, never reinstalled. That is precisely the population still reaching for NoiseTorch, which is why we keep an honest page about it instead of writing it off.

The compatibility layer, and why it confuses people

PipeWire ships pipewire-pulse: a service that speaks the PulseAudio protocol so that the decade of software written against PulseAudio keeps working unmodified. This is why pactl still works, why old scripts still work, and why NoiseTorch — a PulseAudio-API application — can run on a PipeWire desktop at all.

It's also why the question feels slippery. Your system can be honestly described as "running PulseAudio" (the protocol) and "running PipeWire" (the actual server) in the same breath. For our purposes the distinction is sharp: native PipeWire tools need real PipeWire; PulseAudio-API tools work either way, through the compat layer. That's precisely why our scoring gives compat-layer paths 16 points for stack fit rather than the full 20 — they work, with a translation step and a dependency on that translation continuing to behave.

What to do with your answer

Should you migrate just for this?

No. We're a noise suppression site, not a distro-upgrade evangelist, and "reinstall your audio stack to get a slightly newer denoiser" is bad advice when the model underneath is the same model either way. If you're on PulseAudio and NoiseTorch works, you have a working setup.

Migrate when you were going to anyway — a distro upgrade, a fresh install, a new machine — and take the better-maintained tooling as a bonus rather than a motive. The one situation where we'd actively nudge you: if your PulseAudio box is old enough that you're also fighting Bluetooth headset profiles and device-switching bugs, PipeWire fixes a pile of those, and cleaner audio comes along for free.