How many lines? And which ones are actually empty?
Paste your text in, and this tool breaks it down: total lines, non-empty lines, blank lines, duplicate lines, longest line length, and average line length. It even shows you a snippet of the longest line so you can see exactly what’s blowing past your limit. All the stats show up instantly. No clicking required.
It’s the kind of tool you don’t think you need until you’re staring at a 800-line config file wondering how much of it is actual content vs. empty padding.
What you get
- Total line count, including blanks
- Separate counts for non-empty and blank lines
- Duplicate line count (how many repeated lines you could collapse)
- Longest line length (great for checking against 80-char or 120-char limits), with a preview snippet of that line
- Average line length
- Updates in real-time as you type or paste
- One-click “Copy stats” to grab all the numbers as plain text
- Browser-only processing, your text is yours
How to use it
Paste your text, code, log output, or data. Stats appear immediately. Compare the non-empty count against the total, if your 600-line file has 200 blank lines, that’s 33% whitespace.
Here’s a specific scenario: your team’s style guide says no file should exceed 500 non-empty lines. Paste the file contents, check the non-empty count. Done in seconds. Way faster than running wc -l and then trying to subtract blanks manually.
When it’s useful
Counting lines of code: LOC is a rough complexity metric, but it’s one almost every project tracks. The non-empty count gives you the meaningful number without the blank-line noise.
Log file analysis: got a log dump and need to know how many entries are in it? Paste it in. The blank line count tells you how many are just separators.
CSV row counting: total lines minus one (for the header) gives you your data row count. Quick and dirty but effective.
Code review prep: the longest line stat is perfect for checking line length compliance. If anything exceeds your 120-character limit, you’ll know immediately.
Poetry and lyrics: checking that formatted text has the expected number of lines. Fourteen lines? Congrats, it might be a sonnet.
For word-level analysis, pair this with the Word Counter. For character-level detail, try the Character Counter.
One quirk to know: trailing newlines at the end of a file add a blank line to the total. Most text editors insert these automatically, so your count might be one higher than expected.
FAQ
How are lines counted?
The tool splits on newline characters (\n). One line of text with no breaks = one line. Each newline creates an additional line.
Does it handle Windows line endings?
Yes. Both Unix (\n) and Windows (\r\n) endings work correctly.
Can I count lines of code with this?
Absolutely. Paste your source code and use the non-empty line count for actual content lines, ignoring blank spacing.
How does the duplicate count work?
It counts exact-match non-empty lines that appear more than once. If a line shows up three times, that’s two duplicates. Blank lines are ignored, so a file full of empty spacing won’t inflate the number. Whitespace and case have to match exactly to count as a repeat.
Is my text stored?
No. All counting happens in your browser. Nothing gets transmitted.