# \&audiolatency

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

## Aliases

* `&latency`
* `&al`

## Options

Example: `&audiolatency=50`

| Value            | Description   |
| ---------------- | ------------- |
| (no value given) | 10-ms latency |
| (integer value)  | latency in ms |

## Details

This is an audio buffer for the microphone. Can be applied to the publisher of an audio stream. The browser default tends to be 10 milliseconds, but 20 or 30 might be a useful option to help reduce audio clicking caused by buffer underruns. The latency value sets the LatencyHint value of the WebAudio audioContext function.

Default is 10-ms (lowest also) and higher than like 100-ms is probably a bad idea (causes, not reduces, clicking).

That will upscale the sample rate and add a small latency buffer at the same time, so I hope that will help such issues before even hitting the webRTC pipeline.

## Related

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

{% content-ref url="/pages/-MZdvss-ktTf4GVpebJs" %}
[\&sync](/advanced-settings/audio-parameters/sync.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/audio-parameters/and-audiolatency.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.