If your OBS scene captures the whole display, OBS can appear in the stream when its window is visible on that display. The simplest documented fix is to minimise OBS; Windows and recent macOS versions also offer capture-exclusion options for supported capture setups.
The loop and the desktop capture are separate things. First check which source your scene uses, then choose a fix that matches your operating system and whether viewers need to see the whole desktop or just one app. Test the resulting output before leaving the stream unattended.
Why OBS can appear in its own display capture
A Display Capture source records the selected display. If the OBS window is open on that display, the source can include the OBS interface along with the video or other content you intended to show. This is a capture feedback problem: the scene is recording a screen that contains the software controlling the scene.
That is different from a problem with the loop file. If the source is playing the right video but the picture also shows OBS controls, the first thing to inspect is the scene’s capture source, not the file itself. Conversely, a black picture or a loop that stops is a different symptom and needs a different investigation. For a file that does not appear as expected, the checks in video-file fixes for a black YouTube stream are more relevant than hiding the desktop.
Open the scene’s Sources list and identify the source type. Display Capture is broad: it takes the selected display rather than one chosen application. Window Capture or an application capture, where supported, can narrow the content. OBS’s Sources Guide explains source visibility and capture-source behaviour; OBS’s video feedback troubleshooting guide also documents why a visible OBS window can end up in a display capture.
Do not confuse the eye icon beside a source with hiding the OBS application. The eye controls whether that particular source contributes to the OBS scene. Turning off the eye for a Display Capture source changes the scene content; it does not prevent the OBS window from being recorded by that source when it is on. Likewise, Studio Mode can keep edits in preview until you transition them to the live programme, but it is not an exclusion setting for the desktop.
For a 24/7 loop, you may only need to configure the scene before going live and then leave OBS minimised. If you need to watch controls during operation, decide where those controls can live without appearing in the captured image. A second monitor is one possibility, but it is optional rather than a requirement.
Quick fix: minimise OBS
If you are capturing the display that holds OBS, minimise the OBS window after confirming the scene. OBS says a minimised window is not visible to the capture, so the display source no longer includes the OBS interface. On Windows you can minimise it to the taskbar or tray; on macOS it can be minimised to the Dock or menu bar.
The trade-off is simple: you cannot see the OBS controls in their normal window while they are minimised. If you restore the window on the captured display, it may appear in the stream again. This can happen during an ordinary check, such as reopening OBS to inspect a scene, so minimise it again before relying on the display capture.
This method is useful when the loop itself is already behaving and the unwanted content is only the visible OBS window. It does not correct a wrong scene, remove other desktop notifications, or ensure that a particular application is the only thing shown. If you capture a full desktop, other visible windows can still be included.
Before minimising, verify that the intended scene is active and that the source is visible. If you use Studio Mode, look at the programme output rather than assuming the preview is what viewers receive. OBS’s overview of Studio Mode and the interface describes how the live programme and preview differ. Once the output is correct, minimise and check the stream’s visible result through your normal monitoring path.
If your workflow depends on seeing OBS while you operate it, consider a separate display. OBS identifies a secondary monitor or television as a way to keep controls apart from the display being captured. Keep the capture source pointed at the display containing the loop, and put OBS on the other one. This is only practical if the computer and display arrangement already suit it; it is not necessary when minimising works.
Hide OBS from capture on Windows
On Windows, OBS documents a setting called Hide OBS windows from screen capture. In OBS Studio, open Settings → General, enable that option, and apply the change. This is intended to keep OBS windows out of supported screen-capture output without requiring you to keep the application minimised.
There is an important side effect: OBS documentation says screenshots of OBS will not work while this setting is enabled. Do not assume you can later take a screenshot of the OBS interface for a support request while exclusion remains active. If you need a screenshot, change the setting as appropriate and remember that the OBS window could then be visible to the display capture.
Treat the setting as a capture-specific tool, not a general privacy control. It does not hide other applications, desktop notifications, or unrelated windows from a display capture. It also does not replace checking the scene source and actual programme output. If the source is capturing the entire desktop, content outside OBS can remain visible.
Enable the option before you leave the stream running, then test with the exact scene and capture source you intend to use. Reopen or restore OBS carefully: the point is to confirm the interface is excluded, not to assume that every capture path on every setup behaves identically. After testing, keep the stream output visible in your monitoring path and ensure the scene has not changed.
This is a better fit than minimising when you need OBS available on the same computer while the display is captured. If the setting interferes with a workflow that relies on screenshots, or if the capture still shows OBS, revert to minimising or choose a narrower source instead. For broader computer-side arrangements, running a continuous YouTube stream from a Windows cloud virtual machine covers a different operating model; it does not change the capture rules described here.
Hide OBS from capture on macOS 13 or later
On macOS 13 Ventura or later, OBS documents an exclusion option in the macOS Screen Capture source. Add or select a macOS Screen Capture source, set it to Display Capture mode, and enable Hide OBS from capture. This is a platform- and source-specific workflow, not a universal switch for every macOS source or version.
Check that you are using the macOS Screen Capture source and the required mode before looking for the option. Older macOS versions use different capture paths, and OBS’s documented instructions limit this particular setting to macOS 13 and later. If the setting is unavailable in your setup, use the minimise method or a supported window/application capture instead of assuming the same exclusion control exists.
As on Windows, exclusion addresses OBS’s own visible window in capture. It does not hide other apps, notifications, or anything else on the captured display. It also does not prove that the loop source is correct or that the scene being sent to YouTube is the one you intended. Check those separately.
After enabling it, inspect the output with OBS visible and then with the state you expect to use during the loop. If you intend to leave OBS open, test it open; if you intend to minimise it, test that too. Confirm the content through a monitoring view that does not depend on the excluded OBS window appearing in a screenshot. A screenshot of the application may not be a reliable validation method when capture exclusion is active.
Capture only the app or window when supported
If viewers need to see only one video player, browser, or application, capture that window or application rather than the entire desktop where OBS and the platform support it. A narrower source reduces the amount of unrelated screen content that can enter the scene. It can also make the OBS window irrelevant if OBS is not the selected target.
Support differs by platform and OBS source. OBS lists Window Capture for Windows, Linux, and macOS 12.6 and earlier. For macOS 13 and later, macOS Screen Capture can capture a display, window, or application. Select the source that corresponds to the app containing the loop, and confirm that it remains the intended target after reopening or changing windows.
A window source is not the right answer for every loop. If the scene must show several desktop elements together, a single window may omit parts of the intended image. If the loop is a video file already loaded as a media source in OBS, you may not need desktop capture at all; use the source appropriate to that workflow and verify its behaviour. Narrowing capture is about showing the desired content, not adding complexity for its own sake.
The practical choice is between the breadth of the source and the controls you need during operation:
| Method | Where it fits | Main trade-off |
|---|---|---|
| Minimise OBS | Any setup where OBS is visible on the captured display | Simple, but restoring OBS can make it visible again |
| Windows capture exclusion | Windows, using OBS’s documented setting | Keeps OBS available, but screenshots of OBS do not work while enabled |
| macOS capture exclusion | macOS 13 or later, with macOS Screen Capture in Display Capture mode | Specific to the documented source and mode |
| Window or application capture | When the desired loop content is in a supported app or window | Shows a narrower target, which may omit other desktop content you need |
| Secondary display | When OBS controls can be placed away from the captured display | Requires another display and a suitable workflow |
There is no single choice that fits every machine. If you only need a fixed loop image, a narrow source is often easier to reason about than an entire desktop. If you need a whole-display composition, minimising or a documented exclusion setting may fit better. The OBS Sources Guide is the primary reference for the source types available in OBS; check it alongside the choices exposed by your installed version.
Check the scene and output before leaving it live
Test the exact scene before you leave a 24/7 loop running. First identify whether the scene uses Display Capture, Window Capture, macOS Screen Capture, or another source. Then confirm the desired video is visible and that the OBS interface is not part of the intended image. If you changed source type or exclusion settings, test those changes rather than relying on how they looked in a different scene.
Look at the programme output, especially if you use Studio Mode. Preview is where you can prepare a scene; programme is the live scene until you transition. Moving or editing sources in preview does not necessarily change what viewers see until the transition. This is useful protection against accidental scene changes, but it is separate from excluding OBS from a display capture.
Test the moments when you are most likely to reveal the interface: restoring OBS, switching scenes, moving between windows, and checking the loop. If you use Windows exclusion, do not make a screenshot of OBS the only proof that it is hidden; the setting itself prevents those screenshots while active. Use the actual stream output or another suitable viewing path to confirm what is being sent.
For a YouTube loop, also make sure you are checking the live output, not only the local OBS preview. A correct preview can still be undermined by a wrong programme scene or a source that changes target. Keep the test focused: does the intended loop appear, does any part of the desktop show that should not, and does the image remain correct after the operator action you plan to use?
If OBS continues to show despite a documented setting, return to the source definition and platform. Confirm the operating-system version, the capture source type, and the mode selected. Do not infer that an exclusion option applies to Linux, every macOS source, or all third-party capture paths. Use minimising or a supported narrower source when the exclusion path does not match your setup.
If the loop itself is a prerecorded file, file stability and capture visibility are separate checks. The guide to choosing a file format for a 24/7 YouTube bhajan playlist concerns the media file; the advice here concerns whether OBS’s interface enters the captured image. Keep those investigations distinct so a screen-capture issue does not send you down an unnecessary encoding path.
If you do not want a computer window or desktop to be part of the workflow at all, StreamNeo removes the need to keep an OBS desktop capture open for a file-based loop: you upload the video and use your YouTube stream key, with the broadcast continuing while your computer is off. It is YouTube-only, so it does not solve a setup where the content itself must be captured live from a desktop application.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does minimising OBS stop the YouTube loop?
Minimising changes whether the OBS window is visible to a display capture; it is not itself a command to stop the stream. OBS documents minimising as a way to avoid capturing the visible window, but you should test the actual scene and output on your setup before relying on it unattended.
Does hiding a source hide the OBS desktop?
No. The eye control in the Sources list shows or hides that source within the scene. It does not exclude the OBS application window from a Display Capture source; use minimising, a documented platform-specific exclusion, or a narrower capture source.
Does Studio Mode keep OBS controls out of the stream?
Studio Mode separates preview edits from the live programme until you make a transition. That can help prevent an unplanned scene change, but it does not hide a visible OBS window from a desktop capture.
Can I use the same exclusion option on Linux or every macOS source?
Do not assume so. The documented Windows setting and the macOS 13-or-later macOS Screen Capture workflow have specific platform and source requirements; OBS’s reviewed guidance does not describe a matching Linux exclusion toggle. Use minimising or a supported window/application source if those documented paths do not fit your system.