pavucontrol Alternatives for Linux Audio Routing

Immediate answer

The best direct replacement for pavucontrol on a modern PipeWire system is pwvucontrol. It follows the same volume-control purpose and familiar per-application, per-device layout while using the native PipeWire interface instead of the PulseAudio compatibility layer. For graph-style routing and patchbay work, Helvum and qpwgraph provide views that pavucontrol was never designed to offer.

The qualification is that no single tool replaces every part of pavucontrol on every stack. If the system still runs PulseAudio, pwvucontrol will not be the appropriate choice. If the need is only for per-stream volume and device selection, pavucontrol itself remains widely available, but PipeWire users gain more coherent behavior from a native control tool.

Choosing the right alternative

The alternatives differ mainly in scope: simple mixer controls versus connection editors, and graphical tools versus scripts. The best choice depends on whether the workflow is everyday volume management, deliberate audio routing between applications, or repeatable setup that should be expressible as configuration.

Tool	Typical role	Best-fit situation
pwvucontrol	Native PipeWire mixer	Direct replacement for pavucontrol volume and device switching on PipeWire
Helvum	PipeWire graph and patchbay	Inspecting or changing live connections between nodes
qpwgraph	Graph editor with persistence	Managing complex routing and saving session-style connection arrangements
wpctl	Command-line WirePlumber control	Scriptable device and node control without a GUI
pactl	PulseAudio compatibility command	PipeWire with pipewire-pulse, scripts, or systems still using PulseAudio

For a straightforward volume mixer, pwvucontrol is the closest alternative. Helvum is more appropriate when the user needs to see route connections as a graph, while qpwgraph is favored when those connections must be restored conveniently. Command-line tools suit headless systems, scripts, and keyboard-driven setups.

What pwvucontrol offers

pwvucontrol is a GTK-based mixer that directly targets PipeWire through the pw library. It presents output and input devices together with per-application streams, allowing users to adjust volumes, mute streams, and move a playback stream between devices.

Because it does not depend on the pipewire-pulse compatibility server, it can operate in a PipeWire session where pavucontrol would still work through the PulseAudio-compatible layer but would represent that compatibility path rather than the native WirePlumber session manager.

pwvucontrol vs pavucontrol

The comparison is valid only when both tools are considered on the same PipeWire system, because pavucontrol uses the PulseAudio protocol view exposed by pipewire-pulse. In that condition, pwvucontrol provides the familiar mixer interaction with a native PipeWire connection. pavucontrol brings maturity and long-standing distribution support, while pwvucontrol is the more aligned choice for a system that intentionally runs PipeWire and WirePlumber.

A direct feature-for-feature equivalence should not be assumed. pavucontrol includes additional panels and settings tied to the PulseAudio server model, and not every panel has a one-to-one equivalent in pwvucontrol. The relevant difference is the stack the tool talks to, not only the visual layout.

Graph-based alternatives

Helvum displays the PipeWire graph of nodes, ports, and links. It allows users to connect and disconnect ports interactively. This is a different mental model from pavucontrol: instead of choosing a stream and assigning it to a sink, the user sees the actual node topology and edits connections.

qpwgraph expands that model with named configurations and session-oriented graph handling. For users who repeatedly build the same studio-style routing layout, qpwgraph offers persistence features that are more practical than reconnecting every node by hand after each application start.

A caveat is that graph editing bypasses the policy layer that WirePlumber normally applies. Connections created this way can conflict with automatic device or stream handling, so graph tools are best used with deliberate routing intent and an understanding that they expose more direct control than a mixer-style tool.

Command-line alternatives

wpctl is the WirePlumber control utility. It can list devices and nodes, set volume and mute state, and change the default sink or source. It is suitable for headless systems and for embedding audio changes in scripts.

wpctl status
wpctl set-volume @DEFAULT_AUDIO_SINK@ 0.7
wpctl set-mute @DEFAULT_AUDIO_SINK@ toggle

pactl can also be used on PipeWire when pipewire-pulse is running. It is useful when existing automation or muscle memory already targets the PulseAudio command model, and it remains the primary command-line control on systems that still use PulseAudio directly.

Installing the tools

Package availability varies by distribution and release. The safest approach is to install from the distribution package repositories using the package name appropriate to that distribution. The package names pwvucontrol, helvum, and qpwgraph are the common starting points on many current distributions.

After installation, PipeWire and its session manager should already be running on a modern desktop distribution. If a newly installed tool cannot see devices or streams, confirm that the PipeWire service and WirePlumber session manager are active for the current user session.

Limitations and gaps

This guide does not reproduce distribution-specific package versions or guarantee that every package is available in every repository. Support should be verified against the installed distribution release, kernel and media stack versions, because PipeWire integration varies with desktop environment and session configuration.

Documented support, reported behavior, and demonstrated results also differ. A tool may be present in a repository and still behave differently across versions of PipeWire, WirePlumber, and the desktop shell. Where exact behavior matters, test against the actual installed versions rather than assuming that package installation alone proves end-to-end functionality.