0
Characters (with spaces)
Analyze characters, words, sentences, paragraphs, lines, UTF-8 bytes, reading time, target length, and keyword frequency in real time.
0
Characters (with spaces)
0
Characters (no spaces)
0
Words
0
Sentences
0
Paragraphs
0
Lines
0
UTF-8 bytes
0
Reading time (min)
Enter text to see its most frequent terms.
Type or paste your text into the text area.
Eight statistics, target-length progress, and frequent terms update instantly as you type.
Use 'Copy results' to copy the statistics to your clipboard, or 'Clear' to reset the input.
A. Yes. The Intl.Segmenter API performs language-aware word segmentation for Japanese, Chinese, Korean, and other non-space-separated languages. Browsers that don't support Segmenter automatically fall back to space-based counting.
A. There is no fixed input limit, but extremely long documents can update more slowly depending on device performance.
A. Yes. It's ideal for checking Twitter/X's 280-character limit, Instagram captions, email lengths, and any other platform character restrictions.
A. Characters (with spaces) counts every space, tab, and newline as one character. Characters (no spaces) excludes all whitespace — only visible characters are counted. Line count equals the number of newline characters plus one.
A. Yes. The tool counts the raw text as typed, so HTML tags (<p>, <br>, etc.) and Markdown syntax (#, **, -, etc.) are each counted as individual characters. To count only the visible content, paste the plain text without any markup.
JavaScript's str.length returns UTF-16 code units rather than visible characters. This tool uses Intl.Segmenter with grapheme granularity, so joined emoji and combining-mark sequences are counted as user-perceived characters.
Word segmentation uses Intl.Segmenter with word granularity where the browser supports it. This is more useful than whitespace splitting for Japanese, Chinese, and Thai, but segment boundaries are browser- and locale-dependent and should not be treated as a linguistic guarantee.
Line count is the number of newline characters plus one. Windows CRLF endings are normalized to LF first, and an empty input reports zero lines.
The 'no-spaces' character count strips all whitespace using the regular expression /[\s\u3000]/g, which covers ASCII spaces (U+0020), full-width Japanese spaces (U+3000), tabs (U+0009), and all newline variants. This ensures full-width spaces common in Japanese text are excluded alongside standard ASCII whitespace.
Counting uses browser string APIs and does not make a request that uploads the text entered into the tool.
Page assets and unrelated browser activity can still create network entries. To inspect the action, let the page finish loading, clear the DevTools Network log, and type recognizable dummy text.
Input is held in React state for the current page session and is not intentionally persisted by this tool. Shared devices, extensions, clipboard history, and screen capture remain separate risks.