> 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/guides/smooth-playback-with-a-buffer.md).

# Smooth playback with a buffer

Add or remove playback buffering in OBS, understand buffer=0, and choose between normal WebRTC and chunked buffering.

A playback buffer gives late-arriving media more time before it is shown. Try it for uneven delivery when a little extra delay is acceptable. First check the [connection](https://docs.vdo.ninja/guides/streaming-sports-and-events/choose-a-network-for-live-events.md) and [bitrate](https://docs.vdo.ninja/guides/how-do-i-control-bitrate-quality.md); buffering cannot sustain a stream that needs more upload than is available.

## Normal VDO.Ninja video

1. In OBS, right-click the camera's **Browser Source > Properties**.
2. Add `&buffer=200` to the end of its existing **URL**, then click **OK**. Keep the stream ID, password, room, and other settings. If `buffer` is already present, change its value instead of adding it again.
3. Check moving video and sound together. Compare with no added buffer; try a larger value only if it helps enough to justify the delay.

```
https://vdo.ninja/?view=YOURID&buffer=200
```

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-89767fcd3ed024a5ade3b93e215473fd0db8ec53%2Fobs-receive-audio.png?alt=media" alt="OBS Browser Source properties, where the URL field holds the VDO.Ninja viewer link"><figcaption><p>Edit the URL in the existing source. Buffer settings belong on the receiving link.</p></figcaption></figure>

| Setting                          | Meaning                                                                                                                                   |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| No buffer parameter              | Let VDO.Ninja and the browser use their normal behavior.                                                                                  |
| `&buffer=0`                      | Request minimal buffering. This does not disable network delay or the browser's own buffering, and may make uneven delivery more visible. |
| `&buffer=200`                    | Request a 200 ms target.                                                                                                                  |
| `&buffer=1000` or `&buffer=3000` | Request a one- or three-second target. Actual delay can differ.                                                                           |

Normal WebRTC buffer requests are clamped to **0-4000 ms** and are hints to the browser. `&buffer=3000` does not guarantee exactly three seconds of added delay. Check audio sync, especially with larger values. If audio and video separate while adjusting the buffer, add [`&sync=0`](https://docs.vdo.ninja/advanced-settings/audio-parameters/sync.md) before reconnecting.

Remove the parameter to undo the change. If you also added `sync`, remove that too to restore the previous link.

## Other buffer modes

Use one buffer mode at a time:

* [`&buffer2`](https://docs.vdo.ninja/advanced-settings/video-parameters/and-buffer2.md) also accounts for estimated network transit time. It is an advanced timing option, not a stronger packet-loss fix.
* [`&buffer3`](https://docs.vdo.ninja/advanced-settings/video-parameters/and-buffer3.md) adds experimental audio compensation with brief fades during corrections. It can produce audible dips; leave it off unless you need that behavior.
* [Chunked mode](https://docs.vdo.ninja/guides/try-chunked-video.md) has its own playout buffer, controlled by `&chunkbuffer`. If `&buffer` is also present, it takes precedence.
* [SRT latency](https://docs.vdo.ninja/guides/mobile-app/srt-to-meshcast.md#adjust-buffering-or-reconnect) is set in the sending app. An OBS Browser Source buffer does not change that phone-to-Meshcast connection.

For deliberate broadcast delays measured in minutes, use [Delay an incoming feed](https://docs.vdo.ninja/guides/delay-an-incoming-feed.md). See the [`&buffer` reference](https://docs.vdo.ninja/advanced-settings/video-parameters/buffer.md) for runtime support and detailed behavior.


---

# 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/guides/smooth-playback-with-a-buffer.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.
