The Message Too Long Error: How a Discord Text Splitter Rescued My 5,000-Word Lore Guide
What Discord and Telegram really cap a message at, why splitting by hand breaks code blocks, and how to chunk long text at exact limits in your browser.
Discord allows 2,000 characters in one message. That number stays invisible until the exact moment it matters: the guide is written, the box is full, and the reply is a red line saying the message is too long. A discord text splitter turns that from an hour of manual cutting into a two minute job.
The naive fix is to paste the guide into a notes app and chop it every so often. It fails in a specific way: you cannot see where character 2,000 falls, so the cut lands mid word, or worse, in the middle of a code block, and the parts post as an unreadable wall.
What each platform actually caps a message at
The numbers are arbitrary, undocumented in the interface, and different everywhere. Discord gives you 2,000 characters per message. Telegram takes 4,096 and then continues the rest itself across further messages, which is why a long paste looks fine there and reads badly. Slack cuts at 4,000, and most forums sit somewhere between one and ten thousand and only tell you once you have pressed send.
The limit that matters is the smallest one you post to. If the same guide goes to Discord and Telegram, split at 2,000 and the Telegram copy is safe by construction.
- Discord: 2,000 characters per message.
- Telegram: 4,096 per message, with automatic continuation beyond that.
- Cut at boundaries rather than counts wherever the boundary fits, and number the parts so a reader knows what they are looking at.
Why cutting by hand breaks code
Prose survives a clumsy cut: it just reads awkwardly. A code block does not. The triple backticks that open and close it are characters like any other, so a split that lands inside one leaves the opening fence in the first message and the closing fence in the second, and everything between them renders as flat text with no highlighting.
A splitter that understands the block closes the fence at the end of a part and reopens it with the same language tag in the next, which is the only way a multi part snippet stays readable. The same applies to indentation: a chunk that starts in the middle of a nested block looks broken even when every character is correct.
The three details that make a split guide readable
A split is a publishing decision, not just a text operation, and three habits do most of the work.
- Number the parts in the text, so a reader who arrives late knows there are four of them.
- Put the total count in the first message rather than the last.
- Keep the character count visible while you post, so a part that got truncated on the way is obvious rather than invisible.
Splitting without pasting the guide into a website
A public guide is not a secret, so the stakes feel low. The same box is where people paste a client's deployment notes, an exam answer key, or an unpublished draft, and the sites that offer a free split keep whatever they receive as a matter of course.
This is the case for doing it in the tab. Paste the block into the text and code splitter, pick the platform, copy the parts out one at a time, and close the page. The text is never transmitted, and the tool keeps working with the network off, which is worth something on a train or a campus connection that logs you out every few minutes.