Line Ending Converter - CRLF to LF and CR Conversion

Convert between Windows (CRLF), Unix/Linux (LF), and Mac (CR) line endings. Fix git warnings and cross-platform script issues instantly in your browser.

Drop text file here or click to browse

Supports .txt, .sh, .bat, .csv, .log, .md, .js, .py, .java, .cpp, etc.

Input Text

Output Text

Conversion Options

Target Line Ending Format:

LF \n - Unix/Linux/macOS

CRLF \r\n - Windows

CR \r - Classic Mac OS

Line Ending Reference

Format	Escape Sequence	Hex Bytes	Used By	Common Issues
LF	`\n`	`0A`	Unix, Linux, macOS, git standard	None - modern standard
CRLF	`\r\n`	`0D 0A`	Windows, DOS, HTTP headers	Shows ^M in Unix editors, breaks scripts
CR	`\r`	`0D`	Classic Mac OS (pre-OS X)	Rare today, legacy compatibility only

Best Practice: Use LF (Unix) for all source code, scripts, and version-controlled files. Git can auto-convert on checkout/commit with core.autocrlf settings, but consistent LF is simpler.

Processing...

ICS to CSV - Export Calendar Events to S…

vCard to JSON Converter - Contacts to JS…

vCard to CSV Converter - Contacts to Spr…

CSV to SQL INSERT Generator - Create Dat…

BibTeX to CSL-JSON Converter - Citation …

View all Data converters →

Frequently Asked Questions

Line endings are invisible characters that mark the end of a line in text files. Different operating systems use different sequences: Windows uses CRLF (\r\n), Unix/Linux/macOS use LF (\n), and old Mac OS used CR (\r).

CRLF (\r\n) is carriage return + line feed used by Windows. LF (\n) is line feed only, used by Unix/Linux/macOS. CR (\r) is carriage return only, used by old Mac OS before OS X. Most modern systems use LF.

Inconsistent line endings cause problems: git may flag every line as changed, shell scripts fail to execute, files appear corrupted with ^M characters, and some tools may not parse files correctly. Consistent line endings ensure cross-platform compatibility.

This tool auto-detects your file's line ending format. In text editors: vim shows [dos] for CRLF, [mac] for CR. In command line: 'file filename' on Unix shows line terminators. Look for ^M characters for CRLF in some editors.

The ^M symbol represents carriage return (\r). When CRLF files are opened in Unix tools that expect LF, the \r appears as ^M. Convert to LF (Unix) format to remove them.

Git shows 'LF will be replaced by CRLF' warnings when your repository has mixed line endings or when core.autocrlf settings conflict with file content. Standardizing on LF (Unix) for source code is the modern convention.

Use LF (Unix/Linux) for source code, scripts, and version-controlled files. It's the universal standard for git repositories and cross-platform development. Use CRLF (Windows) only for Windows-specific batch files or when required by Windows tools.

Not true corruption, but mixed line endings make files appear broken. Text may run together, scripts may fail to execute, and version control shows false changes. The file data is intact but formatting is inconsistent.

Shell scripts with Windows CRLF line endings will fail with errors like 'bad interpreter' or '\r: command not found' when executed on Unix/Linux. Always use LF line endings for shell scripts, even when editing on Windows.

Yes. The tool detects and reports mixed line endings, then converts all lines to your chosen format. It counts each line ending type in the original file and normalizes them consistently.

Conversion Options

Line Ending Reference

Related Tools