Lines over 80 characters
0 matchesPaste text above to see lines that cross the limit.
About
Lengths scans pasted text for lines that exceed a maximum length you choose.
It answers one question: which lines do I have to cut? Useful when a manifest, a markdown
index, a config, a log format, or a README has a hard column or load budget and you need to
find the offenders without piping through awk.
The character count is the visible measure. The UTF-8 byte count is what disk, network, and most APIs actually measure. The two diverge as soon as the text includes accented letters, em dashes, smart quotes, CJK characters, or emoji.
The threshold and sort mode are encoded in the URL hash so a link preserves them. The text itself stays in your browser and is never sent anywhere.
Questions
- What is Lengths for?
- When a file has a hard length budget. README columns wider than 80, manifest index lines that overflow a load window, log records over a logger's truncation point, code lines blowing past a linter rule. Paste it, set the threshold, see which lines need a cut.
- Why does the byte count differ from the character count?
- UTF-8 encodes most ASCII as one byte per character but multibyte for accented letters, em dashes, emoji, and so on. The character count is what you read; the byte count is what storage and transport limits care about.
- Does the line count include a trailing newline?
- If the text ends with a newline, the last empty line after it is not counted. If you want to count the trailing newline as a line, append a single non-newline character.
- How big a paste does it handle?
- It works on files up to a few megabytes in a normal browser. Past that you may see the textarea slow down on input but the analysis itself stays fast.
- Does it track me or use cookies?
- No. There are no ads, no analytics, no third-party scripts. Your text never leaves the page; the threshold and sort are stored in the URL hash so a link preserves them.