# \&recordcodec

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

## Aliases

* `&rc`

## Options

Example: `&recordcodec=h264`

<table><thead><tr><th width="139">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>h264</code></td><td>request the h264 codec</td></tr><tr><td><code>vp8</code></td><td>request the VP8 codec</td></tr><tr><td><code>vp9</code></td><td>request the VP9 codec</td></tr><tr><td><code>av1</code></td><td>request the AV1 codec</td></tr></tbody></table>

## Details

Adding `&recordcodec` to a source or director link lets you set the video recording codec (saving to disk mode; aka [`&record`](/advanced-settings/recording-parameters/and-record.md)). The container format is still WebM, and not all codecs are going to be supported, but things will fail back to vp8 if not supported. Main reason for this is because vp8 on chrome for android kinda stinks, so at least you have an option to tinker with things now.

As a guest or source side don't forget to add [`&record`](/advanced-settings/recording-parameters/and-record.md) to the URL to get the record button.

## Related

{% content-ref url="/pages/-MZXYl\_nYDzfbdqy-AuC" %}
[\&record](/advanced-settings/recording-parameters/and-record.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdudjg0hJYNiC3VGwt" %}
[\&codec](/advanced-settings/video-parameters/codec.md)
{% endcontent-ref %}

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


---

# Agent Instructions: 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/recording-parameters/and-recordcodec.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.