Skip to content

Line ending converter — LF, CRLF, or CR

Paste text and switch line endings between LF (Unix/macOS), CRLF (Windows), and CR (classic Mac) entirely in your browser — no upload.

TextText

Converts as you type — paste or drop a file.

Input(Text)
Output(Text)

Runs in your browser — nothing is uploaded to our servers.

A Windows CRLF that sneaks into a Unix shell script can break in subtle ways — shebang lines and trailing spaces look fine until CI fails. Normalizing endings before you commit saves that chase.

Pick the ending your target platform expects, convert once, and paste back. The tool does not upload the text; everything stays in the tab.

If the file is really a CSV or env sample you also need to reshape, convert endings first, then open CSV to JSON or dotenv to JSON.

How to use

  1. Paste text
  2. Pick LF, CRLF, or CR
  3. Copy the result

Why this converter

  • Supports LF, CRLF, and classic CR in one place
  • Converts instantly as you change the target
  • Never uploads your paste

Good for

  • Shell scripts
  • CSV and log cleanup
  • Config pastes across OS

Tips

  • After copying, confirm your editor will not rewrite endings on save.
  • Prefer LF in most git repos unless the project documents CRLF.

Examples

Input Output Note
A Windows .bat or .ps1 saved with CRLF Same characters, every break now LF Useful before a Linux CI job reads the file
A Unix shell script opened on Windows Normalize to CRLF if a Windows tool insists on it —

Line-ending FAQ

Does it change the words on each line?
No — only the break between lines. Characters on a line stay the same.
Can I paste binary files?
No. Use this for text only — not images, zips, or executables.
Will my editor undo it?
Many editors re-apply project line-ending settings on save. Check .gitattributes or editorconfig after you copy the result.

Related