> For the complete documentation index, see [llms.txt](https://docs.ndi.video/brand/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/brand/ndi-formats/understanding-ndi-formats/ndi-hx2.md).

# NDI HX2

**NDI HX2** is the official and only name that should be used for this format. Contrary to some wrong usages, HX **cannot** be replaced by "High Efficiency."

{% hint style="success" %}
[Click here](#download) to download the NDI HX2 logo package.
{% endhint %}

## Product Marketing Guidelines

Here are some value propositions, marketing verbiage, and information you can use to build content for your NDI HX2 dedicated page or section:

### Technical information

<table data-header-hidden><thead><tr><th width="303"></th><th></th></tr></thead><tbody><tr><td>Codec</td><td><a href="https://en.wikipedia.org/wiki/Advanced_Video_Coding">AVC</a> (H.264) and <a href="https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding">HEVC</a> (H.265)</td></tr><tr><td>Bandwidth at 1080p60</td><td>H.264: ~ 16 Mbps / H.265: ~ 11 Mbps</td></tr><tr><td>Bandwidth at 2160p60</td><td>H.264: ~ 30 Mbps H.265: ~ 21 Mbps</td></tr><tr><td>Glass-to-glass latency</td><td>Very low - under 150ms average</td></tr><tr><td>Platform integration possibility</td><td>CPU, GPU, FPGA</td></tr><tr><td>Quality</td><td>No visible compression artifacts</td></tr></tbody></table>

***

## Download the NDI HX2 logo package  <a href="#download" id="download"></a>

{% file src="/files/pLfnWEV6XSJTgZbM4IiK" %}

{% hint style="warning" %}
Please follow the general [NDI Format logos guidelines](/brand/ndi-formats/logos-guidelines.md) and adapt them to fit this specific logo.
{% endhint %}


---

# 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 dynamically 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/brand/ndi-formats/understanding-ndi-formats/ndi-hx2.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 `build a script that syncs our docs to a CMS` 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.