To stop notifications from showing on your OBS stream, use two defences: enable Do Not Disturb or an appropriate Focus mode in your operating system, then capture only the study app or its window where your OS and OBS version support it. If you are asking how to hide desktop notifications while streaming, remember that either measure can have exceptions, so check the actual scene before you go live.
Do Not Disturb reduces the chance that a banner appears on your desktop; a narrower capture source reduces what OBS can include in the broadcast. Neither is a universal switch, and the available capture choices differ between operating systems and OBS releases.
Why notifications appear in a study stream
A full-display capture records the monitor area OBS is told to capture. When an operating system draws a notification banner over that area, it can become part of the captured picture, just like a cursor, menu or app window. OBS is capturing the visible composition, not deciding which parts of the desktop are private.
That matters in a study stream because the desktop may be on screen for hours. A message preview, calendar reminder or software update can distract viewers; a notification may also reveal a name or other information you did not intend to show. The practical answer is to prevent banners where possible and avoid capturing more of the desktop than the scene requires.
First ask what viewers need to see. If your scene is a single reading, drawing or study application, a window or application source may be enough. If the scene includes several windows, a clock, reference material or your desktop layout, full-display capture may still be the right choice, but it needs more careful notification settings and testing.
A useful distinction is whether you want alerts silenced for yourself or merely kept off-stream. Do Not Disturb changes which alerts reach you, often directing them to a notification centre or summary. A narrower source changes what the stream displays, but it does not stop the operating system from notifying you outside the captured area. You may want both protections, particularly if you need the computer to remain available for work while you broadcast.
If you are still building the scene, keep its sources simple and label them clearly. The guide to OBS settings for a 24/7 YouTube stream covers the wider job of making an OBS broadcast behave predictably; notification privacy is one small but important part of that setup.
Enable Do Not Disturb or Focus
Turn on the operating system’s Do Not Disturb or Focus control before opening your broadcast scene. It is the first defence because it can stop many banners from appearing over a full-display capture. The exact name, location and behaviour depend on the OS and its version, so follow the current support guidance for the computer you are using rather than relying on instructions for a different release.
On Windows 10 or 11, Microsoft’s current guidance places Do Not Disturb in Settings > System > Notifications. You can also start a Focus session; Microsoft says Focus turns on Do Not Disturb by default. Check the status before you start streaming, and do not assume that opening OBS has activated a quiet mode for you. The Microsoft instructions for Windows notifications and Do Not Disturb explain the controls, while its Focus guidance describes the session feature.
On macOS, use Focus from Control Centre and select Do Not Disturb or a suitable Focus profile. Apple lets you decide which people, apps and time-sensitive notifications can still appear during a Focus. Check those choices as part of setup; turning a Focus on does not mean every possible alert is necessarily blocked. Apple’s guide to setting up a Focus on Mac describes the current controls.
Linux users should identify their desktop environment and consult its current notification settings. There is no single procedure established here that applies to every distribution or desktop. A quiet-mode toggle may suppress banners in one environment but behave differently in another, so verify it with the applications you normally use.
Do Not Disturb has a trade-off: it can keep an important alert from interrupting you as well as keep an unimportant banner out of the picture. If you are expecting a call, a safety alert or a time-critical message, review how your chosen mode treats it before relying on quiet settings for a long session. For a study broadcast, decide which interruptions matter more than a clean desktop, then configure the mode accordingly.
Review allowed exceptions and automatic rules
Do Not Disturb is not always all-or-nothing. A priority list, a chosen person, an alarm, a reminder or a time-sensitive alert may be allowed through. On macOS, review the people and apps permitted by the active Focus. On Windows, review priority notifications and the app settings alongside the Do Not Disturb control. The option labels can change between software releases, so use the current OS documentation if the menu on your machine differs.
Automatic rules can be easy to overlook because the mode may turn on or off without you deliberately changing it. Windows offers rules connected with activities such as displaying or using a full-screen app. Check these rules rather than guessing that a live stream will trigger the behaviour you want. A rule that turns Do Not Disturb on can help, but a rule that ends it at the wrong time can let banners back in during a long session.
On any system, consider the applications you have allowed to interrupt you. Email, chat, calendar and system-management tools are common sources of banners. You might suppress most of them while leaving a genuinely important channel available, but be precise about which exception is enabled. If a notification has to remain available for your own work, a narrower OBS source can help keep it out of the stream without changing how that alert reaches you.
Do not treat the notification centre as a substitute for reviewing the rules. Some systems move silenced notifications there, while other allowed alerts can still appear on screen. The useful question is not simply whether Focus is on, but what is allowed to appear while it is active and what happens when a scheduled or automatic rule changes its state.
Use window or application capture when supported
If viewers only need to see one study app, consider replacing Display Capture with a window or application source. A narrower source limits the captured area and can keep unrelated desktop activity outside the scene. This is a separate defence from Do Not Disturb: it reduces what OBS sees, but it does not mute the computer or remove notifications from your own desktop.
On Windows, OBS Window Capture can show the selected window even when other windows overlap it. That can suit a reading app or a worksheet that should remain visible while you use another program. It also means you need to check that the desired content is actually in the selected window and that the source still behaves as expected if the app is minimised, resized or changed. OBS’s Window Capture documentation describes the source and its advantages over capturing a whole display.
On macOS 13 and later, OBS documents the macOS Screen Capture source, which can target a display, window or application. The older Window Capture source is identified as deprecated on these newer macOS versions, so do not assume a tutorial for an older release uses the right source for your installation. Check OBS’s macOS Screen Capture guidance and compare its options with the sources visible in your own version.
Application capture can be useful when the choice is available and you need the app’s content without the rest of the desktop. Window and application sources are not guaranteed to exist or behave identically on every platform, version or graphics setup. If a source is missing or fails to show the expected content, use a documented option for your particular setup rather than repeatedly changing settings just before a live session.
There is a visibility trade-off. A selected window may exclude useful desktop context, and your scene can look different if the app’s size or layout changes. Make sure viewers can still read the material, see the clock or follow any other element you intended to include. If a study stream uses a planned day-and-night scene, for example, a single app source may not replace its full composition; the guide to building a lofi stream with day and night scenes is relevant to that broader scene design.
Check what full-display capture includes
Before keeping Display Capture, establish exactly which display OBS is capturing and what is visible on it. OBS describes Display Capture as capturing the entire monitor. Anything the operating system draws within that monitor’s captured area, including an overlaid banner, may therefore appear in the stream. OBS’s Display Capture documentation explains the source; the important practical point is that it is a whole-display view, not a privacy filter.
A second monitor does not automatically solve the problem. If OBS captures the monitor that has notifications, those banners may still be part of the picture; if it captures a different monitor, confirm the intended app is actually there. Check the source properties and preview, and make sure the scene is not also using another source that shows the desktop.
On macOS, OBS includes a “Hide OBS from capture” option for the macOS Screen Capture source when using Display Capture. This hides OBS itself from the captured view; it is not a general notification filter. Do not mistake it for a way to keep message banners or system alerts out of the broadcast.
You can also design the scene so that the captured content occupies only a deliberate portion of the output, but cropping a display source does not necessarily help if the notification appears inside the cropped area. Test the arrangement rather than relying on the word “crop” as a privacy guarantee. If a notification can land over the part you show, it can still be visible to viewers.
Test the scene before going live
A reliable check is to inspect a private preview or a short test recording before the public session. Arrange the desktop as you expect it to be during the broadcast, enable the chosen quiet mode, and use a notification-producing app configured as it will be during the session. Then watch the recording or preview as a viewer would, not only the OBS canvas while you are changing settings.
Check more than whether a banner appears once. Confirm that the chosen scene and source are active, the correct monitor or app is captured, and any permitted alert behaves as intended. If you use a window source, move another window over it and check what the audience sees. If a full-display source remains in use, check whether an alert briefly covers the study material or reveals information in a preview.
A test is a workflow recommendation, not proof that every future notification will be suppressed. An app may gain permission, an OS update may change a label or default, or an automatic Focus rule may switch off later. Repeat the check after changing the OS, OBS version, scene, display arrangement or notification policy, and before a long session where you will not be watching the screen closely.
For an always-on channel, also decide who or what will notice a problem once you are away from the computer. A desktop notification is not the only possible interruption in a long broadcast, but the same habit applies: verify the actual output rather than assume that the preview represents every later condition. If your broader setup uses OBS to loop material, see the guide to looping a long lofi video with OBS Media Sources for a related scene workflow.
Choose a fallback if capture options differ
If your version of OBS does not offer the window or application source you expected, use the capture source documented for your operating system and version. On Windows, Display Capture and Window Capture are documented options. On macOS 13 and later, check the macOS Screen Capture source rather than relying on older Window Capture instructions. On Linux, first identify your desktop environment; the available behaviour depends on that environment, and a general OBS source list cannot tell you whether its banners will be suppressed.
If you cannot use a narrower source, keep full-display capture and strengthen the OS-side checks: turn on the appropriate quiet mode, inspect the allowed exceptions, review automatic rules and test the complete scene. You can also close nonessential chat or mail apps before the session, provided doing so does not interrupt other work or remove something you need. This is a practical fallback, not a claim that closing apps or enabling Focus guarantees that no banner can appear.
Choose the fallback according to the content viewers need and the interruptions you need to retain. If the study app must remain visible while another app is used, window capture may be suitable where supported. If the scene depends on multiple desktop elements, full-display capture may be necessary, with stricter notification checks. Where OS controls and capture scope are both inadequate for your needs, consider a different scene composition or a dedicated device for the study display.
A cloud-run broadcast can remove a different kind of distraction: needing to leave a personal computer running for a long stream. StreamNeo turns an uploaded video into a YouTube live stream, so you do not need to keep your own desktop broadcasting; it does not change the notification settings on a computer you use for other work.
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 OBS block desktop notifications by itself?
Do not rely on OBS to block every notification. A full-display source captures the monitor area, so an OS banner drawn over it may be included. Use operating-system notification controls and, where supported, a narrower source, then check the output.
Is Do Not Disturb enough to keep every banner off-stream?
Not necessarily. Priority exceptions, permitted apps or people, alarms, time-sensitive notifications and automatic rules can affect what appears. Review the rules for your own OS and test the settings you intend to use.
Should I use Window Capture instead of Display Capture?
Use a window or application source when viewers only need that content and the option is supported by your OS and OBS version. Display Capture may be more suitable for a scene that relies on several desktop elements, but it can include banners drawn on the captured monitor. Check the source and composition before going live.
What should Linux users do?
Start by identifying your desktop environment and consulting its current notification controls. Linux notification behaviour is not established by one universal procedure, and OBS capture options do not prove that a particular desktop suppresses banners. Test a private preview or recording with the apps and settings you will use.