DocsReference

Limits

Sortr's numbers in one place: panels, options, role lists, questions, messages, images, ticket limits, timers, transcripts, copying, Ticket Tool, rate limits, retries and retention.

The fixed numbers in Sortr, grouped by area. Some are Discord's own limits, which Sortr checks for you so a setting is refused in the dashboard rather than failing in Discord later.

#Panels and options

WhatLimit
Panels per server25
Panel name80 characters
Options per panel (buttons or menu items)25. Buttons sit in rows of 5.
Button label80 characters
Menu option name100 characters
Menu option description100 characters
Menu placeholder150 characters
Deleted panels kept for their tickets200 per server. Past that, a panel that has tickets can't be deleted: "This server already keeps 200 deleted panels for their tickets. Each goes by itself once its tickets are deleted, their answers have expired and their saved transcripts are gone. Keep this panel until then."

See Panels and Buttons.

#Role lists

When a list is full, Add role says so, for example Up to 25 roles.

ListMost roles
Support roles on Who can see it48
Roles added to or removed from the ticket owner when a ticket opens or closes25 in each list
An option's Who can use it, Give roles and Remove roles25 in each list
A slash command's Who can use it25
Bypass roles and blocked roles on Limits and rules50 in each list
A ticket button's Allowed roles and Blocked roles50 in each list
Silently ping on Automations50

#Questions

WhatLimit
Questions per form5
Form title45 characters
Question title45 characters
Placeholder, or a file question's Description100 characters
Answer lengthUp to 4,000 characters. You can set a minimum and maximum per question.
Answer shown in the ticketAt most 1,000 characters per answer in the answers embed, less when the opening message's other embeds leave less room. The full answer is still stored.
Files for one file question (Most files)1 to 10. A new file question starts at 3.
Size of a file Sortr copies into the ticketWhat Sortr may upload in the server: 20 MB, or 25 MB with Server Boost level 2 or 3. Never more than 25 MB. A bigger file is named in the ticket instead.
Time to fetch one file from Discord30 seconds. A file not fetched by then is named instead: "(Discord did not hand it over)".
Files Sortr copies from one form100 MB together, across all its file questions, and 3 minutes of copying. A file that would go past either is named instead: "(more than Sortr copies from one form)".
Files in one message Sortr posts10, and no more than Sortr may upload in the server together. More goes on in another message.
Tickets waiting for their files to be copiedSortr copies one ticket's files at a time. With 20 tickets already waiting across Sortr, or 3 from the same server, a new ticket's files are named instead: "Sortr was too busy to copy these."
A file's name, as Sortr keeps it100 characters
Embeds on the opening message while the form is on and Show answers in the ticket is on4. With either switch off, 10.

See Questions.

#Messages and embeds

These are Discord's limits. The editors count characters as you type.

WhatLimit
Message text2,000 characters
Embeds per message10 (4 on the opening message while the form is on and its answers are shown in the ticket)
Embed title256 characters
Embed description4,096 characters
Author name256 characters
Fields per embed25
Field name256 characters
Field value1,024 characters
Footer2,048 characters
All embeds on one message together6,000 characters

See Panel message, Opening message, Ticket Messages and Formatting.

#Images

