Why does pasted text have extra spaces?

PDFs store text as x/y coordinates, not character strings. When a PDF reader extracts text, it infers word boundaries from the distance between glyph positions — if the gap is wider than expected, it inserts two spaces instead of one. Microsoft Word and InDesign add non-breaking spaces (U+00A0) after abbreviations, between numbers and units ("10 kg"), and after certain punctuation. HTML content pasted from a browser often includes entities that arrive as U+00A0. None of these look different from a regular space on screen, but they break word counts, search indexing, and pattern matching.

What is a non-breaking space and why is it invisible?

A non-breaking space (Unicode U+00A0) is a space character that prevents a line break at that position. Word processors use it intentionally — 'New York' with a non-breaking space stays on the same line rather than splitting across two. The problem: it looks exactly like a regular space (U+0020) in any text editor or word processor. It only reveals itself when you paste into a code editor, run a regex that skips it, or notice a word count tool reading 'New York' (with NBSP) as one word instead of two. The Remove Spaces tool detects and replaces U+00A0 with regular spaces.

What regex pattern removes multiple spaces in a row?

To collapse any run of two or more regular spaces into one, use: /[ \t]+/g with a single space as the replacement. This targets horizontal whitespace only — it won't accidentally collapse your paragraph breaks. To also catch non-breaking spaces in the same pass: /[ \t\u00A0]+/gu — note the u flag, required for Unicode property matching in JavaScript. Avoid /\s+/g for this task — \s matches newlines too, which will flatten your entire document into one paragraph.

Why does the Remove Spaces tool have a separate 'Fix PDF line breaks' option?

PDF text extraction produces two distinct problems needing different fixes. 'Remove extra spaces' collapses multiple spaces into one. 'Fix PDF line breaks' addresses mid-sentence newlines — when you copy text from a two-column PDF, each line ends with a hard return, so 'the quick brown\nfox jumps over' becomes two lines instead of one sentence. The fix removes single newlines (while preserving genuine paragraph breaks — double newlines) and reattaches hyphenated line-end words like 'infor-\nmation' back into 'information'.

Does removing extra spaces change my word count?

Removing regular double spaces does not change word count — word boundaries are determined by letter sequences, not space counts. But replacing non-breaking spaces (U+00A0) with regular spaces can change word count, because a non-breaking space glued between words causes a tokenizer to read 'New York' (with NBSP) as one token. After cleanup with regular spaces, it correctly counts as two words. If you notice a jump in word count after running the space fixer, that's the tokenizer now reading your text correctly.

Can I remove spaces from a very large document without the page freezing?

Yes. All processing in the Remove Spaces tool runs in your browser's JavaScript engine — no file is uploaded anywhere. For typical documents (up to around 50,000 words), the operations complete in under 50ms. For anything a person would realistically paste — blog posts, emails, legal briefs, academic papers — it handles it instantly without UI lag.

What is the difference between 'Trim line endings' and 'Remove extra spaces'?

'Remove extra spaces' collapses multiple consecutive spaces within a line into a single space. 'Trim line endings' removes leading and trailing spaces at the start and end of each individual line. A line like ' hello world ' has both issues — trim cleans the edges to 'hello world', then the space collapsing step turns it into 'hello world'. Running both together is how you get a fully normalized line.

Published: 2026-05-08

How to Remove Extra Spaces From Text Online (Fast Fix)

Paste-and-fix: remove double spaces, non-breaking spaces, and PDF line breaks in seconds. Free browser tool, no upload required.

Text before and after removing extra spaces, showing double spaces and non-breaking spaces cleaned up

If you've ever pasted content from a PDF, a Word document, or a web page and ended up with double spaces between every word, you've hit one of text editing's most common annoyances. Those aren't display glitches — they're real characters embedded in your content, and they don't go away on their own.

Here's how to remove them fast.

The Fast Way: Use the Remove Spaces Tool

Paste your text into our Remove Spaces — runs 100% in your browser tab, your text is never transmitted to any server — select the operations you need, and copy the cleaned result. Done in seconds.

The tool covers seven specific cleanup operations:

Operation	What it fixes	Before → After
Remove extra spaces	Multiple spaces collapsed into one	`word word` → `word word`
Fix PDF line breaks	Mid-sentence hard returns removed	`quick brown\nfox` → `quick brown fox`
Remove all line breaks	Entire document flattened to one block	`line 1\nline 2` → `line 1 line 2`
Remove empty lines	Blank lines between paragraphs stripped	`para\n\n\npara` → `para\n\npara`
Trim line endings	Leading/trailing spaces per line removed	`·· hello ··` → `hello`
Remove special characters	Non-ASCII chars stripped	`résumé` → `resume`
Straighten quotes	Curly typographic quotes → ASCII straight	`"hello"` → `"hello"`

Select one or several — they stack. The preview pane shows exactly what changed before you copy anything.

Why Pasted Text Arrives With Extra Spaces

Understanding the source makes the fix less mysterious.

PDFs: Geometry, Not Text

PDFs store text as glyph coordinates, not character strings. Extraction is a reverse-engineering job:

