OBS Separate Audio Tracks With a Routing Checklist

Know which version and evidence this covers

The stable OBS release endpoint resolved to 32.2.2 when checked on October 22, 2026. This guide uses OBS's multitrack documentation and the English labels in that release's source tree. Those labels confirm names, not the layout or successful operation of an installed application. Recheck the workflow after an OBS upgrade, especially when moving to the 33 series. [1], [2].

The official multitrack guides date from 2021 and 2023. They establish the routing concept, not a fresh test of your operating system, capture source, plugin, container or editing application. Preserve that distinction when copying somebody else's settings.

Check both track assignment and recording output

OBS documents source-to-track assignment in Advanced Audio Properties and enabling the desired tracks in Settings → Output. Its advanced guide describes Advanced Output Mode and up to six tracks. The release's English labels include Output Mode, Advanced, Recording and Tracks. [3], [4].

Our routing rule is an AND condition: an intended source needs the correct assignment and the intended output track needs to be recorded. Fixing one side cannot supply a signal missing from the other. Write down both rather than relying on the appearance of a moving mixer meter.

The guides also explain that ordinary players play one audio track at a time. OBS's example uses track 1 for a complete mix and later tracks for separate sources. A player that exposes only one track is therefore not, by itself, evidence of a failed recording.

Copy the source-to-track plan

This is an illustrative plan to adapt, not a universal preset. The source names describe intended jobs; they do not establish how an application is captured on your computer.

Add the actual output selections to the plan: “record 1, 2, 3, 4” is a decision to verify in OBS, not something the table configures. If your handoff does not need an isolated source, remove the requirement rather than creating an unused track for appearance's sake.

Name the sources by function and identity. “Guest laptop return” is more informative than “Audio 2”. Keep that name in the handoff notes so the editor can connect the intended signal with the recording.

Run a short recording and inspect each source

The following roughly 30-second rehearsal is our proposed reader test. Its duration is a convenience, not a reliability benchmark or a measured result.

1. Save the routing plan and note the OBS version, operating system, selected recording format and editor version.
2. Record the microphone alone, saying a recognisable source label. Keep the other intended sources quiet.
3. Repeat with each other intended source, using a distinct, recognisable sound. Finish with the sources together.
4. Stop normally, preserve the test file and import it into the intended editing application.
5. Inspect the available tracks. Listen to each source-only interval on each isolated track, and check the complete mix separately.
6. Record pass or stop for each row of the plan. Correct the earliest failing checkpoint and repeat the short recording before the full session.

Do not judge isolation from a waveform's appearance alone. The useful question is whether the intended sound is present on the intended track and absent from tracks where the plan excludes it. Use material you are permitted to record, and keep other applications quiet enough to make the check interpretable.

These are diagnostic branches, not findings about your machine. Change one route at a time so a successful retest has an explanation.

Keep application capture and formats in their own checks

The OBS application-audio guide documents Windows 10 version 2004 or later and Windows 11, with per-application sources from OBS 28 and audio inclusion for Window/Game Capture from 30.1. It warns about duplicated global Desktop Audio and notes that some applications are incompatible. That is not a promise that a particular Discord, game or browser configuration will be isolated [5].

This article does not apply that Windows route to macOS or Linux. For another system, use the appropriate OBS capture documentation before assigning track numbers. Nor does a track checkbox turn a mixed source into separate applications: source separation must exist before the track plan can preserve it.

Not all recording formats support multiple audio tracks. The guides do not provide a full current format-and-editor compatibility matrix.

For formats, OBS's recording guides recommend MKV and describe remuxing to MP4. That advice is not a current compatibility matrix for every MP4 variant, codec and editor, nor a guarantee that damaged recordings are recoverable. Use your chosen format in the rehearsal and inspect the actual imported tracks [6].

Accept a handoff rather than a screenshot of settings

The handoff is ready when a colleague can match each required source to a recorded track, recover the complete mix when needed, and explain any deliberately omitted sound. Keep the route card, test file and editor observations together. A screenshot of assignments is supporting context; the file is the result the editor must use.

For longer sessions, combine this check with a recording backup checklist. For distributed conversations, the remote podcast workflow covers the separate problem of obtaining recoverable source recordings. Neither a multitrack file nor a green test card replaces an independent backup.