WhatLimit
File typesPNG, JPEG, GIF and WebP
Size of one imageUnder 8 MB, for embed images and for the bot's profile picture and banner. A picture picked for the bot can be up to 30 MB, since framing it makes a smaller file, and up to 50 megapixels. An embed image over 1 MB or more than 2560 pixels on its longer side is made smaller in your browser first, to at most 2560 pixels, and the 8 MB counts after that, so a photo of up to 40 MB can still fit. Animated images go as they are.
Images stored per server100 images or 200 MB, whichever comes first
Images stored per Discord account300 MB, across every server the account uploads to, or 40 MB for an account less than 30 days old. Images copied with Copy to other servers count for whoever copies them.
Images stored by all servers togetherA limit for Sortr as a whole. When it is reached, uploads say "Sortr's image storage is full right now. Try again later or remove unused images." Once all images together pass 80% of that limit, an upload that would take your account, or the server, past 1% of it is refused: "Sortr's image storage is nearly full, so accounts and servers that already keep a lot of images can't add more for now. Take images you no longer need out of your panels, or try again later."
Uploads per server100 a day
Uploads at onceOne at a time from your browser, and one per Discord account. A second one from another tab answers "Another image is still uploading. Wait for it, then try again." When Sortr is receiving many images from everyone, an upload waits a few seconds and tries again by itself, then answers "Sortr is receiving a lot of images right now. Try again in a moment." An image that takes more than 30 seconds to arrive, or that arrives at less than 16 KB in 10 seconds, answers "The image took too long to arrive. Try again."
Uploaded images in one message10, and 25 MB together. A save past either is refused, for example "Panel message: its uploaded images add up to 31 MB, and one message can carry 25 MB."
Images on their way to Discord at once100 MB across Sortr, 25 MB per server. A post that waits more than 15 seconds for room is not sent: Send panel and Update answer "Sortr is sending a lot of images right now. Try again in a moment.", and a new ticket gets a plain opening message instead.
Images no panel usesDeleted automatically, at the earliest 3 days after upload. An image counts as used only by panels in its own server, including the settings kept for a deleted panel's tickets, until the last of those tickets is deleted.

#Ticket limits and rules

Set per panel under Limits and rules. Each count only includes that panel's tickets.

SettingRangeDefault
Open tickets per member0 to 5001
Open tickets in total0 to 500500
Closed tickets per member0 to 50010
Closed tickets in total0 to 500500
Wait after opening a ticket (cooldown)0 to 10,080 minutes (7 days)5 minutes
Support hoursOff, or open and close times with days of the weekOff. When switched on: 09:00 to 17:00, Monday to Friday

#Automations

Set per panel under Automations. Sortr checks every 5 minutes, so timings are accurate to about that. Each check closes at most 5 tickets and deletes at most 5 in one server, and at most 20 of each across Sortr, so a larger backlog takes a few checks.

SettingRangeWhen switched on
Warn afterUp to 30 days of silence. Part days work, so 0.5 is 12 hours.1 day
Close afterUp to 30 days of silence. Part days work, so 0.5 is 12 hours.2 days
Delete afterUp to 365 days closed, in whole days7 days

All three are off for a new panel. When a ticket is deleted, its channel goes 8 seconds after the delete is confirmed, or 10 seconds after the automatic delete timer starts the delete.

#Transcripts

WhatLimit
Save itWhen the ticket closes (the default) or When the ticket is deleted. See when a transcript is saved.
Keep it for (copy on sortr.xyz)30 days, 90 days, 180 days, 1 year, or until deleted by hand. Default 90 days. Any other length, such as one stored before these choices were enforced, counts as the longest choice that isn't longer, and at least 30 days, so nothing is kept longer than the choices allow.
Messages in one transcriptThe first 5,000. A longer ticket's transcript says the rest were left out.
Size of one transcript12 MB. A larger one keeps the messages from the start that fit, and says "This ticket was too long to keep whole."
Site copies of one ticketThe first and the 3 newest. Saving more removes the older ones in between.
Site copies of one server1 GB together. Past that, or while Sortr is low on storage, a new site copy is not kept, and the event log says so. A taken-over Ticket Tool ticket's copy kept off Discord is kept past the 1 GB and the two limits below.
Site copies of every server one owner owns3 GB together, counting the servers with Sortr that the same Discord account owns. Past that, a new site copy is not kept, and the event log says so.
Site copies across Sortr40 GB together. Past that, a new site copy is not kept, and the event log gives the low-storage reason.
Transcripts being openedUp to 4 at a time across Sortr, fewer when they are large, and 1 at a time per Discord account, whose second waits up to 8 seconds for the first. Past that, a transcript link says "A lot of transcripts are being opened right now. Reload in a moment.", and the dashboard "A lot of transcripts are being opened right now. Try again in a moment."
Saves being made2 at a time across Sortr, 1 at a time per server. With 10 already waiting for a server, a save by hand is refused: "Sortr is saving many transcripts for this server right now. Try again in a few minutes." Saves at a close or a delete wait their turn.
Saving with the Transcript button or /transcriptOnce per ticket every 2 minutes. Saves at the close and at the delete do not count.
Saving a transcript from the dashboardOnce per ticket every 10 minutes, and 2 in a row, then 3 a minute, per sign-in
Direct messages: the close message and the transcript copy for the ticket owner4 in a row, then 8 an hour, to one person, across every server. A transcript saved by hand is never sent by DM.
Searching Closed tickets by nameLooks through the names on the server's newest 500 transcripts. 10 searches in a row, then 30 a minute, per server: "Too many name searches in this server just now. Try again in a moment."
Every site copy, after Sortr is removed from the serverDeleted 30 days later, whatever Keep it for says

