Is the line break normalizer free?
Yes. This line break normalizer is completely free to use with no signup or account required.
Does it upload my text?
No. Normalization runs entirely in your browser on your own device, so your text is never uploaded to a server and stays private.
Does it change the text itself?
No. It only normalizes the line-ending style. The words and characters of each line stay exactly the same.
Can I choose between LF and CRLF?
Yes. You can convert your text to either LF (Unix-style) or CRLF (Windows-style) output.
Why would I need to normalize line endings?
Mixed line endings cause broken formatting, noisy diffs, and script errors when text moves between Windows and Unix systems. Normalizing keeps everything consistent.
What is the actual difference between LF and CRLF?
LF is a single character, U+000A. CRLF is two characters, a carriage return followed by a line feed, and it is what Windows text files historically use. A file with CRLF endings read by a tool that expects LF gets a stray carriage return at the end of every line, which is why a value looks correct but never matches a comparison.
Which mode should I choose?
LF unless something specifically requires otherwise. It is what git stores, what Unix tools expect, and what almost every modern editor defaults to. Choose CRLF when the destination is an old Windows application, a Notepad-opened file, or an import format whose specification demands it, such as some strict CSV consumers.
Does normalizing change the text itself?
No. Only the line terminators are rewritten. Every character on every line stays exactly where it was, including trailing spaces, indentation and blank lines. That is what makes this safe to run on data you cannot afford to alter.
How do I tell what my text currently uses?
You usually cannot see it, which is the problem. The symptoms are more reliable than the appearance: a diff that marks every line as changed, a trailing character that shows up as ^M in a terminal, or a value that never matches even though it looks identical. If you are seeing those, normalize and try again.
Will this fix a CSV that imports with an extra blank column or row?
Sometimes. A stray carriage return at the end of each line can be read as part of the last field, which produces exactly that symptom. Normalizing to LF removes it. If the problem persists, the cause is elsewhere, usually a quoted field containing a delimiter.
Is the text uploaded?
No. The normalization is a regular expression replacement in the page, so nothing is sent anywhere.