> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/panels/panel-limits.md).

# Panel limits

Every cap that applies to panels in one place.

A reference for every cap that applies to panels. If something's failing with an "exceeds limit" error, you'll find the value here. For the full free-plan breakdown, see [Free plan limits](https://ticketking.xyz/docs/getting-started/free-plan-limits.md) or the [free Discord ticket bot](https://ticketking.xyz/free-discord-ticket-bot) page.

## Per-server limits

| Limit                      | Free   | Premium   |
| -------------------------- | ------ | --------- |
| Panels per server          | **10** | Unlimited |
| Saved templates per server | **1**  | **25**    |

## Per-panel limits

| Limit                     | Value      | Reason                                                               |
| ------------------------- | ---------- | -------------------------------------------------------------------- |
| Component rows            | 5          | Discord limit.                                                       |
| Buttons per row           | 5          | Discord limit.                                                       |
| Buttons per panel (max)   | 25 (5 × 5) | Discord limit.                                                       |
| Dropdown menus per panel  | up to 5    | One dropdown menu fills a whole row, and a panel has up to 5 rows.   |
| Options per dropdown menu | 25         | Discord limit.                                                       |
| Form questions per option | 5          | Discord pop-up form limit. Applies to both tickets and applications. |
| Embeds per panel message  | 10         | Discord limit.                                                       |

## Character limits

| Field                                                          | Cap                |
| -------------------------------------------------------------- | ------------------ |
| Panel content (above embeds)                                   | 2000               |
| Embed title                                                    | 256                |
| Embed description                                              | 4096               |
| Embed field name                                               | 256                |
| Embed field value                                              | 1024               |
| Embed footer text                                              | 2048               |
| Embed author name                                              | 256                |
| Total embed character length                                   | 6000 (Discord cap) |
| Button label                                                   | 80                 |
| Link button URL                                                | 512                |
| Dropdown-menu placeholder                                      | 100                |
| Dropdown-menu option label                                     | 100                |
| Dropdown-menu option value                                     | 100                |
| Dropdown-menu option description                               | 100                |
| Form question label                                            | 45                 |
| Form question placeholder                                      | 100                |
| Form text response length (configurable, default 500)          | 1 to 4000          |
| Custom Embed Content (per option)                              | 2048               |
| Custom Ticket Message (per option)                             | 1024               |
| Admin Thread Message (<i class="fa-crown">:crown:</i> Premium) | 1024               |
| Custom Ticket Name input                                       | 100                |
| Final ticket channel name (Discord cap)                        | 100                |

## Application-specific limits

| Field                  | Cap                              |
| ---------------------- | -------------------------------- |
| Application Type label | 50                               |
| Application questions  | 5 (same Discord pop-up form cap) |
| Min Account Age        | 0 to 365 days                    |
| Min Server Membership  | 0 to 365 days                    |
| Cooldown Period        | 0 to 365 days                    |
| Decision reason        | 1000                             |
| Decision note          | 1000                             |

## Discord-side limits

| Limit                             | Value |
| --------------------------------- | ----- |
| Channels per Discord server       | 500   |
| Children per Discord category     | 50    |
| Active threads per Discord server | 1000  |
| Roles per Discord server          | 250   |
| Fields per pop-up form            | 5     |

## What happens when you hit a limit

* **In the dashboard editor:** the field stops accepting input. Counter shows in red.
* **At ticket-open time:** the bot replies with a polite localized error.
* **At panel-create time:** the wizard refuses to save and shows which field is over.

## Related

{% content-ref url="/pages/exzL4IxFJ6d9jWNjp6BF" %}
[The premium-only feature list](https://ticketking.xyz/docs/premium/feature-list.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://ticketking.xyz/docs/panels/panel-limits.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.
