> 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-bitrate-parameters/and-maxvideobitrate.md).

# \&maxvideobitrate

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

## Aliases

* `&maxbitrate`
* `&mvb`

## Options

Example: `&maxvideobitrate=8000`

| Value                    | Description                              |
| ------------------------ | ---------------------------------------- |
| (positive integer value) | max allowed video bitrate per stream out |

## Details

Useful if you are a director and you wish to prevent guests from pulling more than 500-kbps (LQ) or 1200-kbps (HQ) when in [broadcast](/advanced-settings/video-parameters/broadcast.md) mode.

This is NOT the same as setting the target bitrate as a publisher; this is a software-enforced max limit that viewers can pull video streams at. A viewer-side [`&videobitrate`](/advanced-settings/video-bitrate-parameters/bitrate.md) cannot exceed this value, and it also caps any sender-side default from [`&outboundvideobitrate`](/advanced-settings/video-bitrate-parameters/and-outboundvideobitrate.md).\
\
Please see [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md) or [`&limittotalbitrate`](/advanced-settings/video-bitrate-parameters/limittotalbitrate.md), as well.

{% hint style="info" %}
Set to 600-kbps, 200-kbps, or 80-kbps if the goal is to reduce CPU load also. (2x, 3x, or 4x down-scaling is applied at those bitrate limits).
{% endhint %}

## Related

{% content-ref url="/pages/-MZXYKYAzmk-2IPAChP1" %}
[\&outboundvideobitrate](/advanced-settings/video-bitrate-parameters/and-outboundvideobitrate.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mc\_ovh3qRr03xmQCgII" %}
[\&limittotalbitrate](/advanced-settings/video-bitrate-parameters/limittotalbitrate.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdsHq8G6aE\_RlY7fWi" %}
[\&videobitrate](/advanced-settings/video-bitrate-parameters/bitrate.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdvtBaFUhrjd8ttCqN" %}
[\&totalroombitrate](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vdo.ninja/advanced-settings/video-bitrate-parameters/and-maxvideobitrate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.