Whitespace minifier

This tool identifies every run of whitespace in a text, consecutive spaces, tabs, or whitespace spanning a line break, and reduces each run to exactly one space. Leading and trailing whitespace on the whole result is trimmed as well, producing text with consistent, single spacing throughout.

Processing runs client-side, in JavaScript, entirely within your browser. There is no upload and no server round trip, and accordingly no run limit.

No configuration required.

Step 1

Paste text with irregular spacing into the input field.

Step 2

Run the minify. It executes instantly, locally.

Step 3

Read the result, now evenly spaced.

This is a distinct operation from deleting whitespace entirely, and the difference determines which tool is correct for a given task. This one reduces any run of one or more whitespace characters to exactly one space; it never removes the individual space required between two words. The output remains readable prose with normalized spacing.

For a use case requiring zero spaces, a slug, a key, or a field that rejects whitespace outright, use the text space remover instead, which deletes every space rather than collapsing runs of them.

Because a run of whitespace can include a line break alongside adjacent spaces or tabs, running this on a multi-paragraph document also merges those paragraphs onto a single line: the algorithm makes no distinction between whitespace that constitutes a paragraph break and whitespace that is simply excess spacing. Where paragraph structure must be preserved, process each paragraph individually, or use the line break remover and reinstate paragraph breaks manually afterward.

For text that is already a single block with irregular internal spacing, this behavior is exactly the intended outcome: uneven gaps become one consistent space throughout.

Text copied from a table, a PDF or certain rich-text editors frequently carries the source's column alignment forward as literal repeated spaces, since the original layout relied on visual spacing rather than structural formatting. Text assembled programmatically from multiple fragments, a template with unfilled placeholders, a string built by concatenation, commonly develops doubled spaces at the seams, particularly where an empty variable leaves a gap where a word should have been.

Manual editing over time introduces its own drift: an extra space left behind after a deletion, a tab substituted for spaces by one contributor among several.

A reader rarely notices an extra space inside a sentence; software reliably does. A string comparison expecting single-spaced text fails against a double-spaced variant of otherwise identical content. A search index can register 'word word' as distinct from 'word word'. Minified HTML, CSS and JSON depend on collapsed whitespace to achieve a genuinely smaller file size, not merely a visually tidier one.

In data exports, inconsistent spacing between field values is a frequent, quiet cause of a lookup or join failing to match rows that should be identical.

Editorial teams normalize text pulled from a table or a PDF, where the source's column layout left runs of spaces embedded mid-sentence. Engineers normalize a config value, a log line or a data field where consistent single spacing is required for a downstream comparison, since a value that only differs by spacing can otherwise slip past a validation check meant to catch duplicates.

Anyone preparing text for a system that would treat a double space as materially different from a single one runs this as a normalization pass before that text proceeds further.