Why Can't Jarvis See My Screen on Windows?

If Jarvis (getjarvis.eu) isn't reading your screen on Windows 10+, the most common culprits are capture protection on the target app, a multi-monitor mix-up, or hardware-accelerated rendering hiding content. Some apps with DRM or privacy modes, certain banking sites, protected video, deliberately block screen capture, so Jarvis sees a black frame there by design. If you run multiple displays, confirm the window you're asking about is on the screen Jarvis is capturing. If a whole app shows blank, try disabling hardware acceleration in that app, which can interfere with capture. Relaunch Jarvis after changes; the floating bar opens with Ctrl+/. Unlike macOS, Windows has no separate Screen Recording permission to grant. Jarvis routes screen-aware tasks to frontier models from Anthropic, OpenAI, and Google, never stores captures, and hosts data under GDPR. Plans start at $16/month when you need more than the free weekly requests.

On Windows, the leading reason Jarvis sees nothing is intentional capture protection. Apps handling protected content, DRM-restricted video, some banking and finance portals, and certain enterprise tools, mark their windows as non-capturable, so any screen reader, Jarvis included, receives a black rectangle instead of pixels. This isn't a Jarvis failure; the OS is honoring the app's privacy flag. If only specific windows come back blank while everything else reads fine, you've almost certainly hit this protection. The workaround is to ask Jarvis about content that isn't capture-protected, or to paste the relevant text instead.

Two setup issues cause blank or wrong reads. First, multiple monitors: if Jarvis captures one display and the window you mean is on another, it'll describe the wrong screen, so move the target window to the captured display or specify which screen. Second, hardware acceleration: some apps render through the GPU in a way that capture can't always read, producing a blank frame. Toggling off hardware acceleration in that specific app often restores capture. After either change, relaunch Jarvis so it re-initializes capture, then test by asking it to describe the window in front of you.

Getting started