> 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-totalscenebitrate/and-maxmobilebitrate.md).

# \&maxmobilebitrate

Sets the normal mobile sender bitrate cap for guest room publishing

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

## Options

Example: `&maxmobilebitrate=1000`

| Value                  | Description                                                      |
| ---------------------- | ---------------------------------------------------------------- |
| positive integer value | max mobile video bitrate per outgoing guest room stream, in kbps |

## Details

`&maxmobilebitrate` changes the normal mobile sender cap used when a mobile guest is publishing video to other room guests.

The default is `350`-kbps.

This parameter is mainly useful in director or scene controlled rooms where automatic room-only tiering is not active, but you still want a capable mobile guest to send better video to other guests.

Use this carefully. Mobile browsers can overheat or become CPU-limited when sending several peer-to-peer video streams, and audio quality can suffer when the device is overloaded.

For guest-only conferencing rooms, prefer [`&roomtier2bitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/roomtier2bitrate.md) and [`&roomtier1bitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/roomtier1bitrate.md).

## Related

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

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

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

{% content-ref url="/pages/2sMgzgRpMONN0QYeQ2X9" %}
[Room-only mobile bitrate tiers](/guides/room-only-mobile-bitrate-tiers.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-totalscenebitrate/and-maxmobilebitrate.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.