> 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/roombitrate.md).

# \&roombitrate

Limits any guest viewer in the group chat room from pulling the video stream at more than the specified bitrate value

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

## Aliases

* `&roomvideobitrate`
* `&rbr`

## Options

Example: `&roombitrate=200`

| Value                         | Description                                                    |
| ----------------------------- | -------------------------------------------------------------- |
| `0`                           | disables access to your video for other guests in a group room |
| (some positive integer value) | max. allowed bitrate                                           |

## Details

Limits any guest viewer in the group chat room from pulling the video stream at more than the specified bitrate value.

This is not the same as [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md) / `&trb`. Use `&totalroombitrate` to raise or lower the total room viewing budget. Use `&roombitrate` on one guest's link to cap how much other guests can request from that specific guest.

Does not impact what the director sees and does not limit the quality of what OBS has access to.\
This is like [`&maxvideobitrate`](/advanced-settings/video-bitrate-parameters/and-maxvideobitrate.md), but `&roombitrate` only applies to fellow group room guests.\
Practically, a guest normally won't pull more than 1200-kbps and that's only if they click the HQ full-window button.

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

## Related

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

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

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

{% content-ref url="/pages/cmIArVZ1ZIIeKoPAl7As" %}
[Video bitrate in rooms](/guides/video-bitrate-in-rooms.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/roombitrate.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.