Guide
Find non-breaking spaces in Google Docs
Find U+00A0 and U+202F after copy-paste, replace the accidental ones, and keep the spaces that must prevent a line break.
By Kris Vinters · Published · 4 minute read
Identify the space that came with the paste
U+00A0 NO-BREAK SPACE and U+202F NARROW NO-BREAK SPACE commonly arrive with text copied from web pages, chat windows, and PDFs. They look like ordinary spaces, but they tell a layout engine not to break the line at that position. U+202F is also normal typography in some languages.
The different codepoint can make exact search miss a phrase, change how a word counter tokenizes text, disturb column alignment, and break code or data formats that accept only ASCII spaces. At the same time, replacing a deliberate no-break space between a number and its unit can create an unwanted line break.
Find and replace them in Google Docs and Word
In current desktop Google Docs, open Edit, then Find and replace. For a precise replacement, copy one suspect space from the document into Find, enter one ordinary keyboard space in Replace with, and review each result. Repeat for the other space type because U+00A0 and U+202F are different characters.
Google Docs can search regular expressions, but a broad whitespace expression also matches spaces you might want to keep. If you cannot isolate a suspect space, identify its codepoint in Ghostchars first, then return to the exact location in the document. Mobile menus and shortcuts differ, so use the Docs search box for Find and replace when the menu path is not present.
In current desktop Word, open advanced Find and Replace. The special code ^s finds U+00A0. For U+202F, paste a confirmed instance into Find or use Word's Unicode character search with wildcards off. Replace with an ordinary space, and review matches before Replace All.
Word Find what for U+00A0: ^s
Choose whether Ghostchars keeps or replaces the space
The standard cleaner finds U+00A0 and U+202F but leaves them as "found, not targeted" because the space option is off. That preserves no-break behavior, including a deliberate space between a number and a unit. The findings table still gives you the exact line, column, and codepoint.
To replace them, open Advanced and select "Convert exotic spaces". The engine converts every targeted exotic space to an ordinary U+0020 space. It does not infer whether a particular no-break space is load-bearing, so inspect number-unit pairs, names, and language-specific punctuation before you apply that option.
The narrow-space checker is the fastest route for pasted text. For a supported .docx, .odt, or .html file, the document report lists the characters inside the file and lets you decide whether to download a cleaned copy. Nothing is uploaded.
These spaces describe formatting and copy-paste history. They do not identify an author. Ghostchars reports character facts; the prose report gives measurements and no verdict.
No-break space questions
What is the difference between U+00A0 and U+202F?
Both prevent a line break. U+202F is narrower and is used by some writing systems and typography conventions. They remain different codepoints even when the font makes them look alike.
Should I replace every non-breaking space?
No. Keep one when its no-break behavior is intentional, such as between a number and a unit. Replace accidental spaces that interfere with search, code, data, or the layout you want.
Why can word counts disagree after copy-paste?
Applications do not all tokenize exotic spaces the same way. Replacing one with U+0020 can change the count in a particular application even though the visible words did not change.
Continue with all practical guides to hidden characters and the limits of cleaning.