DEV Community

Cover image for Social Media Character Limits: What 11 Networks Actually Count
Clienzo
Clienzo

Posted on Originally published at clienzo.co

Social Media Character Limits: What 11 Networks Actually Count

Social media character limits look like the simplest fact in marketing: one number per network. Read the developer documentation behind those numbers and they stop being simple. Bluesky counts what you see, Threads counts some emoji as several characters, YouTube counts bytes, Mastodon counts every link as 23 and DEV leaves spaces out of its title count.

We read each network's own documentation for the eleven networks a founder is most likely to post to, from Bluesky to a Slack channel. This post gives the limit for each, says exactly what each one counts, and shows where the same sentence comes out at different lengths on different networks.

Key findings

  • Post limits run from 300 graphemes on Bluesky to the 40,000 characters at which Slack truncates a message. Facebook documents none that we could find.
  • "Character" means at least four things: a visible character (Bluesky), a UTF-8 byte for emoji (Threads), a byte for every letter (a YouTube description) or a non-space character (a DEV title).
  • Attaching media changes the limit on Telegram, from 4,096 characters for a message to 1,024 for a caption.
  • Mastodon's 500 is a default. Each server can set its own, links count as 23 and a mention counts only its username.
  • Instagram's API reference still allows 30 hashtags; Instagram itself has limited a post to five since December 2025.

How we checked

On September 22, 2026 we read the current developer or help documentation for each network below and noted the limit, the unit it is measured in and any rule about links, emoji or media. For DEV, which does not publish its limits, we read the validation code of Forem, the open-source software DEV runs on. We did not test posts against each network; every number comes from a page linked where it appears.

We covered Facebook, Instagram, Threads, LinkedIn, Bluesky, Mastodon, DEV, YouTube, Discord, Telegram and Slack. We left out X and TikTok. Pinterest is left out as well: its help pages would not load for us in a form we could quote, and we only publish numbers we have read at the source.

Finding 1: Social media character limits run from 300 to 40,000

Here is each network's limit for the main text of a post, the unit it is counted in, and where it is written down.

Network Limit What is counted Source
Bluesky 300 Graphemes (what you see as one character), and at most 3,000 bytes AT Protocol post schema
Threads 500 Characters, with each emoji counted as its UTF-8 bytes Threads API posts guide
Mastodon 500 by default Characters; each link counts as 23; a mention counts its username only Mastodon posting docs
Discord 2,000 Characters in a message sent through a channel webhook Discord webhook docs
Instagram 2,200 Characters in the caption; 20 @ tags; five hashtags Instagram media API reference
LinkedIn 3,000 Characters in a post LinkedIn Help
Slack 4,000 advised Characters; Slack truncates past 40,000 Slack chat.postMessage docs
Telegram 4,096 (1,024 with media) Characters after formatting is parsed Telegram Bot API
YouTube 100 title, 5,000 description Characters for the title, bytes for the description YouTube Data API videos resource
DEV 128 title, 800 KB body Title characters without spaces; body in bytes; four tags Forem article model
Facebook Not documented No limit stated in Meta's Pages API docs Pages API posts guide

The range matters more than any single row. The same announcement can be ten times too long for Bluesky and comfortably short for LinkedIn. If you write for the long network first and cut down later, the cut-down is where the mistakes happen: a sentence ends mid-thought, the link falls off the end, or the call to action is the part that goes.

Facebook is the odd one out. Meta's Pages API guide, which is what a scheduler uses to post to a Page, states no maximum for the message. A figure of 63,206 characters is widely repeated, but we could not find it in any Meta documentation, so treat it as folklore. In practice no founder post comes near it.

Finding 2: A "character" means four different things

Most people count a character the way they see it: one letter, one emoji, one mark. The documentation shows that networks do not all agree, and the difference decides whether a post that fits on one network fits on the next.

Bluesky counts what you see

Bluesky's post schema sets two limits on the text: 300 graphemes and 3,000 bytes. A grapheme is one visible character, so an accented letter, a flag or a family emoji built from several code points each count once. That makes the 300 honest: what the counter in the app shows is what the network counts. The 3,000-byte ceiling sits behind it and only matters for a post made mostly of complex emoji, such as a family emoji that takes 18 bytes on its own.

Threads counts emoji by their bytes

The Threads API guide says text posts are limited to 500 characters and that "emojis are counted as the number of UTF-8 bytes". A rocket emoji is 4 bytes, so it uses 4 of your 500. A thumbs-up with a skin tone is 8, and the family emoji above is 18. A post with a row of ten emoji at the end has spent at least 30 characters on them, not 10.

For most founders this only bites when a post sits close to the limit. The fix is simple: leave some headroom on Threads if your post uses emoji, and do not trust a generic character counter to tell you whether it fits.

YouTube counts bytes in the description

The YouTube Data API gives the title a maximum of 100 characters and the description a maximum of 5,000 bytes. In English that is roughly 5,000 characters, because plain Latin letters take one byte each. In other languages it is not: an accented letter takes 2 or 3 bytes, and a Japanese or Chinese character takes 3, so a Japanese description fits about 1,666 characters. If you write descriptions in a language other than English, the limit is lower than the number suggests.

