Character Counter

Real-time character counter for any platform or limit

This character counter gives you live counts for characters (with and without spaces), words, sentences, lines, and paragraphs as you type or paste text. Platform limits for Twitter/X (280 for free accounts, 4,000 for Premium), LinkedIn posts (3,000), SMS (160 GSM / 70 UCS-2), and Instagram captions (2,200) are shown as progress indicators with color cues — green under the limit, amber near it, red over.

Nothing is sent to a server. The counting runs entirely in JavaScript in your browser. There is no sign-up, no file upload, and no character limit on the text you can paste — it handles entire articles, email drafts, or screenplay excerpts without slowing down.

How character counting works — with and without spaces

A character is any single unit in a string of text — letters, digits, spaces, punctuation marks, and emoji. The total character count (with spaces) is the length of the raw string. Characters without spaces is the count after removing every whitespace character. Most social platforms count spaces, so 'Hello world' is 11 characters to Twitter, not 10.

Emoji add complexity. Most emoji occupy 2 code units in JavaScript's UTF-16 string model, so 😀 counts as 2 in many systems. Twitter normalized emoji counting to 1 character per emoji in 2018. This counter uses JavaScript's length property for raw character count — the number that matches what most word processors report and what most platform limits are measured against.

Platform character limits — Twitter, LinkedIn, Instagram, SMS

Every platform imposes different limits, and most count differently. Twitter/X: 280 characters free; 4,000 for Premium. URLs always count as 23 characters. LinkedIn post: 3,000 characters. Connection requests: 300. Comments: 1,250. Instagram caption: 2,200 characters; 2–3 lines visible before 'More'. SMS (GSM-7): 160 per message, splits into segments of 153 characters for multi-part. Meta description (SEO): Google displays roughly 155–160 characters. YouTube title: 100 chars, 70 to avoid truncation.

The indicators in this tool track the most common limits. If your target isn't listed, the raw character count at the top is your number — compare it to whatever limit applies to your use case.

Character counter vs. Word, Google Docs, and charactercounter.com

Microsoft Word's character counter lives in Review → Word Count and doesn't update in real time while you type — you press Ctrl+Shift+G each time you want a fresh count. Google Docs is similar: Tools → Word Count on demand, not live. Grammarly's editor shows word count but not character count by default. None show platform-specific limit indicators for Twitter or LinkedIn.

Sites like charactercounter.com and lettercount.com offer similar live counting. The difference here is no ad trackers on the tool page — charactercounter.com loads multiple advertising networks that can observe your text via page parameters. This tool has no third-party ad scripts on the counting page. Once the page loads, it works offline too.

Writing better within character limits

Character limits force concision, which usually improves writing. For Twitter, the constraint is brutal but useful — if your tweet needs 350 characters, it probably has padding that can be cut. For SEO meta descriptions, staying under 160 characters while including the target keyword and a clear benefit is a real discipline that separates effective copy from generic filler.

Practical editing strategies for tight limits: cut filler words ('that', 'very', 'just', 'really'); replace phrase constructions with single words ('in order to' → 'to'); cut unnecessary context from the start of sentences. In SMS, abbreviations are tolerated by convention. For professional copy on LinkedIn or Twitter, abbreviations usually hurt more than they help — clarity matters more than squeezing past the limit.

A brief history of platform character limits — and why they exist

Twitter's 140-character limit was not arbitrary — it was derived from the 160-character cap of SMS messages. The original design planned to deliver tweets via SMS, reserving 20 characters for the @username prefix. That constraint outlasted SMS delivery by years, becoming Twitter's defining feature until November 2017, when the limit doubled to 280 characters for most languages. The change was controversial but data-driven: English speakers regularly hit the 140 cap, while Japanese users (whose characters pack more information per symbol) rarely did. The doubling brought English closer to parity with CJK languages in terms of expressible meaning per tweet.

SMS encoding creates a subtler limit that many users discover the hard way. The GSM-7 character set covers basic Latin letters, digits, and common punctuation — 160 characters fit in a single SMS frame at 7 bits per character. The moment you type an emoji, a curly apostrophe (' instead of '), an accented vowel outside the GSM-7 table, or any character from a non-Latin script, the entire message re-encodes in UCS-2 (a 16-bit encoding), which shrinks the single-message cap to 70 characters. Multi-part UCS-2 messages get only 67 characters per segment because header bytes eat into the payload. A 71-character message with one emoji therefore costs two SMS credits. Marketing platforms that send bulk SMS bill on segment count, making encoding awareness a real cost issue.

SEO character limits are softer than social media limits — Google doesn't refuse to index a page title with 80 characters, it simply truncates the display. Page titles render in search results at roughly 50–60 characters (600 pixels is the true constraint, and character width varies by font). Meta descriptions display approximately 155–160 characters before being cut with an ellipsis; going longer wastes the copy you carefully wrote. YouTube titles allow 100 characters but only about 70 appear in search thumbnails. WhatsApp is at the opposite extreme — its message field accepts up to 65,536 characters, far beyond any practical single message, so it has never required a character counting strategy.

Characters vs. bytes vs. Unicode code points — why counting is harder than it looks

