Line Ending Checker

Line endings are invisible until they are not. A .env edited once on Windows and once on Linux can end up with a mix of CRLF and LF, and while most dotenv libraries cope, the diff noise and the odd \r clinging to a value become real problems in scripts, containers and CI.

The Line Ending Checker counts each flavour — CRLF, LF and legacy CR — breaks the file down line by line, and tells you in one sentence whether the file is consistent or mixed. It also catches values with a stray carriage return hanging off the end.

Everything is computed locally; the file never leaves the page.

• Three-way count: CRLF, LF, CR broken down.
• Verdict line: consistent vs mixed, with total lines.
• Per-line breakdown: which lines use which ending.
• Trailing CR check: stuck to values is flagged.
• Byte-level honesty: counts are shown exactly.
• Copy or download: export the report.
• Instant: re-scans on input.
• Private: 100% in-browser.

1. Paste your .env into the input, or load the sample (it mixes styles on purpose).
2. The counts and verdict update instantly on the right.
3. Read the breakdown to find inconsistent lines.
4. Normalize the file with an editor or a converter.

Example 1 — Diff explosion. A PR touching .env shows every line as changed because someone's editor rewrote line endings. The checker proves the endings were already mixed.

Example 2 — Shell trap. A deploy script reads a value and hits a trailing on real servers. The checker pinpoints which line has the stray carriage return.

Example 3 — Container leak. docker-compose inherits the host file, and a CRLF line feeds a secret with a hidden \r into a container entrypoint.

Example 4 — Heritage files. A legacy .env carries CR-only endings from an old Mac editor; the checker names the exact lines.

Example 5 — Team policy. The team wants LF everywhere; the checker becomes the quick gate before commit.

• Mixed endings exposed: no more invisible drift.
• Stray CR caught: protects shell and containers.
• Exact counts: know how bad, precisely.
• Editor hand-off: report guides the fix.
• Private: file stays in the browser.
• Free: unlimited use.