Resource
Character Counter
Paste any text and see characters, words, lines, and reading time at once — plus whether it fits Twitter, SMS, and meta-description limits.
Character vs Token — When Each One Matters
A character is what you type; a token is what a model reads. This shows when to count which, from the character side.
Overview
People mix up characters and tokens because both measure "how much text", but they answer to different masters: characters and words are capped by platforms and read by people, while tokens are processed and billed by models. This loads a short post and measures it in human units — characters, words, reading time — the units that decide whether it fits a tweet. When the question is a platform limit or a reader, count characters here; when it is a model's context or an API bill, count tokens in the Token Counter. Same text, two different questions.
How to use this resource
-
Measure in human units
Characters, words, and reading time for a real post.
-
See what platforms cap
The limits people and platforms actually enforce.
-
Switch sides when needed
For model context and cost, count tokens instead.
Why This Works
- Characters and tokens answer different questions — platform vs model
- Measuring a real post shows which unit the limit is in
- The boundary is explicit: count here for people, tokens for models
Best for
- Understanding when to count characters vs tokens
- Platform-limited text
- Anyone conflating the two units
Not for
- Estimating token cost — that's the Token Counter
- Context-window fit — that's the Context Window Estimator
FAQ
Which platform limits does this length report check my text against?
The PLATFORM NOTES section measures your character count against six common caps: X / Twitter post (280), SMS single (160), Meta description (160), Google title tag (60), Instagram caption (2,200), and LinkedIn post (3,000). For each it shows fits with characters left or over by a count, so you see which platform your post actually breaks before publishing.
When should I count tokens in the Token Counter instead of measuring characters here?
Switch sides whenever the limit belongs to a model rather than a platform or reader. The report draws that line explicitly: 'AI model inputs are measured in tokens, not characters.' Character metrics answer platform caps and reading time; a model's context window or an API bill is a token question, so count those in the Token Counter, not here.
Why might my emoji or CJK text throw off the character count in this report?
The NOTES warn that some emoji and combined scripts may count as more than one character, since the tool counts the units a text field counts rather than visible glyphs. Language shifts every metric too — word and sentence boundaries differ, and CJK text packs more meaning per character, so a Chinese post can read long while its character count stays low.
More resources from Character Counter
Resource
Word Counter
Count words in any text, with sentence and paragraph structure and reading time — for essays, articles, and anything with a word target.
Resource
Calculate Reading Time for an Article
How long will this take to read? Estimate reading time from word count at a pace you choose — the "5 min read" label, calculated.
Resources that pair well
Resource
Estimate Token Usage Before You Run It
Know how many tokens a job will consume before you send it — input plus an assumed response, costed per call and at scale.
Resource
Estimate Token Budget — Plan Before You Paste
Token budget planning for real workloads: how much of the window a transcript actually consumes, what is left for the answer, and how much headroom remains.
Resource
Prompt Cleanup Examples (Before & After)
A set of before-and-after examples showing exactly what prompt cleanup removes — and what it deliberately leaves alone.
Related tools
Tool
Character Counter
Count characters, words, lines, and reading time — with live platform-limit checks for Twitter, SMS, meta descriptions, and more.