> 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/mixer-scene-parameters/activehighlight.md).

# \&activehighlight

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

`&activehighlight` uses VDO.Ninja's active-speaker detection to automatically control the Highlight / Featured guest state.

Use this when you want the person currently speaking to become larger, while the other guests remain visible in the same scene layout.

## Aliases

* `&activespeakerfeatured`

## Options

| Value                   | Description                                                                                                                     |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| `2` \| (no value given) | Uses the secondary Highlight / Featured mode. The active speaker becomes larger, but other visible guests remain in the layout. |
| `1`                     | Uses normal Highlight, which is closer to a full speaker focus mode.                                                            |

Example:

```
https://vdo.ninja/?room=ROOMNAME&scene=0&activehighlight=2&cleanoutput
```

Alias example:

```
https://vdo.ninja/?room=ROOMNAME&scene=0&activespeakerfeatured&cleanoutput
```

By itself, `&activehighlight=2` does not enable `&activespeaker`, so it does not hide non-speaking guests. If you also add `&activespeaker`, the normal active-speaker hide/show behavior still applies.

You can add `&activespeakerdelay` if speaker changes are happening too quickly.

The scene or view link still needs to receive and process guest audio to know who is speaking. Do not add `&noaudio` or `&noap` to the same link unless another script is controlling Highlight for you.

By default, this mode follows video-capable speakers, similar to `&activespeaker=3`, so audio-only sources do not take over the Featured layout.

## Related

{% content-ref url="/pages/-MZHeaXqdR9WQuzFCjZc" %}
[\&activespeaker](/advanced-settings/mixer-scene-parameters/activespeaker.md)
{% endcontent-ref %}

{% content-ref url="/pages/C3wiMCwjXsgCwbWDJQUr" %}
[\&activespeakerdelay](/advanced-settings/mixer-scene-parameters/and-activespeakerdelay.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/activehighlight.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.