How to Enable and Configure PipeWire on NixOS

Before you start

This task assumes you already have a NixOS configuration and can rebuild it. PipeWire on NixOS is enabled through the system configuration rather than installed only as an ad hoc user package, so the procedure normally runs locally during a rebuild and then affects system services after activation. You do not need a separate PulseAudio setup, but removing or disabling conflicting audio services matters if they are active.

Step-by-step instructions

Open your configuration file and add PipeWire support through NixOS. The service names used below follow the NixOS module approach; option names can vary between releases, so check the manual supplied with your NixOS version before applying changes.

sound.enable = true;
services.pipewire = {
  enable = true;
  audio.enable = true;
  pulse.enable = true;
};

With this configuration, PipeWire provides the sound server and a PulseAudio-compatible interface. The pulse option is useful for programs that expect the older PulseAudio socket, which includes many conferencing and recording applications.

For microphone, camera and video-call use, decide whether you need the camera-related PipeWire features. Basic audio routing is covered by the settings above. If your desktop environment or a specific application requires PipeWire camera support, confirm the exact option set for your release instead of enabling unrelated modules.

If you also want a graphical control tool, install one through your user environment or system packages. Keep in mind that a control panel is separate from the PipeWire service. The service can work without a GUI, but a mixer or routing view can simplify checking devices and levels.

Check the output

Use the supported PipeWire inspection command rather than assuming a device works because it is visible in a settings panel. The command to list or inspect nodes and devices depends on the version installed, so verify the current syntax for your release.

A practical verification path is to open an application that records or plays audio, select the expected input or output, and confirm that the application receives a signal. Quality and format limitations depend on the device, driver and application settings, not only on PipeWire, so avoid treating a working stream as a measurement of latency or sample format.

Common problems and next steps

One common issue is that an old PulseAudio service remains configured. If PipeWire cannot claim the socket or devices behave inconsistently after the switch, review the active audio services and ensure they are not competing. This is easier to diagnose when you make only one audio-related change at a time.

If an application does not show a microphone or camera after enabling PipeWire, check the application's permissions and the surrounding desktop integration. Some environments require portal services for device access, while others expose devices directly. Confirm which path your application uses before changing user or system-level permissions.

When troubleshooting, make changes reversible. Keep the previous working configuration available, rebuild after a single focused change, and test with one application before extending the setup to more devices or custom routing.