Expired copies are removed every hour. See Transcripts.

#Commands in a ticket

WhatLimit
Reason given with /close500 characters

See Commands.

#Limits members can hit when opening tickets

These protect your server and Sortr from floods. No panel setting changes them, and bypass roles don't skip them.

WhatLimitWhat the member sees
Pressing buttons, menus, forms and commands3 in a row, then one every 3 seconds, per member"Slow down a little. Try again in …"
Opening tickets5 in a row, then one every 2 minutes, per member"You have opened a few tickets in a row. Try again in …"
New ticket channels in one server10 in a row, then 10 a minute"Sortr is busy in this server right now. Try again in …"
Tickets being opened at onceOne per member"Already opening your ticket, one moment."
Channels in the serverSortr stops opening tickets at 470 channels, before Discord's limit of 500. Threads do not count."Tickets cannot be opened right now because this server is almost out of channels. Please let a moderator know."

Only tickets that open count towards the two opening limits. A press that a panel's rules turn away, such as a ticket limit, the cooldown, support hours or a role, counts towards neither, and a member turned away by the server's limit keeps their place in their own.

A member who is refused again and again for the same reason is written to the event log once every 10 minutes.

#Ticket channels

WhatLimit
Channel name100 characters
Digits in the ticket number1 to 6. Default 4.
Channels in one category50 (Discord's limit). Add a second category so tickets keep going somewhere.
Renames of one channel2 every 10 minutes (Discord's limit). A rename that would have to wait is skipped. When it was Sortr's rename at a close or reopen, the event log says so under Something went wrong.
Categories Sortr creates when a list is fullIt stops once 10 categories in the server have a name made from that list's Name for new categories, and creates none once the server has 470 channels. See Destination category.
Name for new categories100 characters, with {number} at most once

#Webhooks and Google Sheets

WhatLimit
Webhooks per panel5
Webhook name40 characters
Webhook address500 characters
Time to answer a webhook event10 seconds
Webhook retriesAfter 30 seconds, then 1, 2, 4, 8, 16 and 32 minutes, then hourly, for up to a day
Events waiting for one webhook500. Newer ones are not sent, and show as Failed under Recent deliveries.
Events waiting for one server2,000, across all its webhooks. Newer ones are not sent, and show as Failed.
Events sent in one roundAt most 3 per webhook and 5 per server. Servers take turns.
A slow answerAn address that answers after more than 5 seconds is still delivered to, but that webhook's next events wait 30 seconds
Signing secretwhsec_ and 32 to 64 characters, at least 16 of them different. New secret makes one for you.
Recent deliveriesThe last 10 per webhook, kept for 7 days
Google Sheet link500 characters
Google Sheet Tab100 characters
Google Sheet columnUp to 3 letters
Google Sheet retriesAfter 1 minute, doubling up to every 30 minutes. A sheet that needs fixing is tried every 30 minutes. A form that still cannot be written 3 days after it was sent is given up.
Check access for a Google Sheet5 in a row, then 10 a minute, per panel, and 4 a minute per server across all its panels. Every server's checks also share a small allowance with Google; when it runs out, the answer is "Sortr is busy talking to Google. Try again in a minute."
Servers one spreadsheet can be connected to1. Panels in the same server can share it.

See Webhooks and Google Sheets.

#Copying panels

WhatLimit
Servers in one copy50
Copies to other servers10 in a row, then 30 an hour, per sign-in. Checking what a copy would do does not count.
Changes to one server20 in a row, then 60 a minute, shared with saves in the dashboard. Past that, the copy skips that server with "Too many changes to this server just now. Try again in a minute."
Panels a copy brings alongThe panel and every panel its options open, up to the 25 a server may have

See Copy panels.

#Moving from Ticket Tool

WhatLimit
What one scan readsThe latest 50 messages of up to 250 channels Ticket Tool can post in (none without Message Content access, or without Ticket Tool in the server), up to 200 more in a channel where Sortr's own posts pushed Ticket Tool's out of those 50, and the first 10 messages of up to 60 recent Ticket Tool tickets, and from Discord the names of up to 100 of the members they are for
Panels one scan finds50
How long a scan is kept1 hour. After that, scan again before importing.
Panels picked with Import into Sortr25 per server, each kept for 30 minutes
Images copied in one import20
Questions brought over5
Scans2 in a row, then about one every 10 minutes, per server
Ticket numbers carried overUp to six digits (999,999). A channel name ending in a longer number is not counted.
Listing and taking over Ticket Tool's tickets6 in a row, then 40 an hour, per server, counted together. Each looks at up to 100 ticket channels.
Scans, ticket lists and take-overs at once3 across Sortr, and 1 per server ("Sortr is still reading this server for an earlier scan or take-over. Try again in a minute." or "Sortr is busy reading other servers. Try again in a minute.")

See Switching from Ticket Tool.

#Dashboard

WhatLimit
New panels5 in a row, then 10 an hour, per server
Sending or updating a panel post3 in a row, then 6 a minute, per panel
Sortr's Display name in a server32 characters
Display name, profile picture and banner changes4 in a row, then 2 a minute, per server, counted together. Discord has its own limit on top.
Members offered in a message box's @ listUp to 6, once two letters follow the @. The search runs 20 times in a row, then 40 a minute, per sign-in, and 30 in a row, then 60 a minute, per server. Past that, the list offers roles only for a moment.
Send test for webhooks5 in a row, then 10 a minute, per panel
Closed tickets listShows the latest 300. Search reaches older ones.
Dashboard sign-inLasts 7 days
Signing in, per Discord account10 in a row, then 10 an hour. Past that, sign-ins are refused for a while: "Sign-in did not go through. Wait a few minutes, then try again."
Signing in, from one internet address40 in a row, then 40 an hour, with the same answer. Starting a sign-in: 30 in a row, then 30 a minute, and coming back from Discord: 20 in a row, then 20 a minute; past those, a plain page says "Too many requests. Try again in … seconds."
Browsers signed in to one accountThe 10 newest. An older sign-in is ended.

#Event log

WhatLimit
Message edited and Message deleted entriesAt most 5 edits and 5 deletes a minute per member. The rest are neither posted nor recorded.
Server almost out of channels entriesAt most one an hour per server
Posts waiting for one server's log channels50. Past that, posts are recorded but not posted, except Missing Discord permission, Category full, Panel message gone, Integrations changed and Server almost out of channels.

See Event log.

#How long records are kept

RecordKept for
Event log entries in Sortr90 days
Transcripts on sortr.xyzAs set in Keep it for, default 90 days
A closed ticket's form answers and subjectAs set in Keep it for, counted from the close. A year with Until deleted by hand
A ticket's recordA year after the close, and as long as its channel is in the server or a site copy of its transcript is kept
Webhook delivery records7 days
A Ticket Tool scanAbout an hour, in memory only. A panel picked with Import into Sortr: 30 minutes.
API keysUntil revoked
Everything Sortr holds for a server, after Sortr is removed from it30 days, then deleted: tickets, form answers, every site copy of a transcript, log entries, panels, images and API keys. Added back within the 30 days, Sortr picks up where it left off. Copies posted in Discord stay.

More on what is kept, and for how long, in Privacy and data.

Something unclear or out of date? Tell us and we will fix it.

Updated 4 November 2026