> 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/using-ndi/ndi-for-video.md).

# NDI for Video

{% hint style="success" %}
If you can't find the answers you're looking for here check out our [**community forums**](https://community.ndi.video/mod/forum/view.php?id=39) or see our [**troubleshooting guide**](/all/faq/troubleshooting-guides.md)
{% endhint %}

As a technology designed to connect video, ensuring interoperability across all NDI products—both hardware and software—is one of the fundamental principles that NDI strives to uphold for its growing user community.

In this guide, we will explore how NDI can connect video while maintaining interoperability and consistent performance at the heart of any workflow. We will cover some of the basics of digital video and explain the various ways NDI-enabled devices and NDI formats can work together to create a seamless networking environment.

## Contents

1. [Digital Video Basics](/all/using-ndi/ndi-for-video/digital-video-basics.md)
2. [NDI Video Codecs and Format Matrix](/all/using-ndi/ndi-for-video/ndi-video-codecs-and-format-matrix.md)
3. [NDI Encoding Support Matrix](/all/using-ndi/ndi-for-video/ndi-encoding-support-matrix.md)
4. [Interoperability Scenarios](/all/using-ndi/ndi-for-video/interoperability-scenarios.md)


---

# 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/using-ndi/ndi-for-video.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.