How to Hide Personal Notifications While Streaming

Why personal notifications end up on air

With full monitor capture, OBS sends viewers the entire desktop image: open windows, the taskbar, system banners, and pop-up messages. Emails, conversations, reminders, incoming calls, and update notifications can all end up in the frame. Even a brief banner appearance is enough for a viewer to read it or take a screenshot.

Check your audio separately. With a shared audio channel enabled, viewers may hear the messenger, email, or calendar chime even if the banner itself never appeared. A personal message can also show up inside the captured program: in a browser, game, chat app, or third-party overlay.

That's why protection rests on three settings: the selected video source, disabled notifications, and separate audio. If you're showing a game, use game capture. For a single program, window capture will do. Leave full monitor capture only for tasks where you need to demonstrate switching between multiple applications.

Choose a safe capture source in OBS

The "Monitor Capture" source shows everything that appears on the selected screen. It's convenient for lessons and reviews, but it requires constant vigilance: any open window or system message immediately becomes part of the broadcast.

"Window Capture" limits the image to a specific program. Notifications from other apps usually won't make it into the frame, but messages from the selected window itself remain visible. For example, a browser may show a site banner, a download window, or the contents of another tab if the app is captured in full.

For a game, add a "Game Capture" source if it works correctly with your game and system. In its properties, disable the "Capture third-party overlays" option. Game platforms, chats, and other programs can draw their own windows with personal messages over the game.

Keep only the necessary sources in the scene: the game or working window, camera, microphone, and design elements. Don't add your personal browser, email, and messengers unless you have to. The fewer sources, the easier it is to track down the cause of unwanted imagery.

Turn off system banners and sounds

Before going live, enable "Do Not Disturb" mode in Windows. Check its schedule and exception list: some apps or important notifications may be allowed separately. If your stream runs long, choose a period that covers the entire broadcast, not just its start.

Then open notification settings and separately check messengers, email, calendar, cloud storage, and programs with work data. Disable banners, sounds, and content previews. If you need notifications during the stream, leave only the alert without text, or allow messages from apps that don't contain personal information.

Check incoming calls, lock screen notifications, reminders, and system alerts. On macOS, the equivalent settings are in Focus mode and notification settings. For personal apps, disable text previews so the sender's name and message content don't appear on screen.

You can check Windows system sounds via additional sound settings: open the "Sounds" tab and set the "Notification" event to "None" or choose a sound scheme with no sounds. This doesn't replace configuring the apps themselves, so after changing the settings, send a test message.

Configure notifications inside the captured program

"Do Not Disturb" mode doesn't block messages that a program draws inside its own window. In the game settings, disable invites, new messages, friend requests, achievements, and other pop-ups. If a notification can't be removed entirely, choose an option without text or move it to an area that isn't captured.

In the browser, check site permissions. Open notification settings and block them for personal email, social media, work dashboards, and messengers. Close tabs with conversations, shopping, and personal documents. For streaming, it's more convenient to create a separate browser profile without personal accounts, saved passwords, and extra extensions.

Incognito alone doesn't protect you from all notifications. A site can get permission to show messages regardless of the viewing mode. Also check the extensions panel, address bar, bookmarks, and recently opened pages list: they can reveal personal data even without a pop-up banner.

Use OBS filters to limit the image

Filters don't replace disabling notifications, but they help cover permanent risk areas. For example, if you're capturing a 1920×1080 window and messages usually appear in the top-right corner, open the source properties, select "Filters," add a "Crop/Pad" filter, and specify cropping of the right edge and top. As a test example, you can start with Right 360 and Top 120, then check the result in the preview.

These values only work for a specific window size and position. After cropping, make sure that important buttons, part of the game, or text you planned to show didn't disappear along with the notification. If the banner appears in different places, cropping alone isn't enough. In that case, use the program's own settings, window capture, or a mask with a neutral image over the risky area.

The filter must be added to the source that outputs the image. It won't remove the notification sound or hide a message that appears in another source. Audio channels are configured separately in the OBS audio mixer.

Assign hotkeys to hide sources