PDF internal:  [glyph "w" at x=100] [glyph "o" at x=108] ... [glyph "w" at x=180] ...
                                                                 ↑ gap = 22px
Extractor:     "word" + "  " + "word"    ← gap > threshold → two spaces inserted

If the coordinate gap between two words is slightly wider than the extractor's threshold — common with justified text or wide kerning — it inserts two spaces. Every word pair potentially affected. It's not a bug; it's a geometry inference with no perfect answer.

Word and InDesign: Intentional NBSP

Microsoft Word and InDesign insert non-breaking spaces (U+00A0) in specific positions:

You type:    10 kg
Word stores: 10[U+00A0]kg   ← non-breaking space, prevents line-wrap between number and unit
You see:     10 kg          ← looks identical to a regular space

Legitimate typographic behavior in a word processor. Invisible contamination the moment you paste into any other context.

HTML Copy-Paste: The   Trap

Any   entity in the source HTML arrives as U+00A0 in your clipboard:

HTML source:   <td>New&nbsp;York</td>
Clipboard:     New[U+00A0]York
Text editor:   New York    ← looks fine, behaves broken

Paste a table from a website into a plain text field and you've got dozens of them.

The Five Space Characters That Cause Problems

Not all "spaces" are the same character. Here are the ones you'll actually encounter:

Character	Unicode	How it arrives	Visible difference
Regular space	U+0020	Typed normally	None
Non-breaking space	U+00A0	Word, InDesign, HTML ` `	None — invisible
Zero-width space	U+200B	CMS exports, Markdown parsers	None — truly invisible
Em space	U+2003	Design tools, some CMSs	Slightly wider
Thin space	U+2009	Typographic templates	Slightly narrower

The Remove Spaces tool targets all of these. The regex approach requires explicit Unicode code points for each one — which brings us to the manual method.

The Manual Regex Approach

If you're processing multiple documents, building a pipeline, or just prefer to understand what's happening, the Find & Replace tool handles this with regex patterns.

Collapse double spaces:

Find:    [ \t]+
Replace: (single space)
Flags:   g

Using \s+ instead would also eat your newlines — don't do that unless you want one giant paragraph. [ \t]+ targets horizontal whitespace only.

Replace non-breaking spaces:

Find:     
Replace: (regular space)
Flags:   gu

The u flag is required. Without it, is treated as a literal string, not a Unicode escape, and the pattern silently matches nothing.

Fix PDF line break artifacts:

Find:    (?<!\n)\n(?!\n)
Replace: (space)
Flags:   g

This negative lookahead/lookbehind pattern removes single newlines (the mid-sentence artifact ones) while leaving double newlines intact, so your paragraph breaks survive. More surgical than "remove all line breaks."

For a deeper look at pattern syntax, capture groups, and quantifiers, the regex find & replace guide covers the full reference.

Non-Breaking Spaces: The Invisible Problem

Worth extra attention, because U+00A0 causes downstream issues that regular double spaces don't.

Word count mismatch. A naive whitespace split (text.split(' ')) won't split on U+00A0. "New York" with NBSP stays as one token. Our Word Counter uses Intl.Segmenter — the W3C standard API for language-aware tokenization — which handles Unicode whitespace correctly. But paste your text into any platform that uses a simpler approach, and your count will be off.

Regex patterns break silently. \s in JavaScript matches tab, space, newline, carriage return — but not U+00A0 by default. A pattern like /\s+/g will skip every non-breaking space without warning. If you're writing regex to process user-pasted content, add U+00A0 explicitly: [ \t ]+.

Copy-paste contamination in document formatting. This is the same category of invisible-character problem covered in how many words per page — characters that look fine on screen but throw off character counts, line lengths, and page layout calculations.

Zero-Width Spaces: The Other Invisible Character

Zero-width spaces (U+200B) appear in text exported from CMSs like WordPress, Contentful, and Notion, and from some Markdown parsers. Genuinely invisible — no width at all.

Looks like:  wordhere
Actually is: word[U+200B]here
Code sees:   two tokens: "word" + "here"

Your editor won't highlight it. Spell check ignores it. But word tokenization and character counts see it. To strip them: Find , replace with nothing, gu flags — or run "Remove special characters" in the Remove Spaces tool, which targets all non-ASCII whitespace variants in one pass.

Before You Clean: A 30-Second Triage

Not every document needs all seven operations. A quick check first:

Search for two consecutive spaces. If you get matches → double-space contamination from PDF or old typewriting habit.
Search for in a regex-capable editor. Matches → non-breaking space contamination from Word or HTML.
Look for lines that cut off mid-sentence. Signature of PDF column extraction artifacts.
Check if paragraph spacing looks inconsistent. Multiple empty lines between paragraphs → an "empty lines" cleanup pass will normalize it.

Knowing which problem you have means running only the operations you need — and the preview pane confirms the result before you commit.

Extra spaces are one of those formatting problems that feel minor until they aren't — until your word count is wrong, your regex fails, or your client asks why the document looks different in every paragraph. Two minutes of cleanup at paste time saves significantly more time downstream.

How to Remove Extra Spaces From Text Online (Fast Fix)

Try Our Free Word Counter

Explore More Free Text Tools