Free Normalize Line Endings Tool

🟢 Runs Locally — verified: your files are processed in this browser. No uploads.

Convert Windows CRLF and old Mac CR line endings to clean Unix LF — fix diffs, git warnings and parser errors.

Word Counter

Runs entirely in your browser — paste text and watch the results update instantly. Nothing is uploaded.

100% Client-Side — Your text stays in your browser. Nothing is uploaded.

How to use this tool

  1. 1

    Paste mixed-ending text

    Config files, CSV exports or logs edited across Windows, Mac and Linux.

  2. 2

    Endings become LF

    CRLF (\r\n) and legacy CR (\r) all normalize to LF (\n) invisibly but decisively.

  3. 3

    Download or copy

    Save the normalized file and commit without diff noise.

Key features

EndingBehavior
Windows CRLF (\r\n)Converted to LF
Classic Mac CR (\r)Converted to LF
Unix LF (\n)Already correct — untouched
Mixed in one fileAll unified to LF consistently

Privacy: your text never leaves your browser

Every Toolflect Text Tool is 100% client-side. The moment you type or paste text, it is analyzed by JavaScript running inside this browser tab. Your text is never sent to our servers, never stored in a database, and never shared with any third party or AI service. Visit counting (see the note at the foot of this page) is separate from your text and never receives it.

  • No uploads, no accounts, no sign-up
  • Your text is processed locally in your browser and never stored.
  • Works offline once the page has loaded
  • Close the tab and your text is gone from memory

You can even verify it yourself: open your browser's developer tools, switch to the Network tab, and type into the tool — no request ever carries your text. You will also see the Google Analytics request that counts the visit; it carries a page view and never anything you typed, and no cookie or identifier is stored until you accept analytics.

Frequently asked questions

Why do mixed line endings cause problems?
Git shows phantom whole-file diffs, strict parsers (CSV, YAML, some JSON consumers) choke on stray \r characters, and regexes with $ anchors behave unexpectedly.
Can I convert TO CRLF instead?
This page normalizes to LF (the web/Unix standard). A bidirectional endings tool can be added later if needed — ask!
Will invisible \r show in my copy?
No — they are stripped before you copy or download.
Does it change content otherwise?
Not one character besides the endings themselves.

More free ToolFlect text tools

All free ToolFlect tools

Your text stays in your browser and is not uploaded. We use Google Analytics to count visits; until you choose it runs without cookies and stores nothing on your device. · Privacy Policy