Three counts that people commonly mean
- Characters including spaces: every Unicode code point in the input, including spaces and line breaks.
- Characters excluding spaces: the same input after whitespace is removed. Document Forge removes whitespace for this metric; check the destination's exact rule because some forms remove only ordinary spaces.
- Words: groups separated by whitespace. This is a useful estimate for Latin-script text, but word boundaries work differently in Chinese, Japanese, Korean, and other scripts.
A small example explains the difference
For the two-line sample A B followed by C, this counter reports five characters including the line break, three without whitespace, and three whitespace-separated words. That is not a universal answer for every application: the destination may ignore line breaks, count visible grapheme clusters, or apply its own normalization. Use examples to understand a rule, not to assume that every form follows it.
Why the number may differ from another tool
Different counters normalize line breaks, tabs, emoji sequences, punctuation, and invisible characters differently. Unicode also allows some visible symbols to be represented by more than one code point. A family emoji, a combined accent, or a flag can look like one symbol while containing multiple code points. A form may count code units, code points, grapheme clusters, or a product-specific rule. When a limit is strict, paste a small test string into the destination form and follow its displayed number.
How Document Forge counts
The counter updates in the current browser session. It counts Unicode code points with Array.from, removes all JavaScript whitespace for the no-space metric, splits words on runs of whitespace, and treats non-empty lines as paragraphs. This makes the result predictable and useful for drafting, but it is not a promise that a school, publisher, application portal, or social network uses the same definition. The destination remains the final authority.
A reliable workflow for applications and reports
- Write and revise the content in one editor.
- Keep the final version's punctuation, line breaks, and symbols intact.
- Check both space-inclusive and space-free counts.
- Leave a small margin below the maximum if the destination may normalize whitespace.
- Paste the final text into the destination and verify once more.
- Save the submitted version separately if you may need to prove what was sent.
For Korean and multilingual text
Do not estimate Korean length by multiplying a word count. Korean spacing, English names, URLs, numbers, and punctuation can all affect the final count. For a multilingual application, paste the exact final text, including the line breaks the form will receive. For Japanese or Chinese text, word counts are especially approximate because spaces are not normally used between every word.
Reading time is an estimate
Reading time is calculated from an approximate words-per-minute rate. It helps compare drafts and plan a page, but it is not a promise. Dense technical writing, unfamiliar names, tables, and non-Latin scripts can take longer than the estimate. Treat it as a planning hint, not a publication metric.
Document Forge shows characters, characters without spaces, words, paragraphs, and an estimated reading time without uploading the text for the counter. If the text is confidential, keep the browser tab on a trusted device and clear the field when you are finished.