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

# \&videobitrate

Sets the "desired target" bitrate in kbps

Viewer-Side Option! ([`&view`](/advanced-settings/mixer-scene-parameters/view.md), [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md), [`&room`](/advanced-settings/setup-parameters/room.md))

## Aliases

* `&bitrate`
* `&vb`

## Options

Example: `&videobitrate=6000`

| Value           | Description     |
| --------------- | --------------- |
| (integer value) | bitrate in kbps |

## Details

`&videobitrate` sets the target video bitrate of a video feed in a solo link or the video feeds in a scene.

For rooms, use [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md) / `&trb` when you specifically want to control guest-to-guest room viewing quality. If `&totalroombitrate` is not set on a room link, `&videobitrate` can be used as that guest's initial total room bitrate target.

If the sender uses [`&outboundvideobitrate`](/advanced-settings/video-bitrate-parameters/and-outboundvideobitrate.md), that sets the default target bitrate on the push side. A viewer-set `&videobitrate` overrides that default. A sender-side [`&maxvideobitrate`](/advanced-settings/video-bitrate-parameters/and-maxvideobitrate.md) still caps the maximum bitrate, regardless of what the viewer requests.

In some cases, `&videobitrate` is enforced via SDP munging, so it can also act as a maximum cap depending on browser/negotiation.

{% hint style="info" %}
Default value will target around **2500**-kbps.
{% endhint %}

The maximum achievable bitrate is around 60,000-kbps (60-mbps).

**Lowering** the bitrate can sometimes **reduce CPU load**, **bandwidth**, and **stuttering** issues

{% hint style="info" %}
Camera-video targets of **600-kbps or lower** intentionally enable bitrate-based resolution scaling, reducing encoder work and CPU usage as well as bandwidth. For example, a 1280x720 source may be reduced to about 640x360 at 600-kbps; lower targets can scale it down further. At 601-kbps and above, this particular bitrate-based resolution reduction is removed, although other resolution and congestion limits can still apply.
{% endhint %}

You might want to increase the bitrate for game streams, to ensure smooth frame rates.

{% hint style="danger" %}
Not compatible with **Firefox**.
{% endhint %}

## Related

{% content-ref url="/pages/wJQGxl0KrTeLughBKsSK" %}
[Video bitrate for push/view links](/guides/video-bitrate-for-push-view-links.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdrd6ctsu0zfgskVo\_" %}
[\&audiobitrate](/advanced-settings/audio-parameters/audiobitrate.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/bitrate.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.