> 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/audio-parameters/and-bufferaudio.md).

# \&bufferaudio

Reference for the \&bufferaudio URL parameter in VDO.Ninja including behavior examples and related options.

**Also known as:** `&audiobuffer`

#### **Description**

Sets a minimum audio buffer duration in milliseconds for incoming audio streams to improve playback stability.

#### **Viewer-Side Option**

This parameter controls the audio buffering for received streams, helping to smooth out network jitter.

#### **Usage**

* **`&bufferaudio=100`** - Sets 100ms audio buffer
* **`&bufferaudio=250`** - Sets 250ms audio buffer
* **`&bufferaudio=0`** - Minimal buffering (lowest latency)
* **`&audiobuffer=200`** - Alias usage

#### **Examples**

```
https://vdo.ninja/?view=streamID&bufferaudio=150
https://vdo.ninja/?scene=1&room=roomname&bufferaudio=200
https://vdo.ninja/?director&room=roomname&audiobuffer=100
```

#### **Details**

* Value in milliseconds (ms)
* Higher values increase stability but add latency
* Lower values reduce latency but may cause glitches
* Helps with poor network conditions
* Only affects received audio, not sent audio

#### **Recommended Values**

* **0-50ms**: Ultra-low latency, stable networks only
* **100-200ms**: Good balance for most situations
* **250-500ms**: Poor network conditions
* **500ms+**: Very unstable connections

#### **Trade-offs**

**Low Buffer (0-50ms):**

* ✅ Minimal latency
* ❌ May glitch on poor networks
* ❌ Sensitive to jitter

**High Buffer (200ms+):**

* ✅ Smooth playback
* ✅ Handles network issues
* ❌ Noticeable delay

#### **Use Cases**

* Music performances requiring sync
* Interviews over unstable connections
* International calls with high latency
* Mobile connections with variable quality

#### **Notes**

* Independent from video buffering
* Applies to all incoming audio streams
* May affect lip-sync at high values
* Consider network conditions when setting

#### **Related Parameters**

* [`&buffer`](https://docs.vdo.ninja/advanced-settings/video-parameters/buffer.md) - Video buffer control
* [`&buffer2`](https://docs.vdo.ninja/advanced-settings/video-parameters/and-buffer2.md) - Alternative buffer method
* [`&audiolatency`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-audiolatency.md) - Audio latency control
* [`&sync`](https://docs.vdo.ninja/advanced-settings/audio-parameters/sync.md) - Audio/video synchronization


---

# 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/audio-parameters/and-bufferaudio.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.
