Checklist: What to Verify Before Screen Sharing

Every screen share is a broadcast. Treat it like one. This checklist covers the technical verification steps that prevent the leaks that manual cleanup misses — window titles, metadata exposure, multi-monitor mistakes, and the capture settings that override your preparation.

Before You Click Share

Application Layer

[ ] Verify active window only: If your meeting app supports "Share Window" vs "Share Screen," use "Share Window" unless you genuinely need to show multiple applications.
[ ] Check background windows: Minimized applications are still visible to Display Capture and some Window Capture implementations. Close or cloak applications you don't intend to share.
[ ] Audit browser tab titles: Even inactive tabs display titles in the tab bar. Titles like "[Client] — Termination Discussion" or "[Competitor] Pricing" are visible to capture and window enumeration APIs.
[ ] Close or cloak password managers: 1Password, Bitwarden, and Keeper display vault names and entry titles in the window title. These titles are captured by window enumeration even when the window is minimized.
[ ] Verify email client state: Outlook and Gmail in browser display folder names and message counts in the title bar. A folder named "[Client] Legal Dispute" is visible even when the email client is behind another window.
[ ] Check messaging applications: Slack, Discord, and Teams display workspace names, channel names, and direct message participant names in window titles and taskbar tooltips.

File System Layer

[ ] Clean desktop of sensitive files: Folder and file names on the desktop are visible during application switching, window minimization, and desktop exposure. Move sensitive items to non-desktop locations.
[ ] Audit recent files: PowerPoint, Excel, Word, and PDF readers display recent files in the application start screen and File menu. These lists reveal project names, client names, and document types.
[ ] Verify download folder: Browser download bars and recent download lists display file names. A downloaded file named "[Competitor]_Acquisition_Analysis.pdf" is visible in the browser chrome.
[ ] Check cloud sync indicators: Dropbox, OneDrive, and Google Drive display sync status, file names, and recent activity in Explorer sidebars and system tray menus.

Metadata Layer

[ ] Verify window titles are sanitized: Use a window title inspection tool or PowerShell (Get-Process | Where-Object {$_.MainWindowTitle -ne ""} | Select-Object ProcessName, MainWindowTitle) to audit all visible window titles.
[ ] Check taskbar tooltips: Hover over each taskbar icon to verify that tooltip text doesn't expose sensitive information. Some applications display recent document names or account information in tooltips.
[ ] Audit system tray icons: Right-click system tray icons to verify that context menus don't expose account names, connection details, or recent activity.
[ ] Verify notification settings: Check Windows Settings → System → Notifications to confirm that sensitive applications are suppressed and that priority exceptions won't break through.

Capture Settings Layer

[ ] Confirm share target: In multi-monitor setups, verify that you're sharing the intended display. Zoom and Teams default to the primary display, which may not be the display with your presentation.
[ ] Verify capture resolution: High-resolution captures (4K, ultrawide) reveal more desktop detail than lower resolutions. If your audience doesn't need 4K fidelity, reduce capture resolution to minimize accidental exposure.
[ ] Check recording indicators: Verify whether the meeting is being recorded (cloud or local) and whether participants have recording permissions. Recordings create permanent archives of any accidental exposure.
[ ] Disable annotation if unnecessary: Some platforms allow participants to annotate your shared screen. Disable this unless actively needed to prevent accidental or malicious markup.

Multi-Monitor Specific

[ ] Identify all connected displays: Windows Key + P shows active displays. Verify that unexpected displays (projectors, TVs, capture cards) aren't connected and active.
[ ] Verify display numbering: Windows assigns display numbers that may not match physical arrangement. Confirm that "Display 1" in the share dialog corresponds to your intended monitor.
[ ] Check display mirroring: If displays are mirrored, sharing either display shares both. Disable mirroring unless intentionally presenting to a local audience.
[ ] Audit display content on all monitors: Even if you're sharing only one monitor, cursor movement to other monitors is visible if "Share Screen" captures the extended desktop.

During the Share

[ ] Avoid Alt+Tab during sensitive moments: The Alt+Tab switcher displays window thumbnails and titles for all running applications. Use taskbar clicking or Win + number shortcuts to switch applications if necessary.
[ ] Pause before switching applications: When moving from one application to another, pause for 1-2 seconds to verify that the correct window is active and that no background content is visible during the transition.
[ ] Monitor for notification breakthrough: Even with Do Not Disturb enabled, priority notifications and system alerts can appear. Be prepared to dismiss them immediately.
[ ] Verify cursor visibility: Some platforms display your cursor to viewers. Ensure that cursor movements don't draw attention to sensitive areas of the screen.

After the Share

[ ] Stop sharing before opening sensitive applications: The most common post-share leak is opening a sensitive application while still sharing. Develop the habit of explicitly stopping the share before switching context.
[ ] Verify share is actually stopped: Some platforms have delayed stop responses or UI indicators that lag behind the actual capture cessation. Wait for the "You are screen sharing" indicator to disappear before trusting that sharing is off.
[ ] Check for recording retention: If the meeting was recorded, verify who has access to the recording and whether retention policies align with your privacy requirements.

The One Setting Everyone Forgets

Windows Game Bar (Win + G) and Xbox Game Bar overlay: This overlay captures screenshots, records gameplay, and broadcasts to Xbox Live. It runs by default on Windows 10 and 11 and can be triggered accidentally with Win + Alt + R (record) or Win + Alt + G (capture). The recordings are saved to Videos\Captures and may be synced to OneDrive if camera roll backup is enabled.

[ ] Disable Game Bar: Settings → Gaming → Game Bar → Turn off "Record game clips, screenshots, and broadcast using Game Bar"
[ ] Disable background recording: Settings → Gaming → Captures → Turn off "Record in the background while I'm playing a game"
[ ] Verify Captures folder: Check Videos\Captures for unexpected recordings and delete any that contain sensitive content.
[ ] Disable OneDrive camera roll backup: OneDrive Settings → Backup → Photos and videos → Turn off if you don't want captures synced to cloud storage.

When Manual Checklists Fail

This checklist is comprehensive and time-consuming. A thorough run takes 5-7 minutes. For professionals who share screens 4-6 times daily, that's 20-42 minutes of daily verification — approximately 2-3.5 hours per week, or 100-180 hours per year.

The failure mode of manual checklists is human: fatigue, time pressure, and the assumption that "I did this yesterday, it's probably fine today." The leaks that make headlines — the exposed API keys, the visible termination notices, the leaked client names — occur when someone skips the checklist because they're running late, distracted, or simply human.

The alternative is architectural: persistent, OS-level controls that enforce privacy without requiring a checklist before every call. Window cloaking, title masking, and metadata sanitization that apply automatically, regardless of whether the user remembered to verify.

Both approaches have their place. The checklist is your defense in depth. The architecture is your foundation.

NoCapture provides persistent OS-level window cloaking and title masking for Windows 10 and 11. Define privacy rules once — they apply automatically across reboots, application launches, and screen sharing sessions without manual verification.