> 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/setup-parameters/room.md).

# \&room

Sets a room ID for the session to join

General Option! ([`&push`](/advanced-settings/setup-parameters/push.md), [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md), [`&solo`](/advanced-settings/mixer-scene-parameters/and-solo.md))

## Aliases

* `&roomid`
* `&r`

## Options

Example: `&room=RoomID`

<table><thead><tr><th width="335">Value</th><th>Description</th></tr></thead><tbody><tr><td>(string)</td><td>1 to 49-characters long: aLphaNumEric-characters; case sensitive.</td></tr></tbody></table>

## Details

Rooms broadcast to all participants who have joined.

Rooms are complemented by the [`&director=roomname`](/advanced-settings/director-parameters/director.md) function. Directors can have oversight of a room.

Rooms limit the viewing bitrate that guests of a room can request. OBS does not have these viewing limits though.

On the official hosted service, claimed rooms support admission controls:

* default claim-time room cap is 80 guests
* use [`&roomcap`](/advanced-settings/director-parameters/and-roomcap.md) to set a cap (hard max 80)
* use [`&requireapproval`](/advanced-settings/director-parameters/and-requireapproval.md) for manual director approval

Practically, CPU/network limits usually become the bottleneck before hard server limits.

Adding [`&showonly=xxx`](/advanced-settings/video-parameters/and-novideo.md) and [`&roombitrate=0`](/advanced-settings/video-bitrate-parameters/roombitrate.md) to the guest's URL can be used to help increase the capacity of rooms to 30 or more.

An alternative to a `&room` is a [*faux-room*](/getting-started/multi-person-chat.md), which can be done with:\
`https://vdo.ninja/?push=aaa&view=bbb,ccc,ddd`

## Additional info

There's a documentation page dedicated to rooms [here](/getting-started/rooms.md).

There's also a video below looking at what sort of performance and system load there is when using an unoptimized group room.

{% embed url="<https://www.youtube.com/watch?v=VYYG4rZffcM>" %}

You can reduce CPU load using the [`&broadcast`](/advanced-settings/video-parameters/broadcast.md) flag, if hosting a larger room.

You can also [transfer guests between group rooms](/guides/transfer-rooms.md), using the transfer function that the director has.

## Related

{% content-ref url="/pages/-MZHYK6N0TaNC3pa-8za" %}
[Rooms](/getting-started/rooms.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M\_GN9YKWH8VJmAwHOek" %}
[How to transfer guests to other rooms](/guides/transfer-rooms.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdueo324IDjC0YD\_es" %}
[\&director](/advanced-settings/director-parameters/director.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/setup-parameters/room.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.