CRLF to LF Line Ending Converter
Related tools
Trim Whitespace Normalizer
Trim leading/trailing whitespace and normalize space sequences.
WhitespaceTrim
Remove Blank Lines
Strip empty lines and whitespace-only lines from text.
Blank linesEmpty lines
Line Counter
Count total lines, non-empty lines, and blank lines in text.
Line countLines
Featured
Text Comparison (Diff)
Compare two blocks of text and display additions, deletions, and differences.
DiffCompare text
Text Formatter & Wrapper
Wrap text at specified column width, add line prefixes/suffixes, and indent.
Word wrapText wrap
Files that move between Windows and Unix-based systems often carry mismatched line endings — Windows uses CRLF while macOS and Linux use LF — and this crlf lf converter fixes the mismatch instantly, right in your browser. It's a common need for developers dealing with Git line-ending warnings, teams sharing scripts across operating systems, and anyone importing text files that display incorrectly on the wrong platform. Paste your text, choose the direction you need (CRLF to LF or LF to CRLF), and get correctly formatted output immediately. Since the conversion happens client-side, code containing credentials or proprietary logic never leaves your machine. There's no signup and no size limit. Paste your text below to normalize its line endings now.
Features
- Convert CRLF (Windows) line endings to LF (Unix)
- Convert LF line endings back to CRLF
- Detects and reports the current line ending style
- Handles mixed line endings within the same file
- Instant conversion with live preview
- One-click copy of the converted text
- No file size limit since it runs client-side
- Useful for fixing Git line-ending diff noise
Why use this crlf to lf converter?
- Converts line endings instantly with no upload wait
- Keeps source code and scripts private by processing locally
- Accurately detects and fixes mixed or inconsistent line endings
- Simple two-way toggle with no configuration needed
- Free to use with no signup or file size caps
Frequently asked questions
What's the difference between CRLF and LF line endings?
CRLF (carriage return + line feed) is the Windows convention for ending a line, while LF (line feed only) is used by Unix, Linux, and macOS — mismatched endings can cause files to display incorrectly or trigger diff noise.
Why does Git warn me about line endings?
Git often warns 'LF will be replaced by CRLF' or vice versa when a repository's configured line-ending style doesn't match the file you're committing, which this tool can help you fix before committing.
Can this tool detect which line ending style my text currently uses?
Yes, it analyzes the pasted text and reports whether it detects CRLF, LF, or a mix of both before you convert.
Will converting line endings change the visible content of my file?
No, only the invisible line-ending characters change; the visible text content stays exactly the same.
Why do text files sometimes show as one long line on Unix systems?
That typically happens when a file uses classic Mac (CR-only) or Windows (CRLF) endings and is opened in a Unix tool that only recognizes LF as a line break.
Is there a size limit for converting line endings here?
No, since the tool runs entirely in your browser, it can handle large files without a server-imposed limit.