Why your 280-character tweet is actually too long: weighted counting explained

You write a post, it looks well under the limit, and X (Twitter) still tells you it's too long. Or the opposite: you paste a wall of text with three links and somehow it fits. The reason is that the 280-character limit isn't really about characters — it's about a weighted budget, and the rules are stranger than most people realise.

Understanding how the count actually works saves you from the guess-and-trim cycle, and it's the difference between a thread that breaks cleanly and one that orphans half a sentence. Here's what's going on under the hood, and how the tweet length checker models it.

Links always count as 23 — no matter how long

The single biggest surprise: every URL counts as exactly 23 characters, regardless of its true length. A five-character x.com link and a 200-character monster with tracking parameters both cost the same 23. This is because Twitter wraps all links in its t.co shortener behind the scenes, so the visible length is irrelevant to the budget.

The practical consequences are immediate. Don't waste effort manually shortening URLs to save space — it does nothing. And don't trust a plain character count from your text editor, because it will overcount a long link by a hundred characters or more and tell you you're over the limit when you're fine. The checker applies the 23-character rule automatically (you can toggle it), so the number you see is the number X will see.

Emoji and many scripts count as two

The second rule that trips people up: not every character costs one unit. Twitter's counting standard assigns a weight of 2 to whole ranges of characters — CJK ideographs (Chinese, Japanese, Korean), plus Arabic, Hebrew, and other scripts. A tweet in Japanese effectively has half the character budget of an English one, which is exactly why the limit was raised from 140 to 280 in the first place: 140 was generous for dense scripts and cramped for Latin ones.

This is why pasting the "same" message in two languages can put one version over and leave the other comfortably under. The length checker applies the weight-2 rule across these code-point ranges, so its weighted total reflects what the platform will actually charge you — not the raw character count your keyboard produced.

Raw count vs. weighted count

So there are two numbers that matter, and the tool shows both. The raw character count is how many code points you typed — useful as a sanity check. The weighted count is what's measured against the 280 limit: links collapsed to 23, double-weight characters counted twice, everything else counted once. When the two numbers diverge a lot, you've got links or non-Latin script in play, and the weighted number is the one to trust. The "remaining" figure counts down from your weighted budget, so it tells the truth even when the raw count would mislead you.

Splitting a long post into a thread

When you go over, the real work is breaking the post into a thread that reads naturally — and the wrong way to do it is to slice at exactly 280 characters, which guillotines sentences mid-word. A good split respects sentence boundaries: it fills each tweet with as many whole sentences as fit, then starts the next one, so every piece is a self-contained thought.

The checker's auto-split does exactly this. It walks your text sentence by sentence, packs each tweet up to the weighted limit, and only falls back to a hard word-level split if a single sentence is itself too long to fit. If you turn on thread indicators, it also reserves room for the "(1/4)" style counters and appends them — a detail that matters, because those counters eat into the same budget and an unplanned one can push your last tweet over.

The long-form exception

Verified accounts can post far past 280 — up to tens of thousands of characters. The tool has a long-form mode for this with a 25,000-character ceiling, but the weighted-counting rules don't change: links still cost 23, double-weight scripts still cost two. The only difference is the limit you're measuring against. If you're writing for a standard account, stay in the 280 mode; the threading is where the value is.

Practical habits that keep you under the limit

A few rules of thumb fall straight out of how the count works. First, write your links last and don't fuss over them — every URL is 23, so the time to shorten or "clean" a link is purely cosmetic, never budgetary. Second, watch your emoji: a string of them can quietly burn double weight each, and a tweet that looks short on screen can be over budget. Third, if you find yourself routinely brushing the limit, stop trimming words one at a time and split deliberately instead — a two-tweet thread of complete sentences almost always reads better than one tweet crammed to 279 with every article and conjunction stripped out. The limit rewards clear, whole thoughts, not compression for its own sake.

The takeaway

Twitter's character count is a budget with three quirks: links are flat-rate 23, many scripts and emoji are double, and the limit is weighted rather than literal. Once you know that, the mysterious "too long" errors stop being mysterious. Drop your draft into the tweet / X length checker to see the real weighted count, watch your remaining budget update live, and let it split anything over the limit into a clean, sentence-aware thread — counters included.