What limits does the character counter track?

It counts characters, words, lines, sentences, paragraphs, and UTF-8 bytes in real time, and it tracks the limits that actually matter for publishing: Twitter/X 280, SMS 160, SEO title 60, and meta description 160. As you type, it shows how close you are to each limit, so you never discover a truncated tweet or title after publishing.

Does the counter handle emoji and multi-byte characters correctly?

Yes. The UTF-8 byte count reflects how emoji and CJK characters actually consume bytes on the wire — an emoji is often 4 bytes, not 1 character — which matters for SMS gateways and API payload limits that bill by byte. The code-point and grapheme counts follow what a reader sees, the UTF-16 count matches JavaScript's .length , and the byte count follows what the network and the database charge.

Is the character count calculated locally?

100% client-side. Your text never leaves the browser, so you can safely paste draft posts, code snippets, or sensitive copy. There is no server, no account, and no rate limit on how much you analyze.

Character Counter — Count Characters, Words, Lines, UTF-8 Bytes

🟢📖 Character Count Limits Explained

Twitter/X (280)	Counts Unicode code points (not UTF-16 code units). URLs count as 23 characters regardless of length (t.co wrapped). CJK characters count as 2. This counter shows raw character count.
SMS (160)	Standard GSM-7 encoded SMS maxes at 160 characters. Messages using non-GSM characters (like CJK, emoji) are UCS-2 encoded and limited to 70 chars. Multi-part SMS split at 153 chars (GSM-7) or 67 chars (UCS-2).
SEO title (60)	Google's display limit for title tags in SERPs. Titles longer than ~600px (roughly 60 chars) get truncated with "—". Pixel width matters more than character count — W is wider than i.
Meta description (160)	Google displays up to ~920px (roughly 155-160 chars) of meta description in search results. Longer descriptions are truncated. In 2026, Google may dynamically generate snippets from page content regardless.

Four counts, four answers. A character can mean four different things, so this tool reports the three that disagree. Code points are what most languages call characters, and what X counts. Grapheme clusters are what a reader perceives: a family emoji is one cluster, seven code points, eleven UTF-16 units and 25 UTF-8 bytes. UTF-16 units are what "👍".length returns — two, for one visible character — and they matter because that is the number a JavaScript validator reaches for by default.

UTF-8 bytes matter for database storage, API payloads, CSV encoding and column limits. ASCII is 1 byte, Latin-1 supplement 2 bytes, CJK 3 bytes, and emoji or anything above U+FFFF is 4 bytes — which is why a VARCHAR(255) column under utf8mb4 reserves 1,022 bytes rather than 255. See The 191 Problem for the arithmetic.