In OBS, open "Settings" → "Hotkeys." For the "Monitor Capture" source, assign separate "Hide" and "Show" commands, for example Ctrl+Alt+M and Ctrl+Alt+Shift+M. For the camera or design source, you can assign your own combinations, but don't use keys that are needed in the game or the program being demonstrated.

A practical example: the "Demonstration" scene contains "Window Capture," camera, and chat, while the "Safe Standby" scene contains a neutral background. To switch to the standby screen, assign Ctrl+Alt+0, and to return to the demonstration, Ctrl+Alt+1. Before going live, press each combination several times and make sure the right scene switches, not the volume or another action.

Hiding a source is useful when you need to quickly remove full desktop capture. However, a backup scene is more reliable: if a notification has already appeared, switch to it rather than hunting for the banner with your mouse among open windows.

Create a separate profile and scene collection in OBS

For regular streams, don't rebuild a safe scene before every broadcast. In OBS, create a separate profile for broadcast settings and a separate scene collection for streaming. The profile stores output and encoder settings, while the scene collection holds the set of scenes, sources, and their layout.

For example, in the "Stream" collection, you can prepare the "Game," "Window Demonstration," "Camera," and "Safe Standby" scenes in advance. Keep only the necessary sources in each scene. This reduces the risk of accidentally enabling your personal browser or full monitor capture.

Don't confuse an OBS profile with a scene collection: a profile doesn't replace scene settings. After creating both, check that the correct profile and collection are selected when OBS starts. That way, you won't have to manually change sources, filters, and element layout before going live.

Separate game audio from system alerts

If the shared Desktop Audio channel is enabled in OBS, all computer sounds can end up in the broadcast. Disable it if you don't need it. For the game, add a separate "Application Audio Output Capture" source or another source that receives sound only from the selected program.

After configuring, launch the game and watch the OBS audio mixer. Then send a test notification to the computer without personal text. The indicator should move only on the channel you intentionally connected to the broadcast. If Desktop Audio reacts, remove it from the scene or disable it in the general settings.

If you use a virtual audio device, route only the game sound into it. Notifications, the browser, and messengers shouldn't use the same output, otherwise their signals will also end up in the broadcast. After changing the device, check that you can hear the game in your headphones and that the sound hasn't disappeared from local monitoring.

Phone video needs to be checked separately. When demonstrating it, enable "Do Not Disturb" mode on the mobile device, disable message previews, and block incoming calls. Computer notification settings don't protect a screen that's transmitted directly from the phone.

Check the broadcast with a local recording

Before going live, make a local recording for a few minutes. Switch between all scenes, open the working window, minimize and restore it, trigger a test notification without personal data. Separately check the moment you switch to the desktop and back to the game.

Watch the recording in fullscreen mode. In a small preview window, it's easy to miss text in the corner, a website address, a file name, an avatar, an email subject, or a phone number. Check the taskbar, system tray, pop-up windows, and accidentally opened apps.

Listen to the recording separately from the image. There should be no sounds from messengers, email, calendar, or system notifications. If an unwanted banner or signal appeared, fix the cause and make a new recording. Just closing a message isn't enough: it can appear again the next time the app starts.

What to do if a notification already went on air

Immediately switch to a safe scene or hide the full capture source. Don't close the message in front of viewers: with monitor capture, you might open a conversation, browsing history, or additional windows.

After the stream, determine exactly what was seen or heard. If a password, verification code, login link, or payment data appeared in the frame, change them. Then check the video source, app notification settings, Desktop Audio, third-party overlays, and assigned hotkeys.

After the fixes, repeat the local recording. Only once you've confirmed that the image and sound are safe, return to screen sharing.

Quick pre-stream checklist

1. Choose game or window capture if you don't need full monitor.
2. Enable "Do Not Disturb" mode and disable banners and sounds from personal apps.
3. Check notifications inside the game, browser, or other captured program.
4. Add a "Crop/Pad" filter if you need to cover a permanent screen area.
5. Disable Desktop Audio or leave only the sound of the app you need.
6. Create a separate OBS profile and scene collection for streaming.
7. Assign hotkeys for the safe scene and for hiding the monitor source.
8. Make a local recording and review it in fullscreen mode with sound on.