There is no universal setting that makes every password field invisible to every screen recorder. If a tool has permission to capture your display, it can generally capture whatever is rendered on it — including the dots in a password field. The dots hide the characters from shoulder surfers, not from pixel-level capture.
That said, there are layers of defense that substantially reduce exposure.
Layer 1: Don't Type Passwords on Camera
The most reliable method is also the simplest: don't type passwords while recording or sharing your screen.
- Use a password manager with biometric or PIN autofill. The password is filled without keystrokes, and the exposure window is milliseconds instead of seconds.
- Use passkeys where supported. Passkeys authenticate through your device and never expose a traditional password at all. Microsoft documents Windows Hello passkey support here.
- Pause the recording, authenticate, then resume.
Layer 2: Isolate the Password Manager
If you must keep your password manager open during a screen share, exclude it from capture at the OS level.
Free Option: CaptureGuard
GitHub: xzulab/CaptureGuard
Select your password manager's process (1Password, Bitwarden, KeePass, etc.) and apply protection. The window stays visible to you but disappears from the capture stream.
Limitation: 64-bit only. No notification shield — if your password manager shows a "Password copied" toast, that toast may still appear if it's drawn by a separate process.
Full Protection: NoCapture
NoCapture adds the metadata layer:
- Cloak: The password manager window is excluded from capture.
- Title masking: Taskbar and Alt-Tab show a generic title instead of "1Password — AWS Root Console."
- Notification shield: Suppresses "password copied," "TOTP code," and other sensitive banners from protected apps.
- Live preview: Verify the capture stream contains no password-related UI before you share.
We wrote about how AI screen scrapers harvest window titles and metadata here. A title like "1Password — prod-db-admin" tells a story even if the window itself is hidden.
Layer 3: Use Application-Specific Capture Settings
Some password managers have built-in screen capture protection. KeePass, for example, can prevent screen captures of its window using Windows API calls. Check your password manager's security settings.
Limitation: This only protects the password manager's own window. It doesn't protect browser autofill dropdowns, OS notification toasts, or other apps.
What Doesn't Work
- Minimizing the password manager: Minimized windows can still be captured by some tools, and their taskbar titles remain visible.
- Putting it on a second monitor: See our breakdown of why monitor separation fails.
- Trusting "secure desktop" for everything: Windows UAC uses a protected desktop for elevation prompts, but normal password fields in browsers and apps do not.
The Bottom Line
For recorded tutorials: pause recording during authentication.
For live screen shares: use a password manager + autofill + window cloaking.
For high-stakes presentations: add title masking and notification shielding.
The goal isn't perfect security against a determined attacker. It's deterministic protection against the accidental exposure that happens when you're presenting and your password manager decides to show a notification.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
