Tools · Clean Text
Does AI Leave Hidden Watermarks in Your Text? What's Actually in There

Short version: true cryptographic watermarks in everyday chatbot text are still rare. Detectable leftovers are not. Most AI output carries some mix of invisible Unicode characters, unusual spaces, and punctuation habits that act like a fingerprint whether or not anyone intended one. If you paste AI drafts into emails, documents, or code without cleaning them, there is a decent chance you are shipping characters you cannot see.
Worth separating the two things people mean by "watermark." A deliberate watermark biases the model's word choices in a pattern special software can verify later; Google has shipped a version of this research as SynthID, and OpenAI has published work on it without rolling it out broadly for chat. An artifact is accidental: the model or the pipeline between it and your clipboard leaves traces nobody planned. The watermark question gets the headlines. The artifacts are what actually show up in your pasted text.
The characters that keep turning up
Run enough AI output through a character inspector and the same names repeat. The zero-width space (U+200B) and its cousins the zero-width joiner and non-joiner: no visible width, legitimate in some scripts, trouble inside an English sentence or a variable name. The no-break space (U+00A0): looks like a space, refuses to wrap, quietly breaks CSVs and code. The narrow no-break space (U+202F): the thin typographic space that got this whole topic attention when people started finding it sprinkled through chatbot output a couple of years ago, before vendors cleaned much of it up. The soft hyphen (U+00AD): invisible until a line breaks in the wrong place. Curly quotes and apostrophes (U+201C, U+2018 and friends): visible, pretty, and a bug inside anything expecting plain ASCII. And the byte-order mark (U+FEFF), which occasionally hitchhikes to the top of a pasted block and corrupts imports from a position you cannot see.
Two honest caveats. None of these characters proves AI on its own; Word, websites, and typographically careful humans produce several of them too. It is the density that fingerprints machine text, a dozen exotic characters in a three-paragraph email did not come from your keyboard. And the roster shifts as vendors patch their output, so the specific characters of this year will not be the specific characters of 2028.
Why it matters even if nobody is hunting you
Set the detection anxiety aside; the practical damage comes first. A zero-width space inside a variable name fails a build while looking correct. A no-break space in a config file corrupts an import. Search-and-replace misses strings that look identical but are not. Some terminals and older mail clients render the exotic ones as visible junk. And yes, text dense with machine-flavored characters reads as AI to both people and classifiers, which matters when the words are supposed to be yours.
Checking and cleaning
To check a block, paste it into any Unicode inspector and look for code points that are not plain letters, digits, and ordinary punctuation. Or paste it into TextScrubr, which I built after one too many of these turned up in my own drafts; it shows what it found, strips the hidden characters, converts exotic spaces to regular ones, straightens the quotes, and leaves your actual structure alone. Free, in the browser, nothing you paste leaves your machine, and there is a $29 Claude skill version that cleans drafts inside the chat before you ever copy them. Mine, both of them, built because I ship pasted text constantly. Whatever you use, the principle is the same: normalize the characters, do not nuke the formatting, because paste-through-Notepad flattens your paragraphs along with the ghosts. (The skill is also part of SideRoad All Access, which covers every builder tool I sell.)
Do detectors use this?
Less than people assume. Serious AI detectors lean on statistical patterns in the words themselves, since characters are trivially strippable and they know it. The informal detection, the editor squinting at a submission, the reviewer who notices the dashes, absolutely runs on these tells though. Cleaning will not fool a statistical detector and should not be the goal. The goal is that work you edited and own stops carrying freight you never chose and breaks nothing downstream. That is not evasion, it is proofreading the layer you cannot see. The companion piece on why AI email drafts paste weird covers the visible layer.
FAQ
Do ChatGPT and other AI tools watermark their text?
Mostly no in the cryptographic sense, but practically yes in the artifact sense. Chatbot output has at times contained distinctive invisible or unusual Unicode characters, special space variants, and punctuation habits that act like fingerprints even when no deliberate watermark exists. Research watermarks (like Google's SynthID for text) do exist, but the everyday tells are artifacts, not secret stamps.
What hidden characters show up in AI text?
The usual suspects: zero-width spaces and joiners, narrow and regular no-break spaces where a normal space belongs, curly smart quotes, special dash characters, and occasional byte-order marks. None are visible on screen, and all survive copy-paste into emails, docs, and code.
Can hidden characters actually cause problems?
Yes, practical ones: they break code and config files, corrupt CSV imports, trip up search-and-replace, render as junk in some email clients and terminals, and make otherwise human writing carry a machine fingerprint you did not choose to include.
How do I remove AI artifacts from my text?
Paste it through a cleaner that normalizes Unicode: strip zero-width characters, convert special spaces to regular spaces, straighten smart punctuation, and standardize dashes, while keeping your paragraphs and structure intact. That is exactly what TextScrubr does free in the browser, with a $29 Claude skill that does it inside your chat.


