Word & Character Counter
Count words, characters, sentences, lines, bytes, and reading time.
Counts update locally as you type. Unicode characters are counted as code points.
Document statistics
- Words
- 0
- Characters
- 0
- Without spaces
- 0
- Lines
- 0
- Sentences
- 0
- UTF-8 bytes
- 0
- Reading time
- 0 min
Working notes
Use Word & Character Counter with the boundary visible.
Word & Character Counter reports Unicode-aware words, code-point characters, non-space characters, lines, sentences, UTF-8 bytes, and estimated reading time as text changes.
What is Word & Character Counter?
Accurate text measurement is essential when working with character limits, content requirements, and storage constraints. Social media posts have character limits (X/Twitter: 280 characters), meta descriptions should stay under 160 characters for Google, SMS messages break at 160 characters (or 70 for Unicode), and many APIs enforce payload size limits in bytes. A word counter provides real-time statistics as you type or paste text: word count, character count (Unicode code points, not bytes), non-space characters, line count, sentence count, UTF-8 byte size, and estimated reading time. This tool is Unicode-aware, meaning emoji, CJK characters, and accented letters are each counted as one character regardless of their byte representation. Reading time is estimated at approximately 200 words per minute, the average for technical content. All counting happens locally — your text is never sent to a server.
When to use it
- SEO meta descriptions — verify that your meta description stays within the 150-160 character sweet spot for Google SERP display.
- Social media posts — check that tweets, LinkedIn updates, or Instagram captions fit within platform character limits.
- Academic writing — track word count against assignment requirements (500 words, 1000 words, etc.).
- API payload sizing — measure the UTF-8 byte size of text content before sending it to APIs with byte-level limits.
- Content planning — estimate reading time for blog posts, documentation pages, or email newsletters.
How to use it
- 01Type or paste text into the editor. Counts update in real time.
- 02Read the statistics: words, characters, non-space characters, lines, sentences, UTF-8 bytes, and reading time.
- 03Use the UTF-8 byte count to verify payload sizes for APIs and databases.
- 04Clear the document when finished to remove it from memory.
Common mistakes
- Confusing characters and bytes — a single emoji can be 4 UTF-8 bytes. Character count (code points) and byte count differ for non-ASCII text.
- Platform-specific counting — X/Twitter counts URLs as fixed-length regardless of actual length. This tool counts the literal text, not platform-specific transformations.
- Whitespace variations — different types of whitespace (regular space, non-breaking space, tab, zero-width space) affect character and byte counts differently.
- Sentence detection limitations — sentence counting relies on punctuation patterns and may miscounted abbreviations (Dr., U.S.A.) or decimal numbers.
- Reading time is an estimate — 200 words per minute is an average. Technical content with code samples may take longer; casual prose may be faster.
Synthetic example
Measure a short release note
Input
StackCache works locally. Payloads stay here.
Result
6 words, 2 sentences, and an estimated 1 minute reading time
Related standards
Limits and data boundary
- Language-specific tokenization varies, so editorial word counts can differ between applications.
- Reading time assumes approximately 200 words per minute and is only an estimate.
Frequently asked questions
- How is the word count calculated?
- Words are split on Unicode whitespace boundaries. The count reflects visible words, not markup or code tokens.
- How is reading time estimated?
- Reading time is based on approximately 200 words per minute, a common average for technical content. Actual reading speed varies by complexity and reader.
- Does this tool count Unicode characters correctly?
- Yes. Characters are counted by Unicode code points, not bytes, so emoji and non-Latin scripts are counted as expected.
- What is the difference between characters and bytes?
- A character is one Unicode code point. Its byte representation depends on the encoding: ASCII characters are 1 byte in UTF-8, while emoji can be 4 bytes. The tool shows both counts.
Keep working