Hidden Unicode AI Watermark: Proves Almost Nothing

Four characters account for the overwhelming majority of invisible-character finds in AI output.

• Zero-width space (U+200B): no glyph, no width, used to create line-break opportunities inside long unbroken strings like URLs and hashtags.
• Zero-width non-joiner (U+200C) and zero-width joiner (U+200D): control whether adjacent letterforms connect in Arabic and other complex scripts.
• Byte-order mark (U+FEFF): written at the start of a file to signal byte order or confirm UTF-8 encoding.
• Non-breaking space (U+00A0): keeps two words on the same line, like a name and a title.

Every one of those predates the modern chatbot, in some cases by decades. And each has an ordinary explanation for how it ended up in your text.

The zero-width space does have a less charitable use. Some content generators and spammers sprinkle it to pad word counts or slip past duplicate-content filters, which is a spam signal, not a provider signature.

The joiner is the one people underestimate. It's what glues emoji sequences together, so the family emoji and most skin-tone and profession combinations are literally built out of U+200D.

A byte-order mark is an encoding artifact left by whatever editor, export tool, or paste pipeline last handled the text. It tells you something about the software that saved the file and nothing about who wrote the words inside it.

The non-breaking space is the most common false alarm of the lot. Enormous numbers of web pages use it in their markup in place of a plain space, so any text copied from a browser is likely to carry a few.

No, though homoglyphs are the one category worth a second look. A homoglyph swaps a letter for a visually identical character from another script, like a Cyrillic character standing in for a Latin a. Your eye can't catch it. A Unicode-aware tool can.

Unlike a byte-order mark or a non-breaking space, there's no everyday formatting reason to do this. Security researchers already treat homoglyph substitution as a real technique, used in phishing domains and text obfuscation.

That's why one specific claim deserves naming. In a post dated July 2, 2026, developer Sean Goedecke argued that text watermarks are "trivially removable" and separately wrote that Claude Code had at some earlier point used Unicode homoglyphs inside date strings as a steganographic flag, since discontinued.

That's far more concrete than the usual folklore. It names a tool, a character class, and a use that has ended.

It's also unconfirmed. Goedecke said himself he wasn't certain how Anthropic's current implementation works, and the article he pointed to for corroboration is no longer reachable.

No, not according to Anthropic, which ruled hidden characters out in writing on August 14, 2026. When Anthropic confirmed a Claude text watermark in 2026, the same follow-up question filled every comment section: how does that even work for text? The theories piled up fast.

• hidden Unicode or invisible characters
• statistical word-choice patterns
• overrepresented n-grams
• first-letter or sentence-position patterns
• token-probability nudges
• something SynthID-like
• a hybrid of several signals at once

For twelve days Anthropic's own documentation named none of them, and hidden Unicode, the only guess testable at home, got checked first and reported loudest. On August 14, 2026 Anthropic ended the guessing: the watermark is a version of Google DeepMind's SynthID-Text approach, keyed word selection during generation, and "Nothing is added to the text and there are no hidden characters." That settles this page's question from the provider's side: there is no hidden character to find.

The same pattern shows up elsewhere. Marketing pages for the removal tools gptcleanup.com and scriptbyai.com have claimed hidden Unicode in Grok's text output, a claim with zero corroboration from xAI.

Compare that with getgpt.app, whose scanner checks for 34 or more specific invisible characters and states plainly that it does not detect or remove cryptographic watermarks like SynthID. Same underlying capability, honest label.

Stripping invisible characters is worth doing on its own merits. They break search-in-page, corrupt pastes into code and spreadsheets, and occasionally trip duplicate-content checks.

This site's cleaner runs entirely in your browser and reports per-character counts across eight of them: U+200B, U+200C, U+200D, U+2060, U+FEFF, U+00AD, U+00A0, and U+202F. Nothing is uploaded anywhere.

What it won't do is touch a statistical watermark, because there's no character to delete. Cleaning invisible Unicode and defeating a watermark are separate jobs, and only one of them is available to you in a text box.