Word Counter · observed 2026-08-17
Six counts the Word Counter actually returned
Before you trust a word count on a public page, it helps to know exactly what a counter is counting, and where its rule quietly disagrees with yours.
Pass 1
The plain case
Start with an ordinary two-sentence draft: a greeting and a short claim about the product. Nothing in it is adversarial. If a counter cannot agree with a human reader on this case, nothing more complicated will help. The bench opposite shows exactly what the production interface returned when this input was typed in and read back from its live dashboard on 2026-08-17.
7 words / 40 characters / 34 without spaces / 2 sentences / 2 paragraphs
Observed output
Input:
Hello, world!
This is Pink Banana Tools.
Method: production browser input with one hard line break, observed 2026-08-17.
LIMIT One dated interface observation only.
Pass 2
A URL inside a sentence
Real drafts rarely stay this clean. Contractions, hyphenated compounds, a bare link and an emoji all show up in the same line more often than a style guide would like. This pass feeds the counter a single line carrying all four at once, to see whether the tool's sentence-ending heuristic survives a period sitting inside a web address rather than at the end of a thought.
Input
don't mother-in-law https://example.com 😀
Observed output
3 words 42 characters 39 without spaces 2 sentences 1 paragraph
LIMIT The punctuation inside the URL affected the sentence heuristic; do not read the sentence count as linguistic truth.
Pass 3
Accented text, kept intact
A café menu line with a French circumflex, an acute accent and a hyphenated compound is a small stress test for a counting tool. This pass records whether the accented characters survive the round trip and the exact word total returned for this input; it does not infer the full tokenisation rule.
Input
naïve café déjà-vu
Observed output
3 words 18 characters 16 without spaces 1 sentence 1 paragraph
LIMIT Retaining one accented sample does not prove every Unicode language or token boundary behaves the same way.
Pass 4
One line break, counted as a paragraph
A single hard line break sits between two short lines here, with no blank line and no double newline anywhere in the input: a period-ended clause, then a second line ending in a question mark. This pass checks whether the tool's paragraph rule needs a blank line to register a break, or whether one hard return is already enough, and whether a trailing question mark on that second line is counted as its own sentence rather than folded into the first.
Input
One sentence. Second line?
Observed output
4 words 26 characters 23 without spaces 2 sentences 2 paragraphs
LIMIT A single hard line break was enough to register as a paragraph boundary here; do not assume the rule requires a blank line.
Pass 5
A triple hyphen, read as two words
Long-form writers sometimes lean on a triple hyphen as an improvised em dash between two words with no surrounding spaces. This pass shows exactly how the tool's token rule treats that habit, so a reader can decide in advance whether their own expected word count would agree with the number the dashboard shows for the same string.
Input
hello---world
Observed output
2 words 13 characters 13 without spaces 1 sentence 1 paragraph
LIMIT Compare this exact input against your own token rule before trusting a similar count elsewhere.
Pass 6
Continuous Chinese text
This Chinese sample contains no spaces, and the production tool returned one word for its six characters. This pass is not a claim that the tool supports Chinese word segmentation; it documents the exact input and output without inferring how every unspaced script is tokenised.
Input
中文没有空格
Observed output
1 word 6 characters 6 without spaces 1 sentence 1 paragraph
LIMIT Do not treat this result as supported Chinese word segmentation.
Pass 7
What the extra numbers on the dashboard are not
Alongside every count above, the production interface also shows a read time, a speak time and a draft-check note. None of those three numbers were independently measured against a real reader in this session; the interface itself documents them as heuristics built from the raw counts, not as tested outcomes. The right-hand table below compares the token rule this notebook observed with the plain-language question it answers, so you can hold your own draft up against it before trusting a similar total.
| Rule | What it means for your draft |
|---|---|
| Word | Observed case boundary: hello---world returned two words, while the unspaced Chinese sample returned one. |
| Sentence | In the tested URL input, punctuation affected the sentence count. |
| Paragraph | In the tested inputs, one hard line break registered as a paragraph boundary. |
| Read/speak time | A heuristic from the word count, not a measured outcome. |
LIMIT Read time, speak time and draft-check values are heuristics; never call them measured reader outcomes or quality grades.
Across these six test inputs, the notable outputs were the boundaries visible in the displayed totals. The tested URL affected the sentence count, hello---world returned two words, and the tested unspaced Chinese sample returned one. For a new text, enter the exact difficult case and compare the returned total with the boundary you need instead of generalising from this small sample.