Whitespace Cleaner

Whitespace cleaner: the six cleanup actions and where they apply

What each of the six buttons does

The newline trap: an invisible \r silently corrupts data

Line endings are not all the same, and that is a common root of cross-platform failures:

The most typical failure looks like this: two lines appear completely identical, yet an invisible \r is attached. The symptoms include:

• A whole-file diff comes up red, though the naked eye sees no difference.
• A shell script reports command not found or bad interpreter — the \r is treated as part of the interpreter path.
• The last CSV column gains an invisible character, and length validation fails on import.
• Concatenating a \r-carrying value into a URL or JSON produces an illegal-character error.
• A $ anchor in a regex fails to match (because the \r sits between the line end and the $).

So "CRLF to LF" is not merely a formatting preference; it is the first step when debugging "identical but somehow wrong" problems.

Tab-to-space is not a simple delete

"Remove tabs" only removes the tab character; it does not insert equal-width spaces. So \tif (x) becomes if (x) — the indentation level vanishes rather than turning into four spaces.

That is usually not what you want for code. To truly "tab to 4 spaces", use a replacement action: in the find-and-replace tool, replace \t (regex mode) with four spaces. A tab also matches directly as \t in regex, so the swap is straightforward.

The reverse request is also common: convert space indentation to tabs (to shrink file size or unify a team convention). That is finding (four spaces) and replacing with \t; handle it from the deepest indentation level outward, or it goes wrong. For that kind of formatting, an editor or a tool like Prettier is more reliable.

Collapse spaces does not touch newlines

"Collapse spaces" only processes spaces and tabs; it leaves newlines alone. So paragraph structure is preserved. If you also crush the newlines, the whole text becomes one line — that is the effect of "remove all whitespace".

When you need "compress several lines into one line while keeping a single space between words", the correct two steps are: first replace newlines with a space (in the find-and-replace tool, regex \s*\n\s* replaced by one space), then collapse the remaining runs of spaces.

A practical processing order

For cleaning text copied from outside, this order is recommended:

1. CRLF to LF. Unify line endings first, so later steps have consistent assumptions.
2. Trim ends. Strip per-line leading/trailing whitespace, clearing most formatting noise.
3. Remove tabs or replace with spaces. Decide by the target format.
4. Collapse spaces. Skip this if you need to preserve alignment.
5. Drop blank lines / dedupe. Finish with the line dedupe and sort tool.

This order keeps each step's input clean, avoiding the chain reaction where "whitespace from the previous layer breaks matching in this layer". All steps happen locally in the browser.