News · Membran Digital

How to hide sensitive windows during live screen shares

Keep private notes and messaging apps invisible to Zoom, Teams, and OBS viewers while sharing your desktop.

By Nigel Hawthorne·August 31, 2026·4 min read
Key points
  • NoCapture blocks DXGI, BitBlt, and DWM graphics APIs to hide select windows from screen sharing tools.
  • The lightweight process runs without kernel drivers, using less than 1% CPU and under 20 MB of RAM.
  • A free plan cloaks two windows, while the five-dollar monthly Pro tier permits unlimited cloaked windows.

The Screen Share Dilemma

Sharing your screen during a video call is inherently risky. You want to present a slide deck or demonstrate a software build, but your desktop holds private context. Open Slack channels, financial dashboards, scratchpads, and password managers sit right beside your working windows. One wrong click or unwanted notification exposes internal data to clients, team members, or stream audiences.

The standard workarounds are inefficient. Dragging windows to a secondary monitor forces your gaze away from the camera. Sharing a single window breaks your presentation flow whenever you need to switch tools. Pausing screen sharing creates awkward silences while you navigate your desktop.

Screen capture tools like Zoom, Teams, and OBS grab graphics frames directly from the operating system display pipeline. To share your desktop safely, you must intercept those calls before the broadcast software processes them.

How OS-Level Interception Works

Most screen recording and streaming applications query operating system graphics APIs to capture screen content. On Windows, applications use DXGI, BitBlt, and DWM APIs to assemble frames. Screen capture tools on macOS and Linux rely on equivalent system graphics subsystems.

NoCapture operates by blocking DXGI, BitBlt, and DWM API calls for specifically designated application windows. Instead of painting a digital box over a recording after it renders, it stops the OS from delivering window content to the capture hook entirely. To you, the app remains fully visible, interactive, and crisp on your monitor. To Zoom, Teams, or OBS, the window does not exist on the frame buffer.

Because this interception happens without loading third-party kernel drivers, system performance remains unaffected. The process consumes less than 1% CPU and under 20 MB of RAM.

Step 1: Assign Cloaked Windows

Start by launching NoCapture on Windows 10/11, macOS, or Linux. Identify which apps hold data you cannot risk broadcasting. Common targets include messaging clients, internal notes, CRM dashboards, and code editors containing production keys.

Apply per-window cloaking to those target applications:

  • Free Tier ($0): Pick up to 2 specific windows to cloak permanently. This covers basic setups like keeping a scratchpad and a primary chat window private.
  • Pro Tier ($5/month): Select unlimited windows across complex multi-app workflows.

Select the target window from the application list to mark it for cloaking. Once designated, the window instantly drops out of the operating system capture stream.

Step 2: Enable Title Masking and Global Hotkeys

Hiding a window's body content solves only part of the problem. Taskbars and window switchers can still reveal sensitive information through window titles, such as document names or private channel topics.

Turn on title masking for your cloaked targets. Title masking replaces the authentic window title string inside system lists like Alt+Tab and the taskbar. Anyone watching your screen share sees generic placeholder text instead of confidential document titles.

Next, map global hotkeys for instant manual control. Setting a trigger like Ctrl+Alt+N lets you toggle cloaking status on the fly without minimizing your active presentation or opening a configuration menu.

Step 3: Check the Live Preview Pane

Do not broadcast blind. Before opening your call on Zoom or starting an OBS stream, open the live preview pane in NoCapture.

The live preview pane renders the exact display frame that external capture applications receive. Look at the pane to confirm your setup:

  • Your primary screen displays your working windows, notes, and private apps normally.
  • The live preview pane shows your desktop with the targeted windows completely removed or blacked out.

If the preview frame shows your private apps stripped away, your broadcast feed is secure.

Step 4: Present with Ghost Mode

Maintaining eye contact with your camera while referring to notes is difficult if those notes sit on a separate display. Floating private notes directly over your presentation window solves this, provided the presentation software cannot see them.

Enable ghost mode on your notes window. Ghost mode transforms the cloaked window into a transparent or outline-only overlay. Position this overlay near your web camera at the top of your screen.

Launch your screen share in Zoom, Teams, or OBS, selecting your full desktop display. Deliver your presentation while reading directly from your floating notes. Your audience sees only the underlying slides or code, while you read your notes directly in your line of sight.

Multi-Monitor Setup and Enterprise Admin

If your rig uses multiple displays, cloaking rules apply across all monitors without extra configuration. Windows retain their hidden status even when dragged from one monitor to another.

Settings persist automatically across system reboots. You do not need to reconfigure cloaking rules before morning standup meetings or planned live streams.

For engineering teams or agencies that require standardized privacy policies across multiple workstations, the Teams plan costs $49 per month. It includes 10 user seats along with administrative controls to manage deployment rules centrally.

More from Membran Digital News
Published via Stork Wire — independent trade coverage, in partnership with this site.