Free Line Counter – Count Lines in Text Online

What a Line Counter Measures and Why Four Figures Matter

This reports how many lines your text contains, broken into four numbers: total, non-empty, empty and unique. The reason four rather than one is that each answers a different question. Total tells you the raw size. Non-empty tells you how many lines carry actual content. Empty tells you how much of the file is spacing. Unique tells you how many distinct entries there are, which is the figure that matters when you are about to import a list somewhere. Developers, data analysts, poets working to a line count and anyone verifying an export all use it, and the numbers update as you type. The method is a split and three passes. Your text is divided on line-break characters, handling Unix line feeds and Windows carriage-return pairs alike. The resulting array length is the total. Lines whose trimmed content is empty are counted as empty, and the remainder as non-empty. For the unique figure, each line is trimmed of surrounding whitespace and compared against a record of what has already been seen, so two lines differing only by a trailing space are recognised as the same entry — which is exactly the behaviour you want when checking a pasted export. Alongside these, the length of the longest line in characters is reported, useful for confirming no line breaches a width limit in code or a fixed-format data file. A worked example. Paste six lines: apple, banana, a blank line, apple with a trailing space, cherry, banana. The total is 6. One line is blank, so empty is 1 and non-empty is 5. For uniqueness, trimming makes the fourth line identical to the first, and the sixth repeats the second, so unique comes to 3 — apple, banana and cherry. That gap between 5 non-empty lines and 3 unique ones is the whole point: it tells you immediately that this list contains two duplicates you would otherwise have imported without noticing. Specific situations. A developer checks that a generated config file has exactly the 240 lines the build script expected. A data analyst pastes a 1,500-row export and finds only 1,438 unique entries, which explains a mismatch downstream. A poet confirms a sonnet is 14 lines before submitting to a competition with a strict form requirement. A sysadmin pastes an error log and sees 800 total lines but 12 unique ones, which reframes the problem entirely. A screenwriter checks a page against a formatting requirement of 55 lines per page. A teacher collecting one answer per line from 32 pupils confirms nobody submitted twice before marking. A translator counting subtitle lines checks the target file has the same number as the source, since a missing line means a dropped caption somewhere in the timeline that will be obvious to viewers. The useful habit is to read total and unique together rather than either alone. A big gap between them means duplicates exist, and a big gap between total and non-empty means the file is mostly whitespace — both are things you want to know before importing anywhere that charges per row or enforces uniqueness. One limitation worth naming: uniqueness here trims whitespace but is otherwise exact and case-sensitive by nature, so Apple and apple count as two distinct lines. If your data has inconsistent capitalisation, normalise the case before relying on the unique figure at all. A trailing newline at the end of a file also produces one final empty line, which is why a 100-item list sometimes reports 101 total rather than 100. All counting runs in your browser, so logs, code and private lists are never uploaded, stored or logged.

🔥 Trending Tools