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

# \&outboundvideobitrate

Default target video bitrate for outgoing video streams

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

## Aliases

* `&ovb`

## Options

Example: `&outboundvideobitrate=4000`

| Value           | Description        |
| --------------- | ------------------ |
| (integer value) | value will be kbps |

## Details

Target video bitrate for outgoing video streams (sender-side default).

`&outboundvideobitrate` sets the default target for viewers that do not specify [`&videobitrate`](/advanced-settings/video-bitrate-parameters/bitrate.md). If the viewer uses `&videobitrate`, their request overrides this default. A sender-side [`&maxvideobitrate`](/advanced-settings/video-bitrate-parameters/and-maxvideobitrate.md) still caps the maximum bitrate, regardless of viewer request.

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

It won't override the room's total bitrate parameter, as that's a dynamically set bitrate, so **to get higher bitrate in group rooms you still need to use** [`&totalroombitrate`](/advanced-settings/video-bitrate-parameters/and-totalscenebitrate/totalroombitrate.md).

## Related

{% content-ref url="/pages/-MZXXYjBSAzmoXMv-\_EG" %}
[\&outboundaudiobitrate](/advanced-settings/audio-parameters/and-outboundaudiobitrate.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-outboundvideobitrate.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.