OBS Studio · Practical guide

OBS Window Capture Selects the Wrong Window: Check Matching Rules

Choose a window-matching rule deliberately and test document changes, relaunches and other windows from the same application.

START HERE

Window Capture can match a title strictly or fall back to another window of the same type. Choose the rule that fits your workflow and test what happens when the title changes or the original closes.

Choose a window-matching rule deliberately and test document changes, relaunches and other windows from the same application.

In this guide
Before you start
  • Windows and the application you intend to capture.
  • Two harmless documents or windows for a controlled matching test.

A window title is part of the capture decision

An application may put the current document, project or conversation into its window title. That makes a capture target seem to change when you open a new file. Before rebuilding the source, note the selected title and compare it with the title shown after the workflow step that caused the problem.

OBS documents Window Match Priority in its Windows Window Capture source. A strict title match stays blank when that title cannot be found, while other choices can fall back to a window of the same type. Neither behavior is universally correct; choose the boundary you intend.

Choose predictable failure over an unexpected replacement

For a sensitive demonstration, a blank source may be preferable to silently showing another document from the same app. For a tutorial that deliberately switches project names, a broader matching rule may be more practical. Decide which outcome is acceptable before the original window disappears.

Create two harmless test windows with clearly different labels. Keep private documents closed during this exercise. The aim is to learn the source’s replacement behavior safely, not to find out during a live session that a fallback rule selected a window you never meant to show.

Test the selected rule through a window change

  1. Select and name the target

    Open Window Capture properties, select the intended window, and note its title. Give the source a name that identifies the application and purpose.

    Look for: The source begins with a known target rather than an ambiguous application entry.

  2. Choose the matching policy

    Inspect Window Match Priority and select strict title matching or an appropriate fallback according to the planned workflow. Keep the previous value in your notes.

    Look for: The source’s behavior when the original target disappears is a deliberate choice.

  3. Change the title and close the original

    Using harmless content, open another document, close the original window and relaunch the app. Record the sequence and inspect which window is shown at each stage.

    Look for: You know whether the source stays blank, follows the desired replacement or selects something unsuitable.

Separate window identity from the capture method

If the correct target is selected but its picture is blank, that is a different question from selecting the wrong document. Check the capture method separately. OBS notes that an alternative such as BitBlt can help some applications, with a performance tradeoff; it should be a controlled fallback, not a default fix for every matching issue.

Likewise, client-area and cursor settings affect presentation, not which document the matching rule chooses. Keep those adjustments until the identity test succeeds. Changing them all together makes it difficult to tell why the next sample looks different.

Rehearse the exact document sequence you will present

Run the real sequence with safe copies: open the project, show settings, switch documents, close the temporary window and return. Verify the saved recording from start to finish. A source that survives one rename may still behave differently when two similarly titled windows are open.

Keep a fallback scene ready for an unexpected blank target. When a title or application update changes behavior, revisit the matching test instead of adding another overlapping capture. The useful result is a source whose selection and failure behavior you can explain before the audience sees it.

Still stuck?

Closing the intended document reveals another window.

Use a stricter matching rule if that fallback is unsuitable, then test the blank-state behavior with harmless documents.

Keep troubleshooting

Check the model and connection before trying another change. The device page gathers the related symptoms.

More help with OBS Studio ↗

Sources & references

Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.

  1. OBS — Window Capture Sources ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

OBS Black Screen? How to Fix Game, Window and Display Capture

OBS shows black instead of your game or screen? Try these quick checks for Windows and Mac.

Keep Private Notifications Out of Your Stream Capture

Reduce the capture area, review Windows notification exceptions and test with harmless messages before going live.