> 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/meshcast-parameters/and-meshcastbitrate.md).

# \&meshcastbitrate

Option to change outbound video bitrate of the \&meshcast parameter

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

## Aliases

* `&mcbitrate`
* `&mcb`

## Options

Example: `&meshcastbitrate=2500`

<table><thead><tr><th width="249">Value</th><th>Description</th></tr></thead><tbody><tr><td>(integer value)</td><td>publishing meshcast video bitrate in kbps</td></tr></tbody></table>

## Details

Adding `&meshcastbitrate` to the publisher's side together with [`&meshcast`](/advanced-settings/meshcast-parameters/and-meshcast.md) gives the option to change the video bitrate for Meshcast.

Example usage: `https://vdo.ninja/?meshcast&meshcastbitrate=2000`

Increased the default bitrate of [`&meshcast`](/advanced-settings/meshcast-parameters/and-meshcast.md) from like 500-kbps to max of 3200-kbps; will probably change as the feature evolves and becomes more customizable.

The default Meshcast bitrate is normally set to around 2400-kbps.

Each guest will see a Meshcast video at the same bitrate and resolution as everyone else. It's the same video stream to everyone in the room, control center, view links, and scenes. This is unlike the [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md), which varies the bitrate per video that guests see based on the number of guests in the room; [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md) and [`&videobitrate`](/advanced-settings/video-bitrate-parameters/bitrate.md) will not impact the bitrate of a Meshcast stream, nor will [`&scale`](/advanced-settings/video-parameters/scale.md) change its resolution.

## Related

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

{% content-ref url="/pages/3RZqhJLR9XB9qr95Dzco" %}
[\&meshcastcodec](/advanced-settings/meshcast-parameters/and-meshcastcodec.md)
{% endcontent-ref %}

{% content-ref url="/pages/gzfG0hwU2RdopUnYCf88" %}
[\&meshcastaudiobitrate](/advanced-settings/meshcast-parameters/and-meshcastaudiobitrate.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/meshcast-parameters/and-meshcastbitrate.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.