Counting lines sounds simple, but the answer depends on details: blank lines, the final line, and whether wrapped lines count. This guide explains how line counting works and how to get a count you can trust.
What counts as a line
A line is text ending with a newline character. A file with three newline characters has three lines if the last line also ends with a newline, or a debated fourth line if text follows the last newline without one. Different tools answer this differently, which is why counts sometimes disagree by one.
Step-by-step: count lines in pasted text
- Paste the text into a counter or editor that shows line numbers.
- Decide whether blank lines count. For code and data, they usually do; for prose word counts, they often do not.
- Check the end of the text. If the last line has no newline after it, some tools will not count it.
- Compare two methods when the count matters: a line-number display and a newline count. If they differ by one, the final-line question is the cause.
- For files, the classic Unix command is wc -l, which counts newline characters, so it undercounts by one when the last line lacks a trailing newline.
Why counts disagree
Blank lines are the main source of disagreement: some counters skip them silently. Wrapped lines are another: a long line that wraps on screen is still one line in the file, but looks like several. Line endings also matter: Windows files use two characters per break, Unix files use one, and old Mac files used a different one. A good counter normalizes these before counting.
When line counts matter
Programmers track lines of code, writers track lines in manuscripts, and data workers check that a file has the expected number of rows. In each case, an off-by-one error at the end of the file can look like missing data. Always state your counting rule when the number will be compared with someone else’s.
Try it the faster way
Paste your text into the tool below to count lines instantly.
Prefer the full page? Open the line counter directly.
Quick tips
- State whether blank lines count before comparing numbers.
- Check the final line: a missing trailing newline shifts counts by one.
- For code, count lines with a tool that understands your file’s line endings.
Line counting is only tricky at the edges: blank lines and the final line. Settle those two questions first, and every tool will agree.
Frequently asked questions
Why does wc -l report one fewer line than my editor? Because wc counts newline characters, and a file whose last line lacks a trailing newline has one fewer newline than lines. Editors count the final partial line as a line. Both answers are defensible; the difference is the trailing newline.
Do blank lines count as lines? In most tools, yes, because a blank line is still a line ending with a newline. Some prose counters exclude them. State your rule when sharing a count, especially for code metrics or manuscript lengths.
What are CRLF and LF line endings? LF is the Unix newline, one character. CRLF is the Windows newline, two characters. A file with CRLF endings can confuse naive counters and tools. Good counters normalize endings before counting, so the result is the same either way.
Worked example
Consider a file with three lines of text, where the third line has no newline at the end. An editor shows 3 lines, but wc -l reports 2, because it counts newline characters and only two exist. Neither tool is wrong; they answer different questions. For data files, this matters: a row count from wc -l can undercount by one, making a file look short a row. When a count matters, check the file’s ending and state whether the final partial line counts.