A post on X can be 280 characters long. X Premium subscribers can write longer posts of up to 25,000 characters, and everyone can read them, subscriber or not.
The 280 is a weighted count, which is why a post that fits in your notes app can be rejected by X. X documents the rules in its developer reference, and the open-source twitter-text library it points to publishes the exact weights as a config file. Both are linked at the end of this page.
How X weighs each character
| What you type | Counts as | Detail |
|---|---|---|
| Latin letters, digits, basic punctuation | 1 | Every code point from U+0000 to U+10FF weighs 1. That range also covers Greek, Cyrillic, Hebrew, Arabic, Devanagari, and Thai. |
| Curly quotes, en and em dashes, primes | 1 | Three small blocks of general punctuation (U+2000 to U+200D, U+2010 to U+201F, U+2032 to U+2037) are also weight 1. |
| Any URL | 23 | X wraps every link in t.co, so a 19-character link and a 200-character link both cost 23. |
| Any emoji | 2 | Skin tones and zero-width-joiner sequences, such as the four-person family emoji, still total 2. |
| Chinese, Japanese, Korean | 2 | A post written entirely in CJK text tops out at 140 characters. |
| Everything else | 2 | Includes the ellipsis character (…), the bullet (•), arrows, and the Unicode bold and italic letters that formatting tools produce. |
| An @mention you type | 1 per character | The @mentions X adds by itself at the start of a reply do not count. |
The ellipsis and bold-text traps
Two rows catch people more than the rest. The first is the ellipsis: if your keyboard or writing app turns three dots into a single … character, it costs 2, while three periods cost 3. The second is Unicode bold. A bold-text generator swaps each letter for a symbol from the Mathematical Alphanumeric block, far outside X's weight-1 range, so a 20-letter bold headline costs 40.
Accents are safe. X normalizes text to Unicode NFC before counting, so café is 4 characters whether your keyboard produced the é as one code point or as an e plus a combining accent.
How X compares with the other networks
Other networks count differently. Only X and Mastodon give a link a fixed cost. On the rest, assume a URL costs what it looks like until you have checked.
| Network | Limit | How it counts |
|---|---|---|
| X | 280 (25,000 with Premium) | Weighted: links 23, emoji and CJK 2 |
| Bluesky | 300 | Graphemes, so an emoji counts once. The post record also caps the text at 3,000 bytes. |
| Threads | 500 | Characters, per Meta's Threads API documentation |
| Mastodon | 500 on a standard server | Every link counts as 23, the same rule as X |
| 3,000 | Characters, per LinkedIn Help |
Checking a post before you publish
The free character counter on this site applies the weights above when you pick X: each link at 23, each emoji at 2, Chinese, Japanese and Korean characters at 2. When the weighted count differs from the plain character count, it says which part of the post caused the difference.
X's own composer still has the final word, because it is the one that accepts or refuses the post. My routine is to draft in the counter, fix whatever it flags, then paste into X and check its counter once before posting.
When the idea will not fit in 280
Cut a point before you compress the sentences. Compression saves characters and costs readers, because a post full of fragments and arrows reads like a telegram, and on X each arrow costs 2 anyway. The three versions below are an illustration written for this page.
Illustration: the note you start from
We rewrote onboarding after learning users thought workspace setup was mandatory. Completion improved once the first real task moved ahead of setup.
Compressed to fit, reads like a telegram
Rewrote onboarding. Users thought setup was mandatory (it wasn't). Moved first real task ahead of setup → completion up. Lesson: check what your UI implies is required vs what actually is. Big learning for us this quarter, sharing in case useful.
One point, whole sentences
Users thought our setup screen was mandatory. It never was. We moved the first real task ahead of it and completion jumped. Worth checking what your onboarding merely implies is required.