Quick reference
| Setting | Value / behavior |
|---|---|
| Words | whitespace-separated |
| Characters | Unicode code points |
| Reading estimate | 200 words/minute |
How to use the result
Different text limits count different things. This tool defines a word as a non-empty sequence separated by whitespace. Its character count uses Unicode code points rather than JavaScript UTF-16 code units. UTF-8 bytes are measured with TextEncoder, which helps explain why accented text and emoji can consume more bytes than plain ASCII. Lines count CRLF, LF and CR separators; an empty input has zero lines. A trailing newline adds an empty final line.
Limits and interpretation
Code points are not the same as visible grapheme clusters. A family emoji or a letter with a combining accent can contain several code points while looking like one symbol. Word segmentation also differs between languages; the whitespace rule is not a linguistic tokenizer for scripts without spaces. The reading-time estimate divides the word count by 200 words per minute. It is a simple planning convention, not a measurement of a particular reader, accessibility need or technical difficulty.
Check against your destination
Run the supplied example first, then replace it with a representative input from your own workflow. Change one parameter at a time so the effect is easy to inspect. Copy or download the output and compare it with a small known case before using it in a larger system. A successful calculation establishes only the behavior described on this page; it cannot check the assumptions or access rules of a remote application. Errors are shown next to the workspace rather than silently returning an empty success.
Local processing and data handling
This tool runs in the browser and does not transmit the entered content to a processing service. No input is saved to local storage, added to the URL or synchronized to an account. The clear control removes the current field and displayed result from this page. Clipboard contents and downloaded files remain under your operating system’s control. Keep original inputs when exact byte preservation matters, and avoid including sensitive tokens or private text in screenshots that you later share.
Frequently asked questions
Does the tool contact my server?
No. It processes the provided input locally and does not execute commands on your systems.
Can I download the result?
Yes. Use the Download result control after a successful run.
What happens to my input?
It remains in this page until cleared or closed. It is not saved by the tool.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy