Words per line: why line-level counts matter
When a total word count hides the problem, per-line counts reveal it. How to use them for subtitles, code, CSV rows and poetry.
Why per-line counts beat a single total
A plain word count tells you how much text you have, but not how it is distributed. Two documents can share the same total while one is a tidy list and the other is a wall of run-on lines. Counting words per line exposes that shape, so you can see which rows are overloaded and which are nearly empty. That is the difference between knowing you wrote 300 words and knowing that one line carries 40 of them.
Subtitles and captions live and die by the line
Subtitle guidelines are written per line, not per file. Many broadcasters cap a caption at roughly 32 to 42 characters per line and two lines per cue so viewers can read it in time. Pasting a subtitle block here shows the character count for each line at a glance, making it easy to find the row that overflows. You fix the offender, recount, and move on without eyeballing every line.
Lists, CSV rows and code benefit too
When each line is a record, such as a shopping list, a set of CSV rows or lines of code, the per-line view acts as a quick sanity check. A row with far more words than its neighbours often signals a missing line break or a stray join. The character column helps spot lines that will wrap awkwardly or exceed a column width limit. Because blank lines are counted and labeled, you can also confirm your spacing is where you expect it.
How the counting rules affect your numbers
The counter treats any run of non-whitespace as one word, so hyphenated terms like 'well-known' count as a single word, while a stray symbol padded with spaces counts on its own. Numbers, emoji and symbols each count as characters, and a line of only spaces reports those spaces without any words. Knowing these rules keeps your expectations aligned with the output, especially when a line looks empty but still holds trailing whitespace.