Gemini watermark detector

This tool scans text copied from Gemini for the zero-width and non-printing Unicode characters a chat interface can leave behind, without altering how the text displays. It's built for a specific, searched question, does Gemini put a hidden watermark in its output, and it answers with a list of findings rather than a verdict.

The scan is local and client-side. Nothing is uploaded, no account is required, and there's no limit on how many times you can run it.

Gemini answers are frequently exported into Google Docs or Sheets, or drafted inline inside Gmail, and each of those apps applies its own typography as text passes through: converting straight quotes to curly ones, inserting non-breaking spaces around certain punctuation, and reformatting line breaks.

Zero-width space and joiners

Occupy a character slot and render nothing. The most frequent invisible residue in copied text.

Non-breaking spaces and smart quotes

Introduced automatically by Google Docs' typography engine in specific positions.

Soft hyphens and word joiners

Invisible until a line wraps or a search fails to match text that looks identical on screen.

Byte-order marks and bidi controls

Rarer, but capable of confusing a parser or reordering how text displays when they end up mid-document.

The scan executes entirely client-side. No round trip, no server, nothing transmitted.

Step 1

Copy the reply using Gemini's own copy control rather than a manual selection, since that's the path most likely to carry invisible characters.

Step 2

Paste the sample and run the scan. It executes locally and lists every hidden character found, with its position.

Step 3

Review the findings before drawing a conclusion. A hidden character indicates something about formatting, not about who produced the words.

A zero-width space inside a heading pasted from Gemini splits the keyword, so the slug or anchor stops matching the visible title. A non-breaking space carried over from a Docs export breaks YAML, a shell command or a CSV column, usually without any visible sign of the cause.

The same characters produce EPUB validation failures and CMS fields that silently refuse to save. None of it requires anything unusual; it's the ordinary cost of moving text between formatted surfaces.

The mechanism is structural, not deliberate. Gemini sits inside Google's own productivity apps, with one-click export into Docs and Sheets, and inline drafting inside Gmail. Each of those has its own typography engine that reformats punctuation and spacing as text moves through it, which is a well-documented source of the residue a scan finds.

Copying straight out of the Gemini chat pane is one path; copying out of a Doc the answer was exported to is another, and the second reliably carries more of this kind of character than the first.

This is a character scan, nothing more. It does not analyse sentence structure, vocabulary or writing rhythm, and it makes no attempt to determine whether a passage was written by Gemini, another model, or a person. A clean result is not proof of human authorship, and a flagged character is not proof of Gemini's involvement.

It also cannot detect statistical or token-level watermarking, a research technique that biases a model's word-choice probabilities rather than inserting any character at all. No character-level scan, including this one, can see that kind of signal.

No. The same characters turn up in text copied from Word, plain Google Docs and chat interfaces entirely unrelated to Gemini. A finding here is a formatting lead, worth acting on if it's causing a practical problem, not evidence of source.

It says nothing about whether the text would pass a third-party AI detector either. Those tools weigh statistical properties of the prose itself; this scan only reports what characters are present in the bytes.

Any workflow where Gemini output is copied somewhere that parses text strictly, publishes it, or feeds it into another system.

Editors and publishers

Catching a split slug or heading pulled from an exported Doc before a post goes live.

Developers

Checking a Gemini-drafted snippet or config file before it's committed.

Data and ops teams

Verifying a Gemini answer pasted into JSON, CSV or a database field will actually parse.

Anyone exporting to PDF or EPUB

Catching invisible characters before a layout engine trips on them.