Line Ending & Encoding Fixer
Fix text files that misbehave across Windows, macOS and Linux. Convert line endings between CRLF, LF and CR, add or remove a byte-order mark, and clean up the encoding so the file is consistent.
Read the guide: How to Fix Line Endings (CRLF / LF)Drop a text file here, or click to browse
You can also paste straight into the editor below. Everything stays in your browser.
The corrected text will appear here.
How it works
- 1
Add text or a file
Paste text or drop a file whose line endings need fixing.
- 2
Pick the target
Choose LF, CRLF or CR, and decide whether a BOM should be added or removed.
- 3
Copy or download
Get the corrected text back, ready to commit or hand off.
Instant & 100% private — nothing is uploaded
Everything runs locally in your browser. Your files are processed on your own device and are never sent to a server, so there are no upload waits, no size limits from us, and nothing is ever stored or logged.
Frequently asked questions
- When do I need to change line endings?
- Windows uses CRLF and Unix-based systems use LF. A file made on one and opened on the other can show garbled line breaks or trip up scripts and version control. Converting to a single style fixes that.
- What is a BOM and should I remove it?
- A byte-order mark is an invisible marker at the start of a text file. Some tools add it, others choke on it. If a file shows odd characters at the very beginning, removing the BOM usually fixes it.
- Does it change the actual content?
- No. Only the line-ending characters and the optional BOM change. Your words, code and data stay exactly the same.
- Is my file sent to a server?
- No. Everything runs locally in your browser. Your file is read and processed on your own device, nothing is uploaded, and nothing is logged or stored.
More tools
More from the Hivly network
Free sister tools on our other sites.