> 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-playbacktimer.md).

# \&playbacktimer

Shows the viewer's elapsed video playback time as an overlay

Viewer-Side Option! ([`&view`](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/view.md), [`&scene`](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/scene.md), [`&room`](https://docs.vdo.ninja/advanced-settings/setup-parameters/room.md))

## Options

Example: `?view=STREAMID&playbacktimer` or `?view=STREAMID&playbacktimer=3`

| Value                  | Description                                             |
| ---------------------- | ------------------------------------------------------- |
| No value given, or `7` | Enables the overlay in the bottom left                  |
| `1` - `9`              | Enables the overlay at the corresponding position below |
| `0`, `false`, or `off` | Disables the overlay                                    |

The overlay is disabled when the parameter is omitted. Positions follow the same layout as [`&timer`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-timer.md) and [`&clock`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-clock.md):

|        | Left | Center | Right |
| ------ | ---- | ------ | ----- |
| Top    | `1`  | `2`    | `3`   |
| Middle | `4`  | `5`    | `6`   |
| Bottom | `7`  | `8`    | `9`   |

## Details

`&playbacktimer` displays the received video's elapsed playback time using the existing clock overlay styling. It stays visible when the video's control bar hides, and also works with [`&cleanoutput`](https://docs.vdo.ninja/advanced-settings/design-parameters/cleanoutput.md).

The display updates about once a second in minutes and seconds, such as `02:15`. Minutes continue past 59; one hour appears as `60:00`.

This is the viewer's playback time, not the time since the publisher started broadcasting or OBS started encoding. Each viewer has their own playback timeline. Reloading the viewer starts a new playback timeline; reconnect behavior follows the video element's playback time.

The overlay stays hidden until a received video has started. If there are multiple received videos, it uses the first eligible video, with one overlay for the page. It hides when no eligible received video remains.

The playback overlay is independent of the clock and countdown timer, so they can be used together. Choose different positions to avoid overlapping them.

## Related

{% content-ref url="/pages/i4CGJSQ4HprscBZcPr6k" %}
[\&clock](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-clock.md)
{% endcontent-ref %}

{% content-ref url="/pages/s902imkaZXKhoNM5e0LT" %}
[\&timer](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-timer.md)
{% endcontent-ref %}


---

# 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-playbacktimer.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.
