> For the complete documentation index, see [llms.txt](https://docs.cstplus.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cstplus.org/documentation/feature-reference/branding-and-whitelabel.md).

# Branding and Whitelabel

CST+ supports whitelabel customisation: replace the default branding with your own name, logo, and colours so the admin panel looks like your own product.

{% hint style="warning" %}
Whitelabel is available on **Business** plans only.
{% endhint %}

***

### What you can customise

| Element          | Where                                                          |
| ---------------- | -------------------------------------------------------------- |
| Product name     | Shown in the panel header, page title, and login screen        |
| Logo             | Replaces the CST+ logo in the panel header and login screen    |
| Favicon          | Browser tab icon                                               |
| Accent colour    | Primary colour used for buttons, active states, and highlights |
| Login background | The background image on the login screen                       |
| Support URL      | Link shown on error and help screens                           |

***

### Setting up branding

Go to **Settings > Branding**.

**Product name** Enter your brand name. This replaces "CST+" everywhere in the panel.

**Logo** Upload a PNG or SVG. Recommended size: 200x48px, transparent background. The logo is shown in the top-left of the panel header and on the login screen.

**Favicon** Upload a 32x32 or 64x64 PNG. Shown in the browser tab.

**Accent colour** Pick a hex colour. This becomes the primary action colour throughout the panel: buttons, selected states, progress bars, on-air indicators.

{% hint style="info" %}
The panel uses a dark theme. Choose an accent colour with enough contrast against dark backgrounds. Bright colours (e.g. `#E53935`, `#1E88E5`, `#43A047`) work well. Very light colours or colours close to white will be hard to read.
{% endhint %}

**Login background** Upload an image that fills the login screen background. Recommended: 1920x1080px or larger. JPEG or PNG.

***

### Stream logo overlay

Separate from the panel branding, you can burn a logo into the video stream itself. This is configured per channel, not in the global branding settings.

On the channel page, go to **Settings > Logo overlay**:

| Setting   | What it does                                                      |
| --------- | ----------------------------------------------------------------- |
| Logo file | PNG with transparency. Burned into every frame of the stream.     |
| Position  | Corner: top-left, top-right, bottom-left, bottom-right            |
| Mode      | Standard (corner) or full-frame (centred, for bug-style overlays) |

{% hint style="info" %}
The stream logo is applied at render time and is part of the encoded video. Changing it requires a re-render of the channel.
{% endhint %}

***

### Reseller use case

If you are running CST+ as a whitelabelled platform for your own clients:

1. Set your brand name and logo in Settings > Branding
2. Create a separate line per client with a descriptive name and appropriate connection limit
3. Give each client the panel URL (the unguessable path) and a separate admin account if needed

{% hint style="info" %}
Full multi-tenant reseller functionality (clients managing their own channels without seeing each other) is on the product roadmap as a future release.
{% endhint %}


---

# 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.cstplus.org/documentation/feature-reference/branding-and-whitelabel.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.