Lines are how code, logs, lists and lyrics are measured. Paste text here and get total lines, lines with text, empty lines, words, characters, and the longest line located by its number.
Your files are processed in your browser, on your own device. Nothing is uploaded to a server.
Lines are the native unit of more work than words are: code files, log files, lists, lyrics, subtitles, commits. This line counter counts your text’s total lines, the lines carrying text, the empty ones, the words and characters, and singles out the longest line with its number, the detail that saves the actual debugging time. Counts update as you type, in your browser, and the counting rule is stated on the tool rather than left to folklore.
The rule here is the one most editors use: text is split at every line break, and a trailing line break starts one final empty line – so a file ending in a newline reports one more line than the eye counts, with that last line empty. Different tools choose differently, which is why two counters can disagree by one while both are right under their own rule, and why this page prints its rule instead of hiding it. A line with text means at least one character rides on it. A line of pure spaces counts as carrying characters, and if your question was really about blank-looking lines, compare the empty count here against what an editor shows and the difference will be those space-only lines, named honestly rather than fudged. Companions in the family: the Word Counter for the prose view of the same text, and the shelf at Text Tools.
Code review opens with them: file length budgets, generated files that ballooned, a function whose file doubled overnight. Log analysis lives on them: lines per hour is an incident timeline wearing a simple disguise. Lists and data prep count on them before imports, because a CSV whose line count mismatches its record count is a file with a secret. Subtitlers and lyricists budget by line. And the longest-line number is the quiet hero: lint rules, print margins and terminal widths all break on the longest line, and knowing it is line 4,096 of 5,000 turns a search into a visit.
Words measure prose. Lines measure structure. A poem, a config file and a stack trace can share a word count and share nothing else, while their line counts describe their shape at a glance. Professional writers of code and configuration think in lines the way essayists think in words, and a tool that reports only words leaves that whole world unmeasured. This counter reports both because real text is usually both at once: words for the content, lines for the container.
Because most text files end with a line break, and under the standard counting rule that break starts a final empty line. The count is honest about it: that last line is reported in the empty-lines figure, so you can see exactly where the extra line lives. Editors differ on whether they display it. The difference of one between two tools is a rule difference, not an error in either.
A line with no characters on it at all. A line holding only spaces is not empty by this rule – it carries characters, and they are counted in the character totals. That distinction is usually the answer when this count disagrees with an editor’s blank-line figure, and it matters in code, where space-only lines carry trailing-whitespace sins of their own.
Yes: total words, characters including spaces, characters excluding spaces, and the average words per line that carries text. Lines are the headline because that is the question this page answers, but text rarely needs only one measurement, and flipping between tools to collect the rest wastes the minute this page exists to save. The dedicated Word Counter goes deeper on the prose statistics.
It locates the line most likely to break things: style rules cap line length, terminals wrap, printed code runs off the page, and diffs become unreadable. Getting its number as well as its length means you can jump straight to it. A file whose longest line is ten times its average is telling you something structural, often that generated or pasted content landed in it.
Paste-based counting handles book-length text comfortably in the browser. For truly enormous logs, the honest tool is a command line – wc -l exists for this – because loading tens of megabytes into a web page to count breaks is using a page where a shell belongs. Within pasteable size, the counts here are instant and live as you edit.
No. Counting happens in your browser on every keystroke, and nothing is sent or stored. Paste code, logs and drafts freely. A refresh wipes the box, which is why the download button exists for any count you need to keep.
Same rules as this one: free, in your browser, with nothing uploaded.
Words, characters, sentences and reading time, live.
UPPER, lower, Title and sentence case in one click.
Characters with and without spaces, counted as you type.
Count sentences and check how long they run.
Count paragraphs, lines and words in one paste.
Count letters alone, with spaces and lines shown too.
Headlines capitalized the way style guides ask for.
How many minutes your text takes to read or say aloud.