> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/faq/troubleshooting-guides/screen-capture-troubleshooting.md).

# Screen Capture Troubleshooting

#### Screen Capture is running, but I do not see the source

* Confirm that the Screen Capture icon is visible in the Windows system tray.
* Then open Studio Monitor and check whether the source appears there.
* If the source does not appear in Studio Monitor, check the network connection, firewall or security software, NDI group settings, Access Manager configuration, or discovery settings before troubleshooting the receiving application.

#### The wrong screen or area is being captured

* Open Capture Settings and check whether Screen Capture is set to capture the full screen or a selected region of interest.
* Also check whether the mouse pointer is set to appear or stay hidden, depending on what you want the receiving application to see.

#### Video works, but audio is missing

* Open the Screen Capture settings and check the selected Audio Source.
* Then open the source in Studio Monitor and confirm whether audio is present there. If audio is present in Studio Monitor but not in the receiving application, check the receiving application’s audio input, monitoring, mute, or routing settings.

#### When do I use Screen Capture HX

* Use Screen Capture HX if your workflow needs GPU acceleration, H.264 or HEVC compression, or more control over bandwidth, resolution, and framerate.I need lower bandwidth or GPU-accelerated capture


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ndi.video/all/faq/troubleshooting-guides/screen-capture-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.