Detect whether your text uses CRLF, LF or CR line breaks, then convert it to Windows, Unix/macOS or classic Mac format and download the exact bytes.
Reads pasted content before the browser can normalize it, so CRLF, LF and CR are counted precisely.
Convert to CRLF for Windows, LF for Unix and macOS, or CR for legacy classic Mac files.
The downloaded .txt file contains the exact line-ending bytes you chose, not a browser-normalized version.
Every text line has to end somehow, but the exact bytes used to mark that ending were never fully standardized across computing history. Windows inherited the CRLF convention, a carriage return followed by a line feed, from early teletype and DOS systems. Unix and, later, macOS settled on a single LF character, which is simpler and takes up less space. Classic Mac OS, before OS X, used a lone CR instead, a quirk that still occasionally shows up in very old files. These differences are mostly invisible until they cause a problem: a script with the wrong line endings can fail to run, a git diff can show every single line as changed because the endings flipped, and some parsers or command-line tools choke on an unexpected CR character. Converting a file's line endings to match its destination environment, whether that is a Windows batch script, a Unix shell script, or a config file consumed by a specific tool, resolves these issues without altering the actual text content. This tool detects the current format, shows exact counts, and lets you convert to any of the three standard formats before downloading the byte-accurate result.
Carriage return + line feed. The default on Windows and used by many Windows-authored files.
A single line feed. The standard on Linux, macOS, and most modern command-line tools.
A lone carriage return. Used historically by classic Mac OS before OS X.
CRLF (carriage return plus line feed) is the Windows line ending, LF (line feed alone) is used by Unix, Linux and macOS, and CR (carriage return alone) was used by classic Mac OS before OS X. They all mark the end of a line but use different byte sequences.
It reads the raw pasted text before your browser can normalize it, counts CRLF pairs, lone LF characters and lone CR characters, and reports which style is used or flags the file as mixed.
Some tools, version control diffs, and cross-platform scripts are sensitive to line-ending style. Converting a file to the format your target system expects avoids unexpected diffs or parsing errors.
Yes. The download is built directly from the converted text as raw bytes, so it is not re-normalized by the browser and matches the CRLF, LF or CR format you selected.
Yes. Conversion happens entirely in your browser with no account or upload required.