The hidden friction of line breaks and invisible Unicode
Line endings are among the oldest architectural fault lines in computing. In the 1970s, Unix chose the single Line Feed character (\n, ASCII 0x0A) as its universal newline delimiter. Microsoft MS-DOS and Windows adopted the teleprinter convention of Carriage Return followed by Line Feed (\r\n, ASCII 0x0D 0x0A). Classic Apple Macintosh systems initially relied on a bare Carriage Return (\r).
Today, cross-platform developers and writers frequently collaborate across macOS, Windows, and Linux. When files are opened, edited, and committed without uniform line ending standards, version control systems experience churn. A single save on a Windows workstation can alter the newline byte on every line of a 10,000-line Markdown vault, resulting in massive phantom Git diffs that obscure genuine content revisions.
Beyond line breaks, copying text from web pages, PDFs, and chat clients silently injects invisible Unicode artifacts. The most notorious is the UTF-8 Byte Order Mark (\uFEFF), which causes YAML frontmatter parsers in Obsidian and static site generators to crash because the opening frontmatter delimiter (---) is preceded by hidden bytes.
Sanitization capabilities and preservation rules
The Line-Ending Normalizer provides deterministic, configurable cleanup designed specifically for technical writers and developers:
- Uniform Line Ending Normalization: Converts mixed documents containing both LF and CRLF line breaks into a single consistent format: Unix LF (standard for modern macOS, Linux, and Git), Windows CRLF, or classic CR.
- UTF-8 Byte Order Mark (BOM) Stripping: Removes leading
\uFEFFbytes from the document start, ensuring compatibility with strict frontmatter parsers in Astro, Jekyll, Hugo, and Obsidian. - Zero-Width Space Purging: Detects and removes zero-width spaces (
\u200B), zero-width non-joiners (\u200C), zero-width joiners (\u200D), and word joiners (\u2060) that cause compiler errors and broken links. - Non-Breaking Space Conversion: Converts non-breaking spaces (
\u00A0) introduced by word processors into standard ASCII space characters (0x20). - Markdown Hard-Break Awareness: Trims unnecessary trailing whitespace on lines while intelligently preserving intentional two-space line breaks (
) required by CommonMark for hard line breaks.
Private browser-local text hygiene
Source code, engineering specifications, and confidential notes should never be transmitted over the internet simply to standardize line breaks. This utility executes 100% inside your local browser tab using native JavaScript string processing APIs. No text, file contents, or metadata ever leave your computer.
For companion local utilities, inspect note differences with our Markdown diff viewer, validate frontmatter with the YAML frontmatter validator, convert callouts with the Callout portability converter, or audit your entire knowledge base with the vault health inspector. Browse the entire suite in our browser tools catalog.