Slack Character Limit

Slack messages can hold up to 40,000 characters — roughly 14 pages of text. That is 20 times Discord's message limit and 142 times a tweet. Most people will never hit it. But Slack's other fields tell a different story: your channel name caps at 80 characters, your status at 100, and your channel topic at just 250.

Here is every Slack character limit in one table, verified against Slack's own API and help-center documentation for 2026.

Every Slack character limit (2026)

All figures come from Slack's API documentation and Slack's Help Center.

40,000 characters is absurdly generous

Slack was built for work, not public feeds. Twitter caps messages at 280 characters because brevity is the format. Discord allows 2,000 because chat rooms need room but not essays. Slack went the other direction entirely: 40,000 characters means you can paste a full incident report, a long code review, or meeting notes into a channel without splitting across multiple messages.

Here is how Slack compares to every major platform:

WhatsApp technically beats Slack with 65,536. But for workplace tools, Slack is among the most generous you will find. For a complete comparison across every platform, see our social media character limits guide.

Channel names: 80 characters, strict rules

Channel names are one of the tighter limits in Slack. Eighty characters is enough for descriptive names like eng-backend-incident-response, but the formatting rules are stricter than the length:

• Lowercase only. Slack converts uppercase letters to lowercase automatically.
• No spaces. Use hyphens (-) or underscores (_) instead.
• No special characters beyond hyphens and underscores.
• Must be unique within the workspace.

If your team uses long project names or client codes, 80 characters can fill up. Front-load the important part. proj-acme-q3-budget beats the-budget-review-for-acme-project-q3-cycle when someone scans a sidebar with fifty channels.

The 100-character status squeeze

Slack's custom status field allows 100 characters of text beside your emoji. That sounds generous until you try to write something useful.

"Out sick, back Monday -- check with @Sarah for anything urgent" is already 62 characters. Add context about time zones or a link and you are pushing the wall. The status emoji itself does not count toward the 100. Only the text does.

Keep it short. "OOO until Aug 25" is 16 characters and tells people everything. Move the details to your profile or a pinned channel message.

Formatting inside Slack messages

Slack supports its own markdown-like syntax within that 40,000-character space. The syntax differs slightly from standard Markdown:

• *bold* for bold (single asterisks, not double)
• _italic_ for italic
• ~strikethrough~ for strikethrough
• `inline code` for inline code
• ```code block``` for multi-line code blocks
• > quote for blockquotes
• Ordered and unordered lists work as expected

The formatting characters count toward your total, but at 40,000 characters the overhead is trivial. A few asterisks and tildes are not going to put you over the edge.

For the full guide on Slack's formatting syntax, including tricks that work on mobile, see Slack text formatting: bold, italic, and more. You can also preview and build formatted messages with our Slack text formatter.

Why pasted text sometimes looks wrong

Two issues trip people up when pasting into Slack:

1. Rich text conversion. Slack interprets pasted rich text from Google Docs, Word, or web pages and converts it to Slack's own formatting. Bold in a Google Doc becomes *bold* in Slack. This usually works fine for standard formatting, but styled Unicode text -- like mathematical bold or script characters -- does not convert cleanly and may display inconsistently across devices.

2. Link unfurling. Pasting a URL generates a preview card below your message. The URL counts toward your 40,000 characters; the preview card's content does not. If you want the link without the preview, wrap it in angle brackets: <https://example.com>.

The fields where you actually hit the limit

Nobody runs out of room in a 40,000-character message. The real pain points are the smaller fields:

• Status (100 characters) is where remote teams describe availability, time zones, and context. It fills up fast.
• Channel topic (250 characters) needs to explain what the channel is for, often with links or instructions. Two hundred fifty is not much.
• Channel name (80 characters) with the lowercase-hyphens-only constraint means long project names get abbreviated whether you like it or not.

The quickest way to stay within these bounds is to paste your text into a character counter and see the live count before committing. Editing a channel name or status after the fact works, but checking first saves the round trip.

Count before you send

If you post across Slack and other platforms, the limits diverge fast. A single Slack message holds the equivalent of 142 tweets or 20 Discord messages. What fits in Slack will not fit anywhere else. Always check the target platform's limits before cross-posting, and use a character counter to verify the length before you hit send.