logohsb.horse

Line Ending Accident Forensics

Locate mixed LF, CRLF, and CR endings with byte offsets, inspect final newlines and trailing spaces, and create LF and CRLF corrections.

When Git diffs or CSV imports break only on some systems, count each line-ending type and locate the mixed positions. Files stay inside your browser.

Analysis runs only in this browser. Selected files and pasted text are never uploaded.

Local text file

Supports UTF-8, ASCII, BOM-marked UTF-16LE/BE, up to 10 MiB.

Or paste text

Your browser or OS may normalize pasted CRLF to LF. Select a file when exact byte positions matter.

Diagnostic result

Select a file or enter text to begin.

Line-ending positions

    How to use

    1. 1

      Load the source

      Select a file for exact diagnosis or paste text for a quick check.

    2. 2

      Review positions

      Compare ending types, line numbers, UTF-16 offsets, and file byte offsets.

    3. 3

      Save the required form

      Copy or download the LF or CRLF version required by the destination.

    Scope of the result

    Non-UTF-8 encodings without a BOM, such as Shift_JIS, and editor-specific save transformations are outside the scope. The original file is never overwritten.

    Frequently asked questions

    Why did pasted CRLF become zero?
    Browsers and operating systems may normalize pasted line breaks to LF before the page receives them. Select the original file to inspect bytes.
    Can the corrected file stay UTF-16?
    The initial version outputs corrections as UTF-8. Diagnosis still preserves byte offsets from BOM-marked UTF-16LE/BE input.
    Is the file uploaded?
    No. The File API reads it only inside your browser.