> 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/developing-with-ndi/advanced-sdk/using-h.264-h.265-and-aac-codecs/h.265-support.md).

# H.265 Support

\
The H.265 parameter sets must be provided for every I-frame. For H.265, these are the VPS, SPS, and PPS NAL units. They must be in Annex B format, along with their start codes. Provide them in both of the following places:

* Inline in the main bitstream (the data\_size bytes), immediately before the first slice of the I-frame.
* In the extra data (the extra\_data\_size bytes that follow the main bitstream).

Both copies must be identical and must come from the same encoder output. Set extra\_data\_size to 0 for frames that are not I-frames.

Some decoders, including the hardware decoders used on Windows, only read the parameter sets from the main bitstream. Other decoders, and receivers that record or pass through the compressed stream, use the extra data. Providing both makes sure that your stream can be decoded by all receivers.


---

# 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/developing-with-ndi/advanced-sdk/using-h.264-h.265-and-aac-codecs/h.265-support.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.
