Skip to content

Choose your path

Built around the job you need to finish

Remove or collapse a deliberately selected whitespace set, optionally preserve all line endings and review exact changed runs before using complete raw output.

Data preparation analyst

Remove actual separators without silently trimming only edges.

Compare all Unicode whitespace removal with horizontal-only scope on mixed tabs, NBSP and CRLF.

Can explain which characters disappeared and keeps record boundaries when selected.

JavaScript developer

Distinguish ECMAScript whitespace from Unicode White_Space.

Compare BOM, NEL and zero-width space across Unicode, ECMAScript and ASCII modes.

BOM/NEL differences are explicit; format characters are not guessed away.

Mobile text-file editor

Safely use an empty or long transformed result.

Import a BOM/CRLF file, inspect changed runs, save TXT/JSON, apply output and undo.

Empty output remains a valid zero-byte file and source replacement remains reversible.

Authoritative checks for this tool

Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.

Was this tool helpful?

Reference & details

How it works

Explicit character set

The selected set determines matching; zero-width joiners and bidi controls are not silently stripped.

Traceable changes

Each changed run has original zero-based UTF-16 ranges and escaped before/after values. Unchanged single-space runs are not listed as changes.

Separate source and output

The raw text and complete JSON have separate exports. Using output as source is an explicit action with Undo; no automatic Project or device save.

Updated: August 2026

Example Scenarios

Remove actual separators without silently trimming only edges. Compare all Unicode whitespace removal with horizontal-only scope on mixed tabs, NBSP and CRLF.

Distinguish ECMAScript whitespace from Unicode White_Space. Compare BOM, NEL and zero-width space across Unicode, ECMAScript and ASCII modes.

Safely use an empty or long transformed result. Import a BOM/CRLF file, inspect changed runs, save TXT/JSON, apply output and undo.

Common Mistakes to Avoid

Joining meaningful tokens

Removing separators can change words, code or data. This is not a syntax-aware parser.

Assuming all invisible characters are whitespace

BOM, zero-width and direction controls have different properties; inspect the declared policy.

FAQ

All Unicode White_Space characters, including internal spaces and line endings. It does not remove BOM or zero-width space.

Unicode White_Space includes NEL but not BOM. ECMAScript whitespace includes BOM but not NEL. ASCII selects TAB, LF, VT, FF, CR and SPACE.

Yes. Preserve-line-endings scope keeps CRLF, CR, LF, VT, FF, NEL, LS and PS exactly.

No. Each matched run becomes one ASCII space, including edge runs. Remove deletes matched runs.

Yes. All-whitespace input may produce an empty result. Its .txt download is a valid zero-byte file; the JSON still documents changes.

About Whitespace Remover

Remove or collapse selected Unicode, ECMAScript or ASCII whitespace, preserve line endings when needed and export exact text plus a change report.