Line Ending Converter — CRLF ↔ LF

CRLF vs LF

Text files end each line with an invisible character. Unix, Linux and macOS use LF (\n, line feed). Windows uses CRLF (\r\n, carriage return + line feed). Classic Mac OS used a lone CR. Most editors handle both, but many tools don’t: a shell script with CRLF fails with /bin/bash^M: bad interpreter, Docker entrypoints break, and diffs show every line as changed.

Fixing it for good in Git

Add a .gitattributes file with * text=auto eol=lf (and *.bat text eol=crlf for Windows batch files) so Git normalizes endings on commit. Setting git config --global core.autocrlf input on macOS/Linux and true on Windows also helps. After adding .gitattributes, run git add --renormalize . once.

Mixed line endings

Files edited on different systems often contain both kinds. The counters show exactly how many of each the text contains, and converting makes them uniform.

Private by design

Text and files are converted in your browser and never uploaded.

También se busca como: crlf to lf, lf to crlf, convert line endings, windows line endings, dos to unix, unix to dos, mixed line endings.

Herramientas que combinan con: Line Ending Converter

• Windows Path Converter — Paste a path in any format — C:\Users\me\project, /mnt/c/Users/me/project, /c/Users/me — and get it in every other form, ready to copy: WSL, Git Bash, Cygwin, file URL, UNC and escaped for code.
• Remove Line Breaks — Paste text with broken lines — from a PDF, an email or a terminal — and join it back into clean paragraphs.
• .editorconfig Generator — Make every editor on your team use the same indentation, line endings and charset.
• Generador de .gitignore — Marca todo lo que sepas —Node, Python, React, Next.js, Docker, macOS, VS Code y 40 más— y obtén un archivo limpio y sin duplicados .gitignore con secciones comentadas, listo para descargar.