> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command-connector/configuration/configure-h.265-for-non-verkada-channels.md).

# Configure H.265 for non-Verkada channels

H.265 offers a higher level of video quality than H.264 on a camera connected through a Verkada Command Connector. Devices that cannot play H.265 receive the same video transcoded to H.264.

{% hint style="warning" %}
This article is for non-Verkada channels. H.265 on a Verkada camera is a different setting. See [Camera High Efficiency Video Encoding (HEVC)](/verkada-cameras/video-streaming-and-sharing/live-streaming/camera-high-efficiency-video-encoding-hevc.md) for more information.
{% endhint %}

***

### Before you begin

H.265 requires all of the following:

* The camera supports H.265
* The camera has two H.265 encoders, one for the high quality (HQ) stream and one for the standard quality (SQ) stream
* The channel is not a pan-tilt-zoom (PTZ) camera. PTZ cameras require H.264

***

## Configuration

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**Select the non-Verkada channel.**
{% endstep %}

{% step %}
**At the bottom right, click Settings.**
{% endstep %}

{% step %}
**Select Video Streaming.**
{% endstep %}

{% step %}
**Next to Codec, select H.264 or H.265.**
{% endstep %}
{% endstepper %}

***

## When the codec cannot be changed

Hover over the codec selection on the Settings page to see why you can't change it.

| What you see                                                                | What it means                                                                                                                     |
| --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| PTZ cameras require H.264 encoding.                                         | The channel is a PTZ camera. Leave the codec on H.264.                                                                            |
| The camera hasn't reported which codecs it supports yet. Try again shortly. | Command does not have codec information from the camera yet.                                                                      |
| Channel only supports H.264.                                                | The camera reported H.264 only.                                                                                                   |
| H.265 requires 2 encoders for adaptive quality recording.                   | H.265 is listed, and that option is unavailable. H.264 can still be selected. The camera does not have two usable H.265 encoders. |

### Codec and Manufacturer mode

Streaming Profile Selection and Codec are separate settings. In Manufacturer mode, the codec selected still applies.

* When you click **Change** next to *Current Profile*, profiles that use a different codec stay in the list and are unavailable. With *Codec* set to H.265, you cannot select an H.264 profile, and vice versa.
* *Current Profile* shows H.264 or H.265 for the applied HQ and SQ profiles. When the applied codec is not known, the Codec column shows a dash.


---

# 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://help.verkada.com/command-connector/configuration/configure-h.265-for-non-verkada-channels.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.