How to Capture PipeWire Audio in OBS

Before you start

This guide assumes you are running OBS on a Linux system where PipeWire provides the audio service. The process is local: OBS talks directly to PipeWire on the same machine, and you do not need a separate network service or media server.

Before adding a capture source, check that audio is already working on the desktop. Play a known sound or open an application that produces audio. In OBS, open Settings and go to the Audio section. The Global Audio Devices area may list the system default input and output devices, but PipeWire-specific capture is normally added through the Sources panel rather than only changed here.

Keep the setup reversible. New audio capture sources are added as individual entries, so you can mute, hide, or remove them without changing other video or audio sources. If you plan to record a specific application rather than the entire desktop, start that application before creating the source so it appears in the available targets.

Step-by-step instructions

Open OBS and locate the Sources panel, usually in the lower part of the main window. Select the plus button to add a source. The exact source name depends on your OBS build and installed PipeWire support. In builds with PipeWire capture available, the list may show an audio input capture or audio output capture option that uses PipeWire as the backend. Open that option and create a new source.

In the properties window, choose the capture target. A desktop audio output option may be labelled as a monitor of the default output device. An application capture option may show individual running programs instead of a hardware device. Pick the target that matches the sound you need. If you are recording both a microphone and desktop audio, create separate capture sources for each so their input levels can be controlled independently.

For an application source, select the program from the application list. The list may only contain applications that are currently playing or are able to produce audio. If you add the source first and launch the application later, you may need to reopen the source properties or restart OBS so the new target can be discovered.

After selecting the target, keep the default device behaviour unless you have a reason to change it. The default selection typically follows the current PipeWire output device. If you use separate headphones and speakers, choose the specific output device rather than relying on the default when you need consistent routing.

Confirm the sample rate only when necessary. OBS expects sources to match the configured audio sample rate, commonly 48000 Hz. If a PipeWire source produces silence or distorted sound, check the audio sample rate in OBS settings and compare it with the rate used by the source or application. A mismatch can cause pitch changes, dropouts, or an unusable recording.

Use the Audio Mixer to set a sensible input level. Start with the source volume around the default position and adjust while checking the meter. The meter should stay below the red area during normal sound. Good level control also reduces background noise because you are not forced to boost a weak signal later.

Check the output

Make a short test recording that includes speech or music and silence. Play it back and confirm that the expected sources are present, the left and right channels sound correct, and the audio stays in sync with the video. Watch the mixer during recording to see which source is moving and whether an input level is too high or too low.

Check the recording format and encoding settings separately from the capture source. The capture source defines what audio enters OBS, while the recording format and bitrate define how OBS stores it. Higher bitrate does not fix an overdriven or silent source. If the audio sounds clean in the meter but poor in the recorded file, investigate the recording settings rather than the PipeWire source.

If you need a reference for frame rate, remember that it applies to video, not audio. Audio timing is based on the sample rate and the number of frames produced by the audio system. Avoid changing the video frame rate while trying to solve an audio sync issue unless the recorded picture itself is also wrong.

Common problems and next steps

One of the most common issues with PipeWire audio capture in OBS is seeing the source but hearing silence. First check whether the application is playing sound and whether the PipeWire source is monitoring the correct output device. Then check the OBS audio mixer. If the source meter does not move, open the source properties and choose a different target or restart OBS after starting the audio application.

Distorted or clipping audio is usually an input level problem rather than a PipeWire fault. Lower the source volume in OBS and lower the application volume if needed. If speech sounds quiet and the room has noticeable background noise, move closer to the microphone, reduce nearby noise sources, and then raise the microphone level only enough to reach a clear meter.

Audio drift or sync problems can appear when the audio sample rate is inconsistent. Confirm the OBS sample rate setting is supported by your output device and leave the source using the same rate. Avoid changing sample rates during a recording. If sync issues persist, test with a short recording and a simple source first, then add more capture sources one at a time.

Keep a practical troubleshooting order: verify the sound outside OBS, verify the selected capture source, check the mixer level, then inspect the recording format and encoding settings. This separates a routing problem from a quality problem and makes the next correction easier to identify.