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

# \&nomobilebitratecap

Disables only the mobile sender bitrate safety cap

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

## Options

Example: `&nomobilebitratecap`

| Value    | Description                                      |
| -------- | ------------------------------------------------ |
| no value | disables the app-level mobile sender bitrate cap |

## Details

`&nomobilebitratecap` keeps the normal mobile interface active, but disables VDO.Ninja's extra mobile sender bitrate safety cap.

This is different from [`&notmobile`](/advanced-settings/mobile-parameters/and-notmobile.md), which makes VDO.Ninja treat the device as non-mobile and can also change mobile-specific controls and layout behavior.

This parameter does not override room, director, or viewer bitrate controls. Viewers still request bitrate normally, [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md) still controls room receive budgets, [`&maxvideobitrate`](/advanced-settings/video-bitrate-parameters/and-maxvideobitrate.md) can still cap the publisher, and WebRTC congestion control can still reduce bitrate when needed.

Use this carefully. Mobile browsers can overheat or become CPU-limited when sending several peer-to-peer video streams, especially in mesh rooms. Overloaded mobile devices can cause audio dropouts or unstable video.

## Related

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

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