Minimizing a window is not protection. Moving it to your second monitor is not protection. Covering it with Notepad is not protection.
If the app is running, it can leak. Full stop.
Most people learn this the expensive way. You're in a Zoom call, sharing your whole screen because it's faster, and a Slack DM from your manager flashes in: "heads up, your name came up in the exec restructuring." Everyone saw it. Or you're recording an OBS tutorial, accidentally hit Display Capture instead of Window Capture, and your password manager autofills a login in front of 3,000 subscribers. Or you're presenting Q3 numbers to a client and your banking app pops a wire transfer notification: "$12,847.33 pending."
This stuff happens constantly. It's not bad luck — it's just what happens when you share your whole screen and don't think about what else is running. And "just close your tabs" is terrible advice because it breaks your workflow. You need Slack open. You need your notes. You need your password manager. You just need them absent from the capture stream.
Here's how to actually do that.
Visual Hiding vs. Capture Exclusion
People use "hidden" to mean two completely different things, and only one of them works.
Visual hiding = you can't see it locally. Minimized, covered, on another monitor, transparent. This is what everyone does. It does absolutely nothing against screen capture.
Capture exclusion = the compositor never puts the window in the frame. Zoom, Teams, OBS — they literally don't receive the pixels. The window stays fully visible and usable on your machine. It just doesn't exist in the broadcast.
Windows has a native API for this: SetWindowDisplayAffinity with WDA_EXCLUDEFROMCAPTURE. When set, the OS skips that window for screen capture output while leaving it alone locally. On. Off. No reboot required.
Local view: everything. Capture output: only what you allowed. Excluded windows aren't blacked out or blurred — they're absent. The compositor skips them entirely.
If you haven't checked the actual capture preview, you don't know what's leaking. What you see on your own screen has basically nothing to do with what's going out over the wire.
The Built-In Options (And Why They're Mostly Traps)
Zoom and Teams have "Share Window" instead of "Share Screen." This works fine if you're only showing one thing, never switching apps, and no notifications pop up. The second you switch to Display Capture mid-call, or a Slack notification slides over your shared Excel sheet, you're leaking.
Virtual desktops are cleaner than minimizing but same problem — switch to Display Capture and you're leaking both desktops. Notifications bridge desktops. And if you fat-finger the hotkey to Desktop 2 while live, everyone sees your bank.
Focus Assist / DND helps but it's a blunt instrument. Doesn't hide window titles, taskbar previews, Alt+Tab, or the apps themselves. Forget to turn it on and every calendar reminder broadcasts your therapy appointment.
Browser profiles are good hygiene but Slack, 1Password, your terminal, Excel — they don't live in the browser. A browser profile does nothing for them.
OS-level cloaking is the only thing that actually protects against human error. You set rules once. Protected apps stay locally visible and fully usable. They just never enter the capture stream. Not because you're being careful. Because the OS itself is blocking them.
Manual methods work until they don't. And "until they don't" is always when you're live in front of a client or a thousand viewers.
Password Managers
Don't type passwords while screen sharing unless you've tested what the other person can see. That's the rule.
If you must: share only the specific window where you're entering the credential. Pick "Share Window," select your browser, check the preview. Do it inside the shared window — not in a separate app.
Better: cloak the password manager at the OS level. 1Password, Bitwarden, KeePass — whatever. Stays locally visible, autofill works, capture stream sees nothing. Not a black box. Nothing.
Test it. 10-second local recording. Make sure it's completely absent. Check taskbar thumbnails and Alt+Tab — if the title appears there, that's a metadata leak even if the window itself is hidden.
Banking Apps
These are uniquely dangerous because one frame is enough. Your balance, account numbers, wire confirmations — a single screenshot is a fraud starter kit.
I know a guy who was presenting to a board and his Chase app popped a notification: "Wire transfer of $8,400 to vendor approved." The whole board saw it. He didn't even have the app open — it was running in the background. That's the thing with banking apps, they love to push banners even when you think they're asleep.
Close the banking app during the call. Seriously. If you must check it, pause sharing first. In Zoom that's "Pause Share." In Teams, stop presenting. Do not minimize. Do not move to monitor two.
If you absolutely must keep it open: cloak it. This handles the pop-ups, the titles ("Chase — Wire Transfer: $12,847.33" is a leak even minimized), and the instant exposure when you accidentally switch to Display Capture in OBS.
Slack
Slack is dangerous because the context alone is damaging. A DM that says "heads up, your name came up in the exec restructuring" doesn't need to be fully readable to ruin your day. The channel name #competitor-intel is already a leak.
Best move: quit Slack before the call. Use your phone for internal coordination. Don't keep it on the same machine you're sharing.
If it must stay open: cloak it. Window cloaking + title masking + notification shield. Ask a colleague in the meeting if they can see your Slack window in the participant view. For OBS, check the source preview — not the main window. OBS shows different things depending on whether you're using Window Capture or Display Capture.
OBS
OBS is the most powerful capture tool and therefore the easiest to misconfigure. The distinction that matters: Window Capture vs Display Capture.
Window Capture = one specified window. Other windows don't appear in the source even if they're in front. Use this when recording a single app.
Display Capture = your entire monitor. Everything on it appears in the recording. Switch from Window Capture to Display Capture "just to show something quickly" and every sensitive window on that screen is now in your video permanently.
Also, can we talk about how OBS keeps moving the source properties button? It used to be right there. Now it's... somewhere else. Anyway.
Setup:
- Add a Window Capture source. Not Display Capture.
- Select the exact target window.
- Set Window Match Priority to "Window title must match" so renaming doesn't break the source.
- Review the source preview before you hit record.
- If the target closes, configure blank source until it reappears.
Every time you change sources mid-stream — game capture to "show my desktop" — you're now on a full-display source. Re-verify after every switch. I know I already said this but people keep forgetting and then emailing me panicked.
Before You Go Live
Do this. It takes a minute.
- Confirm your source. "Share Window." Window Capture. Not Display Capture. Not "Share Screen."
- Inspect the preview. Look for sensitive windows, dialogs, notifications.
- Run a 10-second test recording. Review it.
- Check taskbar and Alt+Tab. Protected stuff shouldn't appear.
- Make sure Windows isn't about to force-restart for an update. Yes this happened to me. Client call. Blue screen. Never again.
That's it. I used to have more steps but honestly those are the ones that matter. The rest is just anxiety.
When It Goes Wrong
Second monitor appears: you switched to Display Capture. Stop sharing, reselect, verify. Or cloak everything before you start.
Window renamed or reopened: new handle, title match fails. In OBS this can blank the source or capture the wrong thing. Reselect the target, use a more stable match priority, retest.
Pop-up leaks: notification system sometimes runs higher privilege than cloaking, or the pop-up spawns from a separate process. Enable OS-level notification shielding. If it persists, find the unprotected process in Task Manager and add it.
Source changes mid-stream: the big one. You start with "Share Window," click "Share Screen" to show a PDF, now your whole desktop is visible. Treat every source change as a new verification event. With persistent OS-level cloaking rules this is less critical — protected apps stay excluded regardless — but you should still check.
The Actual Workflow
Low-risk, single-app presentation? Selected-window sharing is fine. Verify once, present, done.
High-risk, multi-app workflow? Use OS-level cloaking. Set it once, trigger automatically, stop thinking about it. What you're sending out contains only what you meant to show. Everything else stays on your end.
NoCapture does this for free — two windows, one device, no card. Most people don't need more than that. If you do, Pro is $5/month. The core protection isn't paywalled. It's just... the thing the app does.
Anyway. Stop minimizing windows and hoping. Test your capture output. Or use something that handles it for you.
If you are tired of manually minimizing, covering, and praying before every screen share, NoCapture automates the entire workflow. Per-window cloaking, title masking, Alt+Tab skipping, live preview, and smart routines — free forever for two windows. Get it here.
