# Embed footers

There is no server-wide footer setting in Ticket King. There are only two footer behaviors.

## Footer text on embeds you build

Ticket King does not force any branding on the panels you build. Every embed you build in the panel editor has its own footer, and you control it completely. This is free on every plan, no Premium required.

In the Embed editor you can set:

* **Footer Text** (up to 2048 characters). Write anything you want, or leave it blank for no footer.
* **Footer Icon URL** (the image shown next to the footer text).

New embeds start with "Powered by Ticket King" pre-filled as a suggestion, but it is just an editable default. Clear it or change it to whatever you like.

## The footer on the quick `/panel` default panel

The `/panel` and `/quicksetup` commands post a ready-made starter panel for you. That starter panel includes a small "Powered by Ticket King" footer on free servers, which Premium removes.

This only affects that one auto-generated starter panel. You can remove the footer for free at any time by editing the panel in the dashboard, the same as any other embed. There is no forced branding on panels you build or edit yourself.

## Related

{% content-ref url="/pages/987R9qKqqc69cNg6Jakh" %}
[Edit the embed](/docs/panels/edit-the-embed.md)
{% endcontent-ref %}

{% content-ref url="/pages/exzL4IxFJ6d9jWNjp6BF" %}
[The premium-only feature list](/docs/premium/feature-list.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://ticketking.xyz/docs/customization-and-branding/embed-footers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.