Protect selected windows from screen sharing, screen recording, and desktop capture while keeping them visible and interactive on your computer.
Website • Download • Meeting privacy • Report an issue
NoCapture is a desktop privacy tool for protecting sensitive windows during Zoom, Microsoft Teams, Google Meet, Discord, OBS, and other screen-sharing workflows.
Screen sharing can expose terminals, password managers, private messages, financial information, and confidential documents.
Minimizing a window or moving it to another monitor does not always protect it from accidental capture. NoCapture applies operating-system-level window capture protection so a selected window remains visible and usable locally while being excluded from supported capture paths.
Recording.2026-08-09.235805.mp4
NoCapture hides selected windows from supported screen capture, recording, and screen-sharing workflows while keeping them visible to you.
It supports automatic protection rules, live preview of shared content, and per-window control across supported Windows, macOS, and Linux environments.
- Protect or unprotect individual application windows.
- Keep protected windows visible and interactive locally.
- Hide selected windows from supported screen capture and recording paths.
- Preview the frame visible to a screen-sharing or recording workflow.
- Hide protected windows from taskbar thumbnails and window switchers where supported.
- Automatically re-apply protection when a protected window loses focus.
- Configure calendar-, application-, time-, and focus-based routines.
- Use customizable global hotkeys.
- Apply different protection rules across multiple displays.
- Use native operating-system APIs without kernel drivers or browser extensions.
- Download NoCapture from the official download page.
- Launch the application.
- Expand an application to view its open windows.
- Select a window and click Protect.
- Open Live Preview to verify what will be visible during screen sharing.
- Start your meeting, presentation, or recording.
Protection behavior depends on the operating system, graphics stack, permissions, and capture method. Test your intended workflow before relying on NoCapture for sensitive information.
NoCapture groups open windows by application. Expand an application, select a window, and click Protect.
The window remains available to you locally while protection is active. You can continue to type, click, resize, and work normally.
The primary toggle controls whether a selected window is protected from supported capture paths.
Click Unprotect to make the window visible to the capture workflow again.
Where supported, remove a protected window from taskbar thumbnails and window switchers.
Keep a protected window above other local windows. This is useful for private notes, reference documents, or chat that you need to see while presenting.
Automatically re-apply protection when a protected window loses focus.
This helps reduce the risk of accidental exposure while switching between applications during a meeting or presentation.
Live Preview shows the frame that a supported screen-sharing or recording workflow can receive.
Before sharing your screen in Zoom, Microsoft Teams, Google Meet, OBS, or another application, use Live Preview to verify that protected windows are excluded from the output.
Always test the exact application, operating system, display, and capture mode you plan to use.
NoCapture can automate repetitive privacy tasks so you do not have to manually protect windows before every call.
Create rules that automatically protect selected windows:
- Calendar-based: Protect applications before a scheduled meeting.
- Application-based: Protect a window when a selected application launches.
- Time-based: Apply protection during specified work hours.
- Focus-based: Re-apply protection when a protected window loses focus.
Use Ctrl+Alt+N to toggle protection for the active window.
Hotkeys can be customized in Preferences for actions such as protect, unprotect, pin, and preview.
- Match your system theme or use dark mode.
- Launch NoCapture with the operating system.
- Start minimized or open the control panel.
- Configure notification handling.
- Apply different rules to different displays.
When you click Protect, NoCapture asks the operating system to exclude the selected window from supported capture output.
- Local view: The window remains visible, interactive, and usable.
- Capture output: The window is omitted from supported screen-sharing or recording output.
- Workflow: You can continue working without minimizing or closing the window.
NoCapture is designed for supported operating-system capture paths. Results may vary depending on the operating system, application, graphics stack, permissions, capture API, and compositor.
NoCapture is designed to help protect windows during workflows involving:
- Zoom
- Microsoft Teams
- Google Meet
- Discord
- Webex
- OBS
- Streamlabs
- XSplit
- NVIDIA ShadowPlay
- Native screenshot and recording tools
- Desktop applications that capture frames through supported operating-system APIs
No software can prevent someone from photographing your physical display with a separate camera. Always verify protection with the exact software and configuration you intend to use.
Desktop AI assistants and automation tools may use screenshots or desktop-capture APIs to interpret what is visible on your screen.
NoCapture applies the same window-level protection to supported capture paths, helping reduce the risk of exposing password managers, private messages, financial information, terminals, and confidential documents.
Protection is not universal. Capture behavior can vary between tools, operating systems, graphics drivers, permissions, and API implementations.
Read about AI screen-capture risks
Protect client documents, internal chats, research, and terminals while presenting or collaborating with customers.
Keep private chats, password managers, production tools, and stream controls out of broadcasts while keeping them visible locally.
Protect terminals, API keys, database consoles, deployment tools, and .env files during pair
programming, support sessions, and technical demonstrations.
Reduce accidental exposure of sensitive records, client information, and private documents during remote meetings.
NoCapture is a technical privacy tool and does not by itself guarantee compliance with HIPAA, attorney-client privilege, GDPR, or any other legal or regulatory requirement.
Reduce the amount of desktop content exposed to applications that use supported screen-capture methods to interpret your computer screen.
Read the AI meeting privacy guide
NoCapture uses native operating-system APIs and does not require kernel drivers, browser extensions, or screen-capture hooks.
| Platform | Technology | Status |
|---|---|---|
| Windows | SetWindowDisplayAffinity and WDA_EXCLUDEFROMCAPTURE |
Supported |
| macOS | Core Graphics window-sharing controls | Verify per release |
| Linux/X11 | X11 and compositor APIs | Verify per release |
| Linux/Wayland | Compositor-dependent protocols | Verify per compositor |
Performance and compatibility can vary by operating system, compositor, graphics driver, display configuration, and capture application.
Check the official download page for current builds, system requirements, and supported versions.
If a capture workflow does not behave as expected, please open an issue with the following information:
- Operating system and version.
- NoCapture version.
- Capture application and capture mode.
- Number of displays and display configuration.
- Graphics hardware and driver version.
- Steps to reproduce the problem.
Please do not include passwords, API keys, private messages, customer information, or other sensitive content in issue reports.
No. A protected window remains visible and interactive locally while protection is active.
NoCapture is primarily designed for window-level protection. Monitor-level behavior depends on the operating system and capture application.
No. A separate camera can photograph a physical display, and NoCapture cannot prevent that.
Yes, NoCapture is designed to protect selected windows from screen recorders, screen-sharing applications, and other supported operating-system capture paths.
However, compatibility may vary depending on the recorder, operating system, graphics driver, permissions, and display configuration. Always test your exact setup before using NoCapture with sensitive information.
Yes, provided the application and capture workflow support the operating-system protection method used by NoCapture. Verify the result with Live Preview before sharing.
I leaked AWS credentials during a client Zoom call. Twice.
The first time, a terminal was minimized behind the browser. I had cleaned my desktop before the call but forgot that the terminal was still open. Someone saw the access key, and we spent 48 hours rotating credentials.
The second time, I moved Slack to another monitor and assumed it was safe. I switched to display capture for a few seconds to show a PDF, and private Slack messages appeared in the meeting.
Minimizing is not protection. Moving a window to another monitor is not always protection. Closing everything also breaks the workflow.
So I learned the relevant operating-system compositor APIs and built the toggle I needed.
- Official NoCapture website
- Download NoCapture
- Meeting privacy use cases
- Why “Just Close Your Tabs” Is Terrible Advice
- The Best App Hider for Screen Sharing
- Hide Apps Without Breaking Workflow
- Screen Capture APIs and Desktop Extraction
- AI Meeting Scrapers and Window Title Harvesting
- NoCapture changelog
Contributions are welcome, especially for:
- macOS and Linux compatibility.
- New capture-workflow tests.
- Accessibility improvements.
- Translations.
- Documentation.
- Bug reports and reproducible test cases.
Before contributing:
- Read the repository guidelines.
- Open an issue for substantial changes.
- Do not submit private data, credentials, or confidential screenshots.
- Include operating-system and capture-application details when reporting bugs.
Do not use GitHub issues to report security vulnerabilities.
For security reports, contact:
Please avoid including credentials, private messages, customer data, or other sensitive information in public reports.
This project is licensed under the terms described in the LICENSE file.
Built with obsession, not surveillance.