
For a Windows application whose window title changes, check the match priority in OBS Application Audio Capture. The official guide recommends matching by executable name for applications such as browsers or music players whose titles vary. Replacing the microphone or changing the recording codec will not correct a source that no longer matches the intended application window.
Key Takeaways
- A changing title can be part of the capture identity problem.
- Check the intended executable and actual source meter after a title change.
- Windows Application Audio Capture controls should not be assumed to exist identically on other platforms.
Confirm the correct capture route
The OBS application-audio guide documents per-application sources on supported Windows systems. It also describes capturing audio through Window Capture or Game Capture in supported OBS versions. Identify which route your scene uses before searching for the matching control.
Keep a working profile or record the present source settings. Confirm that the application itself is producing audible sound and that the OBS source originally responds. If the source never works, a title-change diagnosis is premature.
Change the match rule deliberately
Open the audio source's properties and select the intended application window. Review its window match priority. For a title that varies with the current browser page or song, use the documented executable-name matching route where appropriate.
Give the source a clear name so it is not confused with another capture of the same application. Avoid treating all windows from the same application as independently isolated audio without verifying the actual result; choosing an executable does not prove that unrelated content from that application is excluded.
Proposed browser demonstration check
Suppose a tutorial plays a reference clip in a browser and then moves to a page with a different title. Create a disposable test that starts with sound, changes the page title and plays sound again. Watch the intended source meter and listen to the saved recording at both points.
Also play a harmless sound from a different application to confirm that the intended isolation remains meaningful. This is a proposed verification sequence, not a claim that every browser's audio routing behaves the same way.
Follow the failure to the right layer
If the source meter continues but the recorded sound disappears, check recording-track assignments rather than repeatedly changing the window match. If the meter stops after the title change, revisit the source identity. The official guide notes that some applications route audio incompatibly with this capture method; that possibility requires a different capture plan, not an unsupported promise that matching by executable fixes every missing-audio case. Accept the setup after the relevant title changes survive a saved-output check.
Related tasks
- Why Does an OBS Capture Device Go Black After I Set a Custom Mode?
- Why Is OBS’s VLC Video Source Missing When I Need a Playlist?
- Why Is an OBS Sound Audible Live but Missing From the Twitch VOD?
Sources and scope
- Application Audio Capture Guide: Window match priority can use executable name for apps whose titles change; per-app capture availability starts with Windows 10 version 2004 or Windows 11.
OBS project documentation read directly through the web tool on 2026-10-23 supplies technical support. Community posts, where present, show individual demand only. Examples and listening checks are proposed procedures; no actual recording or repair is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Rumeyda Tutak / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.