When a developer says 'count the characters in this string,' the answer depends entirely on what they mean by character. In ASCII (the 128-character encoding that covers basic English), one character equals one byte equals one code point — the three concepts collapse into one. The complexity starts with Unicode. UTF-8, the encoding of the web, uses 1 byte for ASCII characters, 2 bytes for most accented Latin, Greek, and Cyrillic characters, 3 bytes for CJK ideographs, and 4 bytes for emoji and rare symbols. A 10-character Japanese sentence can consume 30 bytes.

UTF-16 (the internal encoding used by JavaScript, Java, and Windows) uses 2 bytes per code unit, but characters outside the Basic Multilingual Plane — including most emoji — require two code units (4 bytes), called a surrogate pair. This is why ('😀').length returns 2 in JavaScript, not 1. A rainbow flag emoji 🏳️‍🌈 is not a single code point at all — it is a sequence of four code points joined by Zero Width Joiner characters, consuming over 10 bytes in UTF-8 and counting as 6 in JavaScript's length. Twitter normalizes all emoji to a count of 2 regardless of their underlying complexity; most other platforms use the JavaScript length value directly.

This distinction matters for database schema design. MySQL's VARCHAR(255) defines a column of 255 characters, but the storage cost depends on encoding: with utf8mb4 (which supports full Unicode including emoji), each character can cost up to 4 bytes, so a VARCHAR(255) column may store up to 1,020 bytes. A developer who validates 'max 255 characters' in front-end code but uses utf8mb4 in MySQL is safe on length but should understand the byte budget. APIs that size payloads by bytes rather than characters (some SMS gateways, older serial protocols) require byte-level counting, not character-level counting — the distinction is the difference between a message that sends and one that is silently truncated.

Word count, reading speed, and readability metrics

Word count and character count are related but answer different questions. Character count governs whether a platform will accept your text. Word count governs how long a reader will spend with it. The average adult reads approximately 200–250 words per minute; a fifth grader reads around 120 wpm. A 1,000-word blog post takes a typical adult about 4 minutes to read. A 280-character tweet contains roughly 40–50 words and takes under 10 seconds. Knowing both numbers lets you match content length to the attention budget of your audience.

The Flesch Reading Ease score quantifies how easy a passage is to read. The formula combines average sentence length and average syllable count per word: 206.835 − 1.015 × (words/sentences) − 84.6 × (syllables/words). Scores above 70 are considered easy (plain English); below 30 are very difficult (legal or academic text). The related Flesch-Kincaid Grade Level formula outputs the US school grade whose students could read the text: a score of 8 means an eighth grader could understand it. Both formulas count words and syllables — which is why word-count tools that also show sentence averages are a proxy for readability even without running the full formula.

For SEO content, word count acts as a weak but real signal. Google has stated it does not use word count as a ranking factor directly, but longer content tends to cover a topic more thoroughly, attract more backlinks, and answer more related questions — all of which do influence ranking. Research from multiple SEO data providers consistently shows that pages ranking on page one for competitive terms average 1,400–1,800 words. Blog posts under 300 words are sometimes flagged as 'thin content' in site audits. The practical guideline: write until you have covered the topic without padding, then check the word count as a sanity check rather than a target.

Character and word counting across writing systems and professions

A word counter is fundamentally a Western concept. In English and most European languages, words are clearly delimited by spaces, making word count an unambiguous metric. In Chinese and Japanese, text is written without spaces between words — a single Chinese character (汉字, hànzì) often corresponds to a complete concept or word, so character count and word count are nearly equivalent. Japanese mixes three scripts (hiragana, katakana, and kanji), and the boundary between words is inferred from grammar, not spacing. Thai and Khmer similarly write without word spaces; automated word counting requires a dictionary-based segmentation engine. For these scripts, character count is the only reliable universal metric, which is part of why Twitter switched to 280 characters after finding that CJK speakers could express twice the content in 140 characters as English speakers could.

Arabic presents a different challenge: it is written right-to-left, and each Arabic letter has up to four different visual forms depending on its position in a word (isolated, initial, medial, final). Unicode encodes Arabic letters in their base form and uses contextual shaping rules to render them — but some older systems represent each positional form as a separate code point, causing character counts to diverge from what a user sees on screen. Arabic also uses diacritical marks (tashkeel) that are technically separate code points layered on top of consonants; a letter with a vowel mark can be either one code point (with the diacritic precomposed) or two (base letter + combining mark), yielding different character counts for visually identical text — a phenomenon called Unicode normalization (NFC vs. NFD).

By profession, character counting serves distinct purposes. Social media managers track Twitter's 280-character and LinkedIn's 3,000-character limits daily, often across multiple drafts per post. SEO writers target 50–60 characters for page titles and 155–160 for meta descriptions — a discipline enforced not by the CMS but by understanding how Google truncates. Developers use character and byte counts to size database columns, validate API payloads, and set input field limits in forms. Legal writers face court filing rules that specify maximum page counts (often implying a word limit at typical line spacing) or explicit word limits for briefs — the US Supreme Court caps merits briefs at 15,000 words. Academic writers contend with journal abstract limits (usually 250 words), conference paper page limits, and essay word ranges where going 10% over the maximum can disqualify a submission. A reliable character and word counter is a professional tool in every one of these contexts.