Line Endings & BOM Converter
File
Counts CRLF, lone CR, and lone LF separately before normalising, so you can spot files that mix conventions (a common cause of dirty git diffs or Bash scripts that fail on Windows). Output bytes are reported with the BOM included, so you know exactly what will land on disk. All processing is local in your browser.
- LF count1
- CRLF count1
- Lone CR count0
- Total lines3
- Output bytes (UTF-8)28
- Had BOMNo
Mixed-ending files usually mean the source was edited across platforms — normalising fixes most "why does my diff explode" headaches.
How to use
- Paste text or drag a file's contents into the input.
- Pick the target line ending (LF for Unix/macOS, CRLF for Windows, CR for legacy Mac).
- Choose the BOM policy and copy the output.
Frequently asked questions
- When should I keep the BOM?
- Some legacy Windows tools and a few Excel CSV imports rely on it. For everything else (especially shell scripts, JSON, and source code in modern build chains), strip it.
- What's a mixed-ending file?
- Any file that contains more than one of LF/CRLF/CR. Common when text gets edited across platforms or when generators concatenate fragments from different sources. Normalising to a single style makes git diffs and downstream parsers behave.
Related tools
Image → PDF Converter
Combine multiple JPG / PNG images into a single PDF with adjustable page size, orientation, and fit.
ZIP Inspector
Drop a ZIP and see every file inside — sizes, contents, and per-file download — without unpacking it locally.
File Splitter
Split a large file into smaller chunks to bypass attachment or upload size limits.
Text Encoding Converter
Open text files in legacy encodings (EUC-KR, Shift_JIS, Windows-1252…) as readable UTF-8.
File Hash (Checksum)
Compute SHA-1, SHA-256, and SHA-512 checksums of any file.
CSV ↔ JSON Converter
Convert CSV to JSON and JSON back to CSV, with a delimiter option.