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.
Workflow
-
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
Use cases
- Understanding when to count characters vs tokens
- Platform-limited text
- Anyone conflating the two units