Measure every line, find the ones over your limit, spot trailing whitespace, and see whether a file indents with tabs or spaces — or both.
Waiting for text
Every line's length, the ones over your limit, trailing whitespace, and how the file indents.
The report appears here
Every line's length, the ones over your limit, trailing whitespace, and how the file indents.
Line Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Three questions a linter answers for a project it has been configured for, and nobody answers for a file you have just been handed. Which line is over the limit, which lines have trailing whitespace, and does this file indent with tabs or with spaces.
Each line gets two lengths, and they differ for a reason. Length in UTF-16 code units is what a linter's maximum-length rule counts and what an editor's column marker measures. Length in characters a reader sees is what a person means by this line is too long. For ASCII the two agree; for a line containing an emoji or an accented name they do not, and the table shows both rather than picking one and being wrong half the time.
Trailing whitespace is invisible in most editors and is the usual reason a diff reports a line as changed when nothing readable about it changed. It is also the thing a pre-commit hook rejects after you have already written the commit message. Counted here, with the lines listed.
Mixed indentation is reported rather than judged. A file using both tabs and spaces is sometimes a Makefile doing exactly what it must, sometimes a continuation line aligned on purpose, and sometimes two editors with different settings disagreeing. The tool states which it found and leaves the verdict to someone who knows the file.
There is also a length distribution in buckets of ten, a median alongside the average, and the longest and shortest lines named. The median is the more useful of the two for a file with one enormous minified line in it, which is exactly the file where the average tells you nothing. Nothing is uploaded.
UTF-16 code units, which is what a linter's maximum-length rule and an editor's column marker count. Where a line contains something outside ASCII the table also shows the number of characters a reader actually sees.
Because it often is not. A Makefile requires tabs, continuation lines are frequently aligned with spaces deliberately, and the right answer depends on the project. The tool reports what it found.
It is invisible in most editors, it makes a diff show a line as changed when nothing readable changed, and it is what a pre-commit hook rejects after you have written the commit message.
Because one enormous line — a minified bundle, a long data literal — drags the average somewhere unrepresentative. The median tells you what a typical line in the file looks like.
Yes, and blank lines are counted separately so you can see how much of the file they are. They are excluded from the shortest-line figure, where a blank line would be the trivial answer every time.
Comfortably into the tens of thousands of lines. The per-line table is capped so the page stays responsive, and the statistics always cover the whole file rather than the visible part.