Free Gemini zero-width space remover

Gemini zero-width space remover

What the Gemini zero-width space remover does

A zero-width space is a character that occupies a position in your text and renders nothing at all. This tool scans text copied out of Gemini, from the chat window or after an Export to Docs, for U+200B and the small family of related invisible characters that travel with it, and removes them, leaving every visible word exactly where it was.

It runs entirely in your browser. Paste, press the button, copy the result: nothing is uploaded, there is no account, and there is no limit on how much text you clean or how often you come back.

Why it happens

Why Gemini text carries invisible characters, in plain terms

Gemini structures most answers around a bolded lead-in followed by nested sub-points, and rendering that indentation as real, visible spacing rather than letting it collapse is exactly the kind of job a non-breaking space is used for. A copy from the chat window can carry those characters sitting at each indentation level, invisible on screen and identical in appearance to an ordinary space.

Export to Docs adds a second rendering pass on top: the answer is rebuilt as an actual Google Docs document, with its own way of representing indentation and spacing. Text copied back out of that Doc has been through two rendering steps rather than one, and either step can introduce its own invisible characters.

How it works

How to remove zero-width spaces from Gemini text in three steps

There is nothing to preview beforehand, since the problem is invisible until you run the tool.

Step 1

Copy the reply from the Gemini chat window, or from the exported Doc, and paste it into the box.

Step 2

Press Remove hidden characters. It runs instantly, on your own device.

Step 3

Copy the result. Every visible word is exactly as it was.

Worth knowing

This clears more than just the zero-width space

The zero-width space, U+200B, is the character most people mean by the name, but it rarely travels alone. This tool also removes its close relatives: the zero-width joiner and non-joiner, the word joiner, the byte-order mark, the soft hyphen, and the family of non-breaking, narrow and hair spaces that render as an ordinary gap but are a different codepoint underneath.

A joiner sitting inside a real emoji sequence is left alone, since removing it would visually split the emoji apart, and the space-like characters are swapped for an ordinary space rather than deleted outright, so wrapping and word boundaries stay correct.

Why it matters

What these hidden characters actually break

Inside a heading or a URL slug, a hidden character splits the string for anything comparing it byte by byte: search, a regular expression, a string equality check. Two values that look identical on screen simply fail to match, because one carries a character the other does not.

Text pulled from a Docs export is a common place this shows up, since a non-breaking space sitting in what looks like ordinary indentation can silently break a search or a find-and-replace that should have worked.

Straight answer

Does a hidden character mean Gemini watermarked the text?

No. These characters are overwhelmingly a side effect of how nested formatting gets rendered, both in the chat window and again through a Docs export, not a deliberate marker placed to identify the text later. Finding one tells you the text passed through a rendering step; it does not tell you who wrote it.

Separately, there is real research into watermarking AI text by biasing which words a model is statistically more likely to choose, a pattern buried in the writing itself rather than in any single character. No tool that scans for invisible Unicode, this one included, can see or affect that kind of statistical watermark.

Who uses it

Who uses the Gemini zero-width space remover, and when

Publishing teams use it when a heading pulled from Gemini stops matching its slug, or when on-page search returns nothing for text that looks identical to what a reader sees. Anyone who exported a Gemini answer to Docs and then reused it elsewhere runs it through here to clear characters introduced by either rendering pass.

Developers pulling Gemini output into a config file or a commit use it too, since a hidden character in an identifier produces a failure with no visible cause.