Use a live preview to check what a screen share exposes

A clean desktop is not proof of a clean screen share. A private window may remain visible to a capture tool even when you are focused on something else, and a notification can arrive after the meeting starts. The useful check is the one that shows what the capture path is seeing, not just what you expect it to see.

nocapture includes a live preview pane for checking what capture tools see before sharing. Use it as a practical audit: compare the preview with your desktop, protect windows that should stay private, and check again when something changes. The preview is a check of the path in front of you, not a promise about every recorder or every possible desktop state.

Set up the audit before the meeting

First, decide what the audience needs to see. Keep the presentation, document, or application needed for the session available. Identify the windows that should remain private: chat, email, account pages, internal notes, or anything containing sensitive information. This is a short inventory, not a request to close everything else.

Open the capture tool you plan to use and bring up nocapture’s live preview. Compare what appears in the preview with what is on your own desktop. Look for a private application, an exposed title, or a window on another display that you did not intend to include. If the preview does not match your expectations, stop before sharing and adjust which windows are protected.

Do not assume a test of one layout covers another. If you will share a different display, application, or arrangement, inspect that state too. The practical question is not whether the desktop looks tidy. It is whether the view supplied to the capture tool contains only what you mean to share.

Protect windows, then verify the result

Use nocapture to protect the windows you identified as private. Its purpose is to prevent private apps, windows, and titles from being captured during screen sharing, recording, or AI scraping. After applying protection, return to the live preview and check the result. Confirm that the material you intend to present is still visible and that the private windows no longer appear in the preview.

Keep the test specific. Check the actual capture tool and the actual display you will use, rather than treating a successful test in one setup as proof for every setup. nocapture works with tools including Zoom, Teams, OBS, Discord, and Google Meet, but a preview check for one capture path should not be treated as a test of all the others.

Window contents are only one source of exposure. nocapture can mask window titles in Alt+Tab, the taskbar, and window lists, and it can suppress alerts and notifications from protected applications. Those protections address different leak paths. A preview of the shared image does not, by itself, tell you whether a title is exposed elsewhere or whether an alert will appear later. Check those surfaces separately and make sure the relevant windows are protected.

Repeat the check while sharing

Once the session begins, keep the preview available if your workflow allows it. Recheck after switching applications, changing displays, opening a new window, or applying a different privacy routine. These are the moments when the intended boundary can change. If the preview shows something unexpected, pause the share before continuing and correct the protected-window setup.

Notifications deserve their own test. Before a high-stakes session, consider whether a protected application might generate an alert. Verify that notification suppression is part of the protection you are relying on, and check the preview again during the session. Do not rely on a notification that has not happened yet as proof that future alerts are handled.

For recurring calls, smart routines can apply privacy presets in one click. That reduces repeated setup, but it does not remove the need to audit the result. Check the preview after applying the routine, especially if the windows or capture tool have changed since the last time you used it.

Know what the preview can and cannot establish

A live preview is a useful operational check, not a full security test. It can help you see what the active capture path is presenting before and during a session. It cannot establish that every application, recording method, or background process on the device behaves identically. Keep the test tied to the tool and setup you will actually use, and avoid expanding its result into a broader guarantee.

If you need a broader view of the options for isolating sensitive windows, our guide to four methods for isolating windows during live screen shares compares approaches. For the immediate task, the repeatable habit is simpler: decide what can be shown, protect what cannot, inspect the preview, then inspect it again whenever the shared view changes.

That extra check is most valuable before the first audience sees the screen. It is also the check to repeat when the meeting is already underway and you are about to reveal a new window. A few seconds looking at the capture view can catch a mismatch that the presenter’s own desktop view will not.