> 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-maxbandwidth.md).

# \&maxbandwidth

Judges the available bandwidth of a sender's connection

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

## Options

Example: `&maxbandwidth=80`

<table><thead><tr><th width="241">Value</th><th>Description</th></tr></thead><tbody><tr><td>(percentage 1 to 100)</td><td>the connection never uses more than that amount of the available reported bandwidth</td></tr></tbody></table>

## Details

Made a new bitrate option called `&maxbandwidth`, which differs from other commands as it leverages a chromium (chrome/edge/brave/electron) feature to judge the available bandwidth of a sender's connection. Passing a value to it as the sender (a percentage; 1 to 100 ideally), you can try to ensure the connection never uses more than that amount of the available reported bandwidth.

So the notion is, if you want to set the invite link bitrate to 50-mbps, but one guest only has only a 20-mbps connection, `&maxbandwidth=80` will try to limit the bitrate to around 16-mbps. I sometimes will tell people to set the bit rate to about 80% of what their connection can allow, as higher than that can result in some frame stutter when there is packet loss, since the connection lacks headroom to recover. This command will try to do it automatically, for all the viewers of a stream.

My goal here is to use it with the [Mixer App](/steves-helper-apps/mixer-app.md) or [Versus.cam](/steves-helper-apps/versus.cam.md), so eSports users can crank out high bitrates with less tinkering per guest. I have no idea how well it will work in practice so far.

The upcoming and standalone replacement vor vdo.ninja/monitor:\
<https://versus.cam/>

## Related

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

{% content-ref url="/pages/-MZXXYjBSAzmoXMv-\_EG" %}
[\&outboundaudiobitrate](/advanced-settings/audio-parameters/and-outboundaudiobitrate.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-bitrate-parameters/and-maxbandwidth.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.