Character Counter
Count characters against X, SMS and meta-description limits — free and entirely inside your browser
- Characters
- 0
- No spaces
- 0
- Words
- 0
- UTF-16 units
- 0
- Code points
- 0
- Arabic diacritics
- 0
- X (Twitter) post0 / 280
- Page title (SEO)0 / 60
- Meta description (SEO)0 / 160
- Instagram caption0 / 2200
🔒 Your text never leaves the browser — not one character is sent anywhere, and nothing is stored
How to use it
- Paste your textEvery counter updates from the first character — no button, no waiting.
- Pick the number that applies to you"Characters" when what is on screen matters, "UTF-16 units" when the limit belongs to a form field or a database column.
- Watch the metersEach limit turns amber at 90% — before you go over it, not after.
- Read the SMS lineIt tells you which encoding your message will use, how many parts it costs, and how many units remain before the next one.
Enjoying the tool? Help us keep it free forever — Support OMXHub ❤️
Frequently Asked Questions
Why do you give three different lengths?
Because there genuinely are three, and averaging them into one number would be wrong for somebody. "Characters" is what you see — سَلام is four. "UTF-16 units" is what form fields and database columns enforce, and the same word is five there. "Code points" is the number in between, used by Unicode-aware back-ends. The second number is the one that rejects your text; the first is the one on your screen.
Does an Arabic character count as two on X (Twitter)?
No — and this is one of the most widely repeated mistakes about X. X counts by weighted code point: the ranges covering Latin and Arabic weigh 1, while emoji and CJK weigh 2. So an Arabic post gets the full 280, and it is emoji that eat it twice as fast. The meter above runs X’s own weighting, not a plain character count.
Why is an Arabic SMS only 70 characters?
Because SMS has two encodings. GSM-7 covers Latin letters and digits and fits 160 characters in a message; UCS-2 covers everything else and fits 70. A single Arabic letter — or one emoji dropped into an English message — moves the whole message to UCS-2 and cuts it from 160 to 70. Past one part, each part also spends 7 units on the header that stitches them back together, which is where 153 and 67 come from. This is not cosmetic: being one part out means a doubled bill on a bulk send.
Are the meta description and title limits exact?
They are approximate by nature. Google truncates by pixel width, not character count, so a title full of wide letters is cut sooner than a narrow one of the same length. The numbers here — 60 for a title, 160 for a description — are the accepted practical thresholds, offered as guidance. Going slightly over breaks nothing; going well over loses the last thing you wrote.
What counts as "no spaces"?
Everything that is not a space, a tab or a newline. Useful when a limit applies to the content itself — plenty of writing competitions and application forms count that way.
Is my text uploaded anywhere?
No, not one character. Every figure is computed inside your browser; nothing is stored and nothing is sent.