> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/video-parameters/and-height.md).

# \&height

Sets the maximum height of the video allowed in pixels

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Aliases

* `&h`

## Options

Example: `&height=1080`

| Value                         | Description  |
| ----------------------------- | ------------ |
| (some positive integer value) | height in px |

## Details

Sets the maximum height of the video allowed in pixels.

Actual height may be less based on bandwidth allowances.

Limiting the height can force the camera to use higher frame rates.

Limiting the height can reduce the CPU load.

<https://vdo.ninja/supports> will list the support resolutions of your default camera.

<https://webrtchacks.github.io/WebRTC-Camera-Resolution/> Is a tool to help you find the resolutions supported by your camera.

You can use [`&scale=50`](/advanced-settings/video-parameters/scale.md) also, as a viewer, to scale down a selected width/height to something more exact.

{% hint style="danger" %}
If the camera cannot support the height, **it will fail**.
{% endhint %}

You can get [4K](/guides/how-to-stream-4k-video-using-vdo.ninja.md) by adding `&width=3840&height=2160` to the source link if the camera supports it.

## Related

{% content-ref url="/pages/-MZXRA\_jhvR0aFnq3TUg" %}
[\&width](/advanced-settings/video-parameters/and-width.md)
{% endcontent-ref %}

{% content-ref url="/pages/3SOPDc5TkuiOpThaDHMN" %}
[\&aspectratio](/advanced-settings/video-parameters/and-aspectratio.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZXSIoYvjcpLfDbCb8u" %}
[\&quality](/advanced-settings/video-parameters/and-quality.md)
{% endcontent-ref %}


---

# 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.vdo.ninja/advanced-settings/video-parameters/and-height.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.