DEV leaves the spaces out of the title

DEV does not publish its limits, but Forem's source code is public. An article title may have up to 128 characters, and the check removes every space before it counts. A 140-character title with 20 spaces passes. The body is limited by size, 800 KB of Markdown, which no normal article reaches, and an article takes at most four tags.

Telegram does not count your formatting

Telegram's Bot API measures text "after entities parsing". Bold, italic and link markup are turned into formatting first, and only the text that remains is counted. A message with a lot of formatting can be longer in its raw form than 4,096 and still fit.

Finding 3: Mastodon's 500 is a default, and links always cost 23

Mastodon's posting guide says "the default character limit is 500 characters". The word default is the point: Mastodon is many servers, and each server's configuration includes its own maximum characters per post. An admin can change it, so the number can differ from one server to the next. A post that fits on your server may be longer than what readers on other servers are used to seeing.

Two rules make Mastodon friendlier than its number suggests:

  • Every link counts as 23 characters, however long it is. A 90-character URL with tracking parameters costs the same as a short one, and the guide actively discourages link shorteners.
  • A mention counts only its username. In @alice@example.com, the server part is free, so mentioning people on other servers does not eat your post.

No other network in this list documents either rule, so a link that is cheap on Mastodon can cost its full length elsewhere. Cut the tracking parameters before a cross-post goes out.

Finding 4: Adding media changes the limit

On most networks a photo does not change how much text you can write. Two networks behave differently.

Telegram allows 4,096 characters in a text message, but a caption attached to a photo or a video is limited to 1,024 characters. A 2,000-character channel update fits as text and does not fit as a caption. The usual workaround is to send the text as its own message and the media right after it.

Instagram has no text-only post at all, so its 2,200 characters are always a caption. The API reference we read still lists "30 hashtags and 20 @ tags" per caption. Instagram itself cut hashtags to five per post in December 2025, which our check of Instagram's 2026 changes covers with its source. When the documentation and the app disagree, write to the stricter one: five hashtags.

Threads adds an allowance instead of cutting one. On top of the 500 characters, a Threads post can carry a text attachment of up to 10,000 characters, which readers open with a tap. The alt text on a Threads image or video has its own limit of 1,000 characters.

Finding 5: Community channels allow more than you should use

Discord, Telegram and Slack are where many founders talk to their early users, and their limits are generous next to the public networks.

Discord sets 2,000 characters for a message sent through a channel webhook, the usual way a tool posts into a server. It is a limit on the message itself, so a long update needs to be split or cut before it goes out.

Slack is unusual in documenting two numbers. Its chat.postMessage docs advise keeping text to 4,000 characters "for best results" and say Slack "will truncate messages containing more than 40,000 characters". The first is advice about readability, the second is the limit. Between the two, a message goes through but is hard to read in a busy channel.

The same logic applies to all three. A channel is read by people who chose to join it, often on a phone, between other messages. The limit is not the target. A launch note that says what shipped, why it matters and where to try it rarely needs more than a few hundred characters.

Finding 6: LinkedIn and Instagram are the only long public networks

Set aside Facebook, which documents no limit, the community channels, YouTube and DEV, and five public networks remain. Two of them allow long text: LinkedIn at 3,000 and Instagram at 2,200. The other three, Bluesky at 300 and Threads and Mastodon at 500, sit an order of magnitude lower.

That gap is the whole cross-posting problem in one line. A LinkedIn post written to its length is six to ten times too long for the short networks. You cannot trim it by deleting a few words; you need a second, shorter version that keeps the one idea worth keeping. The differences between Bluesky and Threads go deeper into how those two short networks differ beyond length.

What this means for you

You do not need to memorise the table. You need a way of writing that survives it.

  • Write the shortest version first. Start with 300 characters for Bluesky. If the idea fits there, every other network gets the same core plus room for detail. Going the other way, from 3,000 down, is where posts lose their point.
  • Leave headroom on Threads. Aim for about 450 characters if the post uses emoji, since each one counts as 3 to 8 or more.
  • Put links where they cost least. On Mastodon a link costs 23 whatever its length. On the short networks, trim tracking parameters or move the link to the end, where it is the first thing to go.
  • Check your Mastodon server's limit in its about page before you write longer posts there, and write for 500 anyway if your audience is spread across servers.
  • On Telegram, decide text or caption first. Over 1,024 characters with a photo, send the text as its own message.
  • For YouTube in another language, count bytes, not characters. Paste the description into a byte counter if it runs long.
  • Follow the stricter rule when docs and apps disagree, as with Instagram's hashtags.

If you would rather not count by hand, a scheduler that checks each network's limit before the post is queued catches most of this. Clienzo does that per network, on the version of the post written for that network, before anything is scheduled; the features page shows how the per-network wording works.

Related reading


Originally published on the Clienzo blog.

Top comments (0)