> 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/whip-parameters/and-whipoutscreensharecodec-alpha.md).

# \&whipoutscreensharecodec

[WHIP Option](/steves-helper-apps/whip-and-whep-tooling.md) / Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Aliases

* `&wosscodec`

## Options

Example: `&whipoutscreensharecodec=h264`

<table><thead><tr><th width="234">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>h264</code></td><td>h264 codec</td></tr><tr><td><code>vp8</code></td><td>vp8 codec</td></tr><tr><td><code>vp9</code></td><td>vp9 codec</td></tr><tr><td><code>42e01f</code></td><td>open h264 codec</td></tr><tr><td>(xxxxxx)</td><td>h264 profile IDs</td></tr></tbody></table>

## Details

Adding `&whipoutscreensharecodec` to the publisher's side gives the option to change the publishing codec while screen-sharing via WHIP.

There's 4 codec options currently, including the default option:

* The unspecified default, which is software h264.
* There's also `h264`, which is what the browser then sets. This could include hardware encoding, but that will not work with Firefox or Safari viewers then.
* `vp8` is pretty compatible, so if the default codec doesn't work, you can try that.
* `vp9` is also available, which has better compression/quality, but not fully compatible with all devices.
* av1 and SVC are not yet supported, but that is planned at some point.

## Related

{% content-ref url="/pages/zDeNQcpkXYzMdqF73cIT" %}
[WHIP and WHEP tooling](/steves-helper-apps/whip-and-whep-tooling.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/UejtBk5bzK74BvlM8fp4" %}
[\&whipoutcodec](/advanced-settings/whip-parameters/and-whipoutcodec.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vdo.ninja/advanced-settings/whip-parameters/and-whipoutscreensharecodec-alpha.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.