> 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/change-a-non-verkada-camera-resolution.md).

# Change a non-Verkada Camera Resolution

Change a non-Verkada camera resolution for aspect ratio or to gain more channels.

Some non-Verkada cameras connected to Command through a Command Connector allow resolution adjustments to achieve a specific aspect ratio or increase storage efficiency. This is especially useful for wide-angle cameras, such as 4K and fisheye models.

#### Use cases

* **1:1 Ratio:** Some camera models, particularly multi-sensor or panoramic cameras, have a native resolution that isn’t 16:9. Setting a 1:1 ratio can help preserve image integrity for these cameras.
* **Performance:** Using multiple lower-resolution streams instead of a single high-resolution stream reduces bandwidth and processing load on both the camera and the network.
* **Storage Relief:** Lowering resolution decreases video file size, requiring less local storage on the Command Connector and enabling longer retention for other connected cameras.
* **Channel Optimization:** Cameras using multiple channels can be consolidated into a single channel, freeing up capacity for new cameras on the same Command Connector.See [Change Storage Settings on Non-Verkada Cameras](/command-connector/configuration/change-storage-settings-on-non-verkada-cameras.md) for more information.

***

## Configuration

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

{% step %}
**Select the non-Verkada channel you want to configure.**
{% endstep %}

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

{% step %}
**Under Video Streaming, next to HQ Resolution, select the resolution.**

<div align="left" data-with-frame="true"><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2Fgit-blob-fa57ca2790c587132a16b8e8549fcbe2d3e0007b%2F480ebd9e7947e32f674d0c15b3f238c0ba69fa0c.png?alt=media" alt="" width="607"></div>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Resolution cannot be changed when **Streaming Profile Selection** is set to **Manufacturer**.
{% endhint %}

{% hint style="warning" %}
Custom aspect ratio is available only for HQ footage. For SQ footage, the Command Connector automatically adjusts the aspect ratio to maintain optimal streaming and storage.
{% endhint %}

{% hint style="danger" %}
Not all resolutions will be available for every non-Verkada camera.
{% 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 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/change-a-non-verkada-camera-resolution.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.
