CR, LF and CRLF line endings explained
What carriage return and line feed really are, why Windows, Mac and Unix disagree, and how to normalize the breaks in any text.
What a line break actually is
On screen a new line looks like empty space, but in the file it is one or two invisible control characters. The two that matter are carriage return (CR, code point 13) and line feed (LF, code point 10). Editors render these as the start of a new line, which is why you cannot see them yet they change how text flows. When you paste text that was wrapped to fit a narrow column, those hidden characters travel with it and split your sentences apart.
Carriage return versus line feed
The names come from the typewriter era. Carriage return moved the paper carriage back to the left margin, and line feed rolled the paper up one line. Computers kept both ideas as separate characters. LF alone means move down a line, CR alone means return to the start, and the pair CRLF means do both. Understanding the split explains why one stray character can leave your text looking misaligned instead of neatly stacked.
Why Windows, Mac and Unix differ
Unix and modern macOS end a line with a single LF. Windows ends a line with the CRLF pair, a habit inherited from DOS and older printers. Classic Mac systems before OS X used a lone CR. Because these conventions coexist, a document created on one platform can carry line endings another platform did not expect, which is a common source of ragged pastes and odd blank lines.
How this tool normalizes them
Rather than guess which convention produced your text, the remover matches every CRLF, CR and LF and replaces each one with the separator you choose. Collapsing repeated spaces then tidies the seams where lines were joined, and trimming clears any break that sat at the very edges. The result is a single consistent line regardless of where the original text came from.