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

# \&chatlite

Removed. The built-in Social Stream Ninja Lite overlay is no longer part of VDO.Ninja.

{% hint style="danger" %}
**This parameter no longer exists.** The built-in Chat Lite (Social Stream Ninja Lite) overlay was removed from VDO.Ninja in the v30.2 update (July 2026). Current versions ignore `&chatlite` and all of its companion parameters.
{% endhint %}

## What was removed

These parameters no longer do anything:

* `&chatlite`, `&ssnlite`, `&socialstreamlite`
* `&chatlitebutton`, `&ssnchatbutton`
* `&chatlitesession`, `&ssnsession`
* `&chatliteprofile`, `&chatliteposition`, `&chatlitemax`, `&chatlitetransparent`
* `&chatlitenoavatar`, `&chatlitehideavatar`, `&chatliteconfig`, `&chatlitetts`

The standalone `chat-lite/` page was removed from the VDO.Ninja code at the same time.

## What to use instead

* **Live chat from YouTube, Twitch, Kick and other platforms:** run [Social Stream Ninja](https://docs.vdo.ninja/steves-helper-apps/social-stream-ninja.md) separately and add its overlay to OBS as its own browser source.
* **Text chat between people in a VDO.Ninja room:** use VDO.Ninja's built-in chat. [`&chatbutton`](https://docs.vdo.ninja/advanced-settings/buttons-and-control-bar-parameters/chatbutton.md) shows or hides the chat button.

## Related

{% content-ref url="/pages/2pGU9TxBaXEy72kvDG33" %}
[Social Stream Ninja](https://docs.vdo.ninja/steves-helper-apps/social-stream-ninja.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZHfMuNDNQ1dyvvTJX5" %}
[\&chatbutton](https://docs.vdo.ninja/advanced-settings/buttons-and-control-bar-parameters/chatbutton.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-chatlite.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.
