> 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/settings-parameters/and-chunkedbuffer.md).

# \&chunkedbuffer

Sender-side backlog control for chunked/WebCodecs publishing.

Also known as: `&sendingbuffer`

## Description

Sets the sender-side chunk backlog target, in milliseconds, for [`&chunked`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-chunked.md) publishing.

This is not the viewer playout buffer. It does not directly add receiver delay. Use `&chunkbuffer`, `&chunkbufferfloor`, `&chunkbufferceil`, `&chunkbufferadaptive`, iframe `setBufferDelay`, and `&chunkjitterslack` for viewer-side chunked playback tuning.

## Usage

* If not set, the current base sender backlog target is about 500 ms.
* `&chunkedbuffer` or `&sendingbuffer` without a value falls back to about 5000 ms.
* `&chunkedbuffer=5000` keeps about 5 seconds of chunk backlog on the sender side.
* `&chunkedbuffer=1500` reacts quickly to weak peers and is useful for music-sync/mobile profiles.
* `&chunkedbuffer=3000` to `5000` gives more burst tolerance, but adaptation reacts later.
* `&chunkedbuffer=10000` gives more backlog headroom on unstable links, but can increase memory use and delay down-adaptation.
* `&sendingbuffer=3000` is an alias for the same setting.

## Examples

```
https://vdo.ninja/?push=streamID&chunked&chunkedbuffer=3000
https://vdo.ninja/?push=streamID&chunked&sendingbuffer=5000
https://vdo.ninja/?room=roomname&chunked=2500&chunkedbuffer=7000
```

## How it works

1. The sender encodes media into chunk payloads.
2. Those payloads are queued for transmission over DataChannels.
3. `&chunkedbuffer` defines the sender pacing/adaptation window.
4. Per-peer relief and bitrate adaptation use this window to decide how much backlog is tolerable.
5. Larger values can tolerate more bursty delivery, while smaller values react sooner when a viewer or route is weak.

## Guidelines

* `1000-2000` ms: lower latency and faster weak-peer relief; good for sync/mobile testing
* `3000-5000` ms: balanced range for many chunked experiments
* `5000-10000` ms: more burst tolerance, but watch memory, queue growth, and adaptation delay

## Notes

* Requires [`&chunked`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-chunked.md)
* Applies on the publishing side
* Higher values use more memory and can allow more sender backlog
* Viewer-side latency is controlled separately
* NACK resend cache is controlled separately with `&chunkcache`; do not use a huge `chunkedbuffer` just to keep retransmission history

## Related Parameters

* [`&chunked`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-chunked.md) - Enables chunked publishing
* [`&chunkbuffer`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-chunked.md) - Viewer playout target for chunked streams
* [`&chunknack`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-chunked.md) - Selective retransmission control
* [`&chunkcache`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-chunked.md) - Sender resend cache window
* [`&retransmit`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-retransmit.md) - Relays chunked streams without transcoding


---

# 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/settings-parameters/and-chunkedbuffer.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.
