Does a trailing newline create another line in the count?

Yes. Each LF, CRLF pair, or lone CR creates one line boundary, and a boundary at the end of the input produces a final blank line. The only case defined as zero lines is an entirely empty input.

How does the counter tell blank and non-blank lines apart?

A line is counted as blank when trimming its Unicode whitespace leaves nothing. A line made up of only spaces or tabs is blank; a line containing any visible or non-whitespace character is non-blank.

What does longest line in code points actually mean?

It counts Unicode code points, not UTF-16 code units or visual characters. A supplementary-plane emoji like 😀 is one code point even though it is stored as two UTF-16 units. Combining marks and zero-width joiners count separately, so the metric is not the same as grapheme count or terminal width.

What happens if the pasted text exceeds the input limit?

The tool refuses text over 1,000,000 UTF-16 code units in full. Previous statistics are hidden and an error is shown; the tool does not truncate, does not count a prefix, and does not return a partial result.

How to Count Lines in Word When the Status Bar Lies

The number of lines Microsoft Word displays in the status bar is a layout estimate that recomputes every time you change the window width, zoom level, line spacing, or even the document theme. That is why the line count in a Word document can shift by several rows between two saves without you editing a single character. The reliable way to count lines in Word is to count the actual line breaks in the underlying text — the LF, CRLF, or CR characters that separate one logical line from the next — rather than the visual rows Word decides to render on the current page. A browser-based line counter does exactly that: paste your text in, read four stable statistics (total lines, non-blank lines, blank or whitespace-only lines, and the longest line measured in Unicode code points), and compare the result against a clearly stated set of rules so you know what produced the number. This works for plain text, source code, logs, transcripts, CSV exports, and the body of a Word document copied out of the application, all without uploading your content to a remote server.

What Word's Status Bar Is Actually Counting

Word's status bar shows a "Lines:" count, but it is not a count of newline characters. It is the count of visual rows the current layout needs to render the page, and that layout depends on line spacing (single, 1.5, double, At Least, Exactly), the width of the text area after margins, widow and orphan control, whether headings use "Keep with next," the document's zoom level, and even whether the proofing underlines are visible. Two files with identical line breaks can display different line counts in Word simply because one uses 11-point Calibri and the other uses 12-point Times New Roman.

The same logic explains why the count can move inside a single document. The moment you switch from Print Layout to Draft view, Word uses a different set of layout metrics, and the number shifts. Resize the window narrower and the count usually climbs because more lines wrap; widen the window and the count falls. Insert a footnote and the row that holds the footnote marker is counted differently depending on which menu path opened the count dialog.

If you need a number that survives formatting changes, the status bar cannot give it to you. You need to count line breaks instead, and that means taking the text out of Word's layout engine.

When Word's Line Count Shifts Without Any Text Changes

A frequent frustration: you open a fifty-page report, the status bar reads 1,847 lines, you nudge one paragraph's spacing, and the same document now reports 1,851. Nothing in the body changed. Scenarios where Word's count is unstable include:

The document uses justified text and the last line of every paragraph reflows as the column width changes.
You toggle between Print Layout, Draft, and Web Layout views, each of which uses different metrics.
A table or text box sits inline with body text; Word counts its rendered rows separately from the surrounding prose.
Headers, footers, footnotes, endnotes, and text-box contents are counted under some menu paths and excluded under others, so two different dialogs can show two different totals.
Track-changes balloons are visible in one view and hidden in another, changing how Word counts the rows it has to draw.

For anything that needs to match across documents — a script submission with a "no more than X lines" rule, a court filing with a line cap, a code review that compares line-by-line output, a translation project priced per source line — the in-app number is unsafe to rely on.

How to Count Lines in Word Using a Browser Tool

Open the Word document and select the body text you want counted. Press Ctrl+A on Windows or ⌘+A on Mac to grab everything in the document.
Copy the selection to the clipboard with Ctrl+C (Windows) or ⌘+C (Mac).
Open the Line Counter in a new browser tab.
Paste the text into the editor with Ctrl+V or ⌘+V. The four statistics update immediately — there is no submit button.
Read Total lines, Non-blank lines, Blank or whitespace-only lines, and Longest line (code points) from the panel below the editor.
If you need to start over, click Clear to wipe the input and reset every statistic to zero.

The text never leaves your browser. The analysis runs locally, no account is needed, and a counter under the editor shows how much of the 1,000,000 UTF-16 code-unit input budget remains.

How to Read the Four Numbers From the Counter

The tool returns four numbers, and the relationship between them is itself a useful cross-check.

Statistic	What it counts
Total lines	Segments produced by splitting the input on LF, CRLF, and lone CR, with CRLF treated as one boundary. An entirely empty input is the only scenario that returns zero.
Non-blank lines	Lines that contain at least one non-whitespace character after Unicode whitespace has been trimmed from both ends.
Blank or whitespace-only lines	Lines that contain nothing, or only spaces and tabs that trim to empty. A line reading " a " is non-blank; a line reading " " is blank.
Longest line (code points)	The length of the longest segment, measured in Unicode code points rather than visual columns, bytes, or UTF-16 code units.

Total lines should always equal non-blank lines plus blank lines. If the three numbers do not add up, something is wrong before you even start to trust the longest-line metric.

The Line Counter's Rules in Plain English

Because line counting is ambiguous by default, the tool defines its rules explicitly. The following reference table shows how common inputs are classified.

Input	Total	Non-blank	Blank
(empty)	0	0	0
alpha	1	1	0
alpha followed by one LF	2	1	1
alpha followed by CRLF	2	1	1
One lone CRLF on its own	2	0	2
a, blank line, b (a\n\nb)	3	2	1

CRLF is always one boundary, never two, so a document saved on Windows does not inflate the total because each half got counted separately. Mixed endings — some LF, some CRLF, some lone CR — are accepted in the same input, which matters when text has moved between Unix, Windows, classic Mac, terminal, and clipboard environments.

A trailing newline always creates a final blank segment. The text "alpha" without a newline is one non-blank line; "alpha" followed by a single LF is two lines (the alpha line plus an empty trailing line). The counter follows the visible split structure and does not silently drop the final empty segment based on whether the last line contains text.

Common Scenarios Where Two Tools Disagree

When the Line Counter returns a different total than another tool, the cause is almost always one of these:

The other tool suppresses a final empty segment. Many Unix utilities, including wc -l, report one fewer line than this counter when the file ends with a newline. Both behaviors are reasonable; the rules simply differ.
The other tool counts bytes, characters, or grapheme clusters rather than code points. A supplementary-plane emoji such as 😀 occupies two UTF-16 code units but counts as one code point for longest-line purposes. A decomposed accented letter such as "e" followed by a combining acute accent counts as two code points even though it renders as a single visible glyph.
The other tool expanded tabs to a fixed column width before counting. The Line Counter does not expand tabs; each tab character is exactly one code point.
The text was normalized (NFC versus NFD) at some point in its history. The counter does not normalize Unicode, so the same visual text in two different normalizations may have different code-point counts.

For word and character totals from the same source text, use the Word Counter; it is built for those metrics and processes text the same local-only way. The Line Counter deliberately does not count words, sentences, bytes, visual columns, paragraphs, or soft-wrapped display rows — a long line that visually wraps inside the Word editor's window remains one logical line unless the text contains a real LF, CRLF, or CR separator.