X (Twitter) Character Counter

The composer's countdown looks like a character count and behaves like something else. What it actually tracks is a weighted length: each character is assigned a cost, the costs are added up, and the total is compared against 280. For an English sentence every cost is 1, the weighted length and the character count are identical, and nobody notices the distinction exists.

It stops being invisible the moment a post contains a link or a character from outside the Latin block. Then the countdown moves faster or slower than your typing, a draft that looked like it had room refuses to send, and a generic character counter — the kind that measures the string and reports the length — tells you the post is fine when X disagrees.

The rules are not secret. X publishes an open-source library, twitter-text, whose configuration file lists the weights, the ranges they apply to, and the length a link is replaced with. That file is what the tool above implements, which is why it and the composer land on the same number.

Before a post is measured, X substitutes each link with a t.co wrapper of fixed length. The measurement is taken on the wrapper, so the URL you typed never enters the arithmetic. Twenty-three units is the cost, and it is the same cost for http and https links alike.

That cuts both ways, and the second half is the part people miss. A 200-character URL with five tracking parameters costs 23 — which is why stripping utm_source before posting buys you nothing in the counter, however much it improves the look of the link. But a four-character domain also costs 23, so a post reading x.co is charged nineteen units more than it appears to be. Two short links in a post are 46 units, or about a sixth of the whole limit, before you have written a word about them.

The practical consequence is that the link is a fixed budget line. Decide whether the post carries one at all, then write the remaining 257 units around that decision, rather than writing to 280 and discovering the shortfall when the send button greys out.

X defines a small set of code-point ranges that cost 1 unit and charges 2 for everything else. The generous range runs from the start of Unicode up to U+10FF, which takes in Latin, Greek, Cyrillic, Hebrew, Arabic, Devanagari, Thai and Georgian. Three narrow ranges inside General Punctuation are added to it: the typographic spaces and joiners, the dashes and curly quotation marks, and the prime marks.

Everything outside those ranges weighs 2: Chinese, Japanese kana, Korean hangul, and every emoji. A Japanese post therefore has a practical ceiling around 140 characters rather than 280, which is the original limit and not a coincidence — the weighting was introduced so that the 2017 move to 280 gave English-language posts more room without changing what a Japanese post could say.

Emoji are weighed by the character you see rather than the pieces it is built from. A flag is two regional indicators, a family emoji is four people stitched together with zero-width joiners, and a skin-toned wave is a hand plus a modifier — each of them costs 2 units in total, not 2 per component. The breakdown in the tool lists the exact characters that doubled, so you can see whether the culprit is a script or a single stray emoji.

This tool counts against 280 weighted units because that is the ceiling a free account writes against. X Premium raises it into the thousands, so a Premium subscriber pasting a long draft here will see a red bar that does not reflect any real restriction on their account.

Length being available is a different question from length being read, though. However long a Premium post is allowed to be, the timeline shows a truncated preview with a link to expand, so the opening still has to earn the tap. Treating 280 as a working target even when you are not bound by it is a defensible editing habit rather than a limitation.

It measures text. It does not contact X, so it cannot tell you whether a post will send, whether an account is in good standing, or how a draft will perform. The number is arithmetic on the string in the box, and the composer remains the only authority on what X will accept.

One limitation is worth stating plainly. X recognises bare domains — a link written without http or www — by checking the ending against the full public list of top-level domains, which runs to well over a thousand entries and changes. This page carries the common set rather than shipping that list to your browser, so a bare domain on an unusual ending may be counted as ordinary text here when X would charge 23 for it. The error runs the other way too: an address written with http:// but pointing at something that is not a public domain, a localhost or a raw IP, is charged 23 here where X would leave it as prose. Writing real links with https:// removes the ambiguity, and it is what you should do anyway when the link matters.

Once the arithmetic is settled, the editing problem is the interesting one. The units a post wastes are rarely in the argument — they are in the throat-clearing before it. Openers along the lines of I've been thinking about this for a while, but cost forty-odd units and carry nothing. Cutting them is free.

Hedges are the next cheapest win. Sort of, kind of, arguably, it seems like: each one softens a sentence you presumably meant, and each one is billed at full weight. The compression that follows usually reads better than the draft it replaces, which is the unusual case of a constraint improving the work.

After that, decide about the link deliberately. If the post stands on its own, drop the link and reclaim 23 units. If the link is the point, write a shorter post around it and accept that a sixth of the budget is already committed.

None of this fixes the harder problem, which is that a sharply written post reaches almost nobody from an account with no visible audience — replies and reposts are what carry a post outward, and both are far likelier to come from people who see a following behind the name. Most accounts close that gap slowly by posting through it. Some shorten the runway by buying Twitter followers to put credible social proof behind the handle while the organic reach builds.