A standard post on X is capped at 280 characters. That number has held since 2017 and applies to every free account. X Premium subscribers can write up to 25,000 characters in a single post, which is a different product decision rather than a different limit — the timeline still renders the first 280 and folds the rest behind a Show more link.
The number is the easy part. The counting rules are what catch people, and they are the reason a post that fits in your editor gets rejected by X. All three are documented in X's own developer reference, linked at the end; this reviewed them on September 5, 2026.
The three counting rules
- The link rule cuts both ways: shortening a URL yourself saves nothing, and a very long URL costs nothing extra. Do not waste effort on link shorteners for X.
- Budget 23 characters for the link before you write, not after. Discovering you are 12 over with a finished sentence is how good posts get mangled.
- Three emoji cost six characters. That is a real trade against a word, and usually a bad one.
| What you type | What X counts | Why |
|---|---|---|
| A plain Latin character | 1 | The baseline |
| Any URL, of any length | 23 | Every link is rewritten through the t.co shortener before it is counted |
| An emoji | 2 | Counted by weighted code point, not by visual glyph |
| Most Chinese, Japanese, Korean characters | 2 | The same weighting rule applies to CJK ranges |
| A @mention | 1 per character | Mentions are not discounted, unlike replies in older versions of the product |
Write to the fold, not to the cap
The 280 limit is what X enforces. The fold is what decides whether anyone reads you, and it arrives much sooner. On a phone, a post competes for attention against everything above and below it in a scrolling feed, and the first line is the whole pitch.
This is why filling the limit is not a goal. A 180-character post that lands is better than a 279-character post that needed all of them. When an idea genuinely will not fit, the fix is to cut a point rather than to compress every sentence — compression is what makes a post read like a telegram.
Source note
We rewrote onboarding after learning users thought workspace setup was mandatory. Completion improved once the first useful action moved ahead of setup.
Compressed to fit — reads like a telegram
Rewrote onboarding. Users thought setup was mandatory (it wasn't). Moved first useful action 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 useful action ahead of it and completion jumped. Worth checking what your onboarding merely